seo-competitor-pages

Trigger phrases

Phrases that activate this skill when typed to Claude Code:

• comparison page
• vs page
• alternatives page
• competitor comparison
• X vs Y

What it does

seo-competitor-pages is a Claude Code skill from AgriciDaniel’s claude-seo repo. It generates the content architecture for four high-converting page types: direct “X vs Y” comparisons, “alternatives to X” roundups, “best category tools” listicles, and feature matrix comparison tables. Each format targets a distinct competitive-intent keyword pattern and comes with schema markup — Product + AggregateRating for product comparisons, SoftwareApplication for software, and ItemList for roundups.

The output includes a ready-to-implement page structure (COMPARISON-PAGE.md), schema JSON-LD (comparison-schema.json), a keyword strategy with long-tail opportunities, and conversion optimization guidance: CTA placement, social proof sections, pricing transparency, trust signal requirements, and fairness guidelines for presenting competitor data accurately.

When to use it

Reach for it when:

• You have a product and want to capture “your product vs competitor” and “alternatives to competitor” search traffic
• You are building a category roundup and need a structured content brief with schema markup baked in
• You have existing comparison pages that need a trust signal and CTA audit

When not to reach for it:

• The products being compared serve completely different markets — the skill will report no overlap and suggest pivoting to a category roundup format
• You lack current pricing and feature data; the skill flags missing information explicitly rather than filling gaps with guesses

Install

Copy the seo-competitor-pages SKILL.md into .claude/skills/seo-competitor-pages/.

Trigger phrases: “comparison page”, “vs page”, “alternatives page”, “competitor comparison”, “X vs Y”, “versus”, “compare competitors”, “alternative to”.

Invoke with /seo competitor-pages <url> to audit an existing page, or /seo competitor-pages generate <competitor> to build a new one from scratch.

What a session looks like

A typical session has three phases:

1. Page type selection and keyword targeting. The skill identifies which comparison format fits the target keyword (head-to-head vs alternatives roundup vs category ranking), selects title tag formula and primary keyword, and maps secondary long-tail patterns like “X vs Y pricing” and “X vs Y for [use case]”.
2. Feature matrix and content outline. A comparison table is built with data accuracy requirements: all pricing must include an “as of [date]” note, all feature claims must be verifiable from public sources, and missing data points are explicitly flagged as “Not publicly available” rather than guessed.
3. Schema and conversion layer. JSON-LD for Product, SoftwareApplication, or ItemList is generated. CTA placement guidance is specific: above fold, after the comparison table, and at page bottom — with a note that aggressive CTAs placed inside competitor descriptions reduce trust and conversion.

Receipts

Works well: The fairness guidelines section is genuinely useful — it enforces “as of [date]” disclaimers on pricing and the “disclose your own product affiliation” requirement that most comparison pages skip. Pages that follow these guidelines tend to build more trust than the typical self-serving competitor teardown.

Backfires: If competitor pricing is behind a paywall or has changed recently, the skill flags the gap rather than guessing — which means the research burden lands on you before the page can ship.

Pattern that works: Use “X vs Y” for branded searches (both product names in the query) and “alternatives to X” for dissatisfied-user searches (someone looking to leave a specific tool). They attract different intent and need different page structures.

Source and attribution

Originally written by AgriciDaniel. The canonical SKILL.md and supporting files live in the seo-competitor-pages folder of the claude-seo repository.

License: MIT. Install, adapt, and redistribute with attribution preserved.

This page documents the skill from a practitioner’s perspective. For the formal spec and updates, defer to the source repo.