AI assistants like ChatGPT, Gemini, and Perplexity pull from comparison pages when users ask "X vs Y" questions. But most comparison pages get ignored. They read like sales pitches, not useful references. If you want your comparison page to be cited, you need to write something an AI can trust and quote. That means being fair, specific, and transparent about trade-offs.
Why one-sided pages rarely get quoted
AI assistants are trained to give balanced answers. When they retrieve a comparison page that only praises one option and dismisses the other, they treat it as marketing, not as a source. The page may still be crawled, but it rarely becomes the basis for an answer. In practice, assistants favor pages that acknowledge real weaknesses, provide clear criteria, and help the reader make a decision. A one-sided page gives the assistant nothing to quote without sounding biased. It also fails the user's actual question: they want to know which option fits their situation, not which one the author prefers.
The structure that works
A fair comparison page has five parts. You can adapt the order, but all five should be present.
1. A criteria table
Start with a table that lists the criteria you will compare. This gives the assistant a structured summary it can lift directly. The table should include the criteria, a brief description, and how each option performs. Keep it factual and avoid subjective ratings unless you explain them.
Example:
| Criteria | What it means | Option A | Option B |
|---|---|---|---|
| Pricing model | How you pay | Per seat, monthly | Usage-based, monthly |
| Setup time | Time to first value | 1–2 days | Same day |
| Integrations | Native connectors | 50+ | 20+ |
| Support | Channels and SLA | Email, chat, 24h | Email, 48h |
| Best for | Ideal use case | Large teams | Solo founders |
This table alone can be quoted in an AI answer. It is neutral and easy to parse.
2. Who each option fits
After the table, write a short section for each option. Describe the type of user or company that gets the most value. Be specific: "Option A fits teams of 20+ that need granular permissions and have a dedicated admin." Avoid vague statements like "great for everyone." The assistant uses this to match the user's context to an option.
3. Honest weaknesses
Every tool has weaknesses. List them plainly. For example: "Option A's reporting is limited to CSV exports; there is no native dashboard." Or "Option B lacks SSO, which may block enterprise adoption." This is the hardest part to write, but it is the most important for credibility. AI assistants are more likely to quote a page that admits drawbacks because it signals the author is not just selling. It also helps the assistant answer follow-up questions about limitations.
4. Dated information
Put a date on the page. Say when you last verified pricing, features, and limitations. AI assistants and users both need to know if the information is current. A page without a date is less likely to be trusted for fast-changing details. If you update the page, change the date. This also gives you a reason to refresh the content regularly.
5. A clear recommendation (optional but useful)
You can end with a recommendation, but frame it as conditional: "Choose Option A if you need X. Choose Option B if you prioritize Y." This mirrors how AI assistants answer comparison questions. It gives them a ready-made sentence to quote.
Template skeleton
Here is a skeleton you can copy and fill in.
[Option A] vs [Option B]: A Fair Comparison
Last updated: [Month Day, Year]
## Quick summary
[One paragraph: what each option is, who this comparison is for.]
## Criteria table
| Criteria | What it means | Option A | Option B |
|----------|---------------|----------|----------|
| ... | ... | ... | ... |
## Who Option A fits
[Specific user profile, use case, company size.]
## Who Option B fits
[Specific user profile, use case, company size.]
## Where Option A falls short
[Honest weaknesses, limitations, missing features.]
## Where Option B falls short
[Honest weaknesses, limitations, missing features.]
## Recommendation
Choose Option A if... Choose Option B if...
## Sources and verification
[How you verified the information. Date of last check.]
What to avoid
- Superlatives without evidence. "The best" or "the most powerful" without context is not useful. If you make a claim, back it with a specific feature or scenario.
- Ignoring the competitor's strengths. If Option B is better at something, say so. It makes your eventual recommendation more credible.
- Stale pricing. If you list prices, check them. AI assistants may quote outdated numbers, which hurts your credibility and the user's trust.
- Hidden bias. If you work for one of the options, disclose it. A disclosure does not disqualify the page, but hiding it does.
How AI assistants decide what to quote
AI assistants use retrieval systems to find relevant pages. They look for passages that directly answer a comparison question. A criteria table, a clear "who it fits" section, and a dated weakness list are all easy to extract and quote. One-sided pages may still be retrieved, but they are less likely to be used as the primary source because they do not provide balanced information. The assistant's goal is to give a helpful answer, not to repeat marketing copy.
Make it easy to verify
Include a short section on how you verified the information. For example: "Pricing checked on [date] from the vendor's pricing page. Feature list from the vendor's documentation." This does not guarantee a quote, but it increases the chance that an assistant treats your page as reliable. If you use a tool like PromptRanking to track whether your brand is mentioned in AI answers, you can see which comparison pages get cited and which do not. That feedback loop helps you improve the structure over time.
Next step
Pick one comparison page you already have. Add a criteria table, a dated weakness section, and a "who it fits" paragraph for each option. Then check back in a week to see if AI assistants start quoting it. If not, look at the wording: make sure each section answers a specific question directly, without fluff. Keep the page updated, and treat it as a living reference, not a one-time post.