How to write an X vs Y comparison page that AI engines cite

"Is X or Y better for a small team?" is one of the most common things buyers ask an AI assistant just before they choose. To answer it, the assistant needs pages that put the two products side by side. If your competitor has written one and you haven't, theirs is the page that gets read, and their framing is the one the answer repeats.

This guide is a template for comparison pages that are worth citing: clear enough to quote, fair enough to trust, and specific enough to help a buyer decide. Copy the outline, fill in the table, and adapt the wording to your product.

Why comparison pages get cited

When a question names two products, the most relevant pages on the web are the ones that discuss both. That's usually a short list: comparison articles on blogs, review site comparison pages, community threads, and the vendors' own "X vs Y" pages. In our work on which websites AI engines cite, vendor comparison pages show up regularly, especially when they include a clear table and plain-text pricing.

A comparison page also helps on questions that don't name you. "Alternatives to [Rival]" answers are often built from pages that compare the rival with something else. A good "[You] vs [Rival]" page is a reasonable source for both.

Before you write: pick the comparisons that matter

Don't write a page for every competitor. Start with the comparisons buyers actually make:

1. Rivals named instead of you. Look at the buyer questions you track and note which competitors appear when you don't. The two or three that come up most are your first pages.
2. Rivals your prospects mention. Ask sales and support which products people say they're also looking at.
3. Comparison questions you already lose. If an engine answers "[You] vs [Rival]" with mostly the rival's view, your page is missing or weak.
4. Competitor comparison pages that get cited. If a rival's "[Rival] vs [You]" page is among the cited sources for your questions, you need your own version.

One page per rival is the right default. A single page comparing you against six products is harder to read and harder to quote.

The page outline (copy this)

Use this structure for each page. Each numbered item is a section, in this order.

1. Title: "[You] vs [Rival]: [the one real difference]". For example, "Acme vs Rival: simpler invoicing for freelancers, fewer accounting features".
2. The short answer, in two or three sentences: who should pick [Rival], who should pick [You]. Put it at the very top, before any table or image.
3. Quick-facts table: the honest comparison table below.
4. Who [Rival] is best for: one paragraph, written as if you were recommending them. Be specific.
5. Who [You] is best for: one paragraph, equally specific.
6. Key differences: three to five subsections, one per difference that changes the decision. Each with a heading that names the difference and a short, factual explanation.
7. Pricing compared: both products' current prices, what each plan includes, and the date you checked.
8. Switching: what moving from [Rival] to [You] involves, if anything. Import tools, what carries over, what doesn't.
9. Common questions: three to six real questions buyers ask about the two products, each with a direct answer.
10. Last updated: the date, and a line on how you checked the facts (their public pricing page, their docs, a trial account).

Example short answer

Weak: "Acme is the modern, all-in-one platform that outperforms Rival in every way."

Strong: "Pick Rival if you need full double-entry accounting and payroll in one place. Pick Acme if you're a freelancer who mainly needs to send invoices, take card payments and track hours, and wants something you can set up in ten minutes. Acme starts at $9 a month; Rival's comparable plan starts at $25."

The strong version names a buyer, a reason and a fact. That's what an AI answer tends to repeat, because it directly answers the question.

The honest comparison table (copy this)

Fill this in with facts a buyer could check. Keep each cell short. Use "Yes", "No" or a number where you can.

The two "stronger" rows are the most important ones. They force you to state the trade-off, and they're what makes the page credible. If you can't name anything the rival does better, you don't know the rival well enough to write the page yet.

Writing rules that make a page worth citing

• Answer first, details second. The short answer and the table should make sense on their own. Everything below them is supporting detail.
• Use facts, not adjectives. "Exports to CSV and PDF" is useful. "Powerful reporting" says nothing.
• Write numbers as text. Prices, limits and plan names in plain text, not only in images or a screenshot of their pricing page.
• Concede real weaknesses. If the rival has more integrations, say so and say how many. Buyers will find out anyway.
• Don't disparage. No mocking, no "outdated", no guessing about their roadmap. Describe, don't attack.
• Link to your sources. Link to the rival's public pricing page and docs where you got the facts. It shows your work.
• Match your other pages. The price and feature claims on the comparison page must match your pricing page and docs exactly.
• Use plain headings. "Pricing", "Integrations", "Who should pick Rival" are easier to find and quote than clever ones.

Mistakes that get comparison pages ignored

• The page is an ad. Every row is a green tick for you and a red cross for them. Readers stop trusting it in seconds.
• Out-of-date prices. The rival changed their pricing a year ago and your page still shows the old numbers. This is the fastest way to make the page wrong, and wrong facts can end up repeated in answers.
• Content hidden behind a form or a tab. If the comparison only appears after clicking through, or loads inside a widget, it may not be in the page text at all.
• One page for everyone. "Us vs the top ten tools" with a giant table. Split it into one page per rival, plus a separate alternatives page.
• No date. Without a "last checked" date, nobody can tell whether the facts are current.
• Fake neutrality. Presenting your own page as an independent review site. Say clearly that it's written by you.

An alternatives page, too

Alongside your "X vs Y" pages, consider one "[Rival] alternatives" page for your biggest competitor. The format is similar: a short answer up top ("If you're leaving Rival because of price, consider A, B or us; if it's because of missing features, consider C"), a table of options, and an honest note on who each one suits. Including other alternatives, not only yourself, makes the page more useful and more credible. We do this for our own category on our comparison pages.

Keep it current

Set a reminder to check every comparison page each quarter, and whenever a rival announces new pricing. Update the "last checked" date when you do, even if nothing changed. Note what changed if something did.

It's also worth checking what AI engines say about the comparison, not just what your page says. Citemark's fact check flags answers that state a wrong price or wrong features for your product, which is often the first sign that an old page somewhere, yours or someone else's, needs fixing.

Measure whether it worked

Add the matching questions to the list you track: "[You] vs [Rival]", "[Rival] alternatives", and one or two "is [You] or [Rival] better for [buyer]" questions. Record where you stand before publishing. After four to eight weeks, check two things: is your page among the cited sources for those questions, and are you named more often, or higher, in the answers?

Citemark tracks this on a schedule and shows the cited sources for each answer, and its Fixes tab suggests up to three changes per question based on the pages that were cited. You can see where you stand on your own questions today with the free AI visibility check.