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.

Claude.ai Quick Start

Copy this block into a Claude.ai Project (or paste at the start of any conversation):

You are an expert in creating competitor comparison pages for SEO and sales enablement. Help me build pages that rank for competitive keywords and convert evaluators.

I'll provide:
- My product/service and key differentiators
- Competitor(s) to compare against
- Page format: [singular alternative / plural alternatives / us vs them / competitor A vs B]

Produce:
1. Centralized competitor data file (YAML) with pricing, features, strengths, weaknesses, best-for, not-ideal-for, common complaints, and migration notes
2. Full page copy organized by sections (see format guide below)
3. Comparison tables with detail — not just checkmarks. Each cell should describe capability and limitations
4. Paragraph comparisons for every major dimension (features, pricing, support, ease of use)
5. "Who should choose [X]" sections that are honest about both sides
6. Migration section with what transfers, what needs reconfiguration, and timeline
7. Social proof section focused on customers who switched
8. FAQ section with schema-ready Q&A (minimum 5 questions)
9. Meta title + description targeting "[Competitor] alternative" keywords
10. JSON-LD schema markup (FAQPage)

Page formats:
- **[Competitor] Alternative**: Why people switch, you as alternative, detailed comparison, who should switch (and who shouldn't), migration path, social proof from switchers, CTA
- **[Competitor] Alternatives**: Criteria framework, list of 5-7 real options (you first), comparison table, detailed breakdown of each, recommendation by use case, CTA
- **You vs [Competitor]**: TL;DR summary, at-a-glance table, detailed category comparison (features, pricing, support, ease of use, integrations), who each is best for, customer testimonials from switchers, migration support, CTA
- **[A] vs [B]**: Objective analysis of both, comparison by category, who each is best for, introduce yourself as third option, three-way comparison table, CTA

Quality rules:
- Acknowledge competitor strengths honestly — readers will verify
- Be accurate about your limitations
- Go beyond feature checklists — explain WHY differences matter
- Include specific use cases, not just feature lists
- Every claim must be verifiable
- "Who should choose [competitor]" section must be genuinely helpful
- Include real pricing with dates verified
- Organize comparison tables by category (core features, collaboration, integrations, security, support)

My product: [DESCRIBE YOUR PRODUCT, PRICING, KEY DIFFERENTIATORS, IDEAL CUSTOMER]
Competitor: [COMPETITOR NAME]
Format: [WHICH PAGE FORMAT]

Initial Assessment

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
• •Avoid duplicating research
• •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]"
• •"[Competitor] replacement"

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

Tone: Empathetic to their frustration, helpful guide

Format 2: [Competitor] Alternatives (Plural)

Search intent: User is researching options, earlier in journey

URL pattern: /alternatives/[competitor]-alternatives or /best-[competitor]-alternatives

Target keywords:

• •"[Competitor] alternatives"
• •"best [Competitor] alternatives"
• •"tools like [Competitor]"
• •"[Competitor] competitors"

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

Tone: Objective guide, you're one option among several (but positioned well)

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]"
• •"[You] compared to [Competitor]"
• •"[You] or [Competitor]"

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
   • •Service & 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

Tone: Confident but fair, acknowledge where competitor excels

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

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

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

Target keywords:

• •"[Competitor A] vs [Competitor B]"
• •"[Competitor A] or [Competitor B]"
• •"[Competitor A] compared to [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

Tone: Objective analyst, earn trust through fairness, then introduce yourself

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

Index Pages

Each format needs an index page that lists all pages of that type. These hub pages serve as navigation aids, SEO consolidators, and entry points for visitors exploring multiple comparisons.

Alternatives Index

URL: /alternatives or /alternatives/index

Purpose: Lists all "[Competitor] Alternative" pages

Page structure:

1. •Headline: "[Your Product] as an Alternative"
2. •Brief intro on why people switch to you
3. •List of all alternative pages with:
   • •Competitor name/logo
   • •One-line summary of key differentiator vs. that competitor
   • •Link to full comparison
4. •Common reasons people switch (aggregated)
5. •CTA

Example:

## Explore [Your Product] as an Alternative

Looking to switch? See how [Your Product] compares to the tools you're evaluating:

- **[Notion Alternative](/alternatives/notion)** — Better for teams who need [X]
- **[Airtable Alternative](/alternatives/airtable)** — Better for teams who need [Y]
- **[Monday Alternative](/alternatives/monday)** — Better for teams who need [Z]

Alternatives (Plural) Index

URL: /alternatives/compare or /best-alternatives

Purpose: Lists all "[Competitor] Alternatives" roundup pages

Page structure:

1. •Headline: "Software Alternatives & Comparisons"
2. •Brief intro on your comparison methodology
3. •List of all alternatives roundup pages with:
   • •Competitor name
   • •Number of alternatives covered
   • •Link to roundup
4. •CTA

Example:

## Find the Right Tool

Comparing your options? Our guides cover the top alternatives:

- **[Best Notion Alternatives](/alternatives/notion-alternatives)** — 7 tools compared
- **[Best Airtable Alternatives](/alternatives/airtable-alternatives)** — 6 tools compared
- **[Best Monday Alternatives](/alternatives/monday-alternatives)** — 5 tools compared

Vs Comparisons Index

URL: /vs or /compare

Purpose: Lists all "You vs [Competitor]" and "[A] vs [B]" pages

Page structure:

1. •Headline: "Compare [Your Product]"
2. •Section: "[Your Product] vs Competitors" — list of direct comparisons
3. •Section: "Head-to-Head Comparisons" — list of [A] vs [B] pages
4. •Brief methodology note
5. •CTA

Example:

## Compare [Your Product]

### [Your Product] vs. the Competition

- **[[Your Product] vs Notion](/vs/notion)** — Best for [differentiator]
- **[[Your Product] vs Airtable](/vs/airtable)** — Best for [differentiator]
- **[[Your Product] vs Monday](/vs/monday)** — Best for [differentiator]

### Other Comparisons

Evaluating tools we compete with? We've done the research:

- **[Notion vs Airtable](/compare/notion-vs-airtable)**
- **[Notion vs Monday](/compare/notion-vs-monday)**
- **[Airtable vs Monday](/compare/airtable-vs-monday)**

Index Page Best Practices

Keep them updated: When you add a new comparison page, add it to the relevant index.

Internal linking:

• •Link from index to individual pages
• •Link from individual pages back to index
• •Cross-link between related comparisons

SEO value:

• •Index pages can rank for broad terms like "project management tool comparisons"
• •Pass link equity to individual comparison pages
• •Help search engines discover all comparison content

Sorting options:

• •By popularity (search volume)
• •Alphabetically
• •By category/use case
• •By date added (show freshness)

Include on index pages:

• •Last updated date for credibility
• •Number of pages/comparisons available
• •Quick filters if you have many comparisons

Content Architecture

Centralized Competitor Data

Create a single source of truth for each competitor:

competitor_data/
├── notion.md
├── airtable.md
├── monday.md
└── ...

Per competitor, document:

name: Notion
website: notion.so
tagline: "The all-in-one workspace"
founded: 2016
headquarters: San Francisco

# Positioning
primary_use_case: "docs + light databases"
target_audience: "teams wanting flexible workspace"
market_position: "premium, feature-rich"

# Pricing
pricing_model: per-seat
free_tier: true
free_tier_limits: "limited blocks, 1 user"
starter_price: $8/user/month
business_price: $15/user/month
enterprise: custom

# Features (rate 1-5 or describe)
features:
  documents: 5
  databases: 4
  project_management: 3
  collaboration: 4
  integrations: 3
  mobile_app: 3
  offline_mode: 2
  api: 4

# Strengths (be honest)
strengths:
  - Extremely flexible and customizable
  - Beautiful, modern interface
  - Strong template ecosystem
  - Active community

# Weaknesses (be fair)
weaknesses:
  - Can be slow with large databases
  - Learning curve for advanced features
  - Limited automations compared to dedicated tools
  - Offline mode is limited

# Best for
best_for:
  - Teams wanting all-in-one workspace
  - Content-heavy workflows
  - Documentation-first teams
  - Startups and small teams

# Not ideal for
not_ideal_for:
  - Complex project management needs
  - Large databases (1000s of rows)
  - Teams needing robust offline
  - Enterprise with strict compliance

# Common complaints (from reviews)
common_complaints:
  - "Gets slow with lots of content"
  - "Hard to find things as workspace grows"
  - "Mobile app is clunky"

# Migration notes
migration_from:
  difficulty: medium
  data_export: "Markdown, CSV, HTML"
  what_transfers: "Pages, databases"
  what_doesnt: "Automations, integrations setup"
  time_estimate: "1-3 days for small team"

Your Product Data

Same structure for yourself — be honest:

name: [Your Product]
# ... same fields

strengths:
  - [Your real strengths]

weaknesses:
  - [Your honest weaknesses]

best_for:
  - [Your ideal customers]

not_ideal_for:
  - [Who should use something else]

Page Generation

Each page pulls from centralized data:

• •[Competitor] Alternative page: Pulls competitor data + your data
• •[Competitor] Alternatives page: Pulls competitor data + your data + other alternatives
• •You vs [Competitor] page: Pulls your data + competitor data
• •[A] vs [B] page: Pulls both competitor data + your data

Benefits:

• •Update competitor pricing once, updates everywhere
• •Add new feature comparison once, appears on all pages
• •Consistent accuracy across pages
• •Easier to maintain at scale

Section Templates

TL;DR Summary

Start every page with a quick summary for scanners:

**TL;DR**: [Competitor] excels at [strength] but struggles with [weakness].
[Your product] is built for [your focus], offering [key differentiator].
Choose [Competitor] if [their ideal use case]. Choose [You] if [your ideal use case].

Paragraph Comparison (Not Just Tables)

For each major dimension, write a paragraph:

## Features

[Competitor] offers [description of their feature approach].
Their strength is [specific strength], which works well for [use case].
However, [limitation] can be challenging for [user type].

[Your product] takes a different approach with [your approach].
This means [benefit], though [honest tradeoff].
Teams who [specific need] often find this more effective.

Feature Comparison Section

Go beyond checkmarks:

## Feature Comparison

### [Feature Category]

**[Competitor]**: [2-3 sentence description of how they handle this]
- Strengths: [specific]
- Limitations: [specific]

**[Your product]**: [2-3 sentence description]
- Strengths: [specific]
- Limitations: [specific]

**Bottom line**: Choose [Competitor] if [scenario]. Choose [You] if [scenario].

Pricing Comparison Section

## Pricing

| | [Competitor] | [Your Product] |
|---|---|---|
| Free tier | [Details] | [Details] |
| Starting price | $X/user/mo | $X/user/mo |
| Business tier | $X/user/mo | $X/user/mo |
| Enterprise | Custom | Custom |

**What's included**: [Competitor]'s $X plan includes [features], while
[Your product]'s $X plan includes [features].

**Total cost consideration**: Beyond per-seat pricing, consider [hidden costs,
add-ons, implementation]. [Competitor] charges extra for [X], while
[Your product] includes [Y] in base pricing.

**Value comparison**: For a 10-person team, [Competitor] costs approximately
$X/year while [Your product] costs $Y/year, with [key differences in what you get].

Service & Support Comparison

## Service & Support

| | [Competitor] | [Your Product] |
|---|---|---|
| Documentation | [Quality assessment] | [Quality assessment] |
| Response time | [SLA if known] | [Your SLA] |
| Support channels | [List] | [List] |
| Onboarding | [What they offer] | [What you offer] |
| CSM included | [At what tier] | [At what tier] |

**Support quality**: Based on [G2/Capterra reviews, your research],
[Competitor] support is described as [assessment]. Common feedback includes
[quotes or themes].

[Your product] offers [your support approach]. [Specific differentiator like
response time, dedicated CSM, implementation help].

Who It's For Section

## Who Should Choose [Competitor]

[Competitor] is the right choice if:
- [Specific use case or need]
- [Team type or size]
- [Workflow or requirement]
- [Budget or priority]

**Ideal [Competitor] customer**: [Persona description in 1-2 sentences]

## Who Should Choose [Your Product]

[Your product] is built for teams who:
- [Specific use case or need]
- [Team type or size]
- [Workflow or requirement]
- [Priority or value]

**Ideal [Your product] customer**: [Persona description in 1-2 sentences]

Migration Section

## Switching from [Competitor]

### What transfers
- [Data type]: [How easily, any caveats]
- [Data type]: [How easily, any caveats]

### What needs reconfiguration
- [Thing]: [Why and effort level]
- [Thing]: [Why and effort level]

### Migration support

We offer [migration support details]:
- [Free data import tool / white-glove migration]
- [Documentation / migration guide]
- [Timeline expectation]
- [Support during transition]

### What customers say about switching

> "[Quote from customer who switched]"
> — [Name], [Role] at [Company]

Social Proof Section

Focus on switchers:

## What Customers Say

### Switched from [Competitor]

> "[Specific quote about why they switched and outcome]"
> — [Name], [Role] at [Company]

> "[Another quote]"
> — [Name], [Role] at [Company]

### Results after switching
- [Company] saw [specific result]
- [Company] reduced [metric] by [amount]

Comparison Table Best Practices

Beyond Checkmarks

Instead of:

Do this:

Organize by Category

Group features into meaningful categories:

• •Core functionality
• •Collaboration
• •Integrations
• •Security & compliance
• •Support & service

Include Ratings Where Useful

Research Process

Deep Competitor Research

For each competitor, gather:

1. •

   Product research

   • •Sign up for free trial
   • •Use the product yourself
   • •Document features, UX, limitations
   • •Take screenshots
2. •

   Pricing research

   • •Current pricing (check regularly)
   • •What's included at each tier
   • •Hidden costs, add-ons
   • •Contract terms
3. •

   Review mining

   • •G2, Capterra, TrustRadius reviews
   • •Common praise themes
   • •Common complaint themes
   • •Ratings by category
4. •

   Customer feedback

   • •Talk to customers who switched
   • •Talk to prospects who chose competitor
   • •Document real quotes
5. •

   Content research

   • •Their positioning and messaging
   • •Their comparison pages (how do they compare to you?)
   • •Their documentation quality
   • •Their changelog (recent development)

Ongoing Updates

Competitor pages need maintenance:

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

Content Distribution Strategy

Competitor comparison pages are high-intent assets. They work best when they reach evaluators at the right moment. Here is how to amplify them beyond organic search.

Search Intent Matching

Map each page format to the buyer journey stage it serves:

Prioritize distribution spend on pages targeting users closest to a purchase decision.

Internal Linking from Blog Posts

Every blog post that mentions a competitor by name should link to the relevant comparison page. Audit existing content for linking opportunities:

• •Blog posts mentioning competitor pain points -> link to your "[Competitor] Alternative" page
• •How-to guides that reference competitor features -> link to "You vs [Competitor]" page
• •Industry roundups -> link to "[Competitor] Alternatives" page
• •Case studies from customers who switched -> link to the relevant comparison page

Create an internal linking map and update it whenever you publish a new comparison page.

Sales Team Enablement

Comparison pages are sales weapons. Make them easy for your sales team to use:

• •Battle cards: Create one-page summaries of each comparison page for sales reps to reference on calls
• •Email templates: Write 2-3 email templates per competitor that link to the comparison page ("I noticed you're also evaluating [Competitor] — here's how we compare...")
• •CRM triggers: When a prospect mentions a competitor in a call or form submission, auto-send the relevant comparison page
• •Objection handling: Map common competitor-related objections to specific sections of comparison pages

Email Nurture Integration

Insert comparison pages into existing email sequences at the evaluation stage:

• •Trial nurture sequence: Day 3-5 email linking to "You vs [Top Competitor]" page
• •Re-engagement sequence: "Still evaluating options? Here's how we compare to [Competitor]"
• •Post-demo follow-up: Include link to relevant comparison page based on what competitor the prospect mentioned
• •Segmented sends: If you know which competitor a prospect is evaluating (from form data, sales notes, or intent data), send the specific comparison page

Paid Amplification for High-Intent Terms

Competitor comparison keywords are high-intent and often underpriced:

• •Google Ads: Bid on "[Competitor] alternative" and "[Competitor] vs [You]" keywords. Send traffic to the corresponding comparison page, not your homepage
• •Retargeting: Show comparison page ads to visitors who viewed competitor pricing pages (if you have this data from intent platforms)
• •LinkedIn Ads: Target employees at companies using competitor products with sponsored content linking to comparison pages
• •Budget allocation: Start with your top 3 competitors by search volume. Test cost-per-conversion before scaling

Conversion Optimization for Comparison Pages

Comparison page visitors are high-intent evaluators. Standard CTAs are not enough. These pages need conversion-specific optimization because visitors are actively deciding between options.

Sticky CTA Placement

Add a persistent CTA that stays visible as users scroll through long comparison pages:

• •Sticky sidebar (desktop): Fixed panel with "Try [Your Product] Free" button that follows the user
• •Sticky bottom bar (mobile): Slim bar with CTA that appears after the user scrolls past the first comparison section
• •Do not cover content: The sticky CTA should enhance, not obstruct. Keep it minimal

Inline Trial CTAs After Each Comparison Section

Do not wait until the end of the page to ask for conversion. Place contextual CTAs after each major comparison section:

## Features

[Feature comparison content...]

**Ready to see [Your Product]'s features in action?**
[Start your free trial — no credit card required →]

Vary the CTA copy based on the section:

• •After features section: "See these features yourself"
• •After pricing section: "Calculate your savings"
• •After support section: "Talk to our team"
• •After migration section: "Get free migration help"

Exit Intent with Comparison PDF

When a visitor moves to leave the page, offer a downloadable PDF version of the comparison:

• •Trigger: Exit intent (cursor moves toward browser bar on desktop, back button on mobile)
• •Offer: "Take this comparison with you — download the full [You] vs [Competitor] breakdown as a PDF"
• •Lead capture: Name + email in exchange for the PDF
• •Follow-up: Automated email sequence with additional comparison content and trial CTA

This captures evaluators who are not ready to convert but want to share the comparison with their team.

Personalized CTAs Based on Competitor Page

Customize the CTA copy and offer based on which competitor page the visitor is on:

Social Proof from Switchers Near CTAs

Place testimonials from customers who switched from the specific competitor directly next to your CTAs:

[Start your free trial →]

> "We switched from [Competitor] in February and saw a 30% improvement
> in team productivity within the first month."
> — [Name], [Role] at [Company]

Rules for switcher testimonials:

• •Must be from a customer who specifically switched from the competitor featured on that page
• •Must include a specific result or outcome, not just "we love it"
• •Must include real name, role, and company (get permission)
• •Place the testimonial within 100px of the CTA button
• •If you do not have a switcher testimonial for a specific competitor, use a general customer quote but do not fabricate a switching story

Maintenance Playbook

Competitor comparison pages lose credibility fast when data goes stale. A wrong pricing number or outdated feature claim can destroy trust with evaluators who know the competitive landscape well. This playbook defines exactly what to check, when to check it, and who owns updates.

Monthly Maintenance (15 minutes per competitor)

Run these checks on the first Monday of each month:

Pricing verification:

• •Visit competitor pricing page
• •Compare to your published data
• •Update any changes and add "Last verified: [date]" note
• •Check for new tiers, plan changes, or feature shuffles between tiers

Review monitoring:

• •Check G2 and Capterra for new reviews mentioning your product vs. competitor
• •Note any new common complaints or praise themes
• •Add strong quotes to your switcher testimonial bank

Traffic and conversion check:

• •Review analytics for each comparison page
• •Flag pages with declining traffic or conversion rates
• •Note pages that are converting well for potential paid amplification

Quarterly Deep Review (1-2 hours total)

Run these checks at the start of each quarter:

Feature audit:

• •Sign into competitor product (or check their changelog/release notes)
• •Document any major feature launches, removals, or changes
• •Update feature comparison tables and paragraph descriptions
• •Check if any of your feature advantages have been neutralized

Pricing deep dive:

• •Verify all tier pricing, not just the headline number
• •Check for new add-ons, usage limits, or hidden costs
• •Recalculate the "10-person team" cost comparison
• •Look for annual vs. monthly pricing changes

Content refresh:

• •Re-read each comparison page for accuracy
• •Update any dated language ("In 2024, they launched...")
• •Refresh screenshots if UI has changed significantly
• •Add any new sections that have become relevant

SEO performance review:

• •Check keyword rankings for each comparison page
• •Identify new competitor-related keywords worth targeting
• •Review competitor's own comparison pages — have they published one about you?
• •Update internal links if you have published new related content

Trigger-Based Updates (As Needed)

These events should trigger an immediate review of affected comparison pages:

Ownership and Accountability

Assign clear ownership for comparison page maintenance:

• •Content owner: One person responsible for accuracy of all comparison pages. This is typically a product marketer or content strategist
• •Review cadence: Content owner runs monthly checks, flags issues to product team for quarterly deep review
• •Update SLA: Pricing changes updated within 48 hours. Feature changes updated within 1 week. Full quarterly review completed within first 2 weeks of quarter
• •Tracking: Maintain a simple spreadsheet or project board with each comparison page, last review date, next review date, and any open issues

Version History

Add a visible "Last updated" date on every comparison page. This builds credibility with evaluators and forces discipline on your maintenance schedule:

*Last updated: January 2026. We verify competitor information quarterly.
[See something outdated? Let us know.](mailto:feedback@yourcompany.com)*

SEO Considerations

Keyword Targeting

Internal Linking

• •Link between related competitor pages
• •Link from feature pages to relevant comparisons
• •Link from blog posts mentioning competitors
• •Hub page linking to all competitor content

Schema Markup

Consider FAQ schema for common questions:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the best alternative to [Competitor]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Your answer positioning yourself]"
      }
    },
    {
      "@type": "Question",
      "name": "How does [Your Product] compare to [Competitor]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Specific comparison highlighting key differences in features, pricing, and ideal use cases]"
      }
    },
    {
      "@type": "Question",
      "name": "Is [Your Product] cheaper than [Competitor]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Honest pricing comparison with specific numbers and what's included at each tier]"
      }
    },
    {
      "@type": "Question",
      "name": "Can I migrate from [Competitor] to [Your Product]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Migration details including what transfers, timeline, and support available]"
      }
    },
    {
      "@type": "Question",
      "name": "What do customers say about switching from [Competitor] to [Your Product]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Summary of switcher experiences with specific outcomes and results]"
      }
    }
  ]
}

Output Format

Competitor Data File

# [competitor].yaml
# Complete competitor profile for use across all comparison pages

Page Content

For each page:

• •URL and meta tags
• •Full page copy organized by section
• •Comparison tables
• •CTAs

Page Set Plan

Recommended pages to create:

1. •[List of alternative pages]
2. •[List of vs pages]
3. •Priority order based on search volume

Quality Gates

Before publishing any comparison page, verify:

• • Competitor information is accurate and current
• • Competitor strengths are honestly acknowledged
• • Your limitations are fairly stated
• • "Who should choose [competitor]" is genuinely helpful
• • Pricing data is verified and dated
• • No fabricated quotes or testimonials
• • Comparison tables use detail, not just checkmarks
• • Paragraph comparisons explain why differences matter
• • Migration section is specific and actionable
• • FAQ schema markup included
• • Internal links to related comparison pages
• • Last updated date visible on page
• • CTAs are contextual to each section
• • Social proof from switchers is placed near CTAs

Questions to Ask

If you need more context:

1. •Who are your top 3-5 competitors?
2. •What's your core differentiator?
3. •What are common reasons people switch to you?
4. •Do you have customer quotes about switching?
5. •What's your pricing vs. competitors?
6. •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

Attribution

Built on the original AI marketing skills framework by Corey Haines. Enhanced with operational depth and quality scoring by Single Grain, the agency behind Uber, Amazon, Salesforce, and hundreds of growth-stage companies.