Comparison pages: how to write X vs Y pages that get cited
Searchers and AI engines both look for fair comparisons before a purchase. Here is how to build vs and alternatives pages that rank and get quoted.
People who search for "X vs Y" or "X alternatives" are close to a decision. They already know the category. They want help choosing. That makes comparison pages some of the most valuable pages on a site, and some of the most abused. Most of them read like ads, and both Google and AI engines have learned to skip those.
Why comparison queries matter
Comparison queries carry strong commercial intent. The reader is weighing options, so a good answer can shape the choice. AI engines also get these questions all the time. "Which is better for a small team, A or B" is a natural prompt for a chatbot.
Those engines tend to favor sources that sound neutral and give specifics. A page that says its own product wins every row of a table gives them little to quote. A page that says when each option fits gives them a ready answer. We cannot see inside any engine's ranking, so treat this as a working view, not a rule.
Pick the right page type
Three formats cover most of the demand. Each matches a different search.
- Head-to-head page: your product against one named competitor. Matches "X vs Y" searches.
- Alternatives page: a list of options to a well-known product. Matches "X alternatives" searches.
- Category roundup: a ranked or grouped list of tools for one job. Matches "best tools for Z" searches.
Do not put all three on one URL. They answer different questions, and mixing them blurs the page. This is the same intent-matching problem covered in our guide to search intent. Check what the current results look like first. If the top ten are all roundups, a head-to-head page will struggle.
Structure the page so it can be lifted
Start with a short verdict near the top. Two or three sentences that say who each option suits. Readers get the answer fast, and an engine gets a clean passage to quote.
Choose A if you need X. Choose B if you care more about Y.
After the verdict, work through the criteria that actually drive the decision. Use one h2 or h3 per criterion, with a plain heading such as "Pricing" or "Setup time". Keep each section self-contained, because retrieval systems often pull one chunk of a page at a time. Our post on content chunking explains why.
- Open with the verdict and who each option fits.
- List the criteria you will judge on, and say why they matter.
- Give each option a fair, specific paragraph per criterion.
- Note real weaknesses, including your own.
- Close with a short recommendation by use case.
A table helps readers scan a comparison. If you use one, make it a real HTML table, not an image or a script-built grid, so crawlers can read the rows.
Stay fair and accurate
Fairness is not just good manners here. It is the thing that makes the page worth citing. Admit where the other product is better. Say who should not buy yours. Readers notice, and so do the trust signals described in our E-E-A-T post.
Accuracy is the harder part. Competitor pricing and features change often. A stale comparison is worse than none, because it states something false about another company. Put a visible last-checked date on the page and keep dateModified in your markup honest. Only change it when you really recheck the facts.
- Check every price and feature claim against the competitor's own site.
- Link or name your source for any claim that could be disputed.
- Use the competitor's real product names and spell them correctly.
- Avoid claims you cannot back up, such as "fastest" or "most reliable".
- Set a reminder to review each page every few months.
Avoid common mistakes
Thin pages at scale
It is tempting to generate a page for every pair of products from one template. Without real, distinct analysis, those pages look like the thin output that programmatic SEO warns against. Write fewer pages, and make each one worth reading.
Every row says you win
If your product wins every criterion, readers stop trusting the page. A mixed result looks more honest and converts better in many cases, though results vary by audience.
Review markup on your own product
Do not wrap your own ratings of your own product in review schema. Google's self-serving reviews rule can remove your rich results. Plain prose is fine.
Measure and act
Track comparison pages as a group. In Search Console, filter queries containing "vs", "alternative", and "compare" with a regex filter. Watch impressions, clicks, and the pages that win them. For AI visibility, run a few comparison prompts by hand each month and note whether your page is cited.
Your next step: pick your single most-searched competitor, check what ranks for the "vs" query, and write one fair page with a verdict at the top. Add a last-checked date, and put a review on the calendar.