Skill detail
seo-competitor-pages
Generates SEO-optimized competitor comparison and alternatives pages with feature matrices, schema markup, and conversion optimization.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
---
name: seo-competitor-pages
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", "X vs Y", "versus",
"compare competitors", or "alternative to".
user-invocable: true
argument-hint: "[url or generate] [competitor]"
license: MIT
metadata:
author: AgriciDaniel
version: "2.4.2"
category: seo
---
# Competitor Comparison & Alternatives Pages
Create high-converting comparison and alternatives pages that target
competitive intent keywords with accurate, structured content.
## 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
```json
{
"@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)
```json
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "[Software Name]",
"applicationCategory": "[Category]",
"operatingSystem": "[OS]",
"offers": {
"@type": "Offer",
"price": "[Price]",
"priceCurrency": "USD"
}
}
```
### ItemList (for roundup pages)
```json
{
"@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 Read the full source on GitHub (opens external page)