Catalog
coreyhaines31/competitor-alternatives

coreyhaines31

competitor-alternatives

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.

global
version:1.1.0
0installs0uses~2.1k
v1.1Saved Apr 20, 2026

Competitor & Alternative Pages

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.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md 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:

  1. Your Product

    • Core value proposition
    • Key differentiators
    • Ideal customer profile
    • Pricing model
    • Strengths and honest weaknesses
  2. Competitive Landscape

    • Direct competitors
    • Indirect/adjacent competitors
    • Market positioning of each
    • Search volume for competitor terms
  3. Goals

    • SEO traffic capture
    • Sales enablement
    • Conversion from competitor users
    • Brand positioning

Core Principles

1. Honesty Builds Trust

  • Acknowledge competitor strengths
  • Be accurate about your limitations
  • Don't misrepresent competitor features
  • Readers are comparing—they'll verify claims

2. Depth Over Surface

  • Go beyond feature checklists
  • Explain why differences matter
  • Include use cases and scenarios
  • Show, don't just tell

3. Help Them Decide

  • Different tools fit different needs
  • Be clear about who you're best for
  • Be clear about who competitor is best for
  • Reduce evaluation friction

4. Modular Content Architecture

  • Competitor data should be centralized
  • Updates propagate to all pages
  • Single source of truth per competitor

Page Formats

Format 1: [Competitor] Alternative (Singular)

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:

  1. Why people look for alternatives (validate their pain)
  2. Summary: You as the alternative (quick positioning)
  3. Detailed comparison (features, service, pricing)
  4. Who should switch (and who shouldn't)
  5. Migration path
  6. Social proof from switchers
  7. CTA

Format 2: [Competitor] Alternatives (Plural)

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:

  1. Why people look for alternatives (common pain points)
  2. What to look for in an alternative (criteria framework)
  3. List of alternatives (you first, but include real options)
  4. Comparison table (summary)
  5. Detailed breakdown of each alternative
  6. Recommendation by use case
  7. CTA

Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.


Format 3: You vs [Competitor]

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:

  1. TL;DR summary (key differences in 2-3 sentences)
  2. At-a-glance comparison table
  3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)
  4. Who [You] is best for
  5. Who [Competitor] is best for (be honest)
  6. What customers say (testimonials from switchers)
  7. Migration support
  8. CTA

Format 4: [Competitor A] vs [Competitor B]

Search intent: User comparing two competitors (not you directly)

URL pattern: /compare/[competitor-a]-vs-[competitor-b]

Page structure:

  1. Overview of both products
  2. Comparison by category
  3. Who each is best for
  4. The third option (introduce yourself)
  5. Comparison table (all three)
  6. CTA

Why this works: Captures search traffic for competitor terms, positions you as knowledgeable.


Essential Sections

TL;DR Summary

Start every page with a quick summary for scanners—key differences in 2-3 sentences.

Paragraph Comparisons

Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.

Feature Comparison

For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.

Pricing Comparison

Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.

Who It's For

Be explicit about ideal customer for each option. Honest recommendations build trust.

Migration Section

Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.

For detailed templates: See references/templates.md


Content Architecture

Centralized Competitor Data

Create a single source of truth for each competitor with:

  • Positioning and target audience
  • Pricing (all tiers)
  • Feature ratings
  • Strengths and weaknesses
  • Best for / not ideal for
  • Common complaints (from reviews)
  • Migration notes

For data structure and examples: See references/content-architecture.md


Research Process

Deep Competitor Research

For each competitor, gather:

  1. Product research: Sign up, use it, document features/UX/limitations
  2. Pricing research: Current pricing, what's included, hidden costs
  3. Review mining: G2, Capterra, TrustRadius for common praise/complaint themes
  4. Customer feedback: Talk to customers who switched (both directions)
  5. Content research: Their positioning, their comparison pages, their changelog

Ongoing Updates

  • Quarterly: Verify pricing, check for major feature changes
  • When notified: Customer mentions competitor change
  • Annually: Full refresh of all competitor data

SEO Considerations

Keyword Targeting

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]

Internal Linking

  • Link between related competitor pages
  • Link from feature pages to relevant comparisons
  • Create hub page linking to all competitor content

Schema Markup

Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"


Output Format

Competitor Data File

Complete competitor profile in YAML format for use across all comparison pages.

Page Content

For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.

Page Set Plan

Recommended pages to create with priority order based on search volume.


Task-Specific Questions

  1. What are common reasons people switch to you?
  2. Do you have customer quotes about switching?
  3. What's your pricing vs. competitors?
  4. Do you offer migration support?

  • programmatic-seo: For building competitor pages at scale
  • copywriting: For writing compelling comparison copy
  • seo-audit: For optimizing competitor pages
  • schema-markup: For FAQ and comparison schema
  • sales-enablement: For internal sales collateral, decks, and objection docs
Files4
4 files · 20.3 KB

Select a file to preview

Overall Score

86/100

Grade

A

Excellent

Safety

88

Quality

88

Clarity

87

Completeness

82

Summary

This skill guides AI agents in creating competitor comparison and alternative pages for SEO and sales enablement. It provides four page formats (singular alternative, plural alternatives, you vs competitor, competitor vs competitor), core principles for honest positioning, research processes, and content architecture patterns. The skill emphasizes centralized competitor data, modular content architecture, and honest differentiation to build trust with evaluators.

Detected Capabilities

Page format selection and structure guidance (4 formats with distinct use cases)SEO keyword targeting strategy for competitive search termsCompetitor research methodology (pricing, features, reviews, customer feedback)Centralized competitor data architecture and maintenance approachContent modularization for scalable multi-page hubsPricing comparison methodology including hidden costs and TCO calculationInternal linking and site architecture for comparison contentMigration path documentation from competitor productsSocial proof integration and switcher testimonialsSchema markup recommendations (FAQ schema for comparisons)

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

competitor comparison pagealternative product pagesvs pagebattle cardcompetitive positioningSEO competitor contentcomparison hub

Risk Signals

INFO

Skill instructs creation of comparison content that positions competitor products against user's product

Core Principles, Page Formats sections
INFO

References to competitor data gathering including pricing, review mining, and customer feedback collection

Research Process section
INFO

Instruction to defer internal sales enablement tasks to separate 'sales-enablement' skill

Eval 6, Related Skills section

Use Cases

  • Create a 'Best Asana Alternatives' page targeting small teams who want simpler, cheaper project management
  • Build a 'HubSpot vs Salesforce' comparison page positioning your product for SMB sales teams
  • Develop a 'Mailchimp Alternative' page for e-commerce brands seeking better email marketing features
  • Create objective third-party 'Notion vs Coda' comparison for content aggregation or review sites
  • Structure a multi-page competitor comparison hub with 5+ alternative pages and head-to-head comparisons
  • Build internal sales battle cards and competitive objection handling materials

Quality Notes

  • Strong structure with clear section hierarchy and practical page format definitions (4 distinct formats with URL patterns, target keywords, and complete page structures)
  • Explicit core principles (honesty, depth, helping readers decide) set ethical guardrails for comparison content
  • Comprehensive templates and content architecture guidance in supporting files enable agents to execute at scale
  • Well-defined research process with quarterly update cadence provides practical maintenance guidance
  • Excellent use of examples and tables (feature comparison table, pricing comparison, keyword targeting table) makes instructions concrete and actionable
  • Clear internal linking strategy and SEO considerations demonstrate advanced content strategy thinking
  • Supportive files are well-organized with ready-to-use templates (TL;DR, feature comparison, pricing section, migration section, social proof)
  • Evals in evals.json are comprehensive and test all four page formats plus hub-level strategy, with specific assertions for accuracy
  • Content architecture guidance (centralized competitor data as YAML) shows understanding of scalability and maintenance challenges
  • Honest treatment of limitations is emphasized throughout (e.g., 'be clear about who competitor is best for'), building trust rather than dismissing alternatives
  • Minor: No explicit guidance on when to avoid creating comparison pages (e.g., if competitor data is unavailable or market position is weak) — could add negative use cases
  • Minor: No mention of competitive intelligence ethics or potential legal considerations (e.g., false advertising, tortious interference) — could strengthen guardrails
Model: claude-haiku-4-5-20251001Analyzed: Apr 20, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.1

Content updated

2026-04-20

Latest
v1.0

No changelog

2026-04-19

Add coreyhaines31/competitor-alternatives to your library

Command Palette

Search for a command to run...