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.
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:
Your Product
Core value proposition
Key differentiators
Ideal customer profile
Pricing model
Strengths and honest weaknesses
Competitive Landscape
Direct competitors
Indirect/adjacent competitors
Market positioning of each
Search volume for competitor terms
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:
Why people look for alternatives (validate their pain)
Summary: You as the alternative (quick positioning)
Detailed comparison (features, service, pricing)
Who should switch (and who shouldn't)
Migration path
Social proof from switchers
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:
Why people look for alternatives (common pain points)
What to look for in an alternative (criteria framework)
List of alternatives (you first, but include real options)
Comparison table (summary)
Detailed breakdown of each alternative
Recommendation by use case
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:
TL;DR summary (key differences in 2-3 sentences)
At-a-glance comparison table
Detailed comparison by category:
Features
Pricing
Service & support
Ease of use
Integrations
Who [You] is best for
Who [Competitor] is best for (be honest)
What customers say (testimonials from switchers)
Migration support
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)
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:
Headline: "[Your Product] as an Alternative"
Brief intro on why people switch to you
List of all alternative pages with:
Competitor name/logo
One-line summary of key differentiator vs. that competitor
Link to full comparison
Common reasons people switch (aggregated)
CTA
Example:
## Explore [Your Product] as an Alternative
Looking to switch? See how [Your Product] compares to the tools you're evaluating:
- **[Notion Alternative](#)** — Better for teams who need [X]
- **[Airtable Alternative](#)** — Better for teams who need [Y]
- **[Monday Alternative](#)** — Better for teams who need [Z]
Alternatives (Plural) Index
URL: /alternatives/compare or /best-alternatives
Purpose: Lists all "[Competitor] Alternatives" roundup pages
Page structure:
Headline: "Software Alternatives & Comparisons"
Brief intro on your comparison methodology
List of all alternatives roundup pages with:
Competitor name
Number of alternatives covered
Link to roundup
CTA
Example:
## Find the Right Tool
Comparing your options? Our guides cover the top alternatives:
- **[Best Notion Alternatives](#)** — 7 tools compared
- **[Best Airtable Alternatives](#)** — 6 tools compared
- **[Best 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:
Headline: "Compare [Your Product]"
Section: "[Your Product] vs Competitors" — list of direct comparisons
Section: "Head-to-Head Comparisons" — list of [A] vs [B] pages
Brief methodology note
CTA
Example:
## Compare [Your Product]
### [Your Product] vs. the Competition
- **[[Your Product] vs Notion](#)** — Best for [differentiator]
- **[[Your Product] vs Airtable](#)** — Best for [differentiator]
- **[[Your Product] vs Monday](#)** — Best for [differentiator]
### Other Comparisons
Evaluating tools we compete with? We've done the research:
- **[Notion vs Airtable](#)**
- **[Notion vs Monday](#)**
- **[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 credibility
Number of pages/comparisons available
Quick filters if you have many comparisons
Content Architecture
Centralized Competitor Data
Create a single source of truth for each competitor:
Add new feature comparison once, appears on all pages
Consistent accuracy across pages
Easier to maintain at scale
Section Templates
TL;DR Summary
Start every page with a quick summary for scanners:
**TL;DR**: [Competitor] excels at [strength] but struggles with [weakness].
[Your product] is built for [your focus], offering [key differentiator].
Choose [Competitor] if [their ideal use case]. Choose [You] if [your ideal use case].
Paragraph Comparison (Not Just Tables)
For each major dimension, write a paragraph:
## Features
[Competitor] offers [description of their feature approach].
Their strength is [specific strength], which works well for [use case].
However, [limitation] can be challenging for [user type].
[Your product] takes a different approach with [your approach].
This means [benefit], though [honest tradeoff].
Teams who [specific need] often find this more effective.
Feature Comparison Section
Go beyond checkmarks:
## Feature Comparison
### [Feature Category]
**[Competitor]**: [2-3 sentence description of how they handle this]
- Strengths: [specific]
- Limitations: [specific]
**[Your product]**: [2-3 sentence description]
- Strengths: [specific]
- Limitations: [specific]
**Bottom line**: Choose [Competitor] if [scenario]. Choose [You] if [scenario].
Pricing Comparison Section
## Pricing
| | [Competitor] | [Your Product] |
|---|---|---|
| Free tier | [Details] | [Details] |
| Starting price | $X/user/mo | $X/user/mo |
| Business tier | $X/user/mo | $X/user/mo |
| Enterprise | Custom | Custom |
**What's included**: [Competitor]'s $X plan includes [features], while
[Your product]'s $X plan includes [features].
**Total cost consideration**: Beyond per-seat pricing, consider [hidden costs,
add-ons, implementation]. [Competitor] charges extra for [X], while
[Your product] includes [Y] in base pricing.
**Value comparison**: For a 10-person team, [Competitor] costs approximately
$X/year while [Your product] costs $Y/year, with [key differences in what you get].
Service & Support Comparison
## Service & Support
| | [Competitor] | [Your Product] |
|---|---|---|
| Documentation | [Quality assessment] | [Quality assessment] |
| Response time | [SLA if known] | [Your SLA] |
| Support channels | [List] | [List] |
| Onboarding | [What they offer] | [What you offer] |
| CSM included | [At what tier] | [At what tier] |
**Support quality**: Based on [G2/Capterra reviews, your research],
[Competitor] support is described as [assessment]. Common feedback includes
[quotes or themes].
[Your product] offers [your support approach]. [Specific differentiator like
response time, dedicated CSM, implementation help].
Who It's For Section
## Who Should Choose [Competitor]
[Competitor] is the right choice if:
- [Specific use case or need]
- [Team type or size]
- [Workflow or requirement]
- [Budget or priority]
**Ideal [Competitor] customer**: [Persona description in 1-2 sentences]
## Who Should Choose [Your Product]
[Your product] is built for teams who:
- [Specific use case or need]
- [Team type or size]
- [Workflow or requirement]
- [Priority or value]
**Ideal [Your product] customer**: [Persona description in 1-2 sentences]
Migration Section
## Switching from [Competitor]
### What transfers
- [Data type]: [How easily, any caveats]
- [Data type]: [How easily, any caveats]
### What needs reconfiguration
- [Thing]: [Why and effort level]
- [Thing]: [Why and effort level]
### Migration support
We offer [migration support details]:
- [Free data import tool / white-glove migration]
- [Documentation / migration guide]
- [Timeline expectation]
- [Support during transition]
### What customers say about switching
> "[Quote from customer who switched]"
> — [Name], [Role] at [Company]
Social Proof Section
Focus on switchers:
## What Customers Say
### Switched from [Competitor]
> "[Specific quote about why they switched and outcome]"
> — [Name], [Role] at [Company]
> "[Another quote]"
> — [Name], [Role] at [Company]
### Results after switching
- [Company] saw [specific result]
- [Company] reduced [metric] by [amount]
Comparison Table Best Practices
Beyond Checkmarks
Instead of:
Feature
You
Competitor
Feature A
✓
✓
Feature B
✓
✗
Do this:
Feature
You
Competitor
Feature A
Full support with [detail]
Basic support, [limitation]
Feature B
[Specific capability]
Not available
Organize by Category
Group features into meaningful categories:
Core functionality
Collaboration
Integrations
Security & compliance
Support & service
Include Ratings Where Useful
Category
You
Competitor
Notes
Ease of use
⭐⭐⭐⭐⭐
⭐⭐⭐⭐
[Brief note]
Feature depth
⭐⭐⭐⭐
⭐⭐⭐⭐⭐
[Brief note]
Research Process
Deep Competitor Research
For each competitor, gather:
Product research
Sign up for free trial
Use the product yourself
Document features, UX, limitations
Take screenshots
Pricing research
Current pricing (check regularly)
What's included at each tier
Hidden costs, add-ons
Contract terms
Review mining
G2, Capterra, TrustRadius reviews
Common praise themes
Common complaint themes
Ratings by category
Customer feedback
Talk to customers who switched
Talk to prospects who chose competitor
Document real quotes
Content research
Their positioning and messaging
Their comparison pages (how do they compare to you?)
Their documentation quality
Their changelog (recent development)
Ongoing Updates
Competitor pages need maintenance:
Quarterly: Verify pricing, check for major feature changes
When notified: Customer mentions competitor change
Annually: Full refresh of all competitor data
SEO Considerations
Keyword Targeting
Format
Primary Keywords
Secondary Keywords
Alternative (singular)
[Competitor] alternative
alternative to [Competitor], switch from [Competitor], [Competitor] replacement
Alternatives (plural)
[Competitor] alternatives
best [Competitor] alternatives, tools like [Competitor], [Competitor] competitors
You vs Competitor
[You] vs [Competitor]
[Competitor] vs [You], [You] compared to [Competitor]
Competitor vs Competitor
[A] vs [B]
[B] vs [A], [A] or [B], [A] compared to [B]
Internal Linking
Link between related competitor pages
Link from feature pages to relevant comparisons
Link from blog posts mentioning competitors
Hub page linking to all competitor content
Schema Markup
Consider FAQ schema for common questions:
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the best alternative to [Competitor]?",
"acceptedAnswer": {
"@type": "Answer",
"text": "[Your answer positioning yourself]"
}
}
]
}
Output Format
Competitor Data File
# [competitor].yaml
# Complete competitor profile for use across all comparison pages
Page Content
For each page:
URL and meta tags
Full page copy organized by section
Comparison tables
CTAs
Page Set Plan
Recommended pages to create:
[List of alternative pages]
[List of vs pages]
Priority order based on search volume
Questions to Ask
If you need more context:
Who are your top 3-5 competitors?
What's your core differentiator?
What are common reasons people switch to you?
Do you have customer quotes about switching?
What's your pricing vs. competitors?
Do you offer migration support?
Related Skills
programmatic-seo: For building competitor pages at scale
copywriting: For writing compelling comparison copy
seo-audit: For optimizing competitor pages
schema-markup: For FAQ and comparison schema
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
