Fix SEO skill 34 bugs, Korean labels, and transition Ahrefs refs to our-seo-agent (#2)

This commit is contained in:
Andrew Yim
2026-02-14 01:09:35 +09:00
committed by GitHub
parent d2d0a2d460
commit a28bfbf847
34 changed files with 265 additions and 262 deletions

View File

@@ -8,12 +8,12 @@ description: |
## Purpose
Comprehensive site migration planning and post-migration monitoring for SEO: crawl-based URL inventory, traffic/keyword baseline capture via Ahrefs, redirect map generation with per-URL risk scoring, pre-migration checklist creation, and post-launch traffic/indexation/ranking recovery tracking with automated alerts. Supports domain moves, platform changes, URL restructuring, HTTPS migrations, and subdomain consolidation.
Comprehensive site migration planning and post-migration monitoring for SEO: crawl-based URL inventory, traffic/keyword baseline capture via our-seo-agent CLI, redirect map generation with per-URL risk scoring, pre-migration checklist creation, and post-launch traffic/indexation/ranking recovery tracking with automated alerts. Supports domain moves, platform changes, URL restructuring, HTTPS migrations, and subdomain consolidation.
## Core Capabilities
1. **URL Inventory** - Crawl entire site via Firecrawl to capture all URLs and status codes
2. **Traffic Baseline** - Capture per-page traffic, keywords, and backlinks via Ahrefs
2. **Traffic Baseline** - Capture per-page traffic, keywords, and backlinks via our-seo-agent CLI
3. **Redirect Map Generation** - Create old URL -> new URL mappings with 301 redirect rules
4. **Risk Scoring** - Score each URL (0-100) based on traffic, backlinks, and keyword rankings
5. **Pre-Migration Checklist** - Generate type-specific migration checklist (Korean)
@@ -26,15 +26,10 @@ Comprehensive site migration planning and post-migration monitoring for SEO: cra
## MCP Tool Usage
### Ahrefs for SEO Baseline & Monitoring
### SEO Data
```
mcp__ahrefs__site-explorer-metrics: Current organic metrics (traffic, keywords)
mcp__ahrefs__site-explorer-metrics-history: Historical metrics for pre/post comparison
mcp__ahrefs__site-explorer-top-pages: Top performing pages for baseline
mcp__ahrefs__site-explorer-pages-by-traffic: Pages ranked by traffic for risk scoring
mcp__ahrefs__site-explorer-organic-keywords: Keyword rankings per page
mcp__ahrefs__site-explorer-referring-domains: Referring domains for risk scoring
mcp__ahrefs__site-explorer-backlinks-stats: Backlink overview for migration impact
our-seo-agent CLI: Primary SEO baseline data source (future); use --input for pre-fetched JSON
WebSearch / WebFetch: Supplementary migration data
```
### Firecrawl for URL Inventory & Redirect Verification
@@ -58,9 +53,9 @@ mcp__perplexity__search: Research migration best practices and common pitfalls
### Pre-Migration Planning
1. Accept target domain, migration type, and new domain (if applicable)
2. Crawl URL inventory via Firecrawl (capture all URLs + status codes)
3. Fetch Ahrefs top pages baseline (traffic, keywords, backlinks per page)
3. Fetch top pages baseline via our-seo-agent CLI or pre-fetched data
4. Fetch site-level metrics (total traffic, keywords, referring domains)
5. Enrich URL inventory with Ahrefs traffic/backlink data
5. Enrich URL inventory with traffic/backlink data from our-seo-agent CLI
6. Score risk per URL (0-100) based on traffic weight (40%), backlinks (30%), keywords (30%)
7. Generate redirect map (old URL -> new URL) based on migration type
8. Aggregate risk assessment (high/medium/low URL counts, overall risk level)
@@ -69,7 +64,7 @@ mcp__perplexity__search: Research migration best practices and common pitfalls
### Post-Migration Monitoring
1. Accept domain, migration date, and optional baseline JSON
2. Compare pre vs post traffic using Ahrefs metrics history
2. Compare pre vs post traffic using our-seo-agent metrics history
3. Check redirect health via Firecrawl (broken, chains, loops)
4. Track indexation changes (pre vs post page count, missing pages)
5. Track keyword ranking changes for priority keywords
@@ -156,7 +151,7 @@ mcp__perplexity__search: Research migration best practices and common pitfalls
## Limitations
- Ahrefs data has ~24h freshness lag
- Data freshness depends on source and collection method
- Firecrawl crawl limited to 5,000 URLs per run
- Redirect chain detection depends on Firecrawl following redirects
- Recovery estimation is heuristic-based on industry averages