Integrations · SEOConnect Ahrefs to Well
Connect Ahrefs to Well over its MCP server and read your tracked keyword positions, backlink profile, and domain metrics into the workspace. The companies you watch resolve against the rest of your stack, so SEO movement sits next to the accounts it touches.
What Well pulls from Ahrefs
Ahrefs feeds keyword rank, backlink, domain into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Ahrefs’s access.
| From Ahrefs | In Well | Relation | |
|---|---|---|---|
| Keyword rank | SEO signal | Feeds | |
| Backlink | Graph edge | Becomes | |
| Domain | Workspace context | Groups under |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Ahrefs → Well
What Well does with your Ahrefs connection
Connect
Connect Ahrefs over OAuth (MCP DCR): Well registers a client through Ahrefs's OAuth Dynamic Client Registration and you approve on Ahrefs's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings keyword rank, backlink, and domain in from Ahrefs on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Ahrefs entity into SEO signal, graph edge, and workspace context, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Ahrefs lands in the workspace as SEO signal, graph edge, and workspace context you can search, chart, and automate.
Questions Ahrefs unlocks
Ask in plain language. Well answers from your connected Ahrefs connection, resolved against the rest of your stack.
Ask anything about your Ahrefs connection
Ask about your Ahrefs connection…
Connect Ahrefs in three steps
- 01
Authorise Ahrefs over its MCP server
Find Ahrefs in Well's Connections panel and begin. Well reaches the Ahrefs MCP server at api.ahrefs.com, reads its OAuth metadata, and registers a client through Dynamic Client Registration, so you approve read scopes on Ahrefs' own screen with no token to copy across.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverapi.ahrefs.com/mcp/mcp
- 02
Map your entities
Well reads your tracked keyword positions, backlink profile, and domain metrics across the connection and maps each tracked domain to the workspace company it belongs to through Well's data-views layer.
- Mappingpreconfigured by Well
- 03
Use the data
From there, ask which keywords moved or which backlinks are new in conversation, or let an agent join organic visibility to the customer it affects. Ahrefs is an INPUT connector, so the read runs one way and your rank-tracking setup in Ahrefs is never changed.
- First syncstarts as soon as connect completes
The MCP handshake usually finishes inside a minute. Current metrics are read on connect; the longer keyword and backlink history backfills in the background while you work.
How Ahrefs stays secure with Well
Well reaches Ahrefs through its MCP server at api.ahrefs.com over the Model Context Protocol, and OAuth Dynamic Client Registration keeps your Ahrefs token with Ahrefs rather than with Well. The grant is scoped to the keyword, backlink, and domain data Ahrefs exposes, and it refreshes server-side. Every call is a read; Well cannot create a project or change a rank-tracking list in Ahrefs.
- granted
Read Ahrefs records
Resources the Ahrefs MCP server exposes, scoped by your OAuth approval.
- granted
Resolve keyword rank, backlink, and domain across your stack
Match identifiers in Ahrefs against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Ahrefs records
Not granted; Ahrefs is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Ahrefs passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Ahrefs and Well
Open the Connections panel in Well, pick Ahrefs, and start the connect step. Well reaches the Ahrefs MCP server at api.ahrefs.com, reads its published OAuth metadata, and registers itself through Dynamic Client Registration, so there is no API token for you to copy across. You approve the read scopes on Ahrefs' own screen and return to a live connection.
Your tracked keyword positions, the backlinks pointing at your domains, and the domain-level metrics Ahrefs holds come across the connection into the workspace. Ahrefs is an INPUT connector, so the read runs one way: Well pulls the SEO data in and never edits a project or rank-tracking list back in Ahrefs. The data sits in your workspace context next to the rest of your stack.
It does, because Ahrefs maps to the company entity. A domain you track resolves to the workspace company behind it, so the keyword movement and backlink profile for that domain sit against the same record as its deals and activity. A question about a customer's organic visibility then answers in the place that already holds the rest of their context.
Yes. Once the data is read in, an agent can ask which tracked keywords moved most over a period or which new referring domains appeared, and answer from the workspace rather than the Ahrefs dashboard. Each signal keeps the URL and the domain it belongs to, so the answer drills down to a single page when you need the detail behind a number.
Well reads keyword positions, backlinks, and domain metrics across the MCP connection and folds fresh figures into the workspace as they are read, with the first connect pulling the available history in the background. Ahrefs stays the system of record for your rank tracking; Well keeps a queryable copy so the SEO picture sits alongside your other data.
Disconnect Ahrefs from Well's Connections panel and Well stops calling the Ahrefs MCP server immediately and drops the token it was issued. The connection only ever read, so there is nothing to unwind on Ahrefs' side. The keyword and backlink data already brought in stays in your workspace for historical questions; Support can purge it if a policy requires.
Pairs well with Ahrefs
More in SEO
Popular cross-category
Ready to connect Ahrefs?
Connect once. Every keyword rank, backlink, domain from Ahrefs becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.