Write a Comparison Page Buyers Trust

Comparison pages written by the vendor almost always win their own comparison, which readers spot immediately and which invites competitor complaints and platform takedowns. Aiming instead for scrupulous neutrality fails differently, producing a feature table that helps nobody decide. What works is a stated method, an explicit recommendation, and at least one case where you say a competitor is the better answer, because a page that concedes nothing is not read as information. Whether vendors should publish these at all is argued both ways in the industry; if you do, the honesty has to be structural rather than a disclaimer.

The skill file

---
name: comparison-page-without-the-sales-pitch
description: Use when writing a versus, alternatives or best-of page that puts your own product alongside competitors.
---

# Write a Comparison Page Buyers Trust

Comparison pages written by the vendor almost always win their own comparison, which readers spot immediately and which invites competitor complaints and platform takedowns. Aiming instead for scrupulous neutrality fails differently, producing a feature table that helps nobody decide. What works is a stated method, an explicit recommendation, and at least one case where you say a competitor is the better answer, because a page that concedes nothing is not read as information. Whether vendors should publish these at all is argued both ways in the industry; if you do, the honesty has to be structural rather than a disclaimer.

## What you need first

- the competitor set your buyers actually shortlist, taken from sales calls or lost-deal notes rather than from search volume
- current competitor pricing and features read from their own live pages, with the date noted
- an honest list of the segments where you lose
- a review or sign-off route if your sector restricts comparative claims

## Method

1. State the evaluation method and who the page is for in the opening section. Without a stated basis every judgement below it reads as preference.
2. Take each competitor claim from their own live pricing or documentation page and record the URL and the date you read it. Facts lifted from third-party roundups are usually months stale and are what draws the complaint.
3. Name at least one buyer type for whom a competitor is the right answer, specifically. A vague concession costs nothing and buys nothing.
4. Give the recommendation as conditions rather than a winner: choose this if you need X, choose that if you need Y. Conditional advice survives a competitor shipping a feature next month.
5. Hold the comparison table to the criteria that decide the purchase, usually five to eight rows. Long tables exist to accumulate ticks and readers discount them accordingly.
6. Disclose authorship plainly near the top rather than in a footer. A reader who discovers the bias for themselves discounts the entire page.
7. Diarise a review date and recheck every competitor claim on it. Comparison pages rot faster than any other content type, and a wrong price is the quickest route to a legal letter.

## What this produces

A comparison page with a stated method, dated competitor sources, conditional recommendations and a scheduled recheck date.

## Where this goes wrong

- Comparing against a competitor tier nobody buys, which is transparent and discredits the rest of the page
- Citing competitor limitations fixed two releases ago, which is both wrong and the most common trigger for a complaint
- Building the page around search volume for versus queries rather than the shortlist real buyers hold, so it ranks for comparisons your buyers never make

---

From the QuQi skill library - https://www.quqi.io/skills/comparison-page-without-the-sales-pitch

What you need first

• the competitor set your buyers actually shortlist, taken from sales calls or lost-deal notes rather than from search volume
• current competitor pricing and features read from their own live pages, with the date noted
• an honest list of the segments where you lose
• a review or sign-off route if your sector restricts comparative claims

Method

1. 01 State the evaluation method and who the page is for in the opening section. Without a stated basis every judgement below it reads as preference.
2. 02 Take each competitor claim from their own live pricing or documentation page and record the URL and the date you read it. Facts lifted from third-party roundups are usually months stale and are what draws the complaint.
3. 03 Name at least one buyer type for whom a competitor is the right answer, specifically. A vague concession costs nothing and buys nothing.
4. 04 Give the recommendation as conditions rather than a winner: choose this if you need X, choose that if you need Y. Conditional advice survives a competitor shipping a feature next month.
5. 05 Hold the comparison table to the criteria that decide the purchase, usually five to eight rows. Long tables exist to accumulate ticks and readers discount them accordingly.
6. 06 Disclose authorship plainly near the top rather than in a footer. A reader who discovers the bias for themselves discounts the entire page.
7. 07 Diarise a review date and recheck every competitor claim on it. Comparison pages rot faster than any other content type, and a wrong price is the quickest route to a legal letter.

What this produces

A comparison page with a stated method, dated competitor sources, conditional recommendations and a scheduled recheck date.

Where this goes wrong

• Comparing against a competitor tier nobody buys, which is transparent and discredits the rest of the page
• Citing competitor limitations fixed two releases ago, which is both wrong and the most common trigger for a complaint
• Building the page around search volume for versus queries rather than the shortlist real buyers hold, so it ranks for comparisons your buyers never make

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Questions about this skill

More in Content production