alternatives-pages
installsforks
How to install alternatives-pages?
jonathimer/devmarketing-skills/alternatives-pages
$npx -y skills add jonathimer/devmarketing-skills --skill alternatives-pagesCreate "[Competitor] alternative" and comparison pages for developer tools. Build honest, high-converting comparison content that ranks for competitive search terms. Trigger phrases: "alternatives page", "comparison page", "vs page", "[competitor] alternative", "competitor compar
SKILL.md
| 1 | # Alternatives Pages |
| 2 | |
| 3 | Create effective "[Competitor] alternative" and comparison pages that rank for competitive keywords, convert developers honestly, and support your competitive positioning. |
| 4 | |
| 5 | ## Overview |
| 6 | |
| 7 | 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. |
| 8 | |
| 9 | The key principles: |
| 10 | - Be honest - developers will fact-check you |
| 11 | - Be helpful - even if they don't choose you |
| 12 | - Be specific - vague comparisons waste everyone's time |
| 13 | - Be current - outdated comparisons are worse than none |
| 14 | |
| 15 | ## SEO Research for Competitive Keywords |
| 16 | |
| 17 | ### Keyword Categories |
| 18 | |
| 19 | **Alternative keywords:** |
| 20 | - "[Competitor] alternative" |
| 21 | - "[Competitor] alternatives" |
| 22 | - "Alternative to [competitor]" |
| 23 | - "Best [competitor] alternatives" |
| 24 | - "[Competitor] replacement" |
| 25 | |
| 26 | **Comparison keywords:** |
| 27 | - "[Competitor] vs [your product]" |
| 28 | - "[Your product] vs [competitor]" |
| 29 | - "[Competitor] vs [other competitor]" (consider if you should play here) |
| 30 | - "[Competitor] comparison" |
| 31 | - "Compare [category] tools" |
| 32 | |
| 33 | **Migration keywords:** |
| 34 | - "Migrate from [competitor]" |
| 35 | - "Switch from [competitor]" |
| 36 | - "[Competitor] to [your product]" |
| 37 | - "Moving away from [competitor]" |
| 38 | |
| 39 | **Problem-aware keywords:** |
| 40 | - "[Competitor] pricing too expensive" |
| 41 | - "[Competitor] limitations" |
| 42 | - "[Competitor] [specific problem]" |
| 43 | - "Frustrated with [competitor]" |
| 44 | |
| 45 | ### Research Developer Conversations |
| 46 | |
| 47 | Use social listening tools to identify which competitive keywords have real search intent based on developer conversations. Search for: |
| 48 | |
| 49 | - "[competitor] alternative" or "alternative to [competitor]" |
| 50 | - "[competitor] vs" |
| 51 | - Negative sentiment mentions of competitors |
| 52 | |
| 53 | Look for patterns in: |
| 54 | - Which competitors developers frequently compare |
| 55 | - What problems drive people away from competitors |
| 56 | - What features developers ask about when evaluating |
| 57 | - Migration concerns and blockers |
| 58 | |
| 59 | ### Prioritizing Which Pages to Create |
| 60 | |
| 61 | **High priority:** |
| 62 | - Direct competitors with significant search volume |
| 63 | - Competitors you frequently encounter in deals |
| 64 | - Competitors developers organically compare you to |
| 65 | |
| 66 | **Medium priority:** |
| 67 | - Indirect competitors in adjacent categories |
| 68 | - Competitors you can clearly beat on specific use cases |
| 69 | |
| 70 | **Lower priority:** |
| 71 | - Competitors in different market segments |
| 72 | - Competitors with minimal overlap |
| 73 | |
| 74 | ## Page Structure That Converts |
| 75 | |
| 76 | ### Alternatives Page Structure |
| 77 | |
| 78 | **1. Hero Section** |
| 79 | - Clear headline: "[Your product]: A [Competitor] Alternative for [Use Case]" |
| 80 | - One-sentence value proposition |
| 81 | - Quick social proof (logos, stats) |
| 82 | - Primary CTA |
| 83 | |
| 84 | **2. Why Developers Switch Section** |
| 85 | - Common pain points with competitor (from social listening research) |
| 86 | - Be specific and factual, not snarky |
| 87 | - Cite real developer feedback when possible |
| 88 | |
| 89 | **3. Key Differences Section** |
| 90 | - 3-5 major differentiators |
| 91 | - Focus on things that matter to your ICP |
| 92 | - Be honest about where you're similar or worse |
| 93 | |
| 94 | **4. Comparison Table** |
| 95 | - Feature-by-feature comparison |
| 96 | - Include pricing comparison |
| 97 | - Honest checkmarks (don't claim features you don't have) |
| 98 | - Date the comparison ("Last updated: [date]") |
| 99 | |
| 100 | **5. Migration Section** |
| 101 | - How hard is it to switch? |
| 102 | - Migration guide or resources |
| 103 | - Data portability information |
| 104 | - Support available during migration |
| 105 | |
| 106 | **6. Social Proof** |
| 107 | - Case studies from companies who switched |
| 108 | - Testimonials mentioning the switch |
| 109 | - Quantified results if available |
| 110 | |
| 111 | **7. FAQ Section** |
| 112 | - Address common concerns |
| 113 | - SEO opportunity for long-tail keywords |
| 114 | - Objection handling |
| 115 | |
| 116 | **8. CTA Section** |
| 117 | - Primary: Start trial/demo |
| 118 | - Secondary: Migration guide, comparison deep-dive |
| 119 | |
| 120 | ### Comparison Page Structure (You vs Them) |
| 121 | |
| 122 | **1. Hero** |
| 123 | - "[Your Product] vs [Competitor]: [Key Differentiator]" |
| 124 | - Neutral, informative tone |
| 125 | - Both logos (don't be weird about it) |
| 126 | |
| 127 | **2. Quick Comparison** |
| 128 | - At-a-glance summary for scanners |
| 129 | - 3-4 key differences highlighted |
| 130 | - Who each product is best for |
| 131 | |
| 132 | **3. Detailed Comparison Table** |
| 133 | - Comprehensive feature comparison |
| 134 | - Categorize features logically |
| 135 | - Include pricing |
| 136 | - Include subjective but fair assessments |
| 137 | |
| 138 | **4. Detailed Analysis Sections** |
| 139 | - Deep dive on major difference areas |
| 140 | - Use cases where each excels |
| 141 | - Developer experience comparison |
| 142 | |
| 143 | **5. Migration Information** |
| 144 | - If relevant, how to switch between them |
| 145 | - Bidirectional if y |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
