LLM Skills
~/catalog/seo content//SKILL
SEO contentGitHub source

Competitor alternatives

/SKILL

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative pa

// skill content

--- name: competitor-alternatives description: "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,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables." --- # 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 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

// original public source
strataga/claude-setup
/skills/competitor-alternatives/SKILL.md
License: License not specified. Review the repository before reusing it.
Independent project, not affiliated with Anthropic. This skill remains the property of its original author.
// install this skill
Paste this command in your terminal at the root of your project:
mkdir -p .claude/commands && curl -o ".claude/commands/SKILL.md" "https://raw.githubusercontent.com/strataga/claude-setup/master/skills/competitor-alternatives/SKILL.md"
Then in Claude Code, type /SKILL to activate it.
open_in_newOpen original source
// save
Save available after sign in.
loginSign in to save
// information
Creatorstrataga
CategorySEO content
Format.md
AccessFree
// similar

Skills SEO content

View allarrow_forward