Competitor Alternatives

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

.codex/skills/a11y-audit

.codex/skills/ab-test-setup

.codex/skills/account-executive

.codex/skills/ad-creative

.codex/skills/aeo

Audit 0.4.1 · source sha 6e3fcbdbb5cf · 19 Oct 2026Report an issue or request a re-scan

• Publisherborghei GitHub userOwner of the repository this skill is read from
• Source folderborghei/Claude-Skills/business-growth/competitor-alternativesThe exact folder we audited
• LicenceNOASSERTIONAs the repository states it
• Commit pinned for this verdict6e3fcbdbb5cfA new audit runs when the source changes
• Repository statusNot archivedLast push 12 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Create competitor comparison and alternative pages for SEO and sales enablement. Use when building alternative pages, vs pages, or competitor-vs-competitor pages, planning comparison content, or managing competitor data.

---
name: competitor-alternatives
description: >
  Create competitor comparison and alternative pages for SEO and sales
  enablement. Use when building alternative pages, vs pages, or
  competitor-vs-competitor pages, planning comparison content, or managing
  competitor data.
license: MIT + Commons Clause
metadata:
  version: 1.0.0
  author: borghei
  category: business-growth
  updated: 2026-03-31
  tags:
    - competitive-content
    - seo
    - comparison-pages
    - alternative-pages
    - sales-enablement
---
# 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 |

---

## Clarify First

Before writing the comparison content, confirm these inputs. If any is unknown or vague, ASK — do not assume:

- [ ] **Page format** — singular alternative, plural alternatives, you-vs-competitor, or competitor-vs-competitor (selects the page structure template)
- [ ] **Primary goal** — SEO traffic capture vs sales enablement (changes tone, depth, and whether to include objection handling)
- [ ] **Target competitor + data freshness** — who, and how recent the pricing/feature data is (every claim must be verifiable)
- [ ] **Honest positioning** — who you genuinely win for and who the competitor wins for (drives the trust-building "who it's for" sections)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the page.

## 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 c

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/borghei/Claude-Skills
git -C Claude-Skills checkout 6e3fcbdbb5cf

Works in

1. 2026-10-19
   !CAUTION B 89 / 100

   first audit · source 6e3fcbdbb5cf

Questions about Competitor Alternatives

• github.com/borghei/Claude-Skills/tree/main/business-growth/compe — the audited source at commit 6e3fcbdbb5cf and every finding aboveObserved · 19 Oct 2026

Spotted something wrong? Report a correction · Methodology