alternatives-pages

Files (2)

• README.md
• SKILL.md

SKILL.md (first lines)

# Alternatives Pages

Create effective "[Competitor] alternative" and comparison pages that rank for competitive keywords, convert developers honestly, and support your competitive positioning.

## Overview

Alternatives pages and comparison content are high-intent SEO plays. Developers searching for "[competitor] alternative" or "[your product] vs [competitor]" are actively evaluating solutions. Done well, this content captures demand, educates prospects, and positions your product effectively. Done poorly, it damages trust and brand perception.

The key principles:
- Be honest - developers will fact-check you
- Be helpful - even if they don't choose you
- Be specific - vague comparisons waste everyone's time
- Be current - outdated comparisons are worse than none

## SEO Research for Competitive Keywords

### Keyword Categories

**Alternative keywords:**
- "[Competitor] alternative"
- "[Competitor] alternatives"
- "Alternative to [competitor]"
- "Best [competitor] alternatives"
- "[Competitor] replacement"

**Comparison keywords:**
- "[Competitor] vs [your product]"
- "[Your product] vs [competitor]"
- "[Competitor] vs [other competitor]" (consider if you should play here)
- "[Competitor] comparison"
- "Compare [category] tools"

**Migration keywords:**
- "Migrate from [competitor]"
- "Switch from [competitor]"
- "[Competitor] to [your product]"
- "Moving away from [competitor]"

**Problem-aware keywords:**
- "[Competitor] pricing too expensive"
- "[Competitor] limitations"
- "[Competitor] [specific problem]"
- "Frustrated with [competitor]"

### Research Developer Conversations

Use social listening tools to identify which competitive keywords have real search intent based on developer conversations. Search for:

- "[competitor] alternative" or "alternative to [competitor]"
- "[competitor] vs"
- Negative sentiment mentions of competitors

Look for patterns in:
- Which competitors developers frequently compare
- What problems drive people away from competitors
- What features developers ask about when evaluating
- Migration concerns and blockers

### Prioritizing Which Pages to Create

**High priority:**
- Direct competitors with significant search volume
- Competitors you frequently encounter in deals
- Competitors developers organically compare you to

**Medium priority:**
- Indirect competitors in adjacent categories
- Competitors you can clearly beat on specific use cases

**Lower priority:**
- Competitors in different market segments
- Competitors with minimal overlap

## Page Structure That Converts

### Alternatives Page Structure

**1. Hero Section**
- Clear headline: "[Your product]: A [Competitor] Alternative for [Use Case]"
- One-sentence value proposition
- Quick social proof (logos, stats)
- Primary CTA

**2. Why Developers Switch Section**
- Common pain points with competitor (from social listening research)
- Be specific and factual, not snarky
- Cite real developer feedback when possible

**3. Key Differences Section**
- 3-5 major differentiators
- Focus on things that matter to your ICP
- Be honest about where you're similar or worse

**4. Comparison Table**
- Feature-by-feature comparison
- Include pricing comparison
- Honest checkmarks (don't claim features you don't have)
- Date the comparison ("Last updated: [date]")

**5. Migration Section**
- How hard is it to switch?
- Migration guide or resources
- Data portability information
- Support available during migration

**6. Social Proof**
- Case studies from companies who switched
- Testimonials mentioning the switch
- Quantified results if available

**7. FAQ Section**
- Address common concerns
- SEO opportunity for long-tail keywords
- Objection handling

**8. CTA Section**
- Primary: Start trial/demo
- Secondary: Migration guide, comparison deep-dive

From jonathimer/devmarketing-skills, MIT.

More from jonathimer/devmarketing-skills