$npx -y skills add aitytech/agentkits-marketing --skill competitor-alternativesWhen 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,' or 'competitive lan
| 1 | # Competitor & Alternative Pages |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | ## Initial Assessment |
| 6 | |
| 7 | Before creating competitor pages, understand: |
| 8 | |
| 9 | 1. **Your Product** |
| 10 | - Core value proposition |
| 11 | - Key differentiators |
| 12 | - Ideal customer profile |
| 13 | - Pricing model |
| 14 | - Strengths and honest weaknesses |
| 15 | |
| 16 | 2. **Competitive Landscape** |
| 17 | - Direct competitors |
| 18 | - Indirect/adjacent competitors |
| 19 | - Market positioning of each |
| 20 | - Search volume for competitor terms |
| 21 | |
| 22 | 3. **Goals** |
| 23 | - SEO traffic capture |
| 24 | - Sales enablement |
| 25 | - Conversion from competitor users |
| 26 | - Brand positioning |
| 27 | |
| 28 | --- |
| 29 | |
| 30 | ## Core Principles |
| 31 | |
| 32 | ### 1. Honesty Builds Trust |
| 33 | - Acknowledge competitor strengths |
| 34 | - Be accurate about your limitations |
| 35 | - Don't misrepresent competitor features |
| 36 | - Readers are comparing—they'll verify claims |
| 37 | |
| 38 | ### 2. Depth Over Surface |
| 39 | - Go beyond feature checklists |
| 40 | - Explain *why* differences matter |
| 41 | - Include use cases and scenarios |
| 42 | - Show, don't just tell |
| 43 | |
| 44 | ### 3. Help Them Decide |
| 45 | - Different tools fit different needs |
| 46 | - Be clear about who you're best for |
| 47 | - Be clear about who competitor is best for |
| 48 | - Reduce evaluation friction |
| 49 | |
| 50 | ### 4. Modular Content Architecture |
| 51 | - Competitor data should be centralized |
| 52 | - Updates propagate to all pages |
| 53 | - Avoid duplicating research |
| 54 | - Single source of truth per competitor |
| 55 | |
| 56 | --- |
| 57 | |
| 58 | ## Page Formats |
| 59 | |
| 60 | ### Format 1: [Competitor] Alternative (Singular) |
| 61 | |
| 62 | **Search intent**: User is actively looking to switch from a specific competitor |
| 63 | |
| 64 | **URL pattern**: `/alternatives/[competitor]` or `/[competitor]-alternative` |
| 65 | |
| 66 | **Target keywords**: |
| 67 | - "[Competitor] alternative" |
| 68 | - "alternative to [Competitor]" |
| 69 | - "switch from [Competitor]" |
| 70 | - "[Competitor] replacement" |
| 71 | |
| 72 | **Page structure**: |
| 73 | 1. Why people look for alternatives (validate their pain) |
| 74 | 2. Summary: You as the alternative (quick positioning) |
| 75 | 3. Detailed comparison (features, service, pricing) |
| 76 | 4. Who should switch (and who shouldn't) |
| 77 | 5. Migration path |
| 78 | 6. Social proof from switchers |
| 79 | 7. CTA |
| 80 | |
| 81 | **Tone**: Empathetic to their frustration, helpful guide |
| 82 | |
| 83 | --- |
| 84 | |
| 85 | ### Format 2: [Competitor] Alternatives (Plural) |
| 86 | |
| 87 | **Search intent**: User is researching options, earlier in journey |
| 88 | |
| 89 | **URL pattern**: `/alternatives/[competitor]-alternatives` or `/best-[competitor]-alternatives` |
| 90 | |
| 91 | **Target keywords**: |
| 92 | - "[Competitor] alternatives" |
| 93 | - "best [Competitor] alternatives" |
| 94 | - "tools like [Competitor]" |
| 95 | - "[Competitor] competitors" |
| 96 | |
| 97 | **Page structure**: |
| 98 | 1. Why people look for alternatives (common pain points) |
| 99 | 2. What to look for in an alternative (criteria framework) |
| 100 | 3. List of alternatives (you first, but include real options) |
| 101 | 4. Comparison table (summary) |
| 102 | 5. Detailed breakdown of each alternative |
| 103 | 6. Recommendation by use case |
| 104 | 7. CTA |
| 105 | |
| 106 | **Tone**: Objective guide, you're one option among several (but positioned well) |
| 107 | |
| 108 | **Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better. |
| 109 | |
| 110 | --- |
| 111 | |
| 112 | ### Format 3: You vs [Competitor] |
| 113 | |
| 114 | **Search intent**: User is directly comparing you to a specific competitor |
| 115 | |
| 116 | **URL pattern**: `/vs/[competitor]` or `/compare/[you]-vs-[competitor]` |
| 117 | |
| 118 | **Target keywords**: |
| 119 | - "[You] vs [Competitor]" |
| 120 | - "[Competitor] vs [You]" |
| 121 | - "[You] compared to [Competitor]" |
| 122 | - "[You] or [Competitor]" |
| 123 | |
| 124 | **Page structure**: |
| 125 | 1. TL;DR summary (key differences in 2-3 sentences) |
| 126 | 2. At-a-glance comparison table |
| 127 | 3. Detailed comparison by category: |
| 128 | - Features |
| 129 | - Pricing |
| 130 | - Service & support |
| 131 | - Ease of use |
| 132 | - Integrations |
| 133 | 4. Who [You] is best for |
| 134 | 5. Who [Competitor] is best for (be honest) |
| 135 | 6. What customers say (testimonials from switchers) |
| 136 | 7. Migration support |
| 137 | 8. CTA |
| 138 | |
| 139 | **Tone**: Confident but fair, acknowledge where competitor excels |
| 140 | |
| 141 | --- |
| 142 | |
| 143 | ### Format 4: [Competitor A] vs [Competitor B] |
| 144 | |
| 145 | **Search in |