From 72a6be6a74c84bb718867a2850c42e38274c46cd Mon Sep 17 00:00:00 2001 From: Andrew Yim Date: Fri, 6 Mar 2026 19:52:40 +0900 Subject: [PATCH] [Claude] feat(skills): update SEO skills to use DataForSEO CLI + MCP tools Co-Authored-By: Claude Opus 4.6 --- .../19-seo-keyword-strategy/desktop/SKILL.md | 44 ++++++++++++++----- .../20-seo-serp-analysis/desktop/SKILL.md | 30 ++++++++++--- .../21-seo-position-tracking/desktop/SKILL.md | 31 ++++++++++--- 3 files changed, 80 insertions(+), 25 deletions(-) diff --git a/custom-skills/19-seo-keyword-strategy/desktop/SKILL.md b/custom-skills/19-seo-keyword-strategy/desktop/SKILL.md index 14df4bf..6c2f03b 100644 --- a/custom-skills/19-seo-keyword-strategy/desktop/SKILL.md +++ b/custom-skills/19-seo-keyword-strategy/desktop/SKILL.md @@ -23,11 +23,31 @@ Expand seed keywords, classify search intent, cluster topics, and identify compe ## MCP Tool Usage -### SEO Data +### SEO Data (DataForSEO) + +**Primary — our-seo-agent CLI:** +```bash +our keywords volume "" --location 2410 --language ko +our keywords ideas "" --location 2410 --limit 50 +our keywords for-site --location 2410 --limit 100 +our keywords intent "" "" "" +our keywords difficulty "" "" ``` -our-seo-agent CLI: Primary keyword data source (future); use --input for pre-fetched JSON -WebSearch / WebFetch: Live keyword research and autocomplete data + +**Interactive fallback — DataForSEO MCP:** ``` +mcp__dfs-mcp__dataforseo_labs_google_keyword_overview +mcp__dfs-mcp__dataforseo_labs_google_keyword_ideas +mcp__dfs-mcp__dataforseo_labs_google_keyword_suggestions +mcp__dfs-mcp__dataforseo_labs_search_intent +mcp__dfs-mcp__dataforseo_labs_bulk_keyword_difficulty +mcp__dfs-mcp__kw_data_google_ads_search_volume +mcp__dfs-mcp__dataforseo_labs_google_keywords_for_site +``` + +### Common Parameters +- **location_code**: 2410 (Korea), 2840 (US), 2392 (Japan) +- **language_code**: ko, en, ja ### Web Search for Naver Discovery ``` @@ -38,10 +58,11 @@ WebSearch: Naver autocomplete and trend discovery ### 1. Seed Keyword Expansion 1. Input seed keyword (Korean or English) -2. Query keyword data via our-seo-agent CLI, pre-fetched JSON, or WebSearch -3. Get search suggestions for long-tail variations -4. Apply Korean suffix expansion if Korean market -5. Deduplicate and merge results +2. Fetch search volume via `our keywords volume "" --location 2410 --language ko` +3. Expand with `our keywords ideas "" --location 2410 --limit 50` +4. Get autocomplete suggestions via MCP: `mcp__dfs-mcp__dataforseo_labs_google_keyword_suggestions` +5. Apply Korean suffix expansion if Korean market +6. Deduplicate and merge results ### 2. Intent Classification & Clustering 1. Classify each keyword by search intent @@ -50,10 +71,11 @@ WebSearch: Naver autocomplete and trend discovery 4. Calculate cluster-level metrics (total volume, avg KD) ### 3. Gap Analysis -1. Pull organic keywords for target and competitors -2. Identify keywords present in competitors but missing from target -3. Score opportunities by volume/difficulty ratio -4. Prioritize by intent alignment with business goals +1. Pull organic keywords for target: `our keywords for-site --location 2410 --limit 100` +2. Pull organic keywords for competitors: `our keywords for-site --location 2410 --limit 100` +3. Identify keywords present in competitors but missing from target +4. Score opportunities by volume/difficulty ratio +5. Prioritize by intent alignment with business goals ## Output Format diff --git a/custom-skills/20-seo-serp-analysis/desktop/SKILL.md b/custom-skills/20-seo-serp-analysis/desktop/SKILL.md index 92a7864..e18e885 100644 --- a/custom-skills/20-seo-serp-analysis/desktop/SKILL.md +++ b/custom-skills/20-seo-serp-analysis/desktop/SKILL.md @@ -21,11 +21,27 @@ Analyze search engine result page composition for Google and Naver. Detect SERP ## MCP Tool Usage -### SEO Data +### SEO Data (DataForSEO) + +**Primary — our-seo-agent CLI:** +```bash +our serp live "" --location 2410 --language ko +our serp competitors --location 2410 +our serp ranked-keywords --location 2410 --limit 50 +our serp domain-overview --location 2410 ``` -our-seo-agent CLI: Primary data source (future); use --input for pre-fetched JSON -WebSearch / WebFetch: Live SERP data and keyword metrics + +**Interactive fallback — DataForSEO MCP:** ``` +mcp__dfs-mcp__serp_organic_live_advanced +mcp__dfs-mcp__dataforseo_labs_google_serp_competitors +mcp__dfs-mcp__dataforseo_labs_google_ranked_keywords +mcp__dfs-mcp__dataforseo_labs_google_domain_rank_overview +``` + +### Common Parameters +- **location_code**: 2410 (Korea), 2840 (US), 2392 (Japan) +- **language_code**: ko, en, ja ### Notion for Report Storage ``` @@ -42,13 +58,13 @@ WebFetch: Fetch Naver SERP HTML for section analysis ## Workflow ### 1. Google SERP Analysis -1. Fetch SERP data via `our-seo-agent` CLI, `--input` JSON, or WebSearch for the target keyword and country -2. Detect SERP features (featured snippet, PAA, local pack, knowledge panel, video, ads, images, shopping) -3. Map competitor positions from organic results (domain, URL, title, position) +1. Fetch SERP via `our serp live "" --location 2410 --language ko --format json` +2. Parse SERP features from response (featured_snippet, people_also_ask, local_pack, etc.) +3. Map competitor positions from organic_results (domain, URL, title, position) 4. Classify content type for each result (blog, product, service, news, video) 5. Calculate opportunity score (0-100) based on feature landscape 6. Validate search intent from SERP composition -7. Assess SERP volatility +7. Get competitor domain overview via `our serp domain-overview --location 2410` ### 2. Naver SERP Analysis 1. Fetch Naver search page for the target keyword diff --git a/custom-skills/21-seo-position-tracking/desktop/SKILL.md b/custom-skills/21-seo-position-tracking/desktop/SKILL.md index 7be7e87..fb57a43 100644 --- a/custom-skills/21-seo-position-tracking/desktop/SKILL.md +++ b/custom-skills/21-seo-position-tracking/desktop/SKILL.md @@ -21,11 +21,27 @@ Monitor keyword ranking positions, detect significant changes, calculate visibil ## MCP Tool Usage -### SEO Data +### SEO Data (DataForSEO) + +**Primary — our-seo-agent CLI:** +```bash +our serp ranked-keywords --location 2410 --limit 100 +our keywords volume "" "" --location 2410 --language ko +our serp domain-overview --location 2410 +our serp competitors --location 2410 ``` -our-seo-agent CLI: Primary ranking data source (future); use --input for pre-fetched JSON -WebSearch: Supplementary ranking data + +**Interactive fallback — DataForSEO MCP:** ``` +mcp__dfs-mcp__dataforseo_labs_google_ranked_keywords +mcp__dfs-mcp__dataforseo_labs_google_domain_rank_overview +mcp__dfs-mcp__dataforseo_labs_google_historical_rank_overview +mcp__dfs-mcp__dataforseo_labs_google_keyword_overview +``` + +### Common Parameters +- **location_code**: 2410 (Korea), 2840 (US), 2392 (Japan) +- **language_code**: ko, en, ja ### Notion for Report Storage ``` @@ -36,10 +52,11 @@ mcp__notion__notion-update-page: Update existing tracking entries ## Workflow ### Phase 1: Data Collection -1. Identify tracking project or use --input for pre-fetched data -2. Retrieve tracked keywords via `management-project-keywords` -3. Fetch current positions via `rank-tracker-overview` -4. Fetch competitor data via `rank-tracker-competitors-overview` (if requested) +1. Fetch current ranked keywords: `our serp ranked-keywords --location 2410 --limit 100 --format json` +2. Get domain overview: `our serp domain-overview --location 2410 --format json` +3. Get search volumes for tracked keywords: `our keywords volume "" "" --location 2410` +4. Fetch competitor positions: `our serp ranked-keywords --location 2410 --limit 100` +5. For historical comparison, use MCP: `mcp__dfs-mcp__dataforseo_labs_google_historical_rank_overview` ### Phase 2: Analysis 1. Detect position changes against previous period