When the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.
Guides backlink profile analysis: assessing quality, identifying issues, and planning improvements.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Identify:
| Metric | Meaning | |--------|---------| | Referring domains | Number of unique sites linking | | Backlinks | Total number of links | | Domain Rating (DR) / Domain Authority (DA) | Domain strength score | | Anchor text distribution | Mix of branded, generic, exact match | | Link velocity | Rate of new links over time |
| Signal | Action | |--------|--------| | Toxic links | Consider disavow (use cautiously) | | Spammy anchors | Diversify anchor text naturally | | Link schemes | Remove or disavow | | Sudden spike | Investigate; may trigger penalty |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/backlink-analysis · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/backlink-analysis"
cp -r "skills/seo/off-page/backlink-analysis" ".claude/skills/backlink-analysis"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.