Single Product Review Template: The Eight Sections, in Order, and What Each One Decides
Buyer guides have a well-worn structure: verdict, table, product sections, how we picked, FAQ. Single product reviews mostly don't, which is why so many of them open with the brand's history, bury the verdict under the specs, and end with "overall, a solid choice" after 1,800 words.
A review is a smaller decision than a guide (one product: buy it or not), and it needs a shape that gets the reader to that decision in the first screen and then supports it.
This post is the template: eight sections, in order, with what each one decides, roughly how long it runs, where it comes from, and a filled skeleton you can copy. It ends with the two sections most reviews get backwards and the checks before publishing. The reviews vs guides post covers when to write a review at all; this is how.
The short answer
Verdict (buy it if, skip it if, button) → who it's for and isn't → what it does well against its rivals → what owners complain about → the three alternatives and why you'd pick each → the five or six specs that decide it, in a table → FAQ → button again. Eight hundred to 1,200 words, headings that decide, disclosure above the first link, no invented stars.
The eight sections
| # | Section | Decides | Length | Comes from |
|---|---|---|---|---|
| 1 | Verdict | Buy it or not, for whom, in one screen | 50 to 70 words + button | Your judgment, the comparison, the review pattern |
| 2 | Who it's for, who it isn't | Whether this reader should keep reading | Two short paragraphs | The use cases owners describe; the ones who returned it |
| 3 | What it does well | Why this over its rivals | Three to four points, each compared | Specs against the alternatives; five-star patterns |
| 4 | What owners complain about | The catch, honestly | Two to three points | One- and three-star reviews |
| 5 | The three alternatives | What to buy instead, and when | One sentence each, with a button | The rivals in your buyer guide |
| 6 | The specs that matter | The numbers behind the verdict | A table, five or six rows | The listing, through the API |
| 7 | FAQ | The questions people search | Three to five, answer-first | People Also Ask, the listing's Q&A |
| 8 | Closing verdict + button | The decision again, for the reader who scrolled | Two sentences | Section 1, restated |
Section notes
1. Verdict. The same box a buyer guide opens with, for one product: "Buy the Metro Pro 800 if you commute on lit streets and charge nightly; its beam shape is the best at the price and the mount outlasts the strap types. Skip it if you ride unlit roads or need USB-C." Then the button. The verdict box post covers the sixty words.
2. Who it's for, who it isn't. Two paragraphs that let the reader self-select. The "isn't" paragraph is the one that builds trust and prevents returns; it comes from the reviews of people who bought it for the wrong use.
3. What it does well. Not the spec sheet: the three or four things it does better than the products a reader would otherwise buy, each named. "Its cut-off beam puts light on the road, which the Lezyne's round beam doesn't" is a point; "800 lumens" is a spec and belongs in section 6.
4. What owners complain about. Two or three real complaints from the review pattern, with how common and who it affects. The pros and cons post covers the test for a real con; this section is the cons, in prose or a short list.
5. The three alternatives. The cheaper one, the pricier one, and the different-approach one, each with the reader it suits and its own button. This section converts readers the verdict talked out of the main product, which is the whole point of having talked them out of it honestly.
6. The specs that matter. A table with the five or six rows the decision depends on (beam type, run time on medium, mount, weight, charging port, price band), not the thirty on the listing. Every number through the API or from the listing, checked.
7. FAQ. Three to five real queries ("does the Metro Pro fit 35 mm bars", "how long does it charge"), each answered in the first sentence.
8. Closing verdict and button. Two sentences restating section 1 for the reader who read everything, and the button again.
A filled skeleton
Title: Cygolite Metro Pro 800 Review: The Commuter Light That Gets the Beam Right.
Verdict: Buy it if you commute on lit streets and charge nightly: the cut-off beam is the best at this price and the clamp mount survives winters where straps crack.
Skip it if you ride unlit roads (get the 1,100) or need USB-C. [Check price]
Who it's for: daily commuters, 5 to 15 miles, lit roads, a nightly charger. Who it isn't: trail riders, anyone who moves one light between bikes, USB-C-only households.
What it does well: beam shape vs the Lezyne's round beam; mount vs strap types; run time on medium vs the Knog.
What owners complain about: micro-USB in 2026 (common); the clamp needs a shim on 35 mm bars (occasional); charge time of four hours (a few).
Alternatives: Lezyne Micro Drive for bike-swappers; Metro Pro 1100 for unlit roads; Knog Blinder for the lightest option.
Specs: beam type, lumens on medium, run time on medium, mount, port, weight.
FAQ: fits 35 mm bars? charge time? waterproof rating? difference from the 1100?
Closing: the verdict again, the button again.
The two sections reviews get backwards
- Specs before verdict. The reader doesn't know whether 800 lumens is good until you've told them what it's for. Verdict first, specs sixth.
- Alternatives as an afterthought. "You might also consider…" in the last paragraph, with no reason. The alternatives section is the second-highest-converting part of the page, because it catches the reader the honest verdict sent away. Give each alternative a reader and a button.
Before publishing
- Verdict visible in the first screen on a phone, with a button.
- Every point in section 3 names the rival it beats.
- Section 4 has at least two real complaints.
- Each alternative has a reader and a link to the right variant.
- No stars you invented; no review-rating markup unless the rating is real and defensible.
- Disclosure above the first link; no "we tested" unless you did.
Doing it with AffSERP
AffSERP's X Best Review tool set to a single product writes to this template: verdict box first, who it's for and isn't from the use cases in the review pattern.
Strengths are compared against the alternatives you name in the brief, complaints from the one- and three-star pattern, three alternatives with their own buttons, a specs table of the rows that matter with every number through the API, and an answer-first FAQ.
Your notes supply the one thing it can't: whether you'd buy it yourself, which is the sentence that makes the verdict yours.
FAQ
How do you structure a product review?
Verdict first (buy it if, skip it if), then who it's for and who it isn't, what it does well compared with its rivals, what owners complain about, three alternatives with the reason to pick each instead, the five or six specs that decide the purchase, a FAQ of the questions people actually search, and a button after the verdict and again at the end. Eight sections, 800 to 1,200 words.
What should a product review include?
A decision, a reason, a catch, and a comparison. The decision is the verdict; the reason is what the product does better than its alternatives; the catch is what owners complain about; the comparison is the three products a reader would otherwise buy. Specs go in a short table of the ones that matter. Everything else (unboxing, history of the brand, every spec on the sheet) is padding.
What's the best format for an Amazon product review?
Verdict box at the top with the button, then short sections with headings that decide ('Who it's for', 'What owners complain about', 'The three alternatives'), a specs table with five or six rows, and a FAQ with answer-first paragraphs. No star ratings you made up, no review-rating markup on a page that isn't a real rated review, and the disclosure above the first link.
How long should a single product review be?
Eight hundred to 1,200 words. A review covers one product, so it's shorter than a buyer guide; past 1,200 it's usually the spec sheet rewritten as prose, or an unboxing nobody asked for. The alternatives section is where reviews run long, and it should be three products with a sentence each, not three mini-reviews.
Set AffSERP to one product and it writes the verdict box, who it's for, strengths against the rivals you name, complaints from the reviews, three alternatives and a specs table of the rows that matter.
Start with free wordsKeep reading
