sales-ahrefs
starsforks
How to install sales-ahrefs?
sales-skills/sales/sales-ahrefs
$npx -y skills add sales-skills/sales --skill sales-ahrefsAhrefs (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 unit
SKILL.md
| 1 | # Ahrefs Platform Help |
| 2 | |
| 3 | ## Step 1 — Gather context |
| 4 | |
| 5 | If `references/learnings.md` exists, read it first for accumulated platform knowledge. |
| 6 | |
| 7 | 1. **What are you trying to do?** |
| 8 | - A) Build an API integration — pull backlinks, organic keywords, Domain Rating, rank data |
| 9 | - B) Set up the **MCP server** so Claude/ChatGPT can query your Ahrefs account by prompt |
| 10 | - C) Fix **API units / monthly credits** running out, overage fees, or "suspicious activity" throttling |
| 11 | - D) Migrate a dead **v2** integration to **v3** |
| 12 | - E) Pick/understand a plan — Starter vs Lite vs Standard vs Advanced vs Enterprise; the credit + API-unit model |
| 13 | - F) Use a specific tool — Site Explorer, Keywords Explorer, Rank Tracker, Site Audit, Content Explorer, Brand Radar |
| 14 | |
| 15 | 2. **REST or MCP?** Scheduled pipelines/exports → REST API (tight `select`). Ad-hoc agent questions → the MCP server. Both spend the same **API units**. |
| 16 | |
| 17 | Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2. |
| 18 | |
| 19 | ## Step 2 — Route or answer directly |
| 20 | |
| 21 | | If the question is about... | Route to... | |
| 22 | |---|---| |
| 23 | | SEO strategy, tool selection, or content optimization across vendors | `/sales-seo {question}` | |
| 24 | | AI-search-visibility (Brand Radar–style) tracking strategy across tools | `/sales-ai-visibility {question}` | |
| 25 | | Connecting Ahrefs data to other tools generically (iPaaS/warehouse) | `/sales-integration {question}` | |
| 26 | |
| 27 | 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`". |
| 28 | |
| 29 | ## Step 3 — Ahrefs platform reference |
| 30 | |
| 31 | **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). |
| 32 | |
| 33 | **Read `references/ahrefs-api-reference.md`** for the integration surface — base `https://api.ahrefs.com/v3`, Bearer auth (keys from Account → API keys, owners/admins, 1-yr expiry), the **API-units** 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 **MCP server** setup. |
| 34 | |
| 35 | Answer using only the relevant section. Don't dump the full reference. |
| 36 | |
| 37 | ## Step 4 — Actionable guidance |
| 38 | |
| 39 | Focus on the user's specific situation: |
| 40 | |
| 41 | - **Budget units like money.** Every data call costs **≥50 units**, scaling with rows × fields. Always pass |
| 42 | **`select`** (only needed fields), cap **`limit`**, prefer **`batch-analysis`** for many targets, cache, |
| 43 | and poll **`/subscription-info/limits-and-usage`**. This single discipline prevents most "ran out" pain. |
| 44 | - **v3 only.** v2 was fully shut off **2025-11-01** — any v2 tutorial/endpoint is dead. New keys + v3 paths. |
| 45 | - **Use the MCP for agents, REST for pipelines.** The official MCP (Lite+) lets Claude/ChatGPT pull data by |
| 46 | prompt; it draws on the **same unit budget**, so keep agent queries specific. |
| 47 | - **Pace automated calls.** Ahrefs' anti-abuse "suspicious activity" system throttles bursty access even |
| 48 | within plan limits — add jitter/backoff, don't hammer in parallel. |
| 49 | - **Know the real cost.** Lower tiers meter **credits** (1 per report); heavy **API** use needs a paid API |
| 50 | subscription (~$500–$10k/mo) or Enterprise; Brand Radar/AI Content Helper/Report Builder are paid add-ons. |
| 51 | - **It's read-only.** No write API, no event webhooks — pull data out, push it into your own systems. |
| 52 | |
| 53 | If you discover a gotcha, workaround, |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen 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 sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen 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," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
