Menu
Use when analyzing backlink profiles, link authority, toxic links, link-building opportunities, or competitor link gaps. 外链分析/反向链接
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | backlink-analyzer |
| description | Use when analyzing backlink profiles, link authority, toxic links, link-building opportunities, or competitor link gaps. 外链分析/反向链接 |
| version | 9.9.5 |
| license | Apache-2.0 |
| compatibility | Claude Code, skills.sh, ClawHub, Vercel Labs, Cursor, Windsurf, Codex CLI, Amp, Gemini CLI, Kimi Code, Qwen Code, CodeBuddy |
| homepage | https://github.com/aaron-he-zhu/seo-geo-claude-skills |
| when_to_use | Use when analyzing backlink profiles, link quality, toxic links, referring domains, or anchor text distribution. |
| argument-hint | <domain or URL> |
| metadata | {"author":"aaron-he-zhu","version":"9.9.5","geo-relevance":"low","tags":["seo","backlinks","link-building","link-profile","toxic-links","off-page-seo","link-audit","referring-domains","disavow","ahrefs-alternative","外链分析","被リンク","백링크","backlinks-seo"],"triggers":["analyze backlinks","check link profile","find toxic links","link building opportunities","backlink audit","who links to me","I have spammy links","how do I get more backlinks","disavow links","how to build backlinks","外链分析","反向链接","有毒链接","链接建设","外链怎么做","有垃圾外链","谁链接到我","友链","互换友链","外链建设","被リンク分析","バックリンク","リンク構築","백링크 분석","링크 빌딩","누가 내 사이트 링크해?","백링크 어떻게 늘려?","análisis de backlinks","enlaces entrantes","análise de backlinks"]} |
Analyzes backlink profiles for quality, risk, competitive gaps, and link-building opportunities.
Analyze backlink profile for [domain]
Find link building opportunities by analyzing [competitor domains]
Expected output: a backlink report or delta summary plus the standard handoff summary for memory/monitoring/.
memory/open-loops.md and memory/decisions.md.Emit the standard shape from skill-contract.md §Handoff Summary Format.
All integrations optional (see CONNECTORS.md). With tools, pull backlink profiles from ~~link database and competitor data from ~~SEO tool. Without tools, ask for backlink CSVs, referring domains, competitor domains, and link changes. Respect robots.txt and TOS per SECURITY.md.
When a user requests backlink analysis:
Reference: See references/analysis-templates.md for the compact output templates used in all seven steps.
When running domain-authority-auditor after this analysis, the following data feeds directly into CITE scoring:
| Backlink Metric | CITE Item | Dimension |
|---|---|---|
| Referring domains count | C01 (Referring Domain Volume) | Citation |
| Authority distribution (DA breakdown) | C02 (Referring Domains Quality) | Citation |
| Link velocity | C04 (Link Velocity) | Citation |
| Geographic distribution | C10 (Link Source Diversity) | Citation |
| Dofollow/Nofollow ratio | T02 (Dofollow Ratio Normality) | Trust |
| Toxic link analysis | T01 (Link Profile Naturalness), T03 (Link-Traffic Coherence) | Trust |
| Competitive link intersection | T05 (Profile Uniqueness) | Trust |
Sample outcome: a link-intersection table, top immediate opportunities, and an estimated impact model. Keep the full structure in references/analysis-templates.md.
Prioritize quality, monitor regularly, diversify anchors and link types, and disavow cautiously.
Reference: See references/link-quality-rubric.md for the scoring matrix, toxic-link criteria, benchmarks, and disavow guidance.
Reference: See references/outreach-templates.md for outreach frameworks, subject lines, response benchmarks, follow-up sequences, and templates.
Ask "Save these results?" If yes, write memory/monitoring/YYYY-MM-DD-<topic>.md with headline finding, actions, and open loops. If toxic ratio exceeds 15%, recommend domain-authority-auditor.
Toxic ratio > 15% → domain-authority-auditor. Otherwise → Terminal. Visited-set rule applies per skill-contract.md.
Use when a PR has Codex review comments, unresolved review threads, requested changes, or PR checks requiring attention. Triggers on "codex review", "resolve threads", "fix review comments", "converge branch", "address feedback", or when ultrareview-pr-audit detects unresolved threads (matchedCount > 0).
Use when reviewing or refactoring a branch for SSOT convergence, clean code, drift detection, overengineering, technical debt, dead code, unused code, stale comments, or production-grade maintainability. Triggers on "SSOT audit", "drift check", "clean code review", "technical debt scan", "dead code removal", or when ultrareview-pr-audit Phase 2 static verification is required.
Use when performing comprehensive PR review with browser testing, SSOT validation, and production readiness certification. Triggers on "ultrareview", "super review", "full PR audit", "complete PR verification", "production readiness check", or when user requests comprehensive PR validation with automated testing and multi-source best practices verification.
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.