competitor-alternatives

---
name: competitor-alternatives
description: Use when building competitor comparison or alternative pages for SEO and sales enablement — vs pages, alternative pages, or competitor-vs-competitor comparisons.
category: Marketing
version: 1.0.0
tools: []
---

# Competitor & Alternative Pages

Build competitor comparison and alternative pages that rank for competitive search terms, give evaluators genuine value, and position the product effectively.

## Initial Assessment

Search the Knowledge Base for product-marketing context before asking questions; use what's there and only ask for what's missing.

Understand before writing: **your product** (core value prop, key differentiators, ICP, pricing model, honest strengths and weaknesses); **the competitive landscape** (direct and indirect/adjacent competitors, each one's market positioning, search volume for competitor terms); **the goal** (SEO traffic capture, sales enablement, conversion from competitor users, or brand positioning).

## Core Principles

1. **Honesty builds trust** — acknowledge competitor strengths, be accurate about your own limitations, never misrepresent a competitor's features. Readers are actively comparing and will verify claims.
2. **Depth over surface** — go beyond feature checklists; explain why differences matter with use cases and scenarios.
3. **Help them decide** — be explicit about who you're best for and who the competitor is best for; reduce evaluation friction rather than just selling.
4. **Modular content architecture** — competitor data lives in one centralized source of truth per competitor; updates propagate to every page that references it.

## Page Formats

**Format 1 — [Competitor] Alternative (singular).** Intent: actively looking to switch from one competitor. URL: `/alternatives/[competitor]`. Keywords: "[Competitor] alternative," "switch from [Competitor]." Structure: why people look for alternatives → you as the alternative → detailed comparison → who should switch (and who shouldn't) → migration path → switcher social proof → CTA.

**Format 2 — [Competitor] Alternatives (plural).** Intent: researching options earlier in the journey. URL: `/alternatives/[competitor]-alternatives`. Keywords: "best [Competitor] alternatives," "tools like [Competitor]." Structure: common pain points → criteria framework for evaluating alternatives → list of alternatives (you first, but 4–7 genuinely real options) → summary comparison table → detailed breakdown per alternative → recommendation by use case → CTA. Including real competitors, not just yourself, is what builds trust and ranks.

**Format 3 — You vs. [Competitor].** Intent: directly comparing you to one named competitor. URL: `/vs/[competitor]`. Structure: TL;DR (2–3 sentence summary of key differences) → at-a-glance comparison table → detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations) → who you're best for → who the competitor is best for (be honest) → switcher testimonials → migration support → CTA.

**Format 4 — [Competitor A] vs. [Competitor B].** Intent: comparing two competitors, not you. URL: `/compare/[a]-vs-[b]`. Structure: overview of both → comparison by category → who each is best for → introduce yourself as the third option → three-way comparison table → CTA. This captures competitor-branded search traffic and positions you as a knowledgeable neutral party.

## Essential Sections

**TL;DR summary** opens every page — key differences in 2–3 sentences for scanners. **Paragraph comparisons** go beyond tables: for each dimension, explain the difference and when it matters. **Feature comparison** describes how each product handles a category, lists strengths/limitations, and gives a bottom-line call. **Pricing comparison** covers tier-by-tier detail, what's included, hidden costs, and total cost at a sample team size. **Who it's for** states the ideal customer for each option explicitly — honest recommendations build trust. **Migration section** covers what transfers, what needs reconfiguring, support offered, and quotes from customers who switched.

## Content Architecture

Maintain one centralized competitor profile per competitor covering: positioning and target audience, pricing across all tiers, feature ratings, strengths and weaknesses, best-for / not-ideal-for, common complaints (from reviews), and migration notes. Every comparison page pulls from this single source so updates propagate everywhere instead of drifting out of sync.

## Research Process

For each competitor: sign up and use the product, documenting features/UX/limitations firsthand; research current pricing including hidden costs; mine reviews on G2, Capterra, and TrustRadius for recurring praise/complaint themes; talk to customers who switched in both directions; and study the competitor's own positioning, comparison pages, and changelog. Refresh quarterly (pricing, major features), whenever a customer flags a competitor change, and fully once a year.

## SEO Considerations

Target keywords by format: Alternative (singular) → "[Competitor] alternative," "alternative to [Competitor]"; Alternatives (plural) → "[Competitor] alternatives," "best [Competitor] alternatives"; You vs. Competitor → "[You] vs [Competitor]" and the reverse; Competitor vs. Competitor → "[A] vs [B]" and the reverse. Link related competitor pages to each other, link from feature pages into relevant comparisons, and build a hub page linking to all competitor content. Consider FAQ schema for questions like "What is the best alternative to [Competitor]?"

## Proactive Triggers

Offer to build competitor page work when: a specific competitor gets named in conversation and no comparison page exists yet; sales reports friction from prospects comparing to a named tool (build a vs-page for enablement); keyword research turns up competitor-branded terms with no coverage (propose a full page set with priority order); a switcher testimonial surfaces (build a migration-focused alternative page around it); or during a pricing-page review, note that detailed pricing comparisons belong on dedicated competitor pages, not the pricing page itself.

## Comparison Matrix Method

Build the feature-by-feature comparison table from the centralized Competitor Intelligence data (features + pricing per competitor) rather than hand-building it fresh for every page — treat that data as the canonical source for every Vs Page's table.

## Output Artifacts

Competitor Intelligence data: centralized profile per competitor (pricing, features, weaknesses, review themes). Page Set Plan: ranked list of pages to build with target keywords and search-volume estimates. Alternative Page copy: complete `/[competitor]-alternative` page with all sections. Vs Page copy: complete `/vs/[competitor]` page with comparison table and CTA. Migration Guide section: reusable copy block for reuse across pages.

## Communication

Every comparison page must be factually accurate, legally safe (no false claims), and fair — pages that only disparage competitors lose credibility with evaluators who are actively comparing. Ground positioning in existing ICP/positioning context before writing. Every claim must be verifiable from public sources or a customer quote.

## Related Work

Hand off to a technical/on-page SEO skill to validate pages before publishing. Hand off to copywriting for narrative sections and CTA polish. Hand off to content-strategy when planning a full competitive content program across many pages rather than a single page. Escalate to a strategic competitive-intelligence skill for C-level analysis beyond page creation. Always ground in existing positioning/ICP context first.