comparison-pageslisted
Install: claude install-skill sitetiller/ai-visibility-skills
# Comparison pages that stay true
A comparison page is useful when a buyer can verify it. It earns trust (and avoids policy trouble) by showing what was checked, when, and where the author has a stake. The skill builds pages where every cell in the table has a source and a date, and rejects tactics that look like fake reviews or thin affiliate content.
## Inputs
- The product, the competitor(s), and the buyer question ("X vs Y", "alternatives to X").
- The user's own pricing and feature facts, and access to each competitor's public pricing, docs and changelog pages.
- Queries from `gsc` that the page should serve (see `content-brief`).
## Steps
1. Collect facts only from primary sources: the competitor's pricing page, documentation, terms, status or changelog pages, and the user's own product. Save each source URL with the access date. Take screenshots of pricing pages the day you read them.
2. Pick criteria that buyers decide on (price at stated usage, limits, integrations, support, security docs, data export). Take criteria from the queries and from the questions in `content-brief`, not from what flatters the product.
3. Build the table (format below). Every cell has a value and a source link. Where the competitor does not publish a fact, write "not published" and the date, never a guess.
4. Write the verdicts: who each product fits, and when not to choose yours. Include at least one case where the competitor is the better choice, if true. A page where the author always