Competitor & Alternative Pages
Create comparison and alternative pages that rank and convert. Honesty, depth, help evaluators decide. Use product-marketing-context.
How to Install
Using npx (recommended):
npx skills add github.com/coreyhaines31/marketingskills --skill competitor-alternativesThis will automatically download and install the skill in your .cursor/skills/ directory.
Or install manually:
- Copy the skill content below
- Create folder:
.cursor/skills/competitor-alternatives/in your project - Save as
SKILL.md - Cursor auto-discovers skills when you start a chat
Or install globally to ~/.cursor/skills/competitor-alternatives/SKILL.md
SKILL.md
--- name: competitor-alternatives description: Build competitor comparison and alternative pages. Read product-marketing-context first. --- # 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 **Check for product marketing context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Before creating competitor pages, understand: (1) Your Product: Core value prop, key differentiators, ideal customer, pricing, strengths and honest weaknesses. (2) Competitive Landscape: Direct/indirect competitors, market positioning, search volume. (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 AND who competitor is best for. Reduce evaluation friction. **4. Modular Content Architecture:** Competitor data should be centralized. Updates propagate to all pages. Single source of truth per competitor. ## Page Formats **Format 1: [Competitor] Alternative (Singular)** Search intent: User actively looking to switch. URL: /alternatives/[competitor]. Keywords: "[Competitor] alternative", "alternative to [Competitor]". Structure: Why people look for alternatives → You as the alternative → Detailed comparison → Who should switch → Migration path → Social proof → CTA. **Format 2: [Competitor] Alternatives (Plural)** Search intent: User researching options. URL: /alternatives/[competitor]-alternatives. Keywords: "[Competitor] alternatives", "best [Competitor] alternatives". Structure: Why look for alternatives → Criteria framework → List 4-7 alternatives (you first) → Comparison table → Detailed breakdown → Recommendation by use case → CTA. Important: Include 4-7 real alternatives, being genuinely helpful builds trust and ranks better. **Format 3: You vs [Competitor]** Search intent: Direct comparison. URL: /vs/[competitor]. Keywords: "[You] vs [Competitor]", "[Competitor] vs [You]". Structure: TL;DR summary → Comparison table → Detailed by category → Who each is best for → Testimonials → Migration support → CTA. **Format 4: [Competitor A] vs [Competitor B]** Search intent: User comparing two competitors (not you). URL: /compare/[a]-vs-[b]. Structure: Overview of both → Comparison → Who each is for → The third option (introduce yourself) → Table with all three → CTA. Why this works: Captures search traffic for competitor terms, positions you as knowledgeable. ## Essential Sections **TL;DR Summary:** Key differences in 2-3 sentences for scanners. **Paragraph Comparisons:** Beyond tables. For each dimension, write a paragraph explaining differences and when each matters. **Feature Comparison:** For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation. **Pricing Comparison:** Tier-by-tier, what's included, hidden costs, total cost calculation for sample team size. **Who It's For:** Explicit ideal customer for each option. Honest recommendations build trust. **Migration Section:** What transfers, what needs reconfiguration, support offered, quotes from customers who switched. ## Content Architecture **Centralized Competitor Data:** Create single source of truth for each competitor with: positioning and target audience, pricing (all tiers), feature ratings, strengths and weaknesses, best for / not ideal for, common complaints (from reviews), migration notes. ## Research Process **Deep Competitor Research:** For each competitor: (1) Product research: Sign up, use it, document features/UX/limitations. (2) Pricing research: Current pricing, included features, hidden costs. (3) Review mining: G2, Capterra, TrustRadius for common themes. (4) Customer feedback: Talk to customers who switched (both directions). (5) Content research: Their positioning, comparison pages, changelog. **Ongoing Updates:** Quarterly: Verify pricing, check major feature changes. When notified: Customer mentions competitor change. Annually: Full refresh of all competitor data. ## SEO Considerations **Keyword Targeting:** * Alternative (singular): [Competitor] alternative, alternative to [Competitor] * Alternatives (plural): [Competitor] alternatives, best [Competitor] alternatives * You vs Competitor: [You] vs [Competitor], [Competitor] vs [You] * Competitor vs Competitor: [A] vs [B], [B] vs [A] **Internal Linking:** Link between related competitor pages. Link from feature pages to relevant comparisons. Create hub page linking to all competitor content. **Schema Markup:** Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"
Best For
Related Skills
Design Engineering
Emil Kowalski's design engineering skill: UI polish, animation decisions, component patterns, and the invisible details that make interfaces feel right.
Tailwind Design System
Build scalable design systems with Tailwind CSS v4: CSS-first tokens, OKLCH theming, CVA components, dark mode, and v3-to-v4 migration patterns.
Stitch DESIGN.md
Analyze Stitch projects and generate semantic DESIGN.md files from screen metadata, HTML/CSS, and assets. Produces atmosphere, color roles, typography, component styling, and layout principles.
Taste Design
Generate premium, non-generic DESIGN.md guidelines for Stitch with strict anti-pattern bans, semantic design language, and responsive/motion constraints.