Writing a Versus Page That Is Honest About Trade-Offs
Content · 9 min read ·
A versus page can persuade or deceive. How to write a head-to-head comparison that is accurate, fair, dated and honest about what each product does best.
"X vs Y" is one of the most searched phrases in online buying. People who type it already have a shortlist of two. They are close to a decision and looking for the last piece of evidence. A well-written versus page can be exactly what they need. A badly written one is a sales pitch with a thin disguise, and readers can tell.
This article explains how to write a versus page that is honest, useful and fair, whether you are an independent writer or the maker of one of the products.
Why versus pages matter
A versus page serves a particular moment. The reader is not asking "what is this category?" but "which of these two should I pick?" They want direct comparison on the points that matter, honest strengths and weaknesses, and a clear way to choose.
Google's guidance on helpful content asks whether a page gives original, substantial information and leaves the reader satisfied that they learned enough to achieve their goal. A versus page that does that can serve readers well and earn trust that lasts beyond one search.
Decide your position and say it
Be clear about who you are.
- Independent writer: you have no stake in either product. Say so.
- Maker of one product: say so plainly, near the top. Readers will read your claims with that in mind, and your openness earns credit.
- Affiliate or sponsored: if you earn from referrals or payments, say so, and keep that separate from your analysis.
Disclosure is not an admission of bias. It is information. A maker who writes a fair comparison and discloses the relationship is often more useful than an anonymous site with hidden motives.
Know the rules
Comparing with a competitor is permitted, but there are standards. Wikipedia describes comparative advertising as an advertisement that mentions a competitor by name to show superiority, and notes the commonly accepted conditions: the comparison must be truthful and supported by facts, based on measurable attributes, presented as tested and not damaging to the competitor's reputation or likely to confuse.
In the UK, GOV.UK's guidance on regulations that affect advertising describes rules against false or deceptive messages, against omitting important information, against using a competitor's logo or trademark in advertising and against comparing your product with a competitor's product that is not equivalent. Penalties can be significant. These rules apply in different ways depending on whether you are advertising to consumers or businesses. This article is not legal advice, so take advice if you plan paid promotion or any marketing use of a comparison.
In practice, the standard is simple: say only what is true, be able to prove it, compare like with like and be fair.
Compare like with like
Many misleading comparisons set one product's premium plan against another's free tier, or one's latest version against the other's old one. Ensure that you compare equivalent plans, versions and use cases. State exactly what you compared: "Plan A (the standard paid plan, as of March) versus Plan B (the equivalent standard plan)." If equivalence is imperfect, say so.
Choose attributes before you look
Fix the list of attributes you will compare in advance, based on what readers need, and apply the same list to both products. Avoid adding attributes after seeing which product wins. Our article on choosing attributes covers this in more detail.
Structure of a versus page
A reliable structure:
1. A short summary
At the top: who each product is for, the main difference and a link to the full comparison. A reader in a hurry should be able to leave with the essentials.
2. The disclosure
Who you are, any relationship to either product and when the comparison was last updated.
3. At a glance
A compact table of the main differences, with notes and dates. Use words and symbols, not colour alone.
4. Where X is stronger
Genuinely. Name the attributes, show the evidence and say who benefits.
5. Where Y is stronger
The same, with equal care.
6. Where they are similar
Many differences are small. Saying so is honest and helpful.
7. Who should choose which
A short "choose X if... choose Y if..." section. This is the heart of the page: it turns the comparison into a decision.
8. Costs and limits
Pricing models, plan limits, hidden costs and the total cost of ownership for typical use. Link to each vendor's pricing page for current amounts, rather than copying figures that may change.
9. How we compared
The method: what you tested, how, with what version, on what date. A short statement lets readers judge the reliability.
10. Corrections and updates
A dated change log and a way to report errors.
Be even-handed
Fairness is shown in details.
- Give both products equal space.
- Use the same level of detail for each.
- Use neutral language. "Offers" and "lacks", not "boasts" and "fails".
- Report strengths of the product you prefer less. Readers trust writers who do.
- Report weaknesses of the product you prefer more.
- Avoid loaded images such as a trophy beside one name.
- Do not use the competitor's logo in a way that implies endorsement.
Remember Wikipedia's note that comparisons should not unfairly damage a competitor's reputation. Criticism is fine when it is true, relevant and fairly put.
Prove your claims
For each claim, ask: how would I show this to a sceptical reader?
- Documentation: link to the relevant page.
- A test: describe the test and show results.
- A screenshot, dated.
- A policy or licence: quote the relevant line.
- A source for numbers, with the date.
If you cannot support a claim, soften it or leave it out. Avoid vague superlatives such as "much better" and "far more powerful".
Date everything
Products change often. A versus page that was accurate last year may mislead now. Put the date of last review at the top and, for key claims, the date they were checked. Set a reminder to review quarterly and after any significant release.
Handle disagreements
If the maker of a product contacts you with a correction, treat it seriously. Check the evidence. If they are right, fix it and add a dated note. If they are wrong, explain politely. If you disagree about interpretation, state both views. A page that handles corrections well gains credibility.
Think about search and assistants
A versus page is likely to be read by both people and machines. A clear title in the form "X vs Y: differences, pricing and who each suits", a short summary at the top, a clear table and a frequently-asked-questions section make it easy to understand and quote correctly. Keep the facts consistent with your other pages. Do not stuff keywords or write for algorithms; write for the reader.
A worked example
A writer who runs a small software review site prepares a page on two budgeting apps. She states her position: independent, no affiliate links, and she has used both for three months. The summary says that App A suits people who want detailed categories and App B suits people who want a simple monthly overview.
She compares the same ten attributes for both, fixed before she began testing: setup time, bank connection options, categories and tagging, shared budgets, reports, export, platforms, privacy information, support and pricing model. She dates the page and records the versions tested. Where App A is stronger, such as tagging, she shows a screenshot. Where App B is stronger, such as setup time, she reports her timed test. Where they are similar, she says so.
In the "choose" section she writes: "Choose A if you track spending by category in detail. Choose B if you want to see where your money went last month in a minute." She links to each vendor's pricing page and adds a note on how she compared. After publication, the maker of App B points out a feature she missed. She verifies it, updates the page with a dated note and thanks them. Readers comment that the page helped them choose in ten minutes.
A checklist
- Position and relationships disclosed
- Comparison like for like
- Attributes fixed in advance
- Summary, table, strengths of each, similarities
- A clear who-should-choose section
- Costs and limits, with links to pricing pages
- Method described
- Every claim supported
- Dated, with a correction route
- Fair language and images
The categories page here shows products grouped by purpose, the search page helps you find ones to compare, and the leaderboards page shows how ranking signals are labelled.
Keeping the page useful over time
A versus page earns its value from being right. Assign someone to own it, and put the next review in the calendar when you publish. Watch each product's release notes and pricing page for changes. When something shifts, update the affected rows, change the date and add a short note at the bottom describing what changed and when. Readers who return after a few months will see that the page is maintained, and search tools will see a page that stays current. If a product is discontinued or merged into another, say so clearly at the top, and point readers to what replaced it.
Frequently asked questions
Is it acceptable to recommend one product? Yes, if your recommendation follows from the evidence and you explain who it suits.
Can I use the competitor's name in the title? Usually yes, to identify the comparison. Avoid using logos in a way that suggests endorsement.
What if I find nothing wrong with either product? Say so. Not every comparison needs a loser.
Questions and answers
- What is a versus page?
- A page that compares two products head to head, usually titled in the form 'X vs Y', explaining differences, strengths and who each suits.
- Can I write a versus page about my own product?
- Yes, if you disclose the relationship, stick to verifiable facts, be fair about the other product's strengths and date your claims.
- What rules apply to comparing with a competitor?
- Comparisons should be accurate, verifiable and not misleading, and should compare like with like. Rules vary, so take advice for paid or consumer-facing promotion.
- How often should I update it?
- Whenever either product changes materially, and review it at least every quarter.