A comparison page stops lying the moment it does three things: it picks one intent instead of two, it names at least one place where the competitor is genuinely better, and it only makes claims it can still defend if a reader checks them the same day. Most comparison pages fail at the first step – they try to serve “X vs Y” and “X alternatives” on the same URL, which are different searches with different readers behind them. We publish one comparison page ourselves, and we wrote it against that exact rule before writing this one.
Why this channel fits (or doesn’t) at this stage
Comparison pages assume something most early-stage products don’t have yet: a reader who already knows the category well enough to be choosing between two or more named tools. That’s a late-funnel search. If nobody is typing your product’s name next to a competitor’s, a comparison page has no query to answer – it’s not that the page is bad, it’s that the demand it depends on doesn’t exist yet.
We can say this plainly because we’re tracking it on our own site. As of our most recent Search Console pull, we have 75 distinct queries across 24 pages, and every one of them sits at zero clicks after four months of daily publishing. None of those queries are “our product vs” anything – they’re early-stage, direct-question searches, the kind a pre-revenue SaaS site actually earns first. A comparison page written before that stage is reached is a bet on demand that hasn’t shown up in the data yet, not a bet grounded in it.
So the honest fit test is simple: write a comparison page once you can point to evidence that people search your name next to a named rival – a sales call where a prospect mentions the competitor, a support ticket asking “how is this different from X,” or a query showing up in Search Console with a competitor’s name in it. Write it before that evidence exists and you’re guessing at intent instead of answering it, which is exactly the kind of claim this page is arguing against making.
The concrete play
Once the intent evidence exists, the play is to pick one of two shapes and stay inside it for that URL. A “vs” page answers a reader who already knows both tools and wants a decision – put both names in the title, the URL, and the first paragraph, and structure the body as a direct comparison against named criteria, not a tour of features in isolation. An “alternatives” page answers a different reader – someone leaving a specific named tool who wants a shortlist, not a single rival – and it should read like a list with a clear reason each entry made the cut, not a disguised pitch for one option.
We published exactly one of these ourselves – a “vs” page comparing an AI SEO agent to a traditional SEO automation tool – and held it to the same rule we’re describing here: one intent, one comparison, no attempt to also serve the “alternatives” reader on the same URL. Mixing the two is the single most common way these pages quietly lie – not with a false claim, but with a structure that promises a decision and delivers a vague overview instead, or promises a shortlist and delivers a one-sided pitch.
The credibility test that matters more than any keyword placement is whether the page names a real place the competitor wins. A comparison page that scores every category in the writer’s own favor reads as marketing copy, and both readers and search engines increasingly treat that pattern as low-trust. Naming one genuine strength of the competitor – a feature they ship that you don’t, a price point that’s lower for a specific use case, a workflow they handle better – costs almost nothing to admit and is usually the sentence that makes the rest of the page believable.
What the body should actually contain
Structure matters as much as the decision to write the page at all. A “vs” page should open with a short, direct verdict in the first two sentences – which tool wins for which kind of buyer – because the reader arrived already knowing the category and wants the answer before the reasoning. Bury that verdict under three paragraphs of scene-setting and the reader either leaves or skims past the part that actually persuades them.
After the verdict, a comparison table against named criteria does more work than prose ever will: pricing tiers, the integrations that matter to your actual buyer, support response time if you can state it honestly, and the one or two features that decide most real purchase conversations. Each row should be a claim you could screenshot and defend, not a vague adjective like “more powerful” – a reader comparing tools is comparing specifics, and a table that hedges reads as evasive rather than confident.
Below the table, give each criterion its own short section instead of compressing everything into table cells. This is where the genuine competitor strength belongs – not as a throwaway line, but as its own paragraph with enough detail that a skeptical reader believes you actually used both products. A table row that says “support: faster” next to a paragraph explaining exactly how the competitor’s support model works for a specific use case is far more convincing than a bare table, because it shows the writer understands the alternative well enough to be trusted on the comparison overall.
Sequencing: what first, what later
Comparison and alternatives pages belong at the edge of a keyword portfolio, not at its center, which makes sequencing mostly a question of what to build around them first. A workable order:
- Build the direct-answer cluster for your core capability first – the pages that explain what the product does and solve a specific problem on their own, independent of any competitor’s name. This is the same cluster-first sequencing we describe in how to structure a B2B SaaS keyword portfolio, and comparison pages should sit downstream of it, not substitute for it.
- Write the single “vs” page for the competitor your prospects mention most often in sales conversations, once that pattern is consistent rather than a one-off remark. One well-evidenced comparison page beats five speculative ones.
- Hold off on an “alternatives” page until there’s a specific, named tool your prospects are actively trying to leave – not a general “best tools in this category” list, which competes with every other listicle on the same broad query and rarely earns the trust a named-exit page does.
- Keep exactly one canonical URL per comparison decision. If a second page starts targeting the same “X vs Y” pair, merge it into the first rather than letting both compete for the same query – that’s cannibalization, and it weakens both pages instead of strengthening either.
Measurement and kill criteria
Measure a comparison page the same way we measure every page on this site: against Search Console data for the specific query terms it was built to answer, not against a generic traffic number. A comparison page is working if it starts showing impressions for queries that contain both named products, or the competitor’s name specifically – that’s the signal the intent evidence was correct. It’s failing if it shows impressions only for generic, unrelated terms, which usually means the page is ranking for the wrong reason and will not convert the reader it was actually built for.
The kill rule we’re applying to this page is the same one we apply everywhere: if, 60 days after publish, this URL has zero GSC impressions for any query containing “SaaS comparison pages” or close variants, despite being indexed, the premise was wrong and the page should be revised or folded into a broader piece rather than left standing as evidence of a channel that didn’t pan out. We’d rather state that threshold now, while it’s falsifiable, than quietly stop mentioning the page if the number doesn’t move.









