Competitor & Alternative Pages

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.

How to use it

  1. Hit Copy SKILL.md — or use the Claude Code line below to get every file.
  2. Claude: ⋯ → Download .md, then Customize → Skills → Add → Upload skill.
    ChatGPT: make a Project and paste it into Instructions.
    Neither? Paste it at the top of a new chat — it works for that chat.
  3. Describe your job in plain words. The AI follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit coreyhaines31/marketingskills/skills/competitors#main ~/.claude/skills/competitors

For one project only, change the path to .claude/skills/competitors. This skill also uses product-marketing-context.md — copying SKILL.md alone won't be enough. See the folder on GitHub.

Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Show the full text259 lines
competitors/SKILL.md259 lines8.6 KBpushed 74d agoRawView on GitHub

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.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), 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:

  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
  • 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:

  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

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:

  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

Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.

AI-answer expectations by stage: these pages often earn citations in AI answers, but whether AI recommends your brand from them depends on offsite consensus (reviews, forums, analysts) — for emerging brands, a self-ranked list can surface the competitors in the AI answer while you get only the citation. Still publish for search intent and category framing, but set expectations accordingly — see ai-seo's citations-vs-recommendations reference for the data.


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:

  1. TL;DR summary (key differences in 2-3 sentences)
  2. At-a-glance comparison table
  3. Detailed comparison by category (Features, Pricing, 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

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:

  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

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:

  1. Product research: Sign up, use it, document features/UX/limitations
  2. Pricing research: Current pricing, what's included, hidden costs
  3. Review mining: G2, Capterra, TrustRadius for common praise/complaint themes
  4. Customer feedback: Talk to customers who switched (both directions)
  5. 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

  1. What are common reasons people switch to you?
  2. Do you have customer quotes about switching?
  3. What's your pricing vs. competitors?
  4. 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: For FAQ and comparison schema
  • sales-enablement: For internal sales collateral, decks, and objection docs
1---
2name: competitors
3description: "When 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,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement."
4metadata:
5 version: 2.0.1
6---
7 
8# Competitor & Alternative Pages
9 
10You 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.
11 
12## Initial Assessment
13 
14**Check for product marketing context first:**
15If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
16 
17Before creating competitor pages, understand:
18 
191. **Your Product**
20 - Core value proposition
21 - Key differentiators
22 - Ideal customer profile
23 - Pricing model
24 - Strengths and honest weaknesses
25 
262. **Competitive Landscape**
27 - Direct competitors
28 - Indirect/adjacent competitors
29 - Market positioning of each
30 - Search volume for competitor terms
31 
323. **Goals**
33 - SEO traffic capture
34 - Sales enablement
35 - Conversion from competitor users
36 - Brand positioning
37 
38---
39 
40## Core Principles
41 
42### 1. Honesty Builds Trust
43- Acknowledge competitor strengths
44- Be accurate about your limitations
45- Don't misrepresent competitor features
46- Readers are comparing—they'll verify claims
47 
48### 2. Depth Over Surface
49- Go beyond feature checklists
50- Explain *why* differences matter
51- Include use cases and scenarios
52- Show, don't just tell
53 
54### 3. Help Them Decide
55- Different tools fit different needs
56- Be clear about who you're best for
57- Be clear about who competitor is best for
58- Reduce evaluation friction
59 
60### 4. Modular Content Architecture
61- Competitor data should be centralized
62- Updates propagate to all pages
63- Single source of truth per competitor
64 
65---
66 
67## Page Formats
68 
69### Format 1: [Competitor] Alternative (Singular)
70 
71**Search intent**: User is actively looking to switch from a specific competitor
72 
73**URL pattern**: `/alternatives/[competitor]` or `/[competitor]-alternative`
74 
75**Target keywords**: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"
76 
77**Page structure**:
781. Why people look for alternatives (validate their pain)
792. Summary: You as the alternative (quick positioning)
803. Detailed comparison (features, service, pricing)
814. Who should switch (and who shouldn't)
825. Migration path
836. Social proof from switchers
847. CTA
85 
86---
87 
88### Format 2: [Competitor] Alternatives (Plural)
89 
90**Search intent**: User is researching options, earlier in journey
91 
92**URL pattern**: `/alternatives/[competitor]-alternatives`
93 
94**Target keywords**: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"
95 
96**Page structure**:
971. Why people look for alternatives (common pain points)
982. What to look for in an alternative (criteria framework)
993. List of alternatives (you first, but include real options)
1004. Comparison table (summary)
1015. Detailed breakdown of each alternative
1026. Recommendation by use case
1037. CTA
104 
105**Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
106 
107**AI-answer expectations by stage**: these pages often earn *citations* in AI answers, but whether AI *recommends* your brand from them depends on offsite consensus (reviews, forums, analysts) — for emerging brands, a self-ranked list can surface the competitors in the AI answer while you get only the citation. Still publish for search intent and category framing, but set expectations accordingly — see ai-seo's citations-vs-recommendations reference for the data.
108 
109---
110 
111### Format 3: You vs [Competitor]
112 
113**Search intent**: User is directly comparing you to a specific competitor
114 
115**URL pattern**: `/vs/[competitor]` or `/compare/[you]-vs-[competitor]`
116 
117**Target keywords**: "[You] vs [Competitor]", "[Competitor] vs [You]"
118 
119**Page structure**:
1201. TL;DR summary (key differences in 2-3 sentences)
1212. At-a-glance comparison table
1223. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)
1234. Who [You] is best for
1245. Who [Competitor] is best for (be honest)
1256. What customers say (testimonials from switchers)
1267. Migration support
1278. CTA
128 
129---
130 
131### Format 4: [Competitor A] vs [Competitor B]
132 
133**Search intent**: User comparing two competitors (not you directly)
134 
135**URL pattern**: `/compare/[competitor-a]-vs-[competitor-b]`
136 
137**Page structure**:
1381. Overview of both products
1392. Comparison by category
1403. Who each is best for
1414. The third option (introduce yourself)
1425. Comparison table (all three)
1436. CTA
144 
145**Why this works**: Captures search traffic for competitor terms, positions you as knowledgeable.
146 
147---
148 
149## Essential Sections
150 
151### TL;DR Summary
152Start every page with a quick summary for scanners—key differences in 2-3 sentences.
153 
154### Paragraph Comparisons
155Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.
156 
157### Feature Comparison
158For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.
159 
160### Pricing Comparison
161Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.
162 
163### Who It's For
164Be explicit about ideal customer for each option. Honest recommendations build trust.
165 
166### Migration Section
167Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.
168 
169**For detailed templates**: See [references/templates.md](references/templates.md)
170 
171---
172 
173## Content Architecture
174 
175### Centralized Competitor Data
176Create a single source of truth for each competitor with:
177- Positioning and target audience
178- Pricing (all tiers)
179- Feature ratings
180- Strengths and weaknesses
181- Best for / not ideal for
182- Common complaints (from reviews)
183- Migration notes
184 
185**For data structure and examples**: See [references/content-architecture.md](references/content-architecture.md)
186 
187---
188 
189## Research Process
190 
191### Deep Competitor Research
192 
193For each competitor, gather:
194 
1951. **Product research**: Sign up, use it, document features/UX/limitations
1962. **Pricing research**: Current pricing, what's included, hidden costs
1973. **Review mining**: G2, Capterra, TrustRadius for common praise/complaint themes
1984. **Customer feedback**: Talk to customers who switched (both directions)
1995. **Content research**: Their positioning, their comparison pages, their changelog
200 
201### Ongoing Updates
202 
203- **Quarterly**: Verify pricing, check for major feature changes
204- **When notified**: Customer mentions competitor change
205- **Annually**: Full refresh of all competitor data
206 
207---
208 
209## SEO Considerations
210 
211### Keyword Targeting
212 
213| Format | Primary Keywords |
214|--------|-----------------|
215| Alternative (singular) | [Competitor] alternative, alternative to [Competitor] |
216| Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives |
217| You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] |
218| Competitor vs Competitor | [A] vs [B], [B] vs [A] |
219 
220### Internal Linking
221- Link between related competitor pages
222- Link from feature pages to relevant comparisons
223- Create hub page linking to all competitor content
224 
225### Schema Markup
226Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"
227 
228---
229 
230## Output Format
231 
232### Competitor Data File
233Complete competitor profile in YAML format for use across all comparison pages.
234 
235### Page Content
236For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.
237 
238### Page Set Plan
239Recommended pages to create with priority order based on search volume.
240 
241---
242 
243## Task-Specific Questions
244 
2451. What are common reasons people switch to you?
2462. Do you have customer quotes about switching?
2473. What's your pricing vs. competitors?
2484. Do you offer migration support?
249 
250---
251 
252## Related Skills
253 
254- **programmatic-seo**: For building competitor pages at scale
255- **copywriting**: For writing compelling comparison copy
256- **seo-audit**: For optimizing competitor pages
257- **schema**: For FAQ and comparison schema
258- **sales-enablement**: For internal sales collateral, decks, and objection docs
259 

Discussion

From GitHub

1 comment on 1 thread

Alternatives

Also in Competitor research
Competitor Comparison & Alternatives PagesTell us your product and a rival you keep losing deals to, and get back a ready-to-publish page that shows why customers should pick you.Business & ops · MITAd angle minerMine the highest-converting ad angles from customer reviews, Reddit complaints, support tickets, and competitor ads. Extracts actual pain language, competitor weaknesses, and outcome phrases that real buyers use. Outputs a ranked angle bank with proof quotes and recommended ad formats per angle.Business & ops · MITX audience insightsRead your X (Twitter) audience and niche from real data. Pull a handle's recent tweets (yours or a competitor's) with likes, replies, and views, see which formats and hooks are working, read the repliers on a tweet (X gates likers, so repliers are the signal), and scan a niche query for top tweets. Powered by Apify, no login. Triggers on "analyze my tweets", "what is working on X", "read the replies", "competitor tweets", "who is engaging". Not for writing a tweet (use x-post-writer).Marketing · MITFacebook Audience InsightsRead a Facebook Page and its audience from real data. Pull any Page's public stats (yours or a competitor's): followers, likes, categories, intro, websites. And pull the commenters on a public Page post, since Facebook hides the reactor and liker roster and shows counts only, so commenters are the signal. Powered by Apify, no login. Triggers on "analyze my Page", "competitor Page stats", "who is commenting", "read the comments", "audience insights". Not for writing Page posts (use fb-post-writer).Marketing · MIT