How to write a comparison page AI assistants trust

A comparison page that assistants and readers trust is fair, specific and current. It states its criteria up front, includes real alternatives, describes each accurately, says plainly who each option suits (including when that is not you), and shows when it was last checked. It reads like help, not advertising.

Many brands publish comparison pages. Few are useful. The gap between the two is mostly honesty.

Why does a comparison page matter for AI answers?

Because people ask comparison questions: "A vs B", "alternatives to A", "which is better for a small agency". An assistant answering those has to find pages that discuss several options together. A clear comparison page is shaped like the answer.

There is also a reputation point. If your page is the one that explains the trade-offs fairly, it may be cited and trusted. If it is thin sales copy, it will be ignored by readers whether or not an assistant reads it. For the page types assistants lean on, see the kinds of pages AI assistants cite most.

What should the first paragraph say?

Answer the comparison question directly. Open with a short, usable verdict.

"Choose A if you need X. Choose B if you need Y. Choose us if you need Z." That is easy to read and easy to quote. If your honest summary is that a competitor suits a particular buyer better, say so. Credibility is what the page is for.

Then give the depth, structured around the criteria a buyer actually weighs.

How do you choose the criteria?

Use the criteria buyers use, not the ones where you win. Look at the questions people ask in your category and what they push back on. Common ones include:

• price and what each plan includes;
• who the product is for (size, industry, skill level);
• features that matter for the main job;
• integrations and limits;
• support and onboarding;
• how long it takes to get started.

State the criteria near the top. A reader should know what the comparison is judged on and why. If you chose unusual criteria, explain why. Selecting criteria that happen to favour you without saying so is the quickest way to lose trust.

How should you describe competitors?

Accurately, from sources you can point to, and without adjectives that carry a verdict.

• Check every fact against the competitor's own current pages. Prices and features change.
• Date it. "Checked on [date]" next to a pricing table tells readers how much to trust the numbers.
• Credit what they do well. If a rival's reporting is stronger, say so.
• Never disparage. Describe the limit ("no free plan") and let the reader judge.
• Avoid claims you cannot support, such as "the cheapest" or "the most accurate" without a basis.

If you are not sure of a fact, leave it out or mark it as unconfirmed. A wrong claim about a competitor damages you more than it damages them.

What does a good layout look like?

Keep it scannable, with a table where a table helps and prose where reasoning matters.

1. Verdict at the top, in two or three sentences.
2. A comparison table with the criteria as rows and the options as columns.
3. A short section per option: what it is, who it suits, where it is strong, where it is limited.
4. "Who should choose what" as a final, plain summary.
5. A last-checked date and a note on how you gathered the facts.

Use plain headings that mirror questions, such as "Which is cheaper for a small team?" Those match the way people ask, and they let a reader jump to the answer.

Should you add structured data?

It can help machines parse a page, but it does not replace clear writing. Where it fits your page, such as marking up an FAQ block that is actually visible, it is worth considering. It must match what readers see. See structured data and AI answers.

What are the common mistakes?

• The rigged table: every row favours you, every competitor shows a cross.
• Stale facts: a price from two years ago presented as current.
• No competitors named: a "comparison" of you against "other tools".
• Hidden bias: claiming neutrality while selling.
• Too thin to use: a header and a table, nothing explaining the trade-offs.

An honest page can still help you. Readers who are a good fit for your product will recognise themselves in the description, and those who are not will leave early, which is better for everyone.

How do you know whether it works?

Add the page's target questions to your tracked set and watch them over time. Compare how often assistants recommend you, and whether the page itself is cited, before and after. Allow time: the page needs to be found and read, and answers vary run to run. The routine is in how to track AI visibility over time.

What about "alternatives to" pages?

Searches for alternatives are common, and a page titled around them can be useful if it is honest. List real alternatives, including ones that suit some buyers better than you, and explain the choice criteria. A page that lists only weak options so that you look strong is easy to spot, and readers lose trust quickly. If you are the right choice for a particular buyer, say which one, and say why.

For a quick look at how your site appears to assistants today, try the Citewake checker. To see how Citewake measures what assistants cite, read the methodology.