How to Write 'X vs Y' Comparison Posts That Convert
"X vs Y" is the closest a search gets to a purchase. The person typing it has two products in mind, has probably read a guide already, and wants one more fact to settle it. Most comparison posts fail that reader by describing both products at length and ending with "it depends on your needs", which is the one answer they came to avoid.
This post covers the shape of a comparison that converts, how to pick pairs worth writing, what goes in the table and what doesn't, the "buy X if" section that does the selling, and the mistakes that cost the click. It sits alongside the comparison tables post, which covers the table itself in detail.
The short answer
Open with the verdict in two sentences. Follow with one table of the specs that differ. Then explain the three differences that actually decide it, in order of importance. Then a "buy X if / buy Y if" section with a button under each. Close with a short FAQ. Both products linked, 800 to 1,200 words, and never "it depends".
Picking pairs worth writing
The best pairs come out of your own guides. For each buyer guide, the top pick vs the runner-up is a comparison people make after reading it; so is the top pick vs the famous brand you ranked lower. Add the two most-bought products in the category, which people compare whether or not you've written about them.
Before writing, type "X vs" into Google and see what autocomplete offers. If Y appears, the pair is searched. If it doesn't, and the related searches don't show it either, the comparison won't rank for anything, however good it is. The keyword patterns post covers where "vs" sits among the buying patterns.
The shape of the page
| Section | Length | Job |
|---|---|---|
| Verdict | 2 to 3 sentences | Which one, for whom, and the one reason |
| Comparison table | 5 to 8 rows | Only the specs that differ |
| The three deciding differences | 3 short sections | What the table can't explain |
| Where they're the same | 1 paragraph | Stops the reader hunting for differences that don't exist |
| Buy X if / Buy Y if | 2 short lists + buttons | The sale |
| FAQ | 3 to 4 questions | The "can X do..." questions from People Also Ask |
The verdict goes first
"The X is the better buy for most people because of its battery; the Y wins if you need the smaller size." Two sentences, at the top, before the table. The reader who came for the answer has it; the reader who wants the reasoning keeps going. Putting the verdict at the end is a habit from essay-writing, and it loses the half of readers who skim.
One table, only the differences
A row that says "Bluetooth: yes / yes" tells the reader nothing and makes them scan past the row that matters. Keep rows where the values differ, put the deciding spec in the first row, and don't include a price column: prices go stale and Amazon's rules on displaying them are strict. Two "Check price" buttons under the table do that job.
Three differences, in order
The table says what differs; these sections say why it matters. "The X's battery is 12 hours against the Y's 7, which is the difference between charging weekly and charging every other day." Three is the right number: one feels thin, five means you're listing rather than deciding. Lead with the one that settles it for most buyers.
Where they're the same
One paragraph. Readers assume there must be more differences than there are and keep scrolling to find them; telling them the two share the same motor, warranty and app saves them the hunt and makes the three differences carry more weight.
Buy X if / Buy Y if
Two short lists, three bullets each, each describing a buyer rather than a feature: "you ride more than twice a week", "you keep it in a small flat". A button under each list with the tag. This is where the commission happens, and the reader should be able to find themselves in one of the two lists.
Mistakes that lose the click
- "It depends on your needs." The sentence that sends the reader to the next result. Say which one for whom.
- Two full reviews stapled together. Each product described from the top, then a conclusion. The reader wanted the difference, not two descriptions.
- A spec dump. Twenty rows, most of them identical. The deciding spec is buried.
- Linking only the winner. Everyone who picks the other one buys without your tag.
- Pairs nobody searches. A comparison between the top pick and the ninth pick in your guide. Autocomplete first.
- Hands-on language with no hands on. "The Y felt flimsier" about products you compared from specs. Say what you did.
Linking the comparison into the site
Each comparison links up to the buyer guide it came from ("both appear in our bike lights guide") and across to the single reviews of X and Y where they exist. The guide links down to the comparison from the section where the two products are discussed.
A comparison with no guide above it is a thin page on its own; one that sits inside a cluster is the page that closes the sale the guide opened. The internal linking post covers the anchors.
Doing it with AffSERP
The pairs come out of the guides, and the guides are what AffSERP's X Best Review tool writes: a ranked list from live product data with the top pick and runner-up named, which gives you the first comparison to write for every guide.
Keyword Grouping separates the "vs" keywords from the rest of a list so they're planned as their own batch. The comparison itself is short enough to write by hand in the editor using the shape above, with the product facts from the guide's sections and both links already tagged.
FAQ
How long should an 'X vs Y' comparison post be?
Shorter than a buyer guide: 800 to 1,200 words is usually right. The searcher has two products in mind and wants the difference that decides it, not a tour of both. A verdict, one table, three deciding differences, a 'buy X if / buy Y if' section and a short FAQ cover it.
Which products should I compare?
Pairs people actually weigh against each other: your guide's top pick vs its runner-up, the top pick vs the famous brand, and the two most-bought models in the category. Check the pair appears in Google's autocomplete ('X vs') before writing. A comparison nobody searches for ranks for nothing.
Should I link both products in a comparison post?
Yes. Both links carry your tag and both earn. The reader buys the one that's right for them, and a post that only links the winner loses the commission from everyone who picks the other. Put a button under each product's section and both in the table.
Can I write a comparison without owning either product?
Yes, if you say what you compared: specs, manuals and owner reviews. The deciding differences are usually in the specs and the complaints, not in a hands-on impression. Say your method plainly and don't invent hands-on claims; that's the one thing that discredits the page.
Keep reading
