← ClaudeAtlas

comparisonlisted

Generate a head-to-head comparison page ("[Site] vs [Competitor]" or "[Product A] vs [Product B]") for a chosen managed site. Captures decision-stage searchers comparing the site against a named alternative. Picks the comparison from `service-keywords.csv` (rows with intent=`comparison`) or user input, runs SERP analysis on top 3 comparison pages, builds a feature-by-feature comparison table, balances honesty (real limitations) with conversion (clear differentiators), satisfies Tier 1 on-page SEO, and ships per the site's publishing method. Use when the user types `/comparison` or asks for a "vs" page.
mkreindel/seo-toolkit-template · ★ 0 · AI & Automation · score 70
Install: claude install-skill mkreindel/seo-toolkit-template
# `/comparison` — Head-to-head comparison page generator Creates a decision-stage comparison page. Comparison search intent is the highest-conversion intent on the web — searchers are pre-qualified, already evaluating named options, and ready to choose. This skill captures that traffic without sounding like a hatchet job (one-sided comparisons rank poorly and convert worse). ## Inputs Required (asked at start if not given): - **Site** — must match a folder under `sites/[name]/`. - **Comparison target** — either a primary keyword (`site-a vs accenture ai consulting`) or `{competitor}` slug. The skill picks from `service-keywords.csv` rows with intent=`comparison` if not supplied. Optional (per-run overrides): - **Competitor data source** — defaults to web research; override to a supplied dossier file in `_research/competitors/{slug}.md`. - **Stance** — `balanced` (default — honest pros/cons both sides) | `differentiator-led` (lead with our edge, still honest about limitations). Never `hatchet` — refused. ## Workflow This skill follows `/service`'s workflow (Steps 0–11) with the page-type-specific differences listed below. Read `.claude/skills/service/SKILL.md` end-to-end before running. ### What's unique to `/comparison` **Step 2 — Keyword selection:** pick from `service-keywords.csv` rows where `intent=comparison`, or accept user-supplied keyword. Validate via SERP comparison test (`SEO_GUIDE.md` Section 2.4) — comparison pages must compare exactly the two named entit