competitor-alternatives
Competitor comparison and alternative page creation for SEO and sales enablement. Covers 4 page formats (singular alternative, plural alternatives, vs pages, competitor vs competitor), content architecture, research methodology, and centralized competitor data management.
What this skill does
# Competitor & Alternative Pages
Production-grade framework for creating competitor comparison and alternative pages. Covers 4 page formats, centralized competitor data architecture, deep research methodology, SEO optimization, content templates, and ongoing maintenance strategy. Designed for both SEO traffic capture and sales enablement.
---
## Table of Contents
- [When to Use](#when-to-use)
- [Core Principles](#core-principles)
- [The 4 Page Formats](#the-4-page-formats)
- [Content Architecture](#content-architecture)
- [Research Methodology](#research-methodology)
- [Essential Content Sections](#essential-content-sections)
- [SEO Strategy](#seo-strategy)
- [Maintenance and Updates](#maintenance-and-updates)
- [Quality Standards](#quality-standards)
- [Output Artifacts](#output-artifacts)
- [Related Skills](#related-skills)
---
## When to Use
| Trigger | Action |
|---------|--------|
| Prospects comparing you to competitors | Create vs-pages for top 3 competitors |
| Search volume exists for "[competitor] alternative" | Create singular alternative pages |
| Sales team needs battle card content | Create vs-pages with objection handling |
| Competitor has comparison pages about you | Create counter-comparison pages |
| SEO gap on competitor-branded keywords | Build full alternative page set |
---
## Core Principles
### 1. Honesty Builds Trust
- Acknowledge competitor strengths explicitly
- Be accurate about your own limitations
- Readers are actively comparing -- they will verify your claims
- A dishonest comparison page damages your brand more than no page at all
### 2. Help Them Decide (Not Just Sell)
- Different tools genuinely fit different needs
- Be explicit about who you are best for AND who the competitor is best for
- Reduce evaluation friction -- save prospects research time
### 3. Depth Over Checkbox Tables
- Go beyond feature checklists (every competitor does those)
- Explain WHY differences matter for specific use cases
- Include real scenarios and workflows
- Show, do not just tell
### 4. Single Source of Truth
- Centralize competitor data -- do not maintain facts across 10 pages
- Updates propagate to all pages automatically
- Track last-verified date per data point
---
## The 4 Page Formats
### Format 1: [Competitor] Alternative (Singular)
**Intent:** User is actively looking to switch FROM a specific competitor.
**URL:** `/alternatives/[competitor]` or `/[competitor]-alternative`
**Keywords:** "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"
**Page Structure:**
```
1. Why people look for alternatives (validate their pain, 2-3 paragraphs)
2. TL;DR: You as the alternative (quick positioning, 3-4 bullets)
3. Detailed comparison (features, pricing, support -- paragraph format, not just tables)
4. Who should switch (and who should NOT -- be honest)
5. Migration path (what transfers, what needs reconfiguration)
6. Testimonials from customers who switched
7. CTA: Start free trial or request demo
```
### Format 2: [Competitor] Alternatives (Plural)
**Intent:** User is researching options broadly, earlier in the buying journey.
**URL:** `/alternatives/[competitor]-alternatives` or `/best-[competitor]-alternatives`
**Keywords:** "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"
**Page Structure:**
```
1. Why people look for alternatives (common pain points, 2-3 paragraphs)
2. What to look for in an alternative (evaluation criteria framework)
3. List of 5-7 alternatives (you first, but include real options)
4. Summary comparison table
5. Detailed breakdown of each alternative (150-200 words each)
6. Recommendation by use case ("Best for [X]: [Tool]")
7. CTA
```
**Important:** Include 5-7 REAL alternatives. Being genuinely helpful ranks better and builds trust.
### Format 3: You vs [Competitor]
**Intent:** User is directly comparing you to a specific competitor.
**URL:** `/vs/[competitor]` or `/compare/[you]-vs-[competitor]`
**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 (8-12 dimensions)
3. Detailed comparison by category (paragraph format per category):
- Features
- Pricing
- Ease of use / UX
- Support and documentation
- Integrations
- Security and compliance
4. Who [You] is best for (3-4 bullets)
5. Who [Competitor] is best for (3-4 bullets -- be honest)
6. What customers say (testimonials from switchers)
7. Migration support
8. CTA
```
### Format 4: [Competitor A] vs [Competitor B]
**Intent:** User is comparing two competitors (neither is you directly).
**URL:** `/compare/[competitor-a]-vs-[competitor-b]`
**Page Structure:**
```
1. Overview of both products (neutral, factual)
2. Comparison by category (same categories as Format 3)
3. Who each is best for
4. "Consider a third option" (introduce yourself naturally)
5. Three-way comparison table (both competitors + you)
6. CTA
```
**Why this works:** Captures competitor-branded search traffic, positions you as a knowledgeable authority, and introduces you to buyers who might not have considered you.
---
## Content Architecture
### Centralized Competitor Data
Create a single data file per competitor that feeds all comparison pages.
**Competitor Data Structure:**
```
Competitor: [Name]
Last Verified: [Date]
Website: [URL]
Positioning:
- Tagline: [Their tagline]
- Target audience: [Who they target]
- Primary differentiator: [What they claim is unique]
Pricing:
- Free tier: [Yes/No, details]
- Entry price: [$X/mo]
- Mid-tier price: [$X/mo]
- Enterprise: [Custom / $X/mo]
- Billing: [Monthly, Annual, Both]
- Trial: [Length, CC required?]
Features:
- [Category 1]: [Rating 1-5, notes]
- [Category 2]: [Rating 1-5, notes]
- [Category 3]: [Rating 1-5, notes]
Strengths:
- [Strength 1 with evidence]
- [Strength 2 with evidence]
Weaknesses:
- [Weakness 1 with evidence source]
- [Weakness 2 with evidence source]
Best For: [Description of ideal customer]
Not Ideal For: [Description of poor fit]
Common Complaints (from reviews):
- [Complaint 1] (source: G2/Capterra/etc.)
- [Complaint 2]
- [Complaint 3]
Migration Notes:
- Data export: [Available? Format?]
- API migration: [Available?]
- Switching time: [Estimated]
```
---
## Research Methodology
### Deep Research Process
For each competitor:
1. **Sign up and use the product** -- Create a real account, go through onboarding, test core workflows. There is no substitute for hands-on experience.
2. **Pricing verification** -- Screenshot current pricing page. Note what is included at each tier. Check for hidden costs.
3. **Review mining** -- Read 50+ reviews on G2, Capterra, TrustRadius. Categorize into praise themes, complaint themes, and feature requests.
4. **Customer feedback** -- Talk to your customers who switched from (or to) this competitor. Capture switching reasons and experience quotes.
5. **Content audit** -- Review their positioning, their comparison pages about you (if any), their changelog, their blog.
6. **Financial/growth signals** -- Check Crunchbase for funding, LinkedIn for employee count trends, job postings for strategic direction.
### Verification Schedule
| Frequency | What to Verify |
|-----------|---------------|
| Monthly | Pricing (check for changes) |
| Quarterly | Feature set, major product updates |
| When notified | Customer reports competitor change |
| Annually | Full refresh of all competitor data |
---
## Essential Content Sections
### TL;DR Summary
Every comparison page starts with a 2-3 sentence summary for scanners. This is the most-read section.
**Template:** "[Your product] is the better choice if you need [differentiator 1] and [differentiator 2]. [Competitor] is better if [their strength]. The biggest differences are [difference 1] and [difference 2]."
### Paragraph Comparisons (Not Just Tables)
FoRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".