competitor-alternatives
npx machina-cli add skill eugenepyvovarov/mcpbundler-agent-skills-marketplace/competitor-alternatives --openclawCompetitor & 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 .claude/product-marketing-context.md exists, 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
- Core value proposition
- Key differentiators
- Ideal customer profile
- Pricing model
- Strengths and honest weaknesses
-
Competitive Landscape
- Direct competitors
- Indirect/adjacent competitors
- Market positioning of each
- Search volume for competitor terms
-
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:
- Why people look for alternatives (validate their pain)
- Summary: You as the alternative (quick positioning)
- Detailed comparison (features, service, pricing)
- Who should switch (and who shouldn't)
- Migration path
- Social proof from switchers
- 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:
- Why people look for alternatives (common pain points)
- What to look for in an alternative (criteria framework)
- List of alternatives (you first, but include real options)
- Comparison table (summary)
- Detailed breakdown of each alternative
- Recommendation by use case
- 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:
- TL;DR summary (key differences in 2-3 sentences)
- At-a-glance comparison table
- Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)
- Who [You] is best for
- Who [Competitor] is best for (be honest)
- What customers say (testimonials from switchers)
- Migration support
- 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:
- Overview of both products
- Comparison by category
- Who each is best for
- The third option (introduce yourself)
- Comparison table (all three)
- 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:
- Product research: Sign up, use it, document features/UX/limitations
- Pricing research: Current pricing, what's included, hidden costs
- Review mining: G2, Capterra, TrustRadius for common praise/complaint themes
- Customer feedback: Talk to customers who switched (both directions)
- 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
- What are common reasons people switch to you?
- Do you have customer quotes about switching?
- What's your pricing vs. competitors?
- Do you offer migration support?
Related Skills
- 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
Source
git clone https://github.com/eugenepyvovarov/mcpbundler-agent-skills-marketplace/blob/main/competitor-alternatives/SKILL.mdView on GitHub Overview
Design and optimize competitor comparison and alternative pages for SEO and sales enablement. It covers singular and plural formats, plus you-vs and competitor-vs layouts, anchored by deep research, modular content architecture, and varied sections beyond basic feature tables.
How This Skill Works
Start with your product context and competitive landscape, then centralize data into a single source of truth. Build modular content blocks (pain validation, positioning, detailed comparisons, migration paths, proofs) and render them into the four formats; updates propagate automatically across all pages.
When to Use It
- You need a singular [Competitor] Alternative page targeting terms like '[Competitor] alternative' or 'alternative to [Competitor]'.
- You want a hub of [Competitor] Alternatives with 4-7 real options and a comparison framework.
- You are directly comparing your product to a competitor (You vs [Competitor]).
- You want to surface a Competitor vs Competitor page to aid evaluation across vendors.
- You require a modular, research-driven page architecture with sections beyond feature tables for SEO and sales enablement.
Quick Start
- Step 1: Gather your product context, differentiators, pricing, and a list of direct/indirect competitors.
- Step 2: Create a centralized data model and reusable content blocks (pain, criteria, comparisons, proofs) for all formats.
- Step 3: Build the four formats, optimize target keywords, and enable automated updates from the source of truth.
Best Practices
- Honesty builds trust: acknowledge strengths and weaknesses, don't misrepresent competitors, and verify claims.
- Depth over surface: explain why differences matter with use cases and scenarios, not just feature lists.
- Help them decide: match formats to user intent and be clear about who each option is best for.
- Modular content architecture: centralize data so updates propagate automatically across all pages.
- Proof and appropriateness: include social proof, migration paths, and credible sources to support claims.
Example Use Cases
- Format 1 example: An Alternative page for Product A that validates pain, positions Product A as the alternative, and includes migration steps and a CTA.
- Format 2 example: A hub page 'Product A Alternatives' listing 4-7 real options with criteria, a summary table, and detailed breakdowns.
- Format 3 example: A 'Product A vs Product B' page with TL;DR, at-a-glance table, and category-by-category comparison (Features, Pricing, Use Cases).
- Format 4 example: A 'Product B vs Product A' page that contrasts strengths, weaknesses, and ideal use cases for each side.
- Format 5 example: A multi-vendor competitive landscape page that centralizes data about several competitors and surfaces actionable insights.
