Comparison pages

A comparison page is the fastest-decaying page on any site. Everything on it describes a product somebody else controls, and they ship without telling you. A page that was accurate in March and unreviewed in September is not neutral — it is a page of confident, checkable errors with your name on it.

That is why every claim here carries the date it was verified, and why this category has the strictest gate in the system.

The operational shape

Trigger. A competitor move — pricing, positioning, or a launch — or a competitor showing up repeatedly in lost deals. Not a content calendar.

Reads. Battlecards and verified competitor files from the market map. Positioning and the wedge from decisions.

Cadence. Per competitor, and maintained. This is the distinction that matters: a comparison page is not published, it is kept.

Gate. The strictest in the system. Public claims about a named competitor sit behind a named human, without exception.

What good looks like

It names what they do better, first. Before anything else, and without hedging. A reader arrives already suspecting the page is rigged; the fastest way to lose them is to confirm it in the first screen. The page that says "they are genuinely better at X" buys the right to be believed about everything after it.

Every claim is verified at source. Not from a listicle, not from a review site, and not from the competitor's own comparison page. On the vendor's site, on a dated visit, recorded. Secondary sources are how a wrong price ends up on a page for a year.

It answers "when should you choose them." Honestly, with a real segment. A comparison page with no such section is asserting that one product wins for everyone, which no reader believes and no buyer has ever found to be true.

It compares on architecture, not on feature counts. A checklist comparison invites a checklist response, and whoever has more rows wins a game neither of you should be playing. Compare on what the products fundamentally do differently, because that is the part a competitor cannot ship their way out of by Friday.

It survives the competitor reading it. That is the real standard. If their team would call a sentence unfair, a prospect who talks to them will hear about it.

When it goes stale

Faster than anything else on the site, and in four ways.

They shipped — the limitation the page rests on no longer exists. They repriced — the number is wrong, and pricing is the most-checked claim on the page. They repositioned — the comparison is now against a product that no longer describes itself that way. And you moved, so the page argues a wedge that is narrower or wider than the current one.

The third is the one that catches teams out. A competitor changing what they say they are invalidates a comparison as thoroughly as changing what they do, and it leaves no trace in a changelog.

What it feeds

• Battlecards — the same verified facts, arranged for a conversation instead of a page
• Alternatives pages — a different reader on the same research
• Sales conversations — the comparison-ender, which is a sentence rather than a table

The dependency runs the other way too: a comparison page cannot ship ahead of a verified competitor file. A page whose claims have no owner is the definition of a claim that should not be public.

Where ContentOS fits

As of September 2026 this capability is in build, and it is the one slice of the convince category in the first phase. The verification requirement is enforced in code rather than by convention: a comparison page cannot leave draft while its competitor file is unverified, and the build fails with the vendor URL that needs checking.