Pros and Cons in Product Reviews: How to Write Ones That Aren't Filler
Every product section in every buyer guide has a pros and cons list, and almost all of them are the same list: the specs copied into the Pros column, "slightly pricey" in the Cons column, and nothing a reader couldn't have got from the listing.
The format survives because it scans well. What goes in it is where most guides, and nearly all generated ones, hand the reader nothing.
This post covers why the lists come out as filler, the test that separates a real pro from a restated spec and a real con from a non-con, how many to list, the honest con and what it does for trust, where the block sits in the section, when two sentences beat a list, and the markup question.
The one-star reviews post covers where the cons come from; this is what to do with them.
The short answer
A pro is what this product does better than the others in the guide, in the reader's terms; a con is what owners complain about, stated plainly. Three to four each, after the reason-to-buy paragraph and before the button.
Never a spec as a pro, never "pricey" as a con. If a product has only one real point each side, write two sentences instead of a list. No review-rating markup on it.
Why the lists are filler
The list is easy to fill with things that are true and useless. "Pro: 800 lumens" is true; it tells a reader nothing about whether 800 is good, or better than the next product's 600, or more than they need. "Con: slightly expensive" is true of everything above the cheapest option and warns nobody off.
A generator asked for pros and cons with the spec sheet as input produces exactly this, because the spec sheet is what it has. The fix is the same as everywhere in a guide: the list needs comparison and reviews as input, not specs.
The test
| Column | The test | Passes | Fails |
|---|---|---|---|
| Pro | Does this product do it better than the others in the guide, and does the reader feel the difference? | "Cut-off beam: lights the road without blinding drivers, which the two cheaper picks don't" | "800 lumens", "USB-C charging" (when they all have it), "well-built" |
| Con | Do owners actually complain about it, and would a buyer want to know first? | "The clamp loosens on rough roads; several owners add a rubber shim" | "Slightly pricey", "only one colour", "may not suit everyone" |
A quick way to apply it: for each pro, ask "compared with what?"; if the answer is "nothing in particular", it's a spec. For each con, ask "who said so?"; if the answer is "nobody", it's padding.
How many
Three to four each. Two reads thin, six reads as a spec sheet split in half. The pros should include the reason this product is in the guide at all (if it isn't in the pros, why is it a pick?), and the cons should include the thing the caveat sentence says, in shorter form.
Uneven is fine: a budget pick with four pros and two cons is honest; a pick with five pros and "none" is an advert.
The honest con
The con that costs you nothing and earns the most trust is the one the reader would have found anyway: the sizing that runs small, the battery that takes four hours, the app that wants an account. Naming it does three things. It tells the reader you read the reviews.
It prevents the return, which reverses the commission. And it makes the pros believable, because a page that admits a flaw is a page that isn't selling. A pros-and-cons block with a real con converts better than one without, and the product descriptions post covers the same principle for the paragraph above it.
Where it sits
In the product section: the reason-to-buy paragraph first (why this pick, for whom), then the pros and cons, then the button. The reader who scans sees the list; the reader who reads gets the reason first and the list as confirmation. Above the paragraph it becomes the section, and the section reads as a template.
When two sentences beat a list
A list with one real pro and one real con, padded to three each, is worse than two sentences: "The reason it's here: the beam shape, which none of the cheaper picks match. The catch: the clamp loosens on rough roads, and owners shim it."
Same information, less space on a phone, and no padding to be caught out on. Use the list when there are three real points a side; otherwise write the two sentences and move on.
The markup question
Pros and cons are part of Google's product review guidance (it asks for what the product does well and poorly), and some SEO plugins offer to mark a block up as a Review with a rating.
Don't, unless the page is a single-product review with a real rating you'd defend: self-serving review markup on a buyer guide is against Google's structured-data rules, and the stars it produces get removed with a manual action. The schema post covers what markup a guide should carry; a plain list with a heading is what pros and cons need.
Doing it with AffSERP
AffSERP's X Best Review tool writes each product's pros from the comparison with the other picks in the guide (what this one does that they don't) and its cons from the pattern across owner reviews, so the list fails the filler test by construction: "800 lumens" can't be a pro when every pick has it, and "pricey" never appears because the cons come from complaints.
The block sits after the reason and before the button, and collapses to two sentences when a product has one real point a side. Your own notes add the con only you know about.
FAQ
How do you write pros and cons for a product review?
A pro is something this product does better than the alternatives in the guide, stated as what it means for the reader. A con is something owners actually complain about, stated plainly. Three to four of each, no spec restated as a pro ('800 lumens'), no non-con as a con ('slightly pricey'). If you can't find a real con, read the three-star reviews until you do; a product with no con is a product you haven't looked at.
Should every product in a buyer guide have pros and cons?
In the product sections, yes, briefly: it's the fastest way for a scanning reader to see why this pick exists and what the catch is. But the list format isn't sacred. Two sentences, 'the reason' and 'the caveat', do the same job in less space on a phone, and read less like a template. Use the list where the product has three real points on each side; use the two sentences where it has one.
Is a pros and cons list good for SEO?
Modestly: it's scannable, it's the kind of self-contained passage snippets and AI Overviews lift, and Google's product review guidance asks for 'what the product does well and poorly'. It won't rank the page on its own. Don't attach review-rating schema to it unless the page is a review of one product with a real rating; that markup is for single-product reviews, and self-serving stars are against Google's rules.
What's a good con to list for a product?
One a buyer would want to know before paying: the mount that loosens, the battery that's slow to charge, the app that needs an account, the size that runs small. Not 'a bit expensive', not 'only comes in black', not 'may not suit everyone'. The one-star and three-star reviews are where real cons live; the honest con is also the line that makes readers believe the pros.
AffSERP writes each pick's pros against the other picks in the guide and its cons from the pattern in owner reviews, so '800 lumens' and 'pricey' never make the list.
Start with free wordsKeep reading
