In this blog post I'm going to walk you through how to write product reviews that actually convert in 2026. Specifically, the framework that turns a review from "first paragraph, feature list, affiliate link, goodbye" into a piece of content that builds trust, gets shared, and earns the click without sounding like an advertorial. Not the version where you copy the manufacturer's spec sheet and add three opinions in italics. The version that gets you the higher conversion rate, the longer time-on-page, and the readers who come back for the next one.
Most of what passes for product reviews in 2026 is structured this way: introduction with a problem, three benefits, a feature list, a pros and cons box, an affiliate link, and a closing nudge. You've read a hundred of those this year. So has your reader. They scroll past them.
I've been writing product reviews on lilachbullock.com for nineteen years. That's not because I love writing reviews. It's because reviews are one of the highest-converting formats in business content marketing, and most of them are bad. There's an open lane for any writer who's willing to write reviews that don't read like an affiliate pitch with three extra colours. My clients have included IBM, Twitter, Dropbox, monday.com and Greenpeace. I run a newsletter that sits at 15,000 subscribers with a 70 per cent open rate.
By the end of this blog you'll have the seven-part framework I actually use, a copy-paste template you can swipe today, the five most common mistakes I see in the affiliate marketing space, the FTC and ASA disclosure rules in plain English, and the FAQ that covers the questions I get from sponsored post inquiries every week.
TL;DR
A product review converts when it answers the reader's actual question: "should I buy this, and why or why not." Most reviews answer the wrong question: "what does this product do." The seven-part framework below structures every review around the buyer's decision, not the product's features.
The structure: pre-use state, first-use reality, thirty-day verdict, what it replaces, real cost, who should skip it, what you'd do differently. Each section answers a question the reader actually has.
This works for affiliate reviews, sponsored reviews, and unpaid reviews of products you genuinely use. The framework is the same. The disclosure changes.
Why most product reviews fail
I'll be specific because the rough version of this conversation is useless.
The typical product review you'll see in 2026 has roughly the same shape across the industry. It has an introduction that says "are you looking for X, you've come to the right place," followed by an explanation of why X is important, followed by a feature list lifted from the manufacturer's marketing site, followed by a pros and cons box, followed by an affiliate link, followed by a closing paragraph that essentially says "buy it."
This structure has three specific problems.
The first is that the reader can tell when a review was written by someone who hasn't used the product for long enough to have an opinion. The structure of the review reveals it. A review that starts with the feature list is usually written by someone who started with the manufacturer's website, not with using the product. A real user starts with "I needed something to do X, and here's what happened when I tried."
The second is that the feature-list structure answers the wrong question. The reader doesn't need to know that the product has fourteen integrations. The reader needs to know whether they should buy it for their specific situation. Those are different questions. The first one is answered by the product manual. The second one is what a review is for.
The third is that the pros and cons box is almost always either too balanced (suggesting the writer doesn't have an opinion) or too one-sided (suggesting the writer is being paid). Real opinions are messy. Real reviews need to reflect that mess.
What converts is the review that reads like a friend telling you about a thing they've been using. Not a sales page. Not a journalistic balance piece. A friend's account.
The seven-part framework
I use this on every review I write, including the sponsored ones, including the affiliate ones, including the ones where I'm not getting paid at all. The disclosure changes. The framework doesn't.
Part one: The honest pre-use state
The first section of every review should establish what your situation was before you used the product. Not the abstract version. The specific version. What were you doing? What was annoying you? What had you tried that hadn't worked?
This part is the trust-builder. Without it, the reader can't tell whether the product is right for them, because they don't know whether their situation matches yours. With it, they read the rest of the review through a lens of "is this person like me."
Example, in my voice, for a hypothetical newsletter platform review: I'd been on Mailchimp for eleven years. I had eight thousand subscribers and a deliverability rate that was getting worse every month. I'd tried fixing it twice and the second time I'd lost six hours to a Mailchimp support ticket that ended without a solution. I was looking for a platform with better deliverability for senders my size.
That's a hundred words that establishes the entire context for the review. Without it, every feature mention later is meaningless.
Part two: The first-use reality
The second section should be your first day or two with the product. Not the polished version. The reality. What did setup feel like? What confused you? What was easier than you expected? What was harder?
The first-use section is where you separate yourself from the writers who didn't actually use the product. They cannot fake this section. They can only fake feature lists.
Be specific. Name the steps that took longer than they should have. Name the integration that broke. Name the documentation page that was outdated. Then name the thing that pleasantly surprised you, because every product has at least one.
Part three: The thirty-day verdict
The third section is what the product feels like after a month of using it. This is the section that separates a review from a first-impressions piece.
What's still good? What's started to annoy you? What workflow change has it actually produced? Has anything in your business changed because of it?
If you don't have thirty days of use, you shouldn't be writing a review. You should be writing a first-impressions piece, clearly labelled as such.
Part four: What it replaces
The fourth section should name the tool, process, or workflow this product is replacing in your stack. This is the section most reviews skip and it's the section the buyer cares about most.
Most buyers are not deciding whether to use a product. They're deciding whether to replace something with it. The review that tells them "this is what I stopped using when I started using this" answers their actual question.
If the product is genuinely new (no replacement), say so. But most products replace something. Name the something.
Part five: The real cost
The fifth section is the price, plus the hidden costs the manufacturer doesn't talk about.
Real costs include: the headline subscription price. The setup time investment. The learning curve in hours. The integrations you'll need to add or rebuild. The other tools you'll need to keep using alongside this one. The time cost of migrating off your existing tool.
A review that says "it's twenty pounds a month" without addressing the other costs is misleading the reader. The real cost of a product is rarely just its sticker price.
Part six: Who should skip this
The sixth section is the one most writers refuse to write. It's also the most powerful trust-builder in the entire review.
Tell the reader who this product is NOT for. Be specific. "If your subscriber list is under five hundred, this is overkill." "If you've been doing this for less than two years, the learning curve will kill you." "If you're already happy with X, this isn't enough of an improvement to justify the migration."
The counter-intuitive trust signal: telling someone the product isn't for them increases conversion among the people the product IS for. Because they read your skip-this section, recognise it doesn't apply to them, and trust you more.
Part seven: What I'd do differently
The seventh section closes the review with your specific recommendation, including alternatives.
Not "five stars, buy it." A practitioner's verdict. "I'd buy this if your situation looks like mine. If your situation looks like X instead, you should look at Y. If it looks like Z, stick with what you have."
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
This section signals seniority. Novice reviewers always end with "buy it." Senior reviewers always end with "here's what to do depending on your situation."
A copy-paste template you can swipe
I'll give you the structural template. Fill in the bits in square brackets.
> ## My honest review of [Product Name] after [time period] of using it > > Pre-use state: [What was your situation before you tried this? What were you doing? What was annoying you?] > > First-use reality: [What was setup like? What broke? What pleasantly surprised you in the first 48 hours?] > > Thirty-day verdict: [What's still good? What's started to annoy you? What's changed in your business?] > > What it replaces: [What did you stop using when you started using this? Or, if nothing, what was the gap it filled?] > > The real cost: [Headline price. Setup time. Learning curve. Hidden costs.] > > Who should skip this: [Three specific reader profiles this is NOT for.] > > What I'd do differently: [Your recommendation, including alternatives by situation.]
Use this on the next review you write and notice the difference in how it reads.
The five most common mistakes
These show up in roughly nine out of ten reviews I read across the affiliate marketing space.
One. Starting with the feature list. The feature list belongs in part three or part four, not part one. If your review opens with features, you've put the manufacturer's perspective ahead of the reader's.
Two. The all-positive review with three minor "cons." Real opinions are messy. A review that finds three trivial cons (the interface is a bit slow, the colour scheme isn't to my taste, the mobile app is okay) is signalling that the writer either didn't use the product long enough to find real problems, or is being paid to be polite. Real cons are specific and meaningful.
Three. No concrete examples. A review that says "the email builder is intuitive" is not a review. A review that says "I built my first newsletter in 22 minutes including the embedded video and the signup CTA, which is the fastest I've done that on any platform" is a review.
Four. Missing the comparison. Most products compete with something specific. A review that fails to compare to the most obvious competitor is incomplete. Name the competitor. Say why this one is better or worse for your specific situation.
Five. The disclosure problem. Either no disclosure, or buried disclosure, or disclosure that's so cagey it sets off the reader's BS detector. Be clear. "This post contains affiliate links. I have not been paid by the manufacturer." Or, "This is a sponsored review and the manufacturer paid for placement. The opinions are mine and I would not have agreed to the placement if I didn't actually use the product." Whatever the truth is, say it cleanly at the top.
The disclosure rules in plain English
I'm going to give you the FTC and ASA versions in plain English. Your lawyer will give you the long version.
Affiliate links (FTC and ASA). If you earn a commission from a link, you must disclose it. The disclosure must be clear, prominent, and before the link. "This post contains affiliate links" near the top of the post is the minimum.
Sponsored posts (FTC and ASA). If you've been paid to write the post or paid for placement, you must disclose it. "Sponsored by [brand]" or "This is a paid partnership with [brand]" near the top of the post.
Free products in exchange for review (FTC and ASA). If the manufacturer sent you a product to review for free, that's a material connection and must be disclosed. "[Brand] sent me [product] for review purposes" near the top.
Discount codes (FTC and ASA). If you have a discount code that benefits both you (commission) and the reader (discount), disclose it. "Use code XYZ for 10% off, I earn a small commission if you do" is fine.
The reason for clean disclosure is not just legal. It's commercial. Clean disclosure increases trust, which increases conversion. Hidden disclosure costs you more clicks than it saves.
How to monetise honest reviews
There are five ways to make money from product reviews. They're not mutually exclusive.
One. Affiliate links. Standard. Lower per-click value (typically 5 to 30 per cent commission on the sale). Works on volume. Best for high-traffic review sites.
Two. Sponsored placements. Higher per-post value (typically £200 to £5,000 per post depending on traffic and audience). Lower volume because you can only do a few per month without burning your audience. Best for sites with engaged, high-trust audiences.
Three. Discount codes that convert. Brand gives the reader a meaningful discount, you get a higher commission for using the code. Better conversion than plain affiliate links because the reader gets value in exchange for using your link. My preferred attribution method.
Four. Newsletter sponsorship of the review. Newsletter goes out featuring the review. Brand pays for the newsletter placement separately. Often combined with the sponsored post.
Five. Newsletter mentions of products you genuinely like. Not sponsored. Generates affiliate revenue without the sponsored disclosure overhead. Best for products you'd recommend regardless of payment.
The thing I'd say to anyone starting on this: stack the methods. A review that combines an affiliate link, a discount code, and a newsletter mention will earn more than any single method alone.
FAQ
How long should a product review be? Long enough to actually use the framework. That's typically 1,500 to 3,000 words. Shorter than 1,200 is usually not enough room for all seven sections.
Can you review products you haven't bought? Technically yes. In practice, no, you can't write a useful review of a product you haven't used. You can write a first-impressions piece. That's different. Label it clearly.
How do you handle reviews where you have to be negative? Carefully. Be specific. Be fair. Always include "who would this product work for" because most products work for someone, just not for you. The negative reviews are usually the highest-converting because they signal trust.
When should you use affiliate links versus sponsored versus both? Affiliate links for products you'd recommend regardless. Sponsored for products you've negotiated a placement fee for. Both for products where you've negotiated both. The disclosure changes with each.
How do you write a review of a product you don't actually like? Honestly. The skip-this section becomes the main section. Be specific about what didn't work. Be fair about who it might work for. Don't burn the manufacturer. The negative review you write fairly is the one that earns you the readers who trust your other reviews.
What's the difference between a review and a comparison? A review covers one product in depth. A comparison covers multiple products against a single set of criteria. Both have a place. Reviews are better for trust-building. Comparisons are better for buying-decision content.
Should I rate products with stars or scores? I don't. Star ratings are easy to scan but harder to take seriously. A written verdict tells the reader more than a number. If you must use stars, also include the written version.
Can AI write product reviews for me? AI can write a draft of every section. It cannot write the specific dated details that make a review feel real. The framework above is the easy part. The dated specifics are the hard part. AI helps with the draft. You add the specifics.
The thing to take away
A product review converts when it answers the reader's actual question: should I buy this, and why or why not. The seven-part framework above structures every review around that question. The disclosure rules above keep you legal. The monetisation stack above is how the work actually pays.
If you want to talk about whether sponsored placements or product reviews on lilachbullock.com would fit your brand, the partner inquiry form is linked at the bottom.
If you want the template as a downloadable PDF, subscribe to the newsletter.
Either way, the next review you write will be better than the last one.
Related reading
- What are product reviews actually for? Read: What is the meaning of a product review?
