seo-competitor-pages
Generate SEO-optimized competitor comparison and alternatives pages. Covers "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup, and conversion optimization. Use when user says "comparison page", "vs page", "alternatives page", "competitor comparison", or "X vs Y".
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- seo-competitor-pages
- risk
- unknown
- source
- https://github.com/AgriciDaniel/claude-seo
- date_added
- 2026-03-21
- description
- Generate SEO-optimized competitor comparison and alternatives pages. Covers "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup, and conversion optimization. Use when user says "comparison page", "vs page", "alternatives page", "competitor comparison", or "X vs Y".
- allowed-tools
- [ "Read", "Grep", "Glob", "Bash", "WebFetch" ]
- argument-hint
- [url or generate] [competitor]
- user-invokable
- true
03 SKILL.md 正文
Competitor Comparison & Alternatives Pages
Create high-converting comparison and alternatives pages that target competitive intent keywords with accurate, structured content.
When to Use
- Use when creating
X vs Ycomparison pages or alternatives pages. - Use when targeting competitor-intent keywords with SEO landing pages.
- Use when the user needs structured comparison content, feature matrices, or conversion-oriented competitor pages.
Page Types
1. "X vs Y" Comparison Pages
- Direct head-to-head comparison between two products/services
- Balanced feature-by-feature analysis
- Clear verdict or recommendation with justification
- Target keyword:
[Product A] vs [Product B]
2. "Alternatives to X" Pages
- List of alternatives to a specific product/service
- Each alternative with brief summary, pros/cons, best-for use case
- Target keyword:
[Product] alternatives,best alternatives to [Product]
3. "Best [Category] Tools" Roundup Pages
- Curated list of top tools/services in a category
- Ranking criteria clearly stated
- Target keyword:
best [category] tools [year],top [category] software
4. Comparison Table Pages
- Feature matrix with multiple products in columns
- Sortable/filterable if interactive
- Target keyword:
[category] comparison,[category] comparison chart
Comparison Table Generation
Feature Matrix Layout
| Feature | Your Product | Competitor A | Competitor B |
|------------------|:------------:|:------------:|:------------:|
| Feature 1 | ✅ | ✅ | ❌ |
| Feature 2 | ✅ | ⚠️ Partial | ✅ |
| Feature 3 | ✅ | ❌ | ❌ |
| Pricing (from) | $X/mo | $Y/mo | $Z/mo |
| Free Tier | ✅ | ❌ | ✅ |
Data Accuracy Requirements
- All feature claims must be verifiable from public sources
- Pricing must be current (include "as of [date]" note)
- Update frequency: review quarterly or when competitors ship major changes
- Link to source for each competitor data point where possible
Schema Markup Recommendations
Product Schema with AggregateRating
{
"@context": "https://schema.org",
"@type": "Product",
"name": "[Product Name]",
"description": "[Product Description]",
"brand": {
"@type": "Brand",
"name": "[Brand Name]"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "[Rating]",
"reviewCount": "[Count]",
"bestRating": "5",
"worstRating": "1"
}
}
SoftwareApplication (for software comparisons)
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "[Software Name]",
"applicationCategory": "[Category]",
"operatingSystem": "[OS]",
"offers": {
"@type": "Offer",
"price": "[Price]",
"priceCurrency": "USD"
}
}
ItemList (for roundup pages)
{
"@context": "https://schema.org",
"@type": "ItemList",
"name": "Best [Category] Tools [Year]",
"itemListOrder": "https://schema.org/ItemListOrderDescending",
"numberOfItems": "[Count]",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "[Product Name]",
"url": "[Product URL]"
}
]
}
Keyword Targeting
Comparison Intent Patterns
| Pattern | Example | Search Volume Signal |
|---|---|---|
[A] vs [B] |
"Slack vs Teams" | High |
[A] alternative |
"Figma alternatives" | High |
[A] alternatives [year] |
"Notion alternatives 2026" | High |
best [category] tools |
"best project management tools" | High |
[A] vs [B] for [use case] |
"AWS vs Azure for startups" | Medium |
[A] review [year] |
"Monday.com review 2026" | Medium |
[A] vs [B] pricing |
"HubSpot vs Salesforce pricing" | Medium |
is [A] better than [B] |
"is Notion better than Confluence" | Medium |
Title Tag Formulas
- X vs Y:
[A] vs [B]: [Key Differentiator] ([Year]) - Alternatives:
[N] Best [A] Alternatives in [Year] (Free & Paid) - Roundup:
[N] Best [Category] Tools in [Year], Compared & Ranked
H1 Patterns
- Match title tag intent
- Include primary keyword naturally
- Keep under 70 characters
Conversion-Optimized Layouts
CTA Placement
- Above fold: Brief comparison summary with primary CTA
- After comparison table: "Try [Your Product] free" CTA
- Bottom of page: Final recommendation with CTA
- Avoid aggressive CTAs in competitor description sections (reduces trust)
Social Proof Sections
- Customer testimonials relevant to comparison criteria
- G2/Capterra/TrustPilot ratings (with source links)
- Case studies showing migration from competitor
- "Switched from [Competitor]" stories
Pricing Highlights
- Clear pricing comparison table
- Highlight value advantages (not just lowest price)
- Include hidden costs (setup fees, per-user pricing, overage charges)
- Link to full pricing page
Trust Signals
- "Last updated [date]" timestamp
- Author with relevant expertise
- Methodology disclosure (how comparisons were conducted)
- Disclosure of own product affiliation
Fairness Guidelines
- Accuracy: All competitor information must be verifiable from public sources
- No defamation: Never make false or misleading claims about competitors
- Cite sources: Link to competitor websites, review sites, or documentation
- Timely updates: Review and update when competitors release major changes
- Disclose affiliation: Clearly state which product is yours
- Balanced presentation: Acknowledge competitor strengths honestly
- Pricing accuracy: Include "as of [date]" disclaimers on all pricing data
- Feature verification: Test competitor features where possible, cite documentation otherwise
Internal Linking
- Link to your own product/service pages from comparison sections
- Cross-link between related comparison pages (e.g., "A vs B" links to "A vs C")
- Link to feature-specific pages when discussing individual features
- Breadcrumb: Home > Comparisons > [This Page]
- Related comparisons section at bottom of page
- Link to case studies and testimonials mentioned in the comparison
Output
Comparison Page Template
COMPARISON-PAGE.md: Ready-to-implement page structure with sections- Feature matrix table
- Content outline with word count targets (minimum 1,500 words)
Schema Markup
comparison-schema.json: Product/SoftwareApplication/ItemList JSON-LD
Keyword Strategy
- Primary and secondary keywords
- Related long-tail opportunities
- Content gaps vs existing competitor pages
Recommendations
- Content improvements for existing comparison pages
- New comparison page opportunities
- Schema markup additions
- Conversion optimization suggestions
Error Handling
| Scenario | Action |
|---|---|
| Competitor URL unreachable | Report which competitor URLs failed. Proceed with available data and note gaps in the comparison. |
| Insufficient competitor data (pricing, features unavailable) | Flag missing data points clearly. Use "Not publicly available" in comparison tables rather than guessing. |
| No product/service overlap found | Report that the products serve different markets. Suggest alternative competitors that share feature overlap, or pivot to a category roundup format. |
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.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.