Skip to content
SilktideHelp

Comparison pages

A comparison page is a page on your own website that compares your product against a named alternative, written openly in your own voice. You are the author, your name is on it, and you make the case for yourself with evidence.

Throughout this page, suppose you sell Fernwood, an expense-management product, and your closest competitor is Ledgerly. Your comparison page is "Fernwood vs Ledgerly" - published at fernwood.com, signed by you.

Why it works

People near a buying decision search for comparisons more than anything else. "Fernwood vs Ledgerly", "Ledgerly alternatives", "best expense management for nonprofits" - these are among the highest-intent queries that exist, and they are asked of AI assistants in exactly the same words they were once typed into Google.

When those questions get asked, something answers them. AI assistants lean heavily on whatever comparison content they can find - and most of what they find is affiliate listicles written by strangers with a commission structure you don't control. A comparison page on your own domain is your only guaranteed seat at that table:

  • It targets queries your competitor's brand name generates, which you can rank for legitimately because searchers genuinely want the comparison.
  • It gives AI assistants a citable, current, first-party source for claims about your product. Assistants routinely quote vendor comparison pages when they are specific and factual - and when yours does not exist, the assistant answers "Fernwood vs Ledgerly" from Ledgerly's page instead.
  • It converts. Visitors on a comparison page are late-funnel; this is where the decision happens.

Deciding what to build

Build the set of pages before you write the first one, because the set is what earns the queries:

  1. One page per named competitor you actually lose deals to. "Fernwood vs Ledgerly" is one page; "Fernwood vs Baseline" is another. A single page trying to cover five competitors ranks for none of them, because it can't match the specificity of the query.
  2. One "{Competitor} alternatives" page per major competitor - "Ledgerly alternatives" is a different query from "Fernwood vs Ledgerly", asked by someone earlier in their decision who may not know you exist. List real alternatives including yourself, and say who each suits.
  3. Optionally, one roundup - "Fernwood vs the alternatives" or "How Fernwood compares" - as a hub that links to every head-to-head page.

Where do you find the list? Your sales team knows who appears in deals. Search your own brand name plus "vs" in a search engine and an AI assistant and see what gets asked and who answers. If a competitor already has a "{They} vs Fernwood" page and you have nothing, that page is currently the internet's answer about you - start there.

Give the set a stable, predictable home, such as fernwood.com\/compare\/fernwood-vs-ledgerly. These URLs will be linked, cited, and updated for years; do not tie them to a blog date or a campaign.

Anatomy of the page

Structure each head-to-head page so the answer comes first and the evidence follows. This order exists because of how the page gets consumed: assistants and skimmers take the verdict, evaluators read the table, and buyers close to a decision read everything.

  1. The verdict, first. Two or three sentences at the top: who each product is best for, stated plainly. "Fernwood suits teams that need multi-entity expense approval; Ledgerly is stronger for solo bookkeepers who live in its accounting suite." This summary is what AI assistants most often quote - write it as the quote you want repeated.
  2. A disclosure of who is writing. One sentence, near the top: "This comparison is written by us, the makers of Fernwood. We think we win for the teams described below, and we'll be straight about where Ledgerly is stronger." First-party honesty consistently outperforms fake neutrality - humans and AI assistants both discount vendor pages that pretend not to be vendor pages, and both reward ones that don't.
  3. A comparison table. Feature by feature, priced tier by priced tier, with concrete values in every cell - numbers, limits, supported standards, yes/no. Tables are the most extractable structure on the page: assistants lift rows from them verbatim.
  4. Depth sections on the two or three differences that decide deals. Not every feature - the ones buyers actually switch over. For each: what Fernwood does, what Ledgerly does, and who should care. Screenshots of your own product are evidence; descriptions of theirs stay factual and sourced.
  5. An honest "when to choose Ledgerly" section. A comparison that finds no merit in the alternative reads as marketing and gets treated as marketing. Conceding two or three genuine strengths is what makes your remaining claims credible enough to quote.
  6. Pricing, stated concretely. Both products' published pricing, with the date you checked it. Pricing questions dominate comparison queries; a page that dodges them loses the query.
  7. Migration or switching notes, if you support them. "Moving from Ledgerly to Fernwood" answers the reader's very next question and is a query in its own right.

Writing rules

  • Every claim checkable. "More powerful reporting" is unquotable; "exports itemized reports across up to 40 subsidiary accounts" is a citation waiting to happen. If a claim cannot be verified by reading either product's public materials, cut it or ground it.
  • Source competitor claims from their published materials - their pricing page, their documentation, their changelog - and record where and when each fact came from. This is your correction trail when they change something, and your defense if they dispute something.
  • Write in your voice, not a review site's. Do not cosplay neutrality with phrases like "we tested both products for 30 days" unless you literally did. The disclosure already told the reader who you are; consistency with it is what keeps their trust.
  • Keep the tone one you could read aloud to the competitor. If a sentence would embarrass you in that reading, it is written wrong - not because of politeness, but because that sentence is the one that gets your page dismissed as attack marketing.

Technical checklist

The page has to be readable by the machines you want citing it:

  • Declare publication and update dates in metadata - see Machine-readable dates. Comparison content is exactly where freshness is weighed hardest: an assistant deciding whether to repeat your pricing table needs to know the page is current, and a page it cannot date loses to one it can. A visible "last checked" date next to the pricing figures reinforces the same promise to human readers.
  • Use structured data markup for what the page contains - at minimum the article dates above; FAQ markup if the page has a question-and-answer section.
  • Make the page fully readable without JavaScript - assistants' crawlers are less patient than browsers, and a comparison table that only renders client-side may as well not exist.
  • Title and headings that match the query. The page about Fernwood vs Ledgerly should be titled "Fernwood vs Ledgerly", not "Why teams are making the switch".
  • Link the set together - every head-to-head links the hub, the hub links every head-to-head - and link the pages from your pricing and product pages, where comparison-minded visitors already are.

Maintenance

A comparison page is a commitment, and a stale one is worse than none - a wrong claim about a competitor's pricing damages you more than it damages them:

  • Review on a schedule - quarterly at minimum, and immediately when either product ships or reprices something material.
  • Update the declared dateModified when the content genuinely changes - the honest update you never declared is a citation you never earned - and never bump it when nothing changed.
  • Watch what assistants say. Periodically ask the major AI assistants your target questions ("Fernwood vs Ledgerly", "best expense management for nonprofits") and see whether your page is cited and quoted accurately. That is the scoreboard.

Risks and limits

  • Keep competitor claims factual and sourced. Stating Ledgerly's published pricing or documented features is fine; speculating about their roadmap or misquoting their capabilities invites correction, ridicule, or legal letters. Comparative advertising built on verifiable facts is established practice in most jurisdictions - built on guesses, it is not.
  • Trademark care in paid channels. Publishing organic comparison content using a competitor's name is established practice. Bidding on their trademarked terms in ads is a separate, more contested practice - don't conflate the two.
  • Don't fake the verdict. If you genuinely lose a comparison for a given audience, say so and route those visitors to what you're best at. The concession costs you readers you were going to lose anyway, and buys credibility with the ones you can win.
  • Expect reciprocity. Publishing "Fernwood vs Ledgerly" invites Ledgerly to publish "Ledgerly vs Fernwood". That is fine - their honest page and yours can both exist - but it means your page must be one you are comfortable having read side by side with theirs.
Last updated

Was this page helpful?