Files
Andrew Yim e527fb4b0f feat(seo-skills): multi-backend Data Source Selection (#7)
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>
2026-05-14 03:15:32 +09:00

49 lines
2.4 KiB
Markdown

# OurSEO Agent (CLI + MCP)
In the reporting dashboard, OurSEO owns the **technical health**, **indexed pages**, **first-party (GSC / GA4 / GBP)**, **schema coverage**, and **Korean engine** sections.
## Tools used in dashboard sections
| Section | Command / tool |
|---|---|
| Technical health score | `our audit tech https://<site>` |
| Crawl errors / issues | `our analyze mysql-batch --session <id>` |
| Indexed page count | `our research google index --domain <site>` / `mcp__ourseo__check_index` |
| Schema coverage | `our analyze mysql-batch --session <id> --export missing-schema` |
| First-party clicks/impressions | `our research search-console queries --site sc-domain:<site> --days 28` |
| GA4 sessions / channels | `our research ga4 traffic --property-id <id>`, `our research ga4 channels` |
| GBP visibility | `our collect gbp reviews/locations`, `our audit local` |
| Korean SERP / Naver visibility | `our research naver serp "<keyword>"` |
| Knowledge Graph entity status | `our research kg lookup "<entity>"` |
| Content freshness | `our collect crawl https://<site>` |
| SERP spot-check | `mcp__ourseo__check_serp(...)` |
## MCP tools (Claude Desktop equivalents)
```
mcp__ourseo__check_index(domain="<site>")
mcp__ourseo__audit_page(url="<url>", audit_type="tech")
mcp__ourseo__check_serp(keyword="<kw>", domain="<site>", country="kr")
mcp__ourseo__search_knowledge_graph(query="<entity>")
```
## Strengths for the dashboard
- **First-party data routed through one CLI** — GSC + GA4 + GBP all in `our research *`.
- **MySQL workspace** — period-over-period diff is a SQL query, not a re-pull.
- Only path for **Korean engine** + **Knowledge Graph entity** sections.
- **Audit ID format** convention (KW-, RANK-, COMP-, etc.) baked into the CLI — keeps Notion Audit Log entries consistent.
## Reporting rule
Whenever OurSEO feeds a section, list it in the report's **Sources** subsection with the specific command + date window (e.g., `Technical health: OurSEO audit tech (crawl 2026-05-14)`, `GSC: 28-day window 2026-04-16 → 2026-05-14`).
## Not for this skill when
- **Modelled traffic / traffic value** — Semrush `overview_research`.
- **Backlinks / DR** — Ahrefs `site-explorer-domain-rating`.
- **AI visibility / Brand Radar** — Ahrefs `brand-radar-*`.
- **Multi-vendor visibility benchmarks** — pair with Semrush / Ahrefs.
Cross-reference: see skill 25 (KPI framework) for the per-metric backend map used to feed this dashboard.