competitor-alternatives
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.
What this skill does
# 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 search traffic for competitor terms, positions you as knowledgeable, introduces you to qualified audience. --- ## Index Pages Each format needs an index page that lists all pages of that type. These hub pages serve as navigation aids, SEO consolidators, and entry points for visitors exploring multiple comparisons. ### Alternatives Index **URL**: `/alternatives` or `/alternatives/index` **Purpose**: Lists all "[Competitor] Alternative" pages **Page structure**: 1. Headline: "[Your Product] as an Alternative" 2. Brief intro on why people switch to you 3. List of all alternative pages with: - Competitor name/logo - One-line summary of key differentiator vs. that competitor - Link to full comparison 4. Common reasons people switch (aggregated) 5. CTA **Example**: ```markdown ## Explore [Your Product] as an Alternative Looking to switch? See how [Your Product] compares to the tools you're evaluating: - **[Notion Alternative](/alternatives/notion)** — Better for teams who need [X] - **[Airtable Alternative](/alternatives/airtable)** — Better for teams who need [Y] - **[Monday Alternative](/alternatives/monday)** — Better for teams who need [Z] ``` --- ### Alternatives (Plural) Index **URL**: `/alternatives/compare` or `/best-alternatives` **Purpose**: Lists all "[Competitor] Alternatives" roundup pages **Page structure**: 1. Headline: "Software Alternatives & Comparisons" 2. Brief intro on your comparison methodology 3. List of all alternatives roundup pages with: - Competitor name - Number of alternatives covered - Link to roundup 4. CTA **Example**: ```markdown ## Find the Right Tool Comparing your options? Our guides cover the top alternatives: - **[Best Notion Alternatives](/alternatives/notion-alternatives)** — 7 tools compared - **[Best Airtable Alternatives](/alternatives/airtable-alternatives)** — 6 tools compared - **[Best Monday Alternatives](/alternatives/monday-alternatives)** — 5 tools compared ``` --- ### Vs Comparisons Index **URL**: `/vs` or `/compare` **Purpose**: Lists all "You vs [Competitor]" and "[A] vs [B]" pages **Page structure**: 1. Headline: "Compare [Your Product]" 2. Section: "[Your Product] vs Competitors" — list of direct comparisons 3. Section: "Head-to-Head Comparisons" — list of [A] vs [B] pages 4. Brief methodology note 5. CTA **Example**: ```markdown ## Compare [Your Product] ### [Your Product] vs. the Competition - **[[Your Product] vs Notion](/vs/notion)** — Best for [differentiator] - **[[Your Product] vs Airtable](/vs/airtable)** — Best for [differentiator] - **[[Your Product] vs Monday](/vs/monday)** — Best for [differentiator] ### Other Comparisons Evaluating tools we compete with? We've done the research: - **[Notion vs Airtable](/compare/notion-vs-airtable)** - **[Notion vs Monday](/compare/notion-vs-monday)** - **[Airtable vs Monday](/compare/airtable-vs-monday)** ``` --- ### Index Page Best Practices **Keep them updated**: When you add a new comparison page, add it to the relevant index. **Internal linking**: - Link from index → individual pages - Link from individual pages → back to index - Cross-link between related comparisons **SEO value**: - Index pages can rank for broad terms like "project management tool comparisons" - Pass link equity to individual comparison pages - Help search engines discover all comparison content **Sorting options**: - By popularity (search volume) - Alphabetically - By category/use case - By date added (show freshness) **Include on index pages**: - Last updated date for cred
Related 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".