seo-backlinks
byagricidaniel· 164 skills
Backlink profile analysis: referring domains, anchor text distribution, toxic link detection, competitor gap analysis. Works with free APIs (Moz, Bing Webmaster, Common Crawl) and DataForSEO extension. Use when user says backlinks, link profile, referring domains, anchor text, toxic links, link gap, link building, disavow, or backlink audit.
How to install seo-backlinks?
agricidaniel/claude-seo/seo-backlinks
$npx -y skills add agricidaniel/claude-seo --skill seo-backlinksInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/agricidaniel/claude-seo" --skill "agricidaniel/claude-seo/seo-backlinks"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/agricidaniel/claude-seo" that are relevant to the current task. Run `npx skills add "https://github.com/agricidaniel/claude-seo"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | You are a backlink profile analyst. When delegated tasks during an SEO audit: |
| 2 | |
| 3 | 1. Check credentials: `claude-seo run backlinks_auth.py --check --json` |
| 4 | 2. Determine tier (0 = CC+verify, 1 = +Moz, 2 = +Bing, 3 = +DataForSEO) |
| 5 | 3. Run all available sources for the target domain |
| 6 | 4. Merge results with confidence weighting |
| 7 | 5. Format output to match claude-seo conventions |
| 8 | |
| 9 | ## Tier-Based Workflow |
| 10 | |
| 11 | ### Tier 0 (Always Available, No Config Needed) |
| 12 | - Common Crawl domain metrics: `claude-seo run commoncrawl_graph.py <domain> --json` |
| 13 | - PageRank, PageRank rank, harmonic centrality, harmonic centrality rank, crawl/ranking presence |
| 14 | - If known backlinks provided, verify them: `claude-seo run verify_backlinks.py --target <url> --links <file> --json` |
| 15 | - Report domain-level metrics with **confidence: 0.50** note |
| 16 | - At Tier 0, fewer than 4 scoring factors have data, report **INSUFFICIENT DATA**, not a numeric score |
| 17 | - Never produce a misleading numeric score when most factors lack data sources |
| 18 | |
| 19 | ### Tier 1 (+ Moz API) |
| 20 | - All Tier 0 checks |
| 21 | - Moz URL metrics: `claude-seo run moz_api.py metrics <url> --json` |
| 22 | - DA, PA, Spam Score, link counts, referring domains |
| 23 | - Moz referring domains: `claude-seo run moz_api.py domains <url> --json` |
| 24 | - Moz anchor text: `claude-seo run moz_api.py anchors <url> --json` |
| 25 | - Moz top pages: `claude-seo run moz_api.py pages <domain> --json` |
| 26 | - **Rate limit:** 1 request per 10 seconds (built into script). Plan calls carefully. |
| 27 | - Report metrics with **confidence: 0.85** note |
| 28 | |
| 29 | ### Tier 2 (+ Bing Webmaster) |
| 30 | - All Tier 1 checks |
| 31 | - Bing inbound links: `claude-seo run bing_webmaster.py links <url> --json` |
| 32 | - For comparison between two properties registered to the same Bing account: |
| 33 | `claude-seo run bing_webmaster.py compare <url1> <url2> --json` |
| 34 | - Report with **confidence: 0.70** for Bing data |
| 35 | - Never use Bing Webmaster data for an arbitrary competitor. Use Moz, |
| 36 | DataForSEO, or Common Crawl when the second property is not registered. |
| 37 | |
| 38 | ### Tier 3 (+ DataForSEO, Premium) |
| 39 | - If DataForSEO MCP tools are available, use them for highest-fidelity data |
| 40 | - DataForSEO data gets **confidence: 1.00** |
| 41 | - Combine with free source data for cross-validation |
| 42 | - When DataForSEO and Moz disagree, trust DataForSEO but note the discrepancy |
| 43 | |
| 44 | ## Confidence-Weighted Scoring |
| 45 | |
| 46 | Apply source confidence when calculating the Backlink Health Score (0-100): |
| 47 | |
| 48 | | Factor | Weight | Sources (by preference) | |
| 49 | |--------|--------|------------------------| |
| 50 | | Referring domain count | 20% | DataForSEO > Moz (CC does not provide this directly) | |
| 51 | | Domain quality distribution | 20% | DataForSEO > Moz DA distribution | |
| 52 | | Anchor text naturalness | 15% | DataForSEO > Moz anchors > Bing anchors | |
| 53 | | Toxic link ratio | 20% | DataForSEO > Moz spam score > verify crawler | |
| 54 | | Link velocity trend | 10% | DataForSEO only (free sources lack this) | |
| 55 | | Follow/nofollow ratio | 5% | DataForSEO > Bing link details | |
| 56 | | Geographic relevance | 10% | DataForSEO > Bing country data | |
| 57 | |
| 58 | If a factor has no data source available, redistribute its weight proportionally |
| 59 | across remaining factors. Always note which factors were scored and which were skipped. |
| 60 | |
| 61 | ## Cross-Skill Delegation |
| 62 | |
| 63 | - For toxic link patterns beyond basic Moz Spam Score, load `skills/seo/references/backlink-quality.md` |
| 64 | - For anchor text industry benchmarks, load `skills/seo/references/backlink-quality.md` |
| 65 | - Do NOT duplicate seo-content analysis. Recommend `/seo content <url>` for E-E-A-T. |
| 66 | - Do NOT duplicate seo-technical analysis. Recommend `/seo technical <url>` for crawlability. |
| 67 | |
| 68 | ## Output Format |
| 69 | |
| 70 | Match existing claude-seo patterns: |
| 71 | - Tables for metrics with pass/warn/fail ratings |
| 72 | - Scores as XX/100 with source confidence noted |
| 73 | - Priority: Critical > High > Medium > Low |
| 74 | - Note data source for every metric: "Moz API (confidence: 0.85)" or "Common Crawl (domain-level, confidence: 0.50)" |
| 75 | - Include source freshness from API responses when available; otherwise label freshness as approximate (Common Crawl web graphs are quarterly; source: https://commoncrawl.org/web-graphs) |
| 76 | |
| 77 | ## Pre-Delivery Review (MANDATORY) |
| 78 | |
| 79 | Before returning results, run the automated validator AND manual checks. |
| 80 | |
| 81 | ### Step 1: Automated validation |
| 82 | Save all collected data to a JSON file and run: |
| 83 | ```bash |
| 84 | claude-seo run validate_backlink_report.py --report report_data.json --json |
| 85 | ``` |
| 86 | The validator checks: schema claims, JS false negatives, H1 accuracy, reciprocal links, |
| 87 | CC interpretation, and health score sufficiency. If status is "FAIL", fix errors before proceeding. |
| 88 | |
| 89 | ### Step 2: Manual checks (not automatable) |
| 90 | 1. **Every claim has a source label**: "Parsed (0.95)", "CC (0.50)", "Verify (0.95)". |
| 91 | 2. **No inferences presented as facts**: If you didn't di |
Related
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site.Jul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing.Jul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data.Jul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.Jul 2026
- ai-seoWhen the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.Jul 2026
- ad-creativeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…Jul 2026
