Ahrefs Domain Overview
The Ahrefs Domain Overview node reads a domain's current Domain Rating, backlink volume and estimated organic traffic from the Ahrefs API v3, with per-organisation caching to save API units.
What does the Ahrefs Domain Overview node do?
The Ahrefs Domain Overview node reads a domain’s current standing from the Ahrefs API v3 Site Explorer: Domain Rating and Ahrefs Rank, backlink and referring-domain counts, and estimated organic traffic with its keyword count and traffic value.
Three separate Ahrefs endpoints answer those three questions — domain-rating, backlinks-stats and metrics — and nothing is shared between them but the target. The node runs them together, so a workflow needs one node rather than three.
Each metric group is a separately billed Ahrefs call, which is why each has its own switch: a workflow that only tracks Domain Rating should not pay for a traffic estimate it discards. Every response is cached per Ahrefs integration in the organisation, so a repeated read with the same integration — a re-run, or a second workflow asking the same question — spends no API units at all.
Common use cases:
- Checking a domain’s authority before and after a link campaign.
- Benchmarking a portfolio of domains on the same date.
- Qualifying backlink prospects by Domain Rating and referring domains.
- Capturing a monthly snapshot of traffic, keywords and backlinks in one node.
- Comparing a site against its competitors on identical metrics.
Quick setup
Connect your Ahrefs account
In the Draft & Goal sidebar, open Integrations and connect your Ahrefs API token. You can generate one in the Ahrefs dashboard under Account settings > API keys; the node refuses to run without it.
Add the node to the canvas
Open the Node Library, go to Integrations > SEO Tools > Ahrefs, then drag the Ahrefs Domain Overview node onto your workspace.
Set the target
Type the domain in the Target field, or connect the Target input port to an upstream node (Url, Text, Loop Node…). The scheme is stripped when the node is saved, so https://example.com and example.com share one cached answer.
Pick the metric groups
Leave only the groups you actually consume switched on. Each one is a billed call, and the settings panel shows your remaining unit balance.
Choose a cache window
24 hours is the default. Widen it for a report that tolerates day-old numbers, narrow it when freshness matters more than cost.
Connect the outputs
Connect Domain Rating to a Conditional Node for a threshold test, or Overview to an LLM or a Google Sheets writer for the full payload.
Configuration parameters
Required fields
Ahrefs integration integration required Integration — The connected Ahrefs account whose API token authenticates the call.
Target string required Target domain or URL — The site to read. The scheme (http://, https://) is removed on save, so two spellings of the same site hit the same cache row instead of being billed twice. A trailing slash is removed too, except on a path under Exact URL or Prefix, where /blog/ and /blog are genuinely different requests.
Scope enum required default: domain Target scope — How Ahrefs interprets the target: domain (the host, without its subdomains), subdomains (the host and everything under it), prefix (every URL under a path) or exact (one URL only).
Cache window enum required default: 24h Cache window — How long an answer stays reusable: off, 1h, 6h, 24h, 7d or 30d. off disables both reading and writing, and bills every run.
Optional fields
Protocol enum default: both Protocol — Restricts the read to http, https, or both.
Date string Snapshot date — A YYYY-MM-DD date. Left empty, today’s date is sent: Ahrefs requires a date on these endpoints and refuses the call without one, so “the latest data” is spelled as today rather than as an omitted parameter.
Country string Country — A lowercase ISO 3166-1 alpha-2 code scoping the traffic estimate only. Empty means worldwide. The United Kingdom is gb, not uk, and eu is not a country Ahrefs accepts.
Volume mode enum default: monthly Volume mode — Whether search volumes are reported for the last month (monthly) or as a twelve-month average (average).
Domain Rating boolean default: true Read the Domain Rating — One billed call. Returns domain_rating and ahrefs_rank.
Backlinks boolean default: true Read the backlink counts — One billed call. Returns live and all-time backlinks and referring domains.
Organic traffic boolean default: true Read the traffic estimate — One billed call, the most expensive of the three. Returns organic and paid traffic, keyword counts and traffic value.
Force refresh boolean default: false Ignore the cache — Skips the cached answer and calls Ahrefs. The fresh answer is still written to the cache.
Switching off the two groups you do not read turns a three-call node into a one-call node. That is the single largest saving available on this node, and it is free.
What does the node output?
The node exposes four output anchors rather than one, so a downstream node receives what it asked for instead of the whole payload:
| Anchor | Contents |
|---|---|
| Domain Rating | The score alone, for a threshold test or a chart |
| Backlinks | Live and all-time backlink and referring-domain counts |
| Traffic | Estimated organic traffic, keyword counts and traffic value |
| Overview | The whole payload, including the cache report |
overview string A JSON payload with the requested metric groups, the provenance and the cache report.
{
"target": "example.com",
"mode": "domain",
"date": "2026-10-21",
"domain_rating": 76.5,
"ahrefs_rank": 42138,
"backlinks": {
"live": 184320,
"all_time": 402911,
"live_refdomains": 5120,
"all_time_refdomains": 9874
},
"traffic": {
"org_traffic": 328400,
"org_keywords": 94120,
"org_keywords_top_3": 2150,
"org_cost_cents": 41200000,
"paid_traffic": 1200,
"paid_keywords": 85,
"paid_cost_cents": 320000,
"paid_pages": 40
},
"retrieved_at": "2026-10-21T16:04:11Z",
"source": "Ahrefs API v3 (Site Explorer)",
"cache": {
"hits": [{ "endpoint": "domain-rating", "cached_at": "2026-10-21T08:12:03Z" }],
"misses": ["backlinks-stats", "metrics"],
"units_cost": 142
}
}
Costs are reported in cents of USD, exactly as Ahrefs returns them. The raw value is kept so that a downstream sum is not rounded twice.
Usage examples
Example 1: Qualify a list of backlink prospects
You have a list of candidate domains and want to keep those with a Domain Rating of 40 or more.
Workflow:
- A Text node lists the prospect domains, one per line.
- A Loop Node iterates over them and feeds the Target input.
- Ahrefs Domain Overview runs with Backlinks and Organic traffic switched off — one billed call per domain instead of three.
- The Domain Rating anchor goes into a Conditional Node testing
>= 40. - Qualified domains are appended to a Google Sheets tab.
Example 2: Monthly client snapshot
Workflow:
- A Date node provides the first day of the month.
- Ahrefs Domain Overview reads the three groups with Cache window set to
30d. - The Overview anchor feeds a Merge With Template node producing the report body.
- An Email Sender delivers it.
With a 30-day window, re-running the workflow during the month costs nothing.
Common issues
The node fails with `Ahrefs API token not configured`
Cause: No Ahrefs integration is attached to the node, or the integration was deleted.
Solution: Open the node settings and select a valid Ahrefs integration. Check in the Integrations page that the token is still active on the Ahrefs side.
`Select at least one Ahrefs metric group`
Cause: The three switches — Domain Rating, Backlinks, Organic traffic — are all off, so there is nothing to read.
Solution: Switch at least one back on.
`Ahrefs rejects country='uk'`
Cause: Ahrefs expects a lowercase ISO 3166-1 alpha-2 code from its own list of 210 countries. uk and eu are not on it.
Solution: Use gb for the United Kingdom, and pick a single country rather than a region. The error message lists what the API accepts.
The run reports a 402 or a 429
Cause: A 402 means the API unit balance is exhausted; a 429 means too many calls in too short a window.
Solution: Check the remaining balance shown in the node settings panel. The node never retries a call on its own, because a call that reached Ahrefs may already have been billed. Widen the cache window, or switch off the groups you do not need.
Best practices and pitfalls
Every call is billed in API units — a flat cost per call plus a per-row cost. off on the cache window means every single run pays again. Keep the window as wide as the report allows, and leave Force refresh off unless a change has to be visible immediately.
The cache is shared by the organisation’s workflows that use the same Ahrefs integration, and keyed on the endpoint and its parameters, not on the node. Two workflows asking the same question through the same integration pay once; two different integrations do not share answers.
For a trend rather than a single figure, use Ahrefs Domain History: one call returns the whole range, where two Domain Overview nodes on two dates return two points for two prices.
How does it fit into a workflow?
graph LR
Text[Text<br/>prospect domains] --> Loop[Loop Node]
Loop --> Overview[Ahrefs Domain Overview]
Overview -->|Domain Rating| Cond{DR >= 40?}
Cond -->|Yes| Sheets[Google Sheets<br/>qualified]
Cond -->|No| Drop[Discarded]
Related nodes
The same metrics as a series over a date range, with the first-to-last change computed per metric.
The keywords behind the traffic estimate, with position and landing page.
A second opinion on authority, with Trust Flow and Citation Flow.
Format the metrics into a readable report.