Awesome-omni-skills seo-dataforseo

DataForSEO: Live SEO Data (Extension) workflow skill. Use this skill when the user needs Use DataForSEO for live SERPs, keyword metrics, backlinks, competitor analysis, on-page checks, and AI visibility data. Trigger when the user needs real SEO data rather than static guidance and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/seo-dataforseo" ~/.claude/skills/diegosouzapw-awesome-omni-skills-seo-dataforseo && rm -rf "$T"

manifest: skills/seo-dataforseo/SKILL.md

DataForSEO: Live SEO Data (Extension)

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/seo-dataforseo

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

DataForSEO: Live SEO Data (Extension) Live search data via the DataForSEO MCP server. Provides real-time SERP results, 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.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, API Credit Awareness, SERP Analysis, Keyword Research, Domain & Competitor Analysis, Technical / On-Page.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

Use when the user needs live SEO data instead of static best-practice guidance.
Use for SERP lookups, keyword volumes, backlink checks, competitor data, or AI visibility tracking.
Use only when the DataForSEO extension is available in the environment.
Use when the request clearly matches the imported source intent: Use DataForSEO for live SERPs, keyword metrics, backlinks, competitor analysis, on-page checks, and AI visibility data. Trigger when the user needs real SEO data rather than static guidance.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`SKILL.md`	Starts with the smallest copied file that materially changes execution
Supporting context	`SKILL.md`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Prerequisites

This skill requires the DataForSEO extension to be installed:

./extensions/dataforseo/install.sh

Check 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.

Examples

Example 1: Ask for the upstream workflow directly

Use @seo-dataforseo to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @seo-dataforseo against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @seo-dataforseo for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @seo-dataforseo using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/seo-dataforseo

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@00-andruia-consultant-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@10-andruia-skill-smith-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@20-andruia-niche-intelligence-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@2d-games
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

Imported Reference Notes

Imported: Quick Reference

Command	What it does
`/seo dataforseo serp <keyword>`	Google organic 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

Imported: 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)

Imported: 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. YouTube mentions have the strongest correlation (0.737) with AI visibility, making this critical for GEO analysis.

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.

Imported: 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.

Imported: 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.

Imported: 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).

Imported: 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.

Imported: AI Visibility / GEO

/seo dataforseo ai-scrape <query>

Scrape what ChatGPT web search returns for a query. Real GEO visibility check: see which sources ChatGPT cites for your target keywords.

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.).

Imported: Available Utility Tools

These DataForSEO tools are available for internal use by the agent but do not have dedicated commands:

```
serp_locations
```
:Location code lookups for SERP queries
```
serp_youtube_locations
```
:Location code lookups for YouTube queries
```
kw_data_google_ads_locations
```
:Location lookups for keyword data
```
kw_data_dfs_trends_demography
```
:Demographic data for trend analysis
```
kw_data_dfs_trends_subregion_interests
```
:Subregion interest data for trends
```
kw_data_dfs_trends_explore
```
:DFS proprietary trends data
```
kw_data_google_trends_categories
```
:Google Trends category lookups
```
dataforseo_labs_google_keyword_overview
```
:Quick keyword metrics overview
```
dataforseo_labs_google_historical_serp
```
:Historical SERP results for a keyword
```
dataforseo_labs_google_serp_competitors
```
:Competitors for a specific SERP
```
dataforseo_labs_google_keywords_for_site
```
:Keywords a site ranks for (alternative to ranked)

dataforseo_labs_google_page_intersection

:Page-level intersection analysis

dataforseo_labs_google_historical_rank_overview

:Historical domain rank data

dataforseo_labs_google_historical_keyword_data

:Historical keyword metrics

```
dataforseo_labs_available_filters
```
:Available filter options for Labs endpoints
```
backlinks_competitors
```
:Find domains with similar backlink profiles
```
backlinks_bulk_backlinks
```
:Bulk backlink counts for multiple targets

backlinks_bulk_new_lost_referring_domains

:Bulk new/lost referring domains

```
backlinks_bulk_new_lost_backlinks
```
:Bulk new/lost backlinks
```
backlinks_bulk_ranks
```
:Bulk rank overview for multiple targets
```
backlinks_bulk_referring_domains
```
:Bulk referring domain counts
```
backlinks_domain_pages_summary
```
:Summary of pages on a domain
```
backlinks_domain_pages
```
:List pages on a domain with backlink data
```
backlinks_page_intersection
```
:Shared backlink sources at page level
```
backlinks_referring_networks
```
:Referring network analysis
```
backlinks_timeseries_new_lost_summary
```
:Track new/lost backlinks over time
```
backlinks_bulk_pages_summary
```
:Bulk page summaries
```
backlinks_available_filters
```
:Available filter options for Backlinks endpoints

domain_analytics_whois_available_filters

:WHOIS filter options

domain_analytics_technologies_available_filters

:Technology detection filter options

```
ai_opt_kw_data_loc_and_lang
```
:AI optimization keyword data locations/languages

ai_optimization_keyword_data_search_volume

:AI-specific keyword volume data

```
ai_optimization_llm_response
```
:Direct LLM response analysis
```
ai_optimization_llm_mentions_filters
```
:Available filters for LLM mentions

ai_optimization_chat_gpt_scraper_locations

:Available locations for ChatGPT scraper

Imported: Cross-Skill Integration

When DataForSEO MCP tools are available, other claude-seo skills can leverage live data:

seo-audit:Spawn
```
seo-dataforseo
```
agent for real SERP, backlink, on-page, and listings data

seo-technical:Use

on_page_instant_pages

on_page_lighthouse

for real crawl data,

domain_analytics_technologies_domain_technologies

for stack detection

seo-content:Use

kw_data_google_ads_search_volume

dataforseo_labs_bulk_keyword_difficulty

dataforseo_labs_search_intent

for real keyword metrics,

content_analysis_summary

for content quality

seo-page:Use
```
serp_organic_live_advanced
```
for real SERP positions,
```
backlinks_summary
```
for link data
seo-geo:Use
```
ai_optimization_chat_gpt_scraper
```
for real ChatGPT visibility,
```
ai_opt_llm_ment_search
```
for LLM mention tracking

seo-plan:Use

dataforseo_labs_google_competitors_domain

dataforseo_labs_google_domain_intersection

dataforseo_labs_bulk_traffic_estimation

for real competitive intelligence

Imported: 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

Imported: 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

Imported: Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.