Writing comparison and alternative pages that your competitors' customers trust

The best-converting page we have ever built for a client contained the sentence: “If your team is under fifteen people, honestly, use Notion instead — you will not get value from what we do until you have more process than that.”

That page converts at 11.2%. The client fought us on the sentence for three weeks.

Who is actually on these pages

Someone searching “[competitor] alternative” is not browsing. They have a contract, a renewal date, and a specific thing that is annoying them. They are three-quarters of the way through a decision that has already been made emotionally.

Someone searching “[A] vs [B]” is slightly earlier and more analytical. They have a shortlist of two and are looking for a reason to pick.

Someone searching “best [category] for [context]” is building the shortlist itself, and is the most persuadable of the three.

These are different states and a single page cannot serve all of them well, which is the argument for building comparison, alternative, and best-of pages as separate assets rather than one hybrid.

The structure

Answer first. The top of the page should contain, within the first hundred words, a plain statement of who should choose which. Not a paragraph about how choosing software is a big decision. The reader has one question and the page should answer it before they scroll.

Then the comparison table, and it needs to contain things that can be checked. Real pricing tiers with numbers. Whether SSO is on the base plan or costs extra. Data residency options. API rate limits. Support response times by tier. Vague comparisons — “flexible pricing” versus “rigid pricing” — read as marketing and get discounted entirely.

Then the differences that matter, in prose, three or four of them, each with a concrete example. “We handle multi-entity accounting; they do not” is fine. Better is “if you operate across three legal entities, their workaround is exporting to CSV and reconciling manually, which one of our customers estimated at six hours a month.”

Then the honest section, which I will come back to.

Then proof, specifically from someone who switched. A quote and a number. The migration story is more persuasive than any feature comparison because it addresses the actual objection, which is not “is your product better” but “is it worth the disruption.”

Then a next step calibrated to the reader’s state. On a comparison page, “book a demo” is asking for too much. A recorded product walkthrough, a migration guide, or an interactive comparison tool converts better because it keeps the reader in evaluation mode.

The honest section

Every client argues about this. The argument goes: why would we tell people to buy from a competitor.

Three reasons, and they are practical rather than moral.

The reader already suspects your page is biased, and every unqualified superlative confirms it. One genuine concession recalibrates how they read everything else on the page. This is the single largest lever on comparison page conversion in my experience, and it is not close.

The people you send away were not going to buy anyway, or would have churned in four months. A fifteen-person team on your enterprise product is a support burden and a bad case study.

And it is increasingly what gets your page cited by AI assistants, which are noticeably more likely to surface balanced comparisons than one-sided ones when summarising a category.

Make the concession specific and real. “They have a better mobile app” is only useful if it is true and if mobile matters to a segment of buyers. A fake concession about something nobody cares about is worse than none.

Where the lines are

You are making factual claims about a named competitor’s product in public, which is comparative advertising and it is legal in the US, UK, and EU within limits. The limits are broadly the same everywhere: claims must be accurate, verifiable, and not misleading, and you should not disparage.

Practically, that means:

Date every claim. “Pricing as of March 2026” protects you when they change it and it signals diligence to the reader.

Link to their source. If you say their base plan lacks SSO, link to the page on their site that says so. This is both defensible and, incidentally, a trust signal.

Update on a schedule. A comparison page with two-year-old pricing is inaccurate, and inaccurate comparative claims are the ones that generate letters. We review every comparison page quarterly.

Do not use their logo in a way that implies partnership, and check their trademark guidelines. Nominative use of a name in a comparison is generally fine; reproducing their brand assets is a different question.

Never quote a review out of context to make it look worse than it was.

Scaling this without producing sludge

If you have twelve relevant competitors, that is potentially twelve alternative pages, twelve versus pages, and some number of three-way comparisons. Tempting to template.

Do not, at least not below about thirty. Each of these pages needs someone to have genuinely used or seriously researched the competitor, and that does not template. We have watched a client publish sixty templated versus pages and get four indexed.

The workable approach is a shared structure with genuinely written content per page, produced at a rate of maybe two a week. Eight solid ones in a quarter beats sixty thin ones by an enormous margin, and you can see which patterns work before committing further.

Start with whichever competitors appear most often in your closed-lost reasons. Your CRM already knows the answer.