How to write fair competitor comparison pages

A competitor comparison page puts your product next to one alternative ("Us vs Them") so people searching for that competitor, or choosing between the two, land on a page that answers the question. It works when buyers shortlist products by name. It fails when the page is a sales pitch with a table attached.

How to do it

1. Pick competitors from evidence. Look in Search Console and your keyword tool for "alternative to" and "vs" searches that name your competitors, and ask on sales calls which other products the buyer looked at.
2. Open with a short verdict: who each product suits. Then give a side-by-side table of what buyers actually ask about (price, key features, limits, integrations, support), then migration steps and an FAQ.
3. Take every competitor fact from their own public pages, and put the date you checked on yours. Set a calendar reminder to recheck.
4. Say where the competitor is better. If a segment of buyers should choose them, name it.
5. Link each comparison from the relevant product page and from a "compare" hub, and link the hub from your footer.
6. Have someone read the claims before publishing, since you are making statements about a named company.

For the SEO side of this, see long-tail keyword landing pages: each comparison targets one specific search.

Examples

Plausible vs Google Analytics. The page has a table comparing the two on eight rows (including cookie banner requirement, ad-blocker blocking and open source status). It also has a section on where GA4 is stronger, with lines such as "GA4, especially with BigQuery, has more depth" and a note that the tight integration between GA4 and Google's ad products is hard to replicate elsewhere.

Shopify vs WooCommerce. Shopify's page leads with four reasons to choose it, backs them with customer quotes and analyst mentions, and ends with an FAQ and migration partners. It does not say when WooCommerce is the better fit, and it has no page-level last-updated date.

Ahrefs vs Semrush. Ahrefs dates one table on its page ("Data supplied as of July, 2026") while other figures on it carry no date. Dating each figure is the habit worth copying.

When it backfires

• Wrong or stale claims. The FTC's policy on comparative advertising encourages naming competitors and supports comparisons "where the bases of comparision are clearly identified", but requires "clarity, and, if necessary, disclosure to avoid deception of the consumer". A price or feature that changed last month is a deceptive claim today. This is not legal advice.
• One-sided pages. A table where you win every row and the competitor never does is easy for a buyer to spot, and they will check the competitor's own site next.
• Maintenance. Ten comparison pages mean ten sets of competitor facts to keep current. Start with the two or three competitors that come up most.
• Thin variants. Do not clone one page across competitors with only the names swapped. Google's doorway abuse policy covers creating substantially similar pages to rank for similar queries.

Questions people ask

Should I create "alternative to" pages for competitors? If people search "alternative to" plus a competitor name and you can fairly describe who your product suits better, yes. One page per competitor is easier to keep accurate than a single roundup.

How do comparison pages affect organic conversions? There is no public number that applies to every company. Track sign-ups that start on those pages in your analytics and compare them with your other landing pages.

What goes on a competitor comparison landing page? A verdict, a table of the things buyers ask about, pricing with a date, who each product is for, and how to switch.

Sources

• Plausible: Plausible vs Google Analytics, read Oct 8, 2026
• Shopify: Shopify vs WooCommerce, read Oct 8, 2026
• Ahrefs: Ahrefs vs Semrush, read Oct 8, 2026
• FTC policy statement on comparative advertising (16 CFR 14.15), read Oct 8, 2026
• Google Search spam policies, read Oct 8, 2026