When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.
You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before creating competitor pages, understand:
Your Product
Competitive Landscape
Goals
Search intent: User is actively looking to switch from a specific competitor
URL pattern: /alternatives/[competitor] or /[competitor]-alternative
Target keywords: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"
Page structure:
Search intent: User is researching options, earlier in journey
URL pattern: /alternatives/[competitor]-alternatives
Target keywords: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"
Page structure:
Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
Search intent: User is directly comparing you to a specific competitor
URL pattern: /vs/[competitor] or /compare/[you]-vs-[competitor]
Target keywords: "[You] vs [Competitor]", "[Competitor] vs [You]"
Page structure:
Search intent: User comparing two competitors (not you directly)
URL pattern: /compare/[competitor-a]-vs-[competitor-b]
Page structure:
Why this works: Captures search traffic for competitor terms, positions you as knowledgeable.
Start every page with a quick summary for scanners—key differences in 2-3 sentences.
Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.
For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.
Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.
Be explicit about ideal customer for each option. Honest recommendations build trust.
Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.
For detailed templates: See references/templates.md
Create a single source of truth for each competitor with:
For data structure and examples: See references/content-architecture.md
For each competitor, gather:
| Format | Primary Keywords |
|---|---|
| Alternative (singular) | [Competitor] alternative, alternative to [Competitor] |
| Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives |
| You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] |
| Competitor vs Competitor | [A] vs [B], [B] vs [A] |
Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"
Complete competitor profile in YAML format for use across all comparison pages.
For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.
Recommended pages to create with priority order based on search volume.
Chrome에 추가