Create High-Ranking Competitor Comparison Pages

Provides a structured methodology for building competitor comparison and "alternative" landing pages that both rank for competitive search terms and genuinely help evaluators decide. It defines four page formats - "[Competitor] Alternative" (singular, for users actively switching), "[Competitor] Alternatives" (plural roundup for earlier-stage researchers, recommending 4-7 real alternatives), "You vs [Competitor]" (direct head-to-head), and "[Competitor A] vs [Competitor B]" (capturing traffic for comparisons that don't mention you, then introducing yourself as a third option) - each with its own URL pattern, target keywords, page-section outline, and tone guidance. It also specifies three index/hub pages (Alternatives, Alternatives-plural, and Vs Comparisons) for navigation and SEO consolidation, and a content architecture built on a centralized per-competitor data file - a YAML profile with pricing, feature ratings, strengths, weaknesses, best-for/not-ideal-for lists, common complaints, and migration notes - so updating one fact, like a competitor's price, propagates to every page that cites it.

Use it when building a set of comparison or alternative pages for SEO and sales enablement - capturing "[Competitor] alternative" or "[You] vs [Competitor]" search traffic while helping evaluators choose. It runs on four core principles: honesty (acknowledge competitor strengths, don't misrepresent their features, since readers verify claims), depth over feature checklists, helping the reader decide (be explicit about who each product suits), and centralizing competitor data to avoid duplicated research. It is a content and information-architecture methodology, not a page builder or CMS - it assumes you will do the underlying competitor research yourself (trials, pricing checks, review mining on G2/Capterra/TrustRadius, customer interviews) and refresh it on a quarterly cadence.

Input is a per-competitor YAML profile (name, pricing model and tier prices, feature ratings, strengths, weaknesses, best-for/not-ideal-for lists, common complaints mined from reviews, and migration difficulty/data-export notes) plus the same profile for your own product. Output is page copy assembled from reusable section templates: a TL;DR summary, paragraph-style feature comparisons rather than bare checkmark tables, a pricing table with a "value comparison" narrative, a service/support comparison, "who should choose X" sections for both products, a migration section (what transfers versus what needs reconfiguration), and a social-proof section quoting customers who switched.

{
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the best alternative to [Competitor]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Your answer positioning yourself]"
      }
    }
  ]
}

Complements three related skills from the same collection: programmatic-seo for generating comparison pages at scale, copywriting for the page prose itself, and schema-markup for the FAQ/comparison structured data shown above; a fourth, seo-audit, is suggested for optimizing the pages once published.

Marketing, growth, and SEO teams building a competitor-comparison content hub who want a repeatable page architecture and a single source of truth for competitor facts, rather than one-off comparison pages that go stale and contradict each other.