Key takeaways
- A useful review answers six buyer questions in a fixed order: verdict, who it is for, what it does, where it falls short, what else to consider, and whether to buy, wait or skip.
- Google says its reviews system is built to reward in-depth analysis and original research rather than thin summaries of products [1].
- If you have not bought the product, say so and show your sources: dated pricing pages, official specifications and documented user reports.
- Any rating you mark up should be genuine; Google's documentation warns against fake or undisclosed incentivised reviews [2].
- A pre-publish checklist catches the common failures: missing drawbacks, undated prices and a recommendation that will not commit.
What should a product review template include?
A product review template should give you a slot for the verdict, who the product is for and not for, the features that matter, the drawbacks, the alternatives and your evidence. That order answers a buyer's real questions before they have to ask them, and it stops the review from turning into a list of features.
That is the short answer. The rest of this guide turns it into a fill-in product review template you can copy, with the exact questions each slot has to answer and a checklist for the evidence. The order matters more than the wording. A reader arrives with one question - is this worth my money? - and your job is to answer it, justify it, then tell them when the answer changes.
The structure also lines up with what Google says its reviews system is trying to reward: content that provides insightful analysis and original research, written by people who know the topic, rather than thin content that simply summarises a bunch of products [1].
Why your reviews end up thin (it is not a writing problem)
You open a draft, type the product name, and stall. The only sentences you can find are some version of 'it is good' or 'it is bad', so you pad with a feature list copied from the sales page and hit publish feeling flat. If that sounds familiar, the problem is not your vocabulary.
Thin reviews usually come from three habits:
- Starting with the product instead of the decision. The reader is not shopping for a feature list. They are trying to decide whether to spend money, time or attention.
- Having no slot for evidence. When there is nowhere to put what you checked, the review drifts into opinion and vague adjectives.
- Feeling obliged to recommend. A review that cannot say 'skip it' reads like a sales page, because it is doing a sales page's job.
None of these are moral failures. They are what happens when you sit down without a structure and try to write in a straight line from product name to conclusion. The fix is to plan the review as a set of answers, then fill the answers in.
The seven-slot product review template (copy this)
Use this as a planning grid before you write a sentence. The word budgets are our rough editorial guide, not a rule; they are there to stop one section swallowing the review.
| Slot | Buyer question it answers | What goes in it | Rough guide |
|---|---|---|---|
| 1. Verdict | Should I keep reading? | Product name, who it suits, the main trade-off, in plain language | 40-60 words |
| 2. Who it is for, and not for | Is this me? | Concrete use cases, constraints and the person who should look elsewhere | 80-120 words |
| 3. What it actually does | Will it solve my problem? | Three to five capabilities tied to tasks, not a copied spec dump | 150-250 words |
| 4. Where it falls short | What will annoy me later? | Named limitations, who they affect and the workaround | 100-200 words |
| 5. Alternatives | What else should I look at? | Two or three named options, each with a one-line decision rule | 100-200 words |
| 6. Evidence | Why should I believe you? | Dated pricing, official documentation, what you checked and what you did not | 80-150 words |
| 7. Recommendation | So what should I do? | Buy, wait or skip, with the conditions spelled out | 40-80 words |
Fill it in this order: verdict first, then who it is for, then the evidence you actually have, then drawbacks and alternatives, then the recommendation. Writing the recommendation last stops you from deciding the conclusion before you have looked at the evidence.
- Keep slots 1 and 7 short enough to scan.
- Do not publish the slot names as headings if they sound mechanical; rewrite them as questions a buyer would ask.
- If a slot is empty because you have no evidence, that is a signal to research more or narrow the claim.
How to fill the sections buyers actually read
Start with the verdict, not the product category's life story
Many drafts open with three paragraphs about how the category has changed and why choice is harder than ever. Cut it. The first 40-60 words should tell the reader what the product is, who it suits and the main trade-off. If they stop reading there, they should still have a usable answer. A verdict is not a rating; it is a sentence that commits.
For example, a thin sentence says, “It is good.” A specific verdict says, “PRODUCT is a funnel-builder for solo creators who need email marketing and a checkout page without paying for three separate tools; the trade-off is less design flexibility than a dedicated page builder.” That second sentence answers who, what and the main caveat in one breath.
Write 'who it is for' as a sentence your reader would say
'Perfect for everyone' means nothing. Use constraints: budget, skill level, device, team size, how often they will use it. Then write the mirror section, 'who it is not for', because that is where a reader decides whether to trust you. A specific exclusion is more persuasive than three paragraphs of praise.
Make the drawbacks section earn its place
'May not suit everyone' is not a drawback. Name the limitation, say who it affects, and say what it costs in time or workaround. This is also where you put running costs, setup friction and anything a buyer only discovers after paying. If you're reviewing a tool before you promote it, our due-diligence checklist for judging a product gives you a wider list of things to verify.
Give the alternatives a decision rule
List two or three alternatives and, for each, one line explaining when to pick it instead. That is more useful than a table of ten options with no guidance. Our comparison post template shows how to structure that choice without turning the page into a shopping directory.
How to gather evidence when you have not bought the product
This is the section that separates a review from a sales page. You do not need to own the product to write something useful, but you do need to be honest about the difference between what you verified and what you are inferring. Reviewers who have not bought a product should say so plainly and lean on documentation, not vibes. Our guide to writing an honest product review without buying the product goes deeper on that balance.
| Evidence | What it can support | What it cannot support |
|---|---|---|
| Official documentation | Features, compatibility, stated limits | Real-world reliability |
| Dated pricing page | What the product cost on the date you checked | Future pricing or total cost of ownership |
| Public user reports | Repeated complaints or praise worth investigating | A controlled test |
| Return and cancellation terms | The reader's exit route | The quality of the product itself |
| Your own use, if it is true | First-hand impressions of specific tasks | Broad claims about every use case |
Before you write, collect these six things:
- The official specification or help page, saved with the date you checked it.
- The current pricing page, noted with a date rather than 'recently'.
- The refund, cancellation and warranty terms.
- Support documentation for the two tasks your reader cares about most.
- Public user reports, read for patterns rather than one angry post.
- A short note of what you could not verify.
Then put one sentence in the review that says what you have not checked. It sounds like a weakness and reads like credibility. If you add screenshots, demos or an AI-assisted draft, follow our content creation workflow lesson for graphics, demos, AI drafts and licenses. For the tools themselves, our free content creation tools guide lists what each free plan includes.
Illustrative example: the template filled in
Illustrative example - a filled template for a made-up product. No real product, price or personal experience is implied.
Verdict: PRODUCT is a CATEGORY for READER TYPE who needs JOB. The trade-off is LIMITATION.
Who it is for: people who TASK at least FREQUENCY and need CONSTRAINT. Who it is not for: anyone who SITUATION, because ALTERNATIVE handles that better.
What it does: (1) CAPABILITY tied to TASK; (2) CAPABILITY tied to TASK; (3) CAPABILITY tied to TASK. Skip the rest of the feature list.
Where it falls short: LIMITATION matters if you USE CASE. Also check RECURRING COST before you buy. Workaround: WORKAROUND, which takes TIME OR EFFORT.
Alternatives: ALTERNATIVE A if you need CONDITION; ALTERNATIVE B if CONDITION. Neither is automatically better.
Evidence: checked official specifications on DATE, pricing on DATE, user reports in PLACE. I have not used the product myself.
Recommendation: buy if CONDITION; wait if CONDITION; skip if CONDITION.
Notice what the example does not contain: a fake anecdote, an invented rating or a claim that the product is best for everyone. The placeholders force you to make decisions you can defend, and they show you exactly which facts you still need to look up.

How to keep the recommendation honest when you earn a commission
Here is the uncomfortable question, and it is fair: if a review site earns money when you click, why trust it? The answer is not a promise of purity. It is visible behaviour. A site that discloses the relationship, shows the drawbacks, dates its prices and refuses to crown a winner in every category is giving you something you can check. A site that praises everything and hides the cost is giving you a sales page with a review headline.
We earn commissions through some links on this site. That is not a confession; it is the business model. What matters is whether the review would still be useful if the commission disappeared. Our review methodology page explains how we choose topics and how links work. Read it the way you would read any reviewer's disclosure: as a test of whether the incentives are on the table.
If you write reviews, make the money visible before the first link. Our affiliate disclosure examples show what a plain-English notice looks like on a blog, in email and on video, and our guide to marking affiliate links properly covers the technical side.
Google's review-snippet documentation also puts a boundary around incentives: it warns against fake or undisclosed incentivised reviews, including reviews that are not based on a genuine experience and reviews written in exchange for a benefit that is not clearly and prominently disclosed [2]. If you received the product free, say so prominently. If you did not use it, do not pretend otherwise.
What Google's reviews system rewards (and what it ignores)
Google describes its reviews system as aiming to reward high quality reviews, meaning content that provides insightful analysis and original research and is written by experts or enthusiasts who know the topic well [1]. It says the system exists to surface in-depth research rather than thin content that simply summarises a bunch of products [1].
The scope is narrower than some people assume. The system evaluates first-party standalone review content - articles, blog posts, comparisons and ranked lists - and does not evaluate third-party reviews such as user reviews posted in a product page's review section [1]. It primarily evaluates review content at page level, although sites with a substantial amount of review content may be evaluated more broadly [1].
The practical takeaway for a small site is to add something only you could add. That might be a decision table built from documented specifications, a dated log of price changes, a 'skip it if' paragraph, or a list of questions to ask support before buying. You do not need a testing lab; you need a point of view backed by sources. Our guide to Google's helpful-content guidance for small affiliate sites explains how that fits together, and our methodology for 'best X' lists covers selection criteria when you are comparing several products.
Structured data: the minimum honest markup
Google may show a review snippet, including stars, when it finds valid review or rating markup on a page [2]. Its documentation lists required properties, including the author, the item being reviewed and the rating [2]. It also recommends accepting only ratings that come with a review comment and the author's name [2].
Two warnings matter for beginners. Do not include fake or undisclosed incentivised reviews [2]. Provide review information about a specific item rather than a category or a list, and if you include multiple reviews, include an aggregate rating as well [2]. Do not aggregate reviews or ratings from other websites [2].
For a new site, the safer play is often no star markup at all until you have genuine ratings collected on your own page. Check the current documentation before you implement anything, because eligibility and requirements change.
Publish checklist: nine checks before you hit publish
Run this list against the draft. It takes about five minutes and catches most of the problems that make a review feel thin.
- The verdict appears in the first 60 words and names at least one trade-off.
- A 'who it is not for' section exists and is specific.
- There are at least two named drawbacks, not 'may not suit everyone'.
- The alternatives section gives a decision rule for each option.
- Every price is dated and attributed to the official page.
- Every factual claim has a source, or is clearly labelled as your opinion.
- The affiliate disclosure appears before the first affiliate link.
- You have said what you did not verify.
- The page has a 'last checked' date and a note to recheck prices.
Two follow-on habits keep the page useful. Add it to a review rota so old prices do not rot; our guide to refreshing old affiliate posts lists what to check and change. And link it to the rest of your site with descriptive anchors, using our internal linking plan for a small affiliate site.
Next step
Download the free starter kit: a niche check, an affiliate terms card, a dated tool budget, a first-page brief and a 14-day starter plan for your first choices. Get the free starter kit
Related guides: How to Write a Comparison Post That Actually Helps Readers Choose; "Best X" Lists Done Right; Experience, Expertise and Trust on a Small Affiliate Site; Internal Linking for a 20-Page Affiliate Site.
Want the rest of the publishing workflow?
The template covers the page. If you want the surrounding steps - choosing a topic, checking a product before you promote it, and setting up disclosure - start with our free starter kit.
Frequently asked questions
How do you write a product review step by step?
Start with a one-line verdict that names who the product suits and its main trade-off. Then cover who it is for and not for, what it does in task terms, where it falls short, two or three alternatives with a decision rule, and your evidence. Finish with a clear buy, wait or skip recommendation. Draft the verdict first and the recommendation last, so the conclusion follows the evidence.
Do you have to buy a product to review it?
No, but you have to be honest about the basis of the review. If you have not used the product, say so, and build the review from official documentation, dated pricing, warranty terms and documented user reports. Separate what you verified from what you are inferring. A transparent review based on documents can help readers; a pretend hands-on review cannot.
How can you tell if a product has good quality?
Look for specifics rather than adjectives. Good quality shows up in materials, build details, warranty terms, compatibility, support responsiveness and repeated user reports about the same strength or failure. One glowing comment proves little; a pattern across months is worth investigating. In your review, name the evidence behind the quality claim and say what you could not check.
How long should a product review be?
Long enough to answer the buyer's questions and no longer. The seven-slot template usually needs enough room for a clear verdict, a specific drawbacks section, alternatives and evidence. Cut any paragraph that does not help a reader decide, and do not pad with copied specifications. A tight, well-sourced review beats a long one that repeats the sales page.
Can I use the same product review template for Amazon reviews?
The structure works, but the platform's own review guidelines govern what you can post there. Keep your blog review and any marketplace review separate, check the current guidelines before posting, and disclose any free product or incentive in the way the platform requires. When in doubt, ask the platform's support team rather than guessing.
Sources
- Google Search's Reviews System | Google Search Central | Documentation | Google for Developers (source page, retrieved 2026-10-20)
- Review Snippet (Review, AggregateRating) Structured Data | Google Search Central | Documentation | Google for Developers (source page, retrieved 2026-10-20)
This guide is general education. Program terms and tools change; check the linked official pages for the current version. How we write: editorial policy. This page has no affiliate links.



