Comparison Page Builder

What it does

Comparison pages convert better than almost any other page type and they are the easiest to write badly, because the temptation is to win every row. A page that wins every row is not read as information. This skill writes comparisons where the competitor genuinely wins some rows, every claim is dated and sourced, and the recommendation is conditional on the reader's situation.

When to use it

• write a versus page
• alternatives page
• comparison content
• rank for competitor queries
• compare us to a competitor

What it needs from you

• us: your product with its real limits
• them: the competitor and what they are genuinely good at
• reader: who is searching this and what decision they are making

How it works

1. Build the comparison table from what the reader decides on, not from your feature list. Features you have and they do not are only relevant if the reader cares.
2. Give the competitor the rows they win, plainly. A page where the competitor wins nothing is read as marketing and bounces.
3. Date and source every factual claim about the competitor. Pricing and features change and an out of date claim is both a trust problem and a legal one.
4. Do not compare against a competitor's deprecated behavior or a plan they no longer sell.
5. Write the conditional recommendation: who should pick them, and who should pick you. The first half is what makes the second half credible.
6. Add the migration or evaluation next step, because the reader on this page is close to a decision.
7. Set a review date on the page and put it in the content, since a comparison page is a maintenance commitment.

What you get back

The comparison table with sources and dates, the honest wins on both sides, the conditional recommendation, the next step, and the review date.

The quality bar

• The competitor wins at least one row and it is a row readers care about
• Every competitor claim carries a source and a date
• The recommendation is conditional on the reader's situation
• A review date appears in the published content

Where it runs

• Claude Code
• Codex CLI
• Cursor
• MCP-compatible agents