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

2.2 KiB

Raw Blame History

Semrush MCP

Default keyword-research backend per SKILL.md > Data Source Selection.

Call pattern

The Semrush MCP follows a three-step discovery → schema → execute pattern (see Semrush MCP server instructions):

Discovery — pick the right toolkit for the task:
- mcp__semrush__keyword_research — keyword overview, related, volume, intent, KD
- mcp__semrush__organic_research — domain/URL organic keywords + competitors
- mcp__semrush__overview_research — domain/URL overview (traffic, ranking dist.)
- mcp__semrush__url_research — single-URL deep dive
mcp__semrush__get_report_schema(report_id=...) — fetch the param spec for the chosen report.
mcp__semrush__execute_report(report_id=..., params={...}) — run it.

Default database="us" when the user does not specify a market. Use display_limit=30-50 for exploratory queries.

Available reports (keyword-research toolkit)

Keyword overview (volume, CPC, competition, KD, trend)
Related keywords
Matching phrases (broad / phrase / exact match)
Keyword difficulty (single + bulk)
Search intent
Keyword historical volume

Configuration

Parameter	Value
Default database	`us`
Korean market database	`kr`
Japan market database	`jp`
Auth	Semrush API key on the MCP server side (no local config)

Examples

English keyword volume:

mcp__semrush__keyword_research(query="enterprise CRM software", database="us")
→ pick report_id from response
mcp__semrush__get_report_schema(report_id="phrase_this")
mcp__semrush__execute_report(report_id="phrase_this", params={"phrase": "enterprise CRM software", "database": "us"})

Korean expansion:

mcp__semrush__keyword_research(query="신라호텔", database="kr")
mcp__semrush__execute_report(report_id="phrase_related", params={"phrase": "신라호텔", "database": "kr", "display_limit": 50})

When NOT to use Semrush

Task needs GSC first-party query data — use Ahrefs gsc-keywords or our research search-console instead.
Task needs Knowledge Graph entity expansion — use mcp__ourseo__search_knowledge_graph.
Task needs bulk cheap calls at Korean scale — our keywords * CLI (DataForSEO) is usually cheaper.

2.2 KiB Raw Blame History