agentleFS
Sign inStart free
ZachArticulateVZachArticulateV/designer-pro-and-seo/skills/seo-dataforseo/SKILL.md

seo-dataforseo

Skill10 starsChanged 27 days agoMITView on GitHub

Pulls live SERP, keyword, backlink, and AI-visibility data from the DataForSEO MCP when connected — search volume, keyword difficulty, multi-engine and image SERP, referring domains, and LLM-mention tracking; otherwise reads the current SERP and competitor set from built-in web search, clearly labeled as lower-fidelity with the metrics that need the MCP named. Trigger when the user says "dataforseo", "live SERP", "keyword volume", "keyword difficulty", "backlink data", "AI-visibility data", "image SERP", or "real search data".

18 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • AgriciDanielSkill

    seo-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

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Detect tooling: Check whether the DataForSEO MCP is exposed this session (scripts/workflow/capability_probe.py reports DATAFORSEO_*).

    line 36
  2. Very specific:

    Premium path (Tier 1, if connected): Call the DataForSEO MCP for the request.

    line 38
  3. Distinctive:

    Built-in path (Tier 2, always available): Use WebSearch to read the current SERP for the keyword(s): capture ranking URLs, titles, and …

    line 41
  4. Distinctive:

    Tier 1 — DataForSEO MCP: If connected, use it for volume, difficulty, multi-engine + image SERP, backlinks, and AI-visibility data.

    line 52
  5. Distinctive:

    Tier 4 — guided: If the user needs hard metrics and the MCP isn't connected, deliver the qualitative read and name the setup (add the …

    line 56
  6. Distinctive:

    Always state which tier ran and which metrics need DataForSEO.

    line 59
  7. Very specific:

    When connected, this is the data plumbing other skills draw on (seo-backlinks, seo-cluster, seo-ecommerce, seo-local-unified, …

    line 79

“Common” is measured: kept by at least 6 in 10 of the 17 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

seo-dataforseo

Family: seo Status: Stable

Purpose

The premium data hub for the SEO family. Tool-aware: with the DataForSEO MCP connected it returns hard metrics (search volume, keyword difficulty, multi-engine and image SERP, referring domains, LLM-mention tracking); without it, it gives a qualitative SERP/keyword read from built-in web search so you still get a current ranking snapshot and competitor URLs — clearly labeled as lower-fidelity, with the exact metrics that require the MCP named.

Triggers

  • "dataforseo"
  • "live SERP" / "real search data"
  • "keyword volume" / "keyword difficulty" / "keyword research"
  • "backlink data" / "competitor data"
  • "AI visibility check" / "LLM mentions" / "ChatGPT mentions"
  • "image SERP" / "google images rankings"

Inputs

  • Query type (SERP | keyword | backlinks | AI-visibility)
  • Keyword(s) / domain / parameters per call

Steps

  1. Detect tooling. Check whether the DataForSEO MCP is exposed this session (scripts/workflow/capability_probe.py reports DATAFORSEO_*).
  2. Premium path (Tier 1, if connected). Call the DataForSEO MCP for the request; normalize into a compact table (volume/difficulty/positions/referring domains as applicable).
  3. Built-in path (Tier 2, always available). Use WebSearch to read the current SERP for the keyword(s): capture ranking URLs, titles, and apparent intent, and a competitor URL list. Do not fabricate volume, difficulty, or CPC — state that those require Tier 1.
  4. Report which tier ran and which specific metrics DataForSEO would add.

Capability routing

This skill follows the plugin's capability-tier cascade (references/CAPABILITY-TIERS.md):

  1. Tier 1 — DataForSEO MCP. If connected, use it for volume, difficulty, multi-engine + image SERP, backlinks, and AI-visibility data.
  2. Tier 2 — built-in (default). Otherwise a WebSearch SERP read: ranking URLs, titles, intent, competitor set. Qualitative — no volume/difficulty/CPC.
  3. Tier 4 — guided. If the user needs hard metrics and the MCP isn't connected, deliver the qualitative read and name the setup (add the DataForSEO extension).

Always state which tier ran and which metrics need DataForSEO.

Outputs

  • The requested data as a compact table (hard metrics on Tier 1; a qualitative SERP snapshot + competitor URLs on Tier 2)
  • An explicit "needs DataForSEO" list for any metric the free path can't measure

Dependencies

  • Optional (Tier 1): DataForSEO MCP (extensions/dataforseo/, paid) — adds the hard metrics; free path works without it
  • Built-in (Tier 2): WebSearch
  • scripts/workflow/capability_probe.py

Notes

"AI visibility" here means measuring/tracking LLM mentions with hard data (Tier-1); to optimize a page for AI citation, use seo-geo (free, on-page).

When connected, this is the data plumbing other skills draw on (seo-backlinks, seo-cluster, seo-ecommerce, seo-local-unified, seo-content-brief, seo-sxo). Each of those also has its own free path; none hard-fails without this.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free