What does this skill do, and when should you use it?
This is the Ahrefs extension skill inside the Claude SEO collection. It reads referring domains, backlinks, organic keywords, and Content Explorer data through the official @ahrefs/[email protected] server. It exposes these analyses through /seo ahrefs commands and requires an Ahrefs API token. It is a focused live-data connector for SEO analysis, not a complete site-audit skill.
Uses the official @ahrefs/[email protected] server to analyze a URL, domain, or topic; returns domain or URL rating, referring-domain counts, estimated organic traffic, top referring domains, anchor distribution, follow/nofollow ratios, organic keywords, ranking distribution, traffic by country, Content Explorer results, social shares, and referring domains; prefers Ahrefs when Ahrefs and Moz disagree and records the discrepancy; combines Ahrefs Spam Score with Common Crawl and crawler signals for toxic-link assessment; for batches of 50 or more URLs, estimates cost before execution and logs actual cost after each call.
- An SEO consultant needs a live backlink and referring-domain snapshot for a prospective or existing client.
- A content strategist wants to identify leading Content Explorer results, social shares, and referring domains for a topic.
- An in-house SEO team needs organic-keyword rankings and traffic-by-country data for a domain.
- An analyst needs to pass Ahrefs data into seo-backlinks for confidence weighting across Ahrefs, Moz, Bing, and Common Crawl.
How do you install this skill?
- Ahrefs calls are metered live external operations; add explicit user confirmation, budget limits, and stop-on-failure behavior before batch or repeated queries.
- Token storage, transport, permission scope, and log redaction are not specified in the skill file; do not write tokens or unredacted responses to reports, debug logs, or shared directories.
- Core functionality depends on the official Ahrefs MCP, Node 18+, account entitlements, and overseas network reachability; mainland-China users may encounter connectivity, authentication, or service-availability issues.
- No fixed output schema, pagination, quota, error, or empty-result behavior is defined; users should verify results before relying on them.
- Shell / CLI
- Network access
- Local filesystem
- MCP Server
@ahrefs/[email protected]Node.js 18+Ahrefs API tokenPython 3
Install the repository collection:
- git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git
- bash claude-seo/install.sh
Then install the Ahrefs extension:
- bash claude-seo/extensions/ahrefs/install.sh
On Windows, use powershell -ExecutionPolicy Bypass -File claude-seo\\install.ps1 and the extension's Windows installation script. Provide an Ahrefs API token and ensure Node.js 18+ is on PATH.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/extensions/ahrefs/skills/seo-ahrefs" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Ahrefs (live, confidence 1.00)
After installation and token configuration, use:
- /seo ahrefs metrics https://example.com
- /seo ahrefs backlinks https://example.com
- /seo ahrefs organic https://example.com
- /seo ahrefs content coffee shops
Before calling an Ahrefs tool, verify that an Ahrefs MCP tool is available in the session. If it is unavailable, the extension should be treated as not installed. Every metric should identify its source as “Ahrefs (live, confidence 1.00)”.
What are this skill's strengths and limitations?
- Uses the official Ahrefs MCP server for live SEO data.
- Covers referring domains, backlinks, organic keywords, and Content Explorer data.
- Defines a clear policy for Ahrefs-versus-Moz discrepancies and cross-skill handoff.
- Includes cost-estimation and actual-cost logging guardrails for large batches.
- Requires @ahrefs/[email protected], Node.js 18+, an Ahrefs API token, and MCP setup.
- Ahrefs API usage is metered and large batches may incur additional cost.
- Its /seo ahrefs routing is tied to the surrounding Claude SEO workflow and would need adaptation elsewhere.
- The supplied material does not document standalone test coverage, detailed quota limits, or error-recovery behavior.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Ahrefs SEO Intelligence Extension this page | 45 · Not recommended | ★ 19k | 23d ago | MIT |
| DataForSEO Live SEO Intelligence | 47 · Use with care | ★ 19k | 23d ago | MIT |
| Off-Site & AI Referral Analyzer | 59 · Recommended | ★ 3k | 13d ago | Apache-2.0 |
| Competitor SEO & GEO Analyst | 51 · Use with care | ★ 3k | 13d ago | Apache-2.0 |
| SE Ranking AI Visibility Analyst | 40 · Not recommended | ★ 19k | 23d ago | MIT |
Unlike seo-backlinks, this skill focuses on Ahrefs data rather than multi-source confidence weighting across Moz, Bing, Common Crawl, and Ahrefs. Where Ahrefs and DataForSEO overlap for SERP-feature analysis, the source recommends preferring DataForSEO for live SERP data.
How did FollowSkills review this skill?
The skill requires the official Ahrefs MCP, an API token, and connection checks, and it defines cost estimation and logging for large batches; these reduce misuse risk. However, it does not require user confirmation before metered calls, explain token storage or transport, define least-privilege scopes or data handling, or provide rollback and external-effect guidance, so points are deducted.
Command routing, prerequisites, unavailable-MCP feedback, and cross-skill delegation are reasonably coherent. Reproduction of the install script, cost script, and MCP behavior is not established in the selected file, while handling for invalid input, API errors, quotas, and partial failures is thin. The static cap also prevents a score above 10, so points are deducted.
The audience and four Ahrefs query categories are clear, covering metrics, backlinks, organic keywords, and content exploration. Boundaries, input/output schemas, and semantic trigger exclusions are not specified. Core use also depends on an overseas service whose availability may vary for mainland-China users, with no Chinese-language guidance, so points are deducted.
The document has concise metadata, versioning, compatibility, prerequisites, routing, output conventions, delegation, and cost guardrails. It lacks representative examples, FAQs, troubleshooting, a limitations section, explicit maintenance ownership, and an update path; version and governance evidence is mostly repository-level rather than in the selected skill file, so points are deducted.
The skill can route live Ahrefs data to common SEO analysis tasks and requires source and confidence labeling, giving it clear core utility. However, output schemas, field completeness, pagination, freshness handling, and fallback behavior are unspecified, and there is no direct result verification for this skill path. Manual review remains necessary, so points are deducted.
The skill identifies the official @ahrefs/[email protected] server and requires Ahrefs attribution for metrics; repository CI and tests provide limited supporting evidence. There are no dedicated tests, real execution records, or independently reproducible cross-source results for the selected path, so the evidence remains thin and the static cap applies.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →