142 lines
4.6 KiB
Markdown
142 lines
4.6 KiB
Markdown
---
|
|
name: seo-competitor-intel
|
|
description: |
|
|
Competitor intelligence and SEO benchmarking.
|
|
Triggers: competitor analysis, competitive intelligence, competitor comparison,
|
|
threat assessment, market position, benchmarking, 경쟁사 분석,
|
|
경쟁 인텔리전스, 벤치마킹, 경쟁사 비교.
|
|
---
|
|
|
|
# SEO Competitor Intelligence & Benchmarking
|
|
|
|
## Purpose
|
|
|
|
Comprehensive competitor intelligence for SEO: auto-discover competitors, build profile cards, create head-to-head comparison matrices, analyze keyword overlap, track traffic trends, and score competitive threats. Supports Korean market analysis including Naver Blog/Cafe presence.
|
|
|
|
## Core Capabilities
|
|
|
|
1. **Competitor Discovery** - Auto-discover organic competitors via our-seo-agent CLI
|
|
2. **Profile Cards** - DR, traffic, keywords, referring domains, top pages, content volume
|
|
3. **Comparison Matrix** - Multi-dimensional head-to-head comparison
|
|
4. **Keyword Overlap** - Shared, unique, and gap keyword analysis
|
|
5. **Threat Scoring** - 0-100 score based on DR gap, traffic ratio, keyword overlap, growth
|
|
6. **Competitive Monitoring** - Traffic trends, DR changes, keyword movement, content velocity
|
|
7. **Alert Generation** - Flag significant competitive movements
|
|
8. **Market Share Estimation** - Organic traffic share within competitive set
|
|
|
|
## MCP Tool Usage
|
|
|
|
### SEO Data
|
|
```
|
|
our-seo-agent CLI: Primary competitive data source (future); use --input for pre-fetched JSON
|
|
WebSearch / WebFetch: Supplementary competitor data
|
|
```
|
|
|
|
### Notion for Report Storage
|
|
```
|
|
mcp__notion__notion-create-pages: Save reports to SEO Audit Log
|
|
```
|
|
|
|
### WebSearch for Korean Market
|
|
```
|
|
WebSearch: Check Naver Blog/Cafe presence for competitors
|
|
```
|
|
|
|
## Workflow
|
|
|
|
### Competitor Profiling
|
|
1. Accept target URL/domain
|
|
2. Auto-discover competitors via our-seo-agent CLI or use provided list
|
|
3. Build profile card for target and each competitor (DR, traffic, keywords, backlinks, content)
|
|
4. Analyze keyword overlap between target and each competitor
|
|
5. Build multi-dimensional comparison matrix
|
|
6. Score competitive threats (0-100)
|
|
7. Determine market position (leader/challenger/follower/niche)
|
|
8. If Korean market: check Naver Blog/Cafe presence
|
|
|
|
### Competitive Monitoring
|
|
1. Accept target, competitors, and monitoring period
|
|
2. Fetch traffic trend history for all domains
|
|
3. Fetch DR trend history for all domains
|
|
4. Track keyword movement (new/lost keywords)
|
|
5. Compare content publication velocity
|
|
6. Generate alerts for significant changes (>20% traffic, DR jump, keyword surge)
|
|
7. Estimate market share within competitive set
|
|
|
|
## Output Format
|
|
|
|
### Profiling Report
|
|
```markdown
|
|
## Competitor Intelligence Report: [domain]
|
|
|
|
### Target Profile
|
|
- Domain Rating: [DR]
|
|
- Organic Traffic: [traffic]
|
|
- Keywords: [count]
|
|
- Referring Domains: [count]
|
|
|
|
### Competitors (by threat score)
|
|
1. **[competitor.com]** - Threat: [score]/100
|
|
- DR: [value] | Traffic: [value] | Keywords: [value]
|
|
- Keyword Overlap: [shared] shared, [gap] gap
|
|
- Strengths: [list]
|
|
- Weaknesses: [list]
|
|
|
|
### Comparison Matrix
|
|
| Dimension | Target | Comp1 | Comp2 |
|
|
|-----------|--------|-------|-------|
|
|
|
|
### Market Position: [leader/challenger/follower/niche]
|
|
```
|
|
|
|
### Monitoring Report
|
|
```markdown
|
|
## Competitive Monitoring Report: [domain]
|
|
### Period: [N] days
|
|
|
|
### Alerts
|
|
- [severity] [message]
|
|
|
|
### Traffic Trends
|
|
| Domain | Direction | Growth | Current |
|
|
|
|
### Keyword Movements
|
|
| Domain | New | Lost | Net |
|
|
|
|
### Market Share
|
|
| Domain | Traffic% | Overall% |
|
|
```
|
|
|
|
## Threat Scoring Methodology
|
|
|
|
| Factor | Weight | Scale |
|
|
|--------|--------|-------|
|
|
| DR Gap | 20% | -30 to +30 mapped to 0-100 |
|
|
| Traffic Ratio | 30% | 0x to 2x+ mapped to 0-100 |
|
|
| Keyword Overlap | 25% | 0-50%+ mapped to 0-100 |
|
|
| Gap Keywords | 25% | Ratio to target keywords |
|
|
|
|
## Alert Thresholds
|
|
|
|
| Alert Type | Threshold | Severity |
|
|
|------------|-----------|----------|
|
|
| Traffic change | >20% | warning; >50% critical |
|
|
| DR change | >3 points | warning; >5 critical |
|
|
| Keyword surge | >15% growth | warning |
|
|
| Content burst | >2x avg velocity | info |
|
|
|
|
## Limitations
|
|
|
|
- Data freshness depends on source and collection method
|
|
- Keyword overlap limited to top 1,000 keywords per domain
|
|
- Content velocity based on page index data (not real-time crawl)
|
|
- Naver presence detection is heuristic-based
|
|
|
|
## Notion Output (Required)
|
|
|
|
All reports MUST be saved to OurDigital SEO Audit Log:
|
|
- **Database ID**: `2c8581e5-8a1e-8035-880b-e38cefc2f3ef`
|
|
- **Properties**: Issue (title), Site (url), Category ("Competitor Intelligence"), Priority, Found Date, Audit ID
|
|
- **Language**: Korean with English technical terms
|
|
- **Audit ID Format**: COMP-YYYYMMDD-NNN
|