seo-dataforseo
Skill0 starsChanged 3 months agoMITView on GitHub
Live SEO data via DataForSEO MCP server: SERP analysis, keyword research (volume, difficulty, intent, trends), backlink profiles, on-page analysis, competitor and content analysis, business listings, AI visibility (LLM mention tracking), and domain analytics. Requires DataForSEO extension installed. Use when user says "dataforseo", "live SERP", "keyword volume", "backlink data", "AI visibility check", or "real search data".
19 other projects use a version of this, 15 of them edited.
Adopted by
Most recently taken up by
- martinbattaglia-commits/Claude-skillsedited, first seen Nov 16, 2026
- joaoguirunas/team-osedited, first seen Nov 15, 2026
- alpit-patel/seo-aeo-geo-kitedited, first seen Nov 8, 2026
- zhtyyx/codex-seoedited, first seen Nov 1, 2026
- susantedit/claude-skillsword for word, first seen Oct 20, 2026
- webdevarif/claude-skillsedited, first seen Oct 20, 2026
Used with
Projects with it also use seo-agentic.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AgriciDanielSkillseo-agentic
Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 2
- susantedit/claude-skills★ 0100% same
- Yass5002/agent-skills★ 0100% same
Edited · 15
- AgriciDaniel/claude-seo★ 30k90% same
- zhtyyx/codex-seo★ 15289% same
- joaoguirunas/team-os★ 692% same
- avalonreset/legends-seo-dungeon★ 481% same
- alpit-patel/seo-aeo-geo-kit★ 289% same
- agrivisionai/claude-skills★ 196% same
- mahiunfiltered/claude-code-skills★ 196% same
- unknownking07/claude-skills★ 180% same
- bbeliso/belisodw-★ 096% same
- Biznomad/claude-skills★ 096% same
5 more not listed
Wrote their own version · 2
- ZachArticulateV/designer-pro-and-seo★ 10same name
- david-corroy/skills-seo-geo★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- seo-auditSkill
- seo-backlinksSkill
- seo-clusterSkill
- seo-competitor-pagesSkill
- seo-content-briefSkill
- seo-contentSkill
- seo-driftSkill
- seo-ecommerceSkill
- seo-flowSkill
- seo-geoSkill
- seo-googleSkill
- seo-hreflangSkill
- seo-image-genSkill
- seo-imagesSkill
- seo-localSkill
- seo-mapsSkill
- seo-pageSkill
- seo-planSkill
- seo-programmaticSkill
- seo-reportSkill
- seo-schemaSkill
- seo-sitemapSkill
- seoSkill
- seo-sxoSkill
- seo-technicalSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 6 are common, 0 are distinctive, and 12 are very specific to this project.
6
Common
Most of the 16 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Check availability: Before using any DataForSEO tool, verify the MCP server is connected by checking if serp_organic_live_advanced or any …
- Common: line 42
Prefer bulk endpoints over multiple single calls
- Common: line 43
Use default parameters (US, English) unless user specifies otherwise
- Very specific: line 54
If "status": "approved" → proceed with the API call
- Very specific: line 55
If "status": "needs_approval" → show the cost estimate to the user and ask for confirmation before proceeding
- Very specific: line 56
If "status": "blocked" → inform the user that the daily budget limit would be exceeded.
- Common: line 285
Run on-page analysis including Lighthouse audit and content parsing.
- Common: line 328
Search business listings for local SEO competitive analysis.
- Very specific: line 359
Search LLM mentions with ai_opt_llm_ment_search (find mentions of a brand/keyword across LLM responses)
- Very specific: line 366
Advanced: Use ai_opt_llm_ment_cross_agg_metrics for cross-model comparison (how mentions differ across ChatGPT, Claude, Perplexity, etc.).
- Common: line 376
When DataForSEO MCP tools are available, other claude-seo skills can leverage live data:
- Very specific: line 379
seo-technical: Use on_page_instant_pages / on_page_lighthouse for real crawl data, domain_analytics_technologies_domain_technologies for …
- Very specific: line 380
seo-content: Use kw_data_google_ads_search_volume, dataforseo_labs_bulk_keyword_difficulty, dataforseo_labs_search_intent for real keyword …
- Very specific: line 381
seo-page: Use serp_organic_live_advanced for real SERP positions, backlinks_summary for link data
- Very specific: line 382
seo-images: Use serp_google_images_live_advanced for competitor image SERP data, cross-reference with on-page image audit
- Very specific: line 383
seo-geo: Use ai_optimization_chat_gpt_scraper for real ChatGPT visibility, ai_opt_llm_ment_search for LLM mention tracking
- Very specific: line 384
seo-plan: Use dataforseo_labs_google_competitors_domain, dataforseo_labs_google_domain_intersection, …
- Common: line 397
Use tables for comparative data
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
DataForSEO: Live SEO Data (Extension)
Live search data via the DataForSEO MCP server. Provides real-time SERP results (organic + images), keyword metrics, backlink profiles, on-page analysis, content analysis, business listings, AI visibility checking, and LLM mention tracking across 9 API modules with 79+ MCP tools.
Prerequisites
This skill requires the DataForSEO extension to be installed:
./extensions/dataforseo/install.shCheck availability: Before using any DataForSEO tool, verify the MCP server
is connected by checking if serp_organic_live_advanced or any DataForSEO tool
is available. If tools are not available, inform the user the extension is not
installed and provide install instructions.
API Credit Awareness
DataForSEO charges per API call. Be efficient:
- Prefer bulk endpoints over multiple single calls
- Use default parameters (US, English) unless user specifies otherwise
- Cache results mentally within a session; don't re-fetch the same data
- Warn user before running expensive operations (full backlink crawls, large keyword lists)
Cost Guardrails
Before every DataForSEO MCP call, run cost estimation:
claude-seo run dataforseo_costs.py check <endpoint> [--count N]- If
"status": "approved"→ proceed with the API call - If
"status": "needs_approval"→ show the cost estimate to the user and ask for confirmation before proceeding - If
"status": "blocked"→ inform the user that the daily budget limit would be exceeded; do NOT proceed
After each API call completes, log the cost:
claude-seo run dataforseo_costs.py log <endpoint> <actual_cost>User commands for cost management:
/seo dataforseo costs today→ show today's spending breakdown/seo dataforseo costs summary→ show 7-day spending history/seo dataforseo costs config --mode threshold --threshold 0.50→ configure approval mode
Load references/cost-tiers.md for the full pricing table, budget presets, and cost reduction tips.
Quick Reference
| Command | What it does |
/seo dataforseo serp <keyword> | Google organic SERP results |
/seo dataforseo serp-images <keyword> | Google Images SERP results |
/seo dataforseo serp-youtube <keyword> | YouTube search results |
/seo dataforseo youtube <video_id> | YouTube video deep analysis |
/seo dataforseo keywords <seed> | Keyword ideas and suggestions |
/seo dataforseo volume <keywords> | Search volume for keywords |
/seo dataforseo difficulty <keywords> | Keyword difficulty scores |
/seo dataforseo intent <keywords> | Search intent classification |
/seo dataforseo trends <keyword> | Google Trends data |
/seo dataforseo backlinks <domain> | Full backlink profile |
/seo dataforseo competitors <domain> | Competitor domain analysis |
/seo dataforseo ranked <domain> | Ranked keywords for domain |
/seo dataforseo intersection <domains> | Keyword/backlink overlap |
/seo dataforseo traffic <domains> | Bulk traffic estimation |
/seo dataforseo subdomains <domain> | Subdomains with ranking data |
/seo dataforseo top-searches <domain> | Top queries mentioning domain |
/seo dataforseo onpage <url> | On-page analysis (Lighthouse + parsing) |
/seo dataforseo tech <domain> | Technology stack detection |
/seo dataforseo whois <domain> | WHOIS registration data |
/seo dataforseo content <keyword/url> | Content analysis and trends |
/seo dataforseo listings <keyword> | Business listings search |
/seo dataforseo ai-scrape <query> | ChatGPT web scraper for GEO |
/seo dataforseo ai-mentions <keyword> | LLM mention tracking for GEO |
SERP Analysis
/seo dataforseo serp <keyword>
Fetch live Google organic search results.
MCP tools: serp_organic_live_advanced
Default parameters: location_code=2840 (US), language_code=en, device=desktop, depth=100
Also supports: The serp_organic_live_advanced tool supports Google, Bing, and Yahoo via the se parameter. Specify "bing" or "yahoo" to switch search engines.
Output: Rank, URL, title, description, domain, featured snippets, AI overview references, People Also Ask.
/seo dataforseo serp-youtube <keyword>
Fetch YouTube search results. Valuable for GEO. YouTube mentions correlate most strongly with AI citations.
MCP tools: serp_youtube_organic_live_advanced
Output: Video title, channel, views, upload date, description, URL.
/seo dataforseo youtube <video_id>
Deep analysis of a specific YouTube video: info, comments, and subtitles. Some third-party studies report a 0.737 correlation between YouTube mentions and AI visibility, so treat this as a methodology-dependent GEO signal.
MCP tools: serp_youtube_video_info_live_advanced, serp_youtube_video_comments_live_advanced, serp_youtube_video_subtitles_live_advanced
Parameters: video_id (the YouTube video ID, e.g., "dQw4w9WgXcQ")
Output: Video metadata (title, channel, views, likes, description), top comments with engagement, subtitle/transcript text.
/seo dataforseo serp-images <keyword>
Fetch live Google Images search results. See which images rank for a keyword, which domains dominate image results, and identify visual content opportunities.
MCP tools: serp_google_images_live_advanced
Default parameters: location_code=2840 (US), language_code=en, device=desktop, depth=100
Parameters: keyword (required), depth (optional, max 700, billed per 100-result increment), search_param (optional, e.g. "site:example.com")
Cost warning: Using site: or filetype: operators incurs 5x API cost. Warn user before running filtered queries.
Output: Position, title, alt text, source page URL, direct image URL, domain, encoded URL.
Analysis to provide:
- Domain dominance: which sites own the most image positions (top 10 domains by count)
- Alt text patterns: common title/alt text patterns in top-ranking images
- Format distribution: WebP vs JPEG vs PNG in top results (infer from image_url extension)
- Opportunity identification: keywords where user has organic rankings but no image presence
Keyword Research
/seo dataforseo keywords <seed>
Generate keyword ideas, suggestions, and related terms from a seed keyword.
MCP tools: dataforseo_labs_google_keyword_ideas, dataforseo_labs_google_keyword_suggestions, dataforseo_labs_google_related_keywords
Default parameters: location_code=2840 (US), language_code=en, limit=50
Output: Keyword, search volume, CPC, competition level, keyword difficulty, trend.
/seo dataforseo volume <keywords>
Get search volume and metrics for a list of keywords.
MCP tools: kw_data_google_ads_search_volume
Parameters: keywords (array, comma-separated), location_code, language_code
Output: Keyword, monthly search volume, CPC, competition, monthly trend data.
/seo dataforseo difficulty <keywords>
Calculate keyword difficulty scores for ranking competitiveness.
MCP tools: dataforseo_labs_bulk_keyword_difficulty
Parameters: keywords (array), location_code, language_code
Output: Keyword, difficulty score (0-100), interpretation (Easy/Medium/Hard/Very Hard).
/seo dataforseo intent <keywords>
Classify keywords by user search intent.
MCP tools: dataforseo_labs_search_intent
Parameters: keywords (array), location_code, language_code
Output: Keyword, intent type (informational, navigational, commercial, transactional), confidence score.
/seo dataforseo trends <keyword>
Analyze keyword trends over time using Google Trends data.
MCP tools: kw_data_google_trends_explore
Parameters: keywords (array), location_code, date_from, date_to, language_code
Output: Keyword, time series data, trend direction, seasonality signals.
Domain & Competitor Analysis
/seo dataforseo backlinks <domain>
Comprehensive backlink profile analysis.
MCP tools: backlinks_summary, backlinks_backlinks, backlinks_anchors, backlinks_referring_domains, backlinks_bulk_spam_score, backlinks_timeseries_summary
Default parameters: limit=100 per sub-call
Output: Total backlinks, referring domains, domain rank, spam score, top anchors, new/lost backlinks over time, dofollow ratio, top referring domains.
/seo dataforseo competitors <domain>
Identify competing domains and estimate traffic.
MCP tools: dataforseo_labs_google_competitors_domain, dataforseo_labs_google_domain_rank_overview, dataforseo_labs_bulk_traffic_estimation
Output: Competitor domains, keyword overlap %, estimated traffic, domain rank, common keywords.
/seo dataforseo ranked <domain>
List keywords a domain ranks for with positions and page data.
MCP tools: dataforseo_labs_google_ranked_keywords, dataforseo_labs_google_relevant_pages
Default parameters: limit=100, location_code=2840
Output: Keyword, position, URL, search volume, traffic share, SERP features.
/seo dataforseo intersection <domain1> <domain2> [...]
Find shared keywords and backlink sources across 2-20 domains.
MCP tools: dataforseo_labs_google_domain_intersection, backlinks_domain_intersection
Parameters: domains (2-20 array)
Output: Shared keywords with positions per domain, shared backlink sources, unique keywords per domain.
/seo dataforseo traffic <domains>
Estimate organic search traffic for one or more domains.
MCP tools: dataforseo_labs_bulk_traffic_estimation
Parameters: domains (array)
Output: Domain, estimated organic traffic, estimated traffic cost, top keywords.
/seo dataforseo subdomains <domain>
Enumerate subdomains with their ranking data and traffic estimates.
MCP tools: dataforseo_labs_google_subdomains
Parameters: target (domain), location_code, language_code
Output: Subdomain, ranked keywords count, estimated traffic, organic cost.
/seo dataforseo top-searches <domain>
Find the most popular search queries that mention a specific domain in results.
MCP tools: dataforseo_labs_google_top_searches
Parameters: target (domain), location_code, language_code
Output: Query, search volume, domain position, SERP features, traffic share.
Technical / On-Page
/seo dataforseo onpage <url>
Run on-page analysis including Lighthouse audit and content parsing.
MCP tools: on_page_instant_pages, on_page_content_parsing, on_page_lighthouse
Usage:
on_page_instant_pages:Quick page analysis (status codes, meta tags, content size, page timing, broken links, on-page checks)on_page_content_parsing:Extract and parse page content (plain text, word count, structure)on_page_lighthouse:Full Lighthouse audit (performance score, accessibility, best practices, SEO, Core Web Vitals)
Output: Pages crawled, status codes, meta tags, titles, content size, load times, Lighthouse scores, broken links, resource analysis.
/seo dataforseo tech <domain>
Detect technologies used on a domain.
MCP tools: domain_analytics_technologies_domain_technologies
Output: Technology name, version, category (CMS, analytics, CDN, framework, etc.).
/seo dataforseo whois <domain>
Retrieve WHOIS registration data.
MCP tools: domain_analytics_whois_overview
Output: Registrar, creation date, expiration date, nameservers, registrant info (if public).
Content & Business Data
/seo dataforseo content <keyword/url>
Analyze content quality, search for content by topic, and track phrase trends.
MCP tools: content_analysis_search, content_analysis_summary, content_analysis_phrase_trends
Parameters: keyword (for search/trends) or URL (for summary)
Output: Content matches with quality scores, sentiment analysis, readability metrics, phrase trend data over time.
/seo dataforseo listings <keyword>
Search business listings for local SEO competitive analysis.
MCP tools: business_data_business_listings_search
Parameters: keyword, location (optional)
Output: Business name, description, category, address, phone, domain, rating, review count, claimed status.
AI Visibility / GEO
/seo dataforseo ai-scrape <query>
Scrape what ChatGPT web search returns for a query. ChatGPT visibility check: see which sources ChatGPT cites for your target keywords. Check Google AI Overviews and AI Mode with GSC gen-AI reports when available.
MCP tools: ai_optimization_chat_gpt_scraper
Parameters: query, location_code (optional), language_code (optional). Use ai_optimization_chat_gpt_scraper_locations to look up available locations.
Output: ChatGPT response content, cited sources/URLs, referenced domains.
/seo dataforseo ai-mentions <keyword>
Track how LLMs mention brands, domains, and topics. Critical for GEO. Measures actual AI visibility across multiple LLM platforms.
MCP tools: ai_opt_llm_ment_search, ai_opt_llm_ment_top_domains, ai_opt_llm_ment_top_pages, ai_opt_llm_ment_agg_metrics
Parameters: keyword, location_code (optional), language_code (optional). Use ai_opt_llm_ment_loc_and_lang for available locations/languages and ai_optimization_llm_models for supported LLM models.
Workflow:
- Search LLM mentions with
ai_opt_llm_ment_search(find mentions of a brand/keyword across LLM responses) - Get top cited domains with
ai_opt_llm_ment_top_domains(which domains are most cited for this topic) - Get top cited pages with
ai_opt_llm_ment_top_pages(which specific pages are most cited) - Get aggregate metrics with
ai_opt_llm_ment_agg_metrics(overall mention volume, trends)
Output: LLM mention count, top cited domains with frequency, top cited pages, mention trends over time, cross-platform visibility scores.
Advanced: Use ai_opt_llm_ment_cross_agg_metrics for cross-model comparison (how mentions differ across ChatGPT, Claude, Perplexity, etc.).
Available Utility Tools
Additional DataForSEO MCP tools are available for internal use but do not have dedicated commands. Load references/tool-catalog.md when you need to find a specific utility tool (location lookups, bulk operations, historical data, filter options).
Cross-Skill Integration
When DataForSEO MCP tools are available, other claude-seo skills can leverage live data:
- seo-audit:Spawn
seo-dataforseoagent for real SERP, backlink, on-page, and listings data - seo-technical:Use
on_page_instant_pages/on_page_lighthousefor real crawl data,domain_analytics_technologies_domain_technologiesfor stack detection - seo-content:Use
kw_data_google_ads_search_volume,dataforseo_labs_bulk_keyword_difficulty,dataforseo_labs_search_intentfor real keyword metrics,content_analysis_summaryfor content quality - seo-page:Use
serp_organic_live_advancedfor real SERP positions,backlinks_summaryfor link data - seo-images:Use
serp_google_images_live_advancedfor competitor image SERP data, cross-reference with on-page image audit - seo-geo:Use
ai_optimization_chat_gpt_scraperfor real ChatGPT visibility,ai_opt_llm_ment_searchfor LLM mention tracking - seo-plan:Use
dataforseo_labs_google_competitors_domain,dataforseo_labs_google_domain_intersection,dataforseo_labs_bulk_traffic_estimationfor real competitive intelligence
Error Handling
- MCP server not connected: Report that DataForSEO extension is not installed or MCP server is unreachable. Suggest running
./extensions/dataforseo/install.sh - API authentication failed: Report invalid credentials. Suggest checking DataForSEO API login/password in MCP config
- Rate limit exceeded: Report the limit hit and suggest waiting before retrying
- No results returned: Report "no data found" for the query rather than guessing. Suggest broadening the query or checking location/language codes
- Invalid location code: Report the error and suggest using the locations lookup tool to find the correct code
Output Formatting
Match existing claude-seo output patterns:
- Use tables for comparative data
- Prioritize issues as Critical > High > Medium > Low
- Include specific, actionable recommendations
- Show scores as XX/100 where applicable
- Note data source as "DataForSEO (live)" to distinguish from static analysis
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

