# Comparison Page Playbook

Build comparison pages that help buyers decide, strengthen trust, and create real retrieval value instead of looking like thin attack copy.

## Comparison Intent

Not all comparison pages deserve to exist.

Publish one when at least one of these is true:

- buyers repeatedly ask how you compare with a specific alternative
- a competitor has become the default reference point in your niche
- you need a clear explanation of model differences, not just brand preference
- the comparison helps a buyer choose faster with less confusion

Do not publish one if the only goal is to name-drop a competitor without offering real decision help.

## Decision Frames

Most comparison intent falls into one of four frames:

1. `Category comparison`
   Example: AI receptionist vs answering service
2. `Vendor comparison`
   Example: The Quiet Protocol vs Smith.ai
3. `Model comparison`
   Example: managed front-door system vs self-serve SaaS
4. `Timing comparison`
   Example: fix internal intake first vs buy more traffic first

Choose one frame per page. Mixed frames usually create muddy copy.

## Scorecard Structure

A useful comparison page needs criteria before claims.

Use a scorecard with 4 to 7 dimensions such as:

- setup speed
- response quality
- customization depth
- reporting visibility
- operational ownership
- after-hours strength
- long-term scalability

For each dimension:

- state what matters
- describe the tradeoff honestly
- explain where each option is stronger or weaker
- avoid fake precision if evidence is directional rather than exact

## Comparison Writing Rules

- Lead with who each option is best for.
- Admit tradeoffs directly.
- Use plain language, not theatrical language.
- Back claims with visible proof, examples, or process detail.
- Keep the page useful even if the reader does not choose you.

## Page Modules

Recommended page structure:

### 1. Buyer-fit opener

Explain who the comparison is for and what decision they are trying to make.

### 2. Fast verdict

Give the short answer up front:

- who should choose option A
- who should choose option B
- where the decision usually turns

### 3. Scorecard

Use a dimension-by-dimension table or card grid.

### 4. Operational difference

Explain the real workflow difference, not just the feature list.

### 5. Proof and caveats

Use process detail, examples, screenshots, or service expectations.

### 6. Next step

Offer the right diagnostic, calculator, or booking path.

## Proof Sources

Pull supporting material from:

- customer objections
- onboarding notes
- lost-deal reviews
- implementation timelines
- support tickets
- product demos
- public positioning pages

If the page has no real source material, do not publish it yet.

## Honest Positioning Lines

Strong comparison copy often sounds like:

- “If you want X, the managed model is stronger because…”
- “If cost minimization is the only priority, the lighter option may fit better.”
- “This is a worse fit when…”
- “The tradeoff is…”

That language signals maturity and makes the page easier to trust.

## Risks to Avoid

- fake objectivity
- anonymous attacks
- outdated feature claims
- keyword stuffing around competitor names
- writing that hides where you are weaker

## Refresh Rhythm

### Monthly

- review competitor page changes
- check whether the criteria still reflect real buyer questions
- update screenshots, positioning, and pricing assumptions

### Quarterly

- rerun the scorecard
- review whether the page is still converting or just generating noise
- add fresh proof and better caveats where needed

## 30-Day Rollout

### Week 1

- identify the top 3 comparison intents
- pick one with the strongest buyer value

### Week 2

- define criteria
- gather proof and tradeoff notes

### Week 3

- draft the page
- validate the scorecard with someone operational, not just marketing

### Week 4

- publish
- link the page to relevant calculators, FAQs, and booking paths