agentleFS
ZachArticulateVZachArticulateV/designer-pro-and-seo/skills/seo-backlinks/SKILL.md

seo-backlinks

Skill10 starsChanged 27 days agoMITView on GitHub

Backlink profile analysis — referring domains, anchor-text distribution, toxic-link flags, competitor link gap, and link-building targets. Uses a connected link-data MCP (DataForSEO, Moz, or Bing) for full metrics and authority scores when present; otherwise builds a qualitative profile from web-search mention and linking-domain discovery (no exact counts, authority, or confirmed toxicity without a provider). Trigger when the user says "backlinks", "link profile", "referring domains", "anchor text", "toxic links", "link gap", "link building", "disavow", or "backlink audit".

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-maps, seo-agentic and 1 more.

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

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 14 projects that use this

  • 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 4 projects that use this

  • timruebenachSkill

    seo-flow

    FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.

    Also in 9 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Detect tooling: Check whether a link-data MCP (DataForSEO/Moz/Bing) is exposed this session (scripts/workflow/capability_probe.py reports …

    line 36
  2. Distinctive:

    If you have access to a public web-graph (Common Crawl / Bing Webmaster), fold it in — the plugin ships no such fetcher, so treat it as …

    line 43
  3. Distinctive:

    Tier 4 — guided: If the user needs authoritative counts/scores and no MCP is connected, deliver the qualitative profile and name the setup …

    line 59
  4. Distinctive:

    Always state which tier ran and what a link-data provider would add.

    line 62

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

Family: seo Status: Stable

Purpose

Backlink intelligence on a free-to-premium ladder. Tool-aware: with a link-data MCP connected (DataForSEO/Moz/Bing) it returns a full referring-domain profile with metrics; without one, it assembles a qualitative profile from public signals (Common Crawl web graph, Bing Webmaster) plus web-search mention discovery — rarer than it sounds on the free tier, and a genuine differentiator.

Triggers

  • "backlinks" / "backlink audit"
  • "link profile" / "referring domains"
  • "anchor text"
  • "toxic links" / "disavow"
  • "link gap" / "competitor backlinks"
  • "link building"

Inputs

  • Domain
  • Optional competitor domains (for gap analysis)
  • Tier preference (auto | built-in | premium)

Steps

  1. Detect tooling. Check whether a link-data MCP (DataForSEO/Moz/Bing) is exposed this session (scripts/workflow/capability_probe.py reports relevant keys).
  2. Premium path (Tier 1, if connected). Pull the full profile via the connected MCP (referring domains, anchors, authority metrics); flag toxic links on conservative thresholds; compute competitor gap.
  3. Built-in path (Tier 2, always available). Assemble a qualitative profile with WebSearch: discover brand/URL mentions and likely linking domains, and group them. If you have access to a public web-graph (Common Crawl / Bing Webmaster), fold it in — the plugin ships no such fetcher, so treat it as optional. Label the result qualitative: exact counts, authority, and confirmed toxicity need Tier 1.
  4. Synthesize. Produce the inventory, an anchor-text read, conservatively-flagged toxic candidates (with the caveat that confirmation needs metrics), and a competitor-gap prospect list.
  5. Report which tier ran and what a link-data MCP would add.

Capability routing

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

  1. Tier 1 — link-data MCP. DataForSEO/Moz/Bing if connected → full metric profile.
  2. Tier 2 — built-in (default). Common Crawl / Bing public signals + WebSearch mention discovery → a qualitative profile and prospect list.
  3. Tier 4 — guided. If the user needs authoritative counts/scores and no MCP is connected, deliver the qualitative profile and name the setup to unlock metrics.

Always state which tier ran and what a link-data provider would add.

Outputs

  • Backlink inventory (metric-rich on Tier 1; qualitative on Tier 2)
  • Anchor-text distribution read
  • Toxic-link candidates with a disavow-file recommendation (conservative)
  • Competitor gap with a link-building prospect list

Dependencies

  • Optional (Tier 1): a link-data MCP — seo-dataforseo (DataForSEO), or Moz/Bing — adds full metrics; free path works without it
  • Built-in (Tier 2): WebSearch; public Common Crawl / Bing Webmaster signals
  • scripts/workflow/capability_probe.py

Notes

Toxic-link thresholds are conservative by default — better to under-flag than to recommend disavowing a healthy link. Free-tier backlink intelligence is the differentiator here.

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.