
How to connect Ahrefs to ARIQ
Use this guide when an agency connects a client's Ahrefs account, or when a business connects its own Ahrefs account. The connection is saved on the open project.
Ahrefs API v3 tokenWho connects Ahrefs
The connection is saved on one project. An agency connects each client from that client's project. A business connecting its own account uses its own project. Both follow the same Connect button.
Sign in to ARIQ with your agency user. Open the client project, then connect that client's Ahrefs account. The client does not need an ARIQ login. Use the Ahrefs login that can already see that client's data.
Sign in to ARIQ, open your project, and connect the Ahrefs account this business already uses. You approve access with that same account.
Connect it inside ARIQ
- 1Sign in to ARIQ.
- 2Open the project this account belongs to. Switch projects from the left sidebar if you manage more than one client.
- 3Open Ahrefs from the workspace tabs, or go straight to the Ahrefs page.
- 4Click Connect. ARIQ asks for the key from the Ahrefs account. Copy it from Ahrefs, paste it into ARIQ, and save. The key is stored on this project.
- 5Stay on that project and sync. The page shows live numbers only after this account is connected. Another client's project stays empty until you connect it there too.
On Ahrefs, before you click Connect
Do this in the Ahrefs account that belongs to the client, or in your own account if this project is your business. Then come back to ARIQ and click Connect.
Create an Ahrefs API token
Ahrefs API keysIn Ahrefs, open Account settings, then API keys. Create a token with Site Explorer access. API units are billed by Ahrefs.
Paste the token in ARIQ
Open Ahrefs in the SEO workspace and connect with the token. The format is the raw token, with no prefix.
Sync the project domain
ARIQ queries Domain Rating and recent backlinks for the active project host. Confirm the project domain before the first sync.
What shows up after the account is connected
Sync Domain Rating, backlinks, and referring domains for the active project domain.
- A 401 or 403 means the token is invalid or the plan does not include API access.