How to Write Comparison Pages That AI Assistants Cite (X vs Y and Alternatives Pages)
Put the verdict in the first two sentences, state every difference as text with a number and an "as of" date, keep one source of truth for prices, keep "who should pick the other one" short and honest, and write the FAQ as buyer prompts. The section-by-section structure, a before-and-after table, and the schema to use.
How do you write a comparison page that AI assistants cite? The short answer
Put the verdict in the first two sentences, state every difference as a number or a plain sentence in the page text with an "as of" date, keep one source of truth for your prices, say briefly who should pick the other product, and end with FAQs written as the questions buyers actually type into ChatGPT, Claude, Perplexity and Google. A page built that way persuades a human reader and gives an assistant sentences it can quote without guessing.
Comparison pages ("X vs Y") and alternatives pages ("X alternatives") are the pages buyers read right before they choose, and they're the pages assistants reach for when someone asks which tool to pick. Most of them are built for a skim on a laptop: a hero banner, a grid of checkmark icons and a pricing toggle. Very little of that is text a machine can read and repeat.
What does an AI assistant need from a comparison page?
An assistant that searches the web fetches your page, reads its text, and writes its own answer from the passages it trusts. Google's guidance for its own AI features is plain about this: there are no special optimizations, and the basics include "making sure that important content is available in textual form" and "making sure your structured data matches the visible text on the page."
Google's guidance for review and comparison content asks for the same things a careful buyer wants: "quantitative measurements about how something measures up," a view of "which might be best for certain uses or circumstances," "benefits and drawbacks," and "first-hand supporting evidence" for whatever you call the best. Read together, the rule for a comparison page is simple. Every claim that matters is a sentence or a table cell with a number, a condition and a date. A checkmark icon says nothing a reader can quote, and a price drawn inside an image or loaded by a toggle may not be in the text at all.
The structure, section by section
| Section | What goes in it | Why it gets quoted |
|---|---|---|
| Title and H1 | "[Your product] vs [Competitor] (2026): [the deciding difference]" | Matches the prompt and states the claim up front |
| Verdict, first 75 words | Who should pick which, with the one or two differences that decide it, in plain sentences | Buyers decide from the first screen, and a self-contained opening is the easiest passage to quote |
| Comparison table | An HTML table with words and numbers in every cell, never icons alone | Each row is a fact that can be lifted on its own |
| Pricing | Each plan's price, billing period, what it includes and the common add-ons, with "as of [month year]" | Price questions are the most common buyer prompts, and a dated price can be trusted |
| Who should pick the other one | Two to four honest sentences on when the competitor is the better fit | Balanced pages read as trustworthy, to people and to models |
| Difference sections | One H2 per deciding difference, phrased as the buyer's question | Question-shaped headings match question-shaped prompts |
| Switching | What moves over, what doesn't, how long it takes | Answers the next question a buyer asks |
| FAQ | 4 to 8 questions written the way buyers ask an assistant | Short, self-contained answers are easy to quote |
| Sources and date | Where each competitor fact came from and when it was checked | Lets a reader, or a model, check the claim |
How do you make the page persuasive and quotable at the same time?
Write the verdict with conditions instead of superlatives. "Pick [Product A] if you need [capability] for a team of [size]; pick [Product B] if [condition]" is more convincing than "the best choice for growing teams," and it's the kind of sentence an assistant can repeat to someone in that situation.
Keep the "who should pick the other one" section short and true. Two to four sentences is enough. Its job is to show you've looked at the competitor fairly, which makes the rest of the page believable. A page that never admits a weakness reads as an ad, and a page that spends half its length praising the competitor loses the sale.
Prove the claims you lean on. If you say setup takes a day, say what the day includes. If you say you integrate with a tool, name the plan it's on. Google's review guidance asks for "first-hand supporting evidence" when you call something the best, and assistants weigh pages that show their work the same way buyers do.
What does a quotable row look like?
A generic example, with placeholders instead of real products:
| Hard to quote | Easy to quote |
|---|---|
| A green checkmark icon in the "CRM sync" row | "Two-way sync with [CRM] on the Pro plan and up; Starter syncs one way" |
| A pricing toggle that shows annual prices by default | "[Price] a month billed yearly, or [price] billed monthly, as of [month year]" |
| "Unlimited*" with the limit in a footnote image | "Unlimited projects; [number] automation runs a month, then [overage price]" |
| "Loved by thousands of teams" | A named, countable claim you're allowed to share, with its date |
| A screenshot of a feature grid | The same grid rebuilt as an HTML table |
How is an alternatives page different from a vs page?
A vs page answers "which of these two?" An alternatives page answers "what else should I look at, and why?" The alternatives page needs a short list with one line per option on who it's for, each option's starting price with an "as of" date, and the criteria the reader should use to choose. Put your own product in the list on the same terms as the others. If you place yourself first, say why in one sentence. Then link each serious option to its own vs page, so the reader who has narrowed it to two has somewhere to go next.
How do you keep prices and facts the same on every page?
Keep one source of truth. That can be a fact sheet your team approves or a data file your CMS renders into every pricing table, comparison table and FAQ. When a price changes, it changes once and every page follows. Date every price with "as of," and recheck competitor prices on a schedule, because their pages change without telling you.
This matters more for AI answers than for rankings. An assistant that finds your price stated two ways, on your pricing page and an old comparison page, has no reason to trust either, and may quote a third-party review site instead. The same goes for plan names, limits and integrations.
Which schema should a comparison page use?
Article (or BlogPosting) with an honest dateModified, BreadcrumbList, and FAQPage for the FAQ block. Add Product or SoftwareApplication markup with offers only if the prices in the markup match the prices on the page. Google's AI features guidance says structured data should match the visible text, and mismatched markup is worse than none. Expect FAQPage markup to help machines read the page, not to change how it looks in Google: Google's FAQ documentation says FAQ rich results are no longer shown in Google Search, as of its June 15, 2026 update.
A checklist before you publish
- The verdict is in the first 75 words, with the conditions that decide it.
- Every table cell has words or numbers; no cell relies on an icon.
- Every price has an "as of" date and matches your source of truth.
- Competitor facts come from the competitor's own page, read recently, and are listed in a sources section.
- The "who should pick the other one" section is honest and short.
- FAQs are written as buyer prompts, with answers that stand on their own.
- Schema matches the visible text.
- The page loads its main content in the HTML, not only after a script runs.
Justin's guide to how to get cited by ChatGPT covers what assistants cite beyond your own site, which is the other half of the job.
Who can build comparison pages that get cited?
A team with one or two competitors can follow this checklist in-house. If you're choosing outside help, our guide on how to choose an SEO agency lists the questions to ask, and our AEO agency page covers how we work on AI answers. For software companies, comparison and alternatives pages are the core of our B2B SaaS SEO agency work. Inside an AI Search Program, we rebuild your comparison pages first, check every draft against your fact sheet, and track which assistants pick you for each buyer question afterward. Smaller sites that want a one-time fix can start with the AI Search Optimization build.
Sources
- Google Search Central, AI features and your website, read November 3, 2026.
- Google Search Central, Write high quality reviews, read November 3, 2026.
- Google Search Central, FAQ (FAQPage) structured data, read November 3, 2026: FAQ rich results no longer shown as of the June 15, 2026 update.
Frequently Asked Questions
-
Make the page easy to quote: the verdict in the first two sentences, every difference stated in text with a number and a date, an HTML table instead of icons or screenshots, prices that match your pricing page, and FAQs written as the questions buyers ask. Then make sure the page is crawlable by search crawlers such as OpenAI's OAI-SearchBot.
-
Yes, briefly. Two to four honest sentences on who should pick the other product make the rest of the page believable to readers and to assistants. Google's guidance for comparison and review content asks for benefits and drawbacks and which option is best for certain uses.
-
An icon carries no words a reader or a model can quote. Write what the checkmark means instead, such as which plan includes the feature and its limit. Google's AI features guidance says important content should be available in text form.
-
Article or BlogPosting with an honest dateModified, BreadcrumbList, and FAQPage for the FAQ block. Add Product or SoftwareApplication offers only when the prices match the page. Google says structured data should match the visible text. Google stopped showing FAQ rich results in 2026, so FAQPage markup helps machines read the page but won't change how it looks in results.
-
A vs page helps someone choose between two products. An alternatives page lists the main options with one line on who each fits, a dated starting price, and the criteria for choosing, then links each serious option to its own vs page.
Written by
Justin McKelveyFormer CTO at an AI startup and former Head of Product, with 50+ products shipped. I ran snowboard and bike shops before I taught myself to code, so I build AI systems and websites with the owner in mind.