ourdigital/our-claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(seo-skills): multi-backend Data Source Selection (#7)

Browse Source 
Replaces single-vendor (Ahrefs-only) tool defaults with a per-task
backend menu across all 14 SEO skills. Each skill now lists every
capable MCP in allowed-tools and documents how to pick between
Semrush, Ahrefs, OurSEO Agent (CLI + MCP), DataForSEO, and GSC
in its SKILL.md Data Source Selection section.

Tool stubs (~40 new files) populated per skill with capability
deltas, call patterns, and explicit "not for this skill when"
callouts so the menu is self-correcting.

Skills affected: 19-keyword-strategy, 20-serp-analysis,
21-position-tracking, 22-link-building, 23-content-strategy,
24-ecommerce, 25-kpi-framework, 26-international, 27-ai-visibility,
28-knowledge-graph, 31-competitor-intel, 32-crawl-budget,
33-migration-planner, 34-reporting-dashboard.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Andrew Yim
2026-05-14 03:15:32 +09:00
committed by GitHub
parent 1ca84f67ed
commit e527fb4b0f
71 changed files with 2647 additions and 258 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
custom-skills/33-seo-migration-planner/desktop/tools/gsc.md Normal file
View File

@@ -0,0 +1,54 @@
# Google Search Console
**Required** for migration baseline + post-launch monitoring. GSC is the only source for first-party impressions / clicks per URL pre-migration — modelled estimates from Semrush/Ahrefs cannot substitute.
## CLI commands
```bash
# Pre-migration baseline (PULL THIS BEFORE THE MIGRATION DATE)
our research search-console pages --site sc-domain:<old-domain> --days 90
our research search-console combined --site sc-domain:<old-domain> --days 90
our research search-console queries --site sc-domain:<old-domain> --days 90
# Post-migration (after new domain is verified in GSC)
our research search-console pages --site sc-domain:<new-domain> --days 28
our research search-console combined --site sc-domain:<new-domain> --days 28
```
`sc-domain:` prefix for Domain-verified properties; URL-prefix uses plain URL.
## Baseline checklist
Pre-migration, capture at minimum:
| File | Source | Window |
|---|---|---|
| `gsc-pages-90d.json` | `our research search-console pages` | 90 days pre-migration |
| `gsc-combined-90d.json` | `our research search-console combined` | 90 days pre-migration |
| `gsc-queries-90d.json` | `our research search-console queries` | 90 days pre-migration |
Store these alongside the OurSEO crawl baseline in the migration workspace.
## Post-launch monitoring
1. Wait for the new domain to verify in GSC (~24h after DNS propagation + sitemap submission).
2. Pull `pages` and `combined` on the new domain at +7d, +14d, +28d, +60d, +90d.
3. Diff against the baseline: which URLs lost impressions? Which queries dropped?
4. Cross-reference with OurSEO redirect verification — broken redirects are the most common cause of impression loss.
## Ahrefs GSC alternates
If both old and new domains are connected as Ahrefs projects:
```
mcp__ahrefs__gsc-pages(project_id="<id>")
mcp__ahrefs__gsc-pages-history(project_id="<id>")
mcp__ahrefs__gsc-performance-history(project_id="<id>")
```
## Not for this skill when
- **Pre-migration baseline before GSC verification** of the property — not possible. Get the domain verified well in advance.
- **Competitor migration analysis** — GSC is single-site.
Gotcha: `our-claude-skills/custom-skills/15-seo-search-console/code/gotcha/gsc-cli-integration.md`.