| name | sales-ahrefs |
| description | Ahrefs (ahrefs.com) platform help — industry-leading SEO toolset: Site Explorer (backlinks, organic keywords, Domain Rating), Keywords Explorer, Rank Tracker, Site Audit, Content Explorer, and Brand Radar AI-visibility. REST API v3 (api.ahrefs.com/v3, Bearer key, metered API units; v2 now discontinued) plus an official MCP server (Claude/ChatGPT/Cursor, Lite+). Use when building an Ahrefs API integration, your API units or monthly credits keep running out, setting up the Ahrefs MCP server with Claude, migrating off the dead v2 API to v3, getting throttled or locked by the 'suspicious activity' system within your limits, pulling backlinks/keywords/DR into a warehouse or report, deciding if you need the paid API subscription vs Enterprise, or choosing Starter vs Lite vs Standard vs Advanced. Do NOT use for SEO strategy or tool selection across vendors (use /sales-seo), AI-search-visibility tracking strategy across tools (use /sales-ai-visibility), or content optimization strategy (use /sales-seo). |
| argument-hint | [describe what you need help with in Ahrefs] |
| license | MIT |
| version | 1.0.1 |
| tags | ["sales","seo","content","platform"] |
| github | https://github.com/ahrefs |
Ahrefs Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Build an API integration — pull backlinks, organic keywords, Domain Rating, rank data
- B) Set up the MCP server so Claude/ChatGPT can query your Ahrefs account by prompt
- C) Fix API units / monthly credits running out, overage fees, or "suspicious activity" throttling
- D) Migrate a dead v2 integration to v3
- E) Pick/understand a plan — Starter vs Lite vs Standard vs Advanced vs Enterprise; the credit + API-unit model
- F) Use a specific tool — Site Explorer, Keywords Explorer, Rank Tracker, Site Audit, Content Explorer, Brand Radar
-
REST or MCP? Scheduled pipelines/exports → REST API (tight select). Ad-hoc agent questions → the MCP server. Both spend the same API units.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| SEO strategy, tool selection, or content optimization across vendors | /sales-seo {question} |
| AI-search-visibility (Brand Radar–style) tracking strategy across tools | /sales-ai-visibility {question} |
| Connecting Ahrefs data to other tools generically (iPaaS/warehouse) | /sales-integration {question} |
When routing, give the exact command, e.g. "This is an SEO-tool-selection question — run: /sales-seo Ahrefs vs Semrush for a small content team on a budget".
Step 3 — Ahrefs platform reference
Read references/platform-guide.md for the full reference — the module map (what's API vs MCP vs UI-only), the pricing model (the credit system on lower tiers, API-units allocation vs the paid API subscription/Enterprise for heavy use, $199/$99 add-ons, no free trial), the data model with JSON shapes, and quick-start recipes (pull competitor keywords unit-aware; wire the MCP into Claude; bulk-score domains with batch-analysis).
Read for the integration surface — base , Bearer auth (keys from Account → API keys, owners/admins, 1-yr expiry), the cost model (min 50 units, scales with rows × fields, free endpoints), the endpoint groups (Site Explorer, Keywords Explorer, Rank Tracker, Site Audit, Batch Analysis, limits-and-usage), and the official setup.
