Menu
Mattering Automations connector

An Ahrefs MCP built for an API that charges by the row

Connect one Ahrefs API key and 49 nodes land on the canvas: backlinks and referring domains, seven history reports, organic and paid keyword research, SERP overview, batch analysis, Rank Tracker and Site Audit. Ahrefs meters in units and units are non-refundable, so 17 of these nodes cost nothing, the connection test costs nothing, and every metered node names the columns that make it expensive.

49 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Ahrefs MCP connector does

The Ahrefs connector for Mattering Automations is 49 nodes on Ahrefs API v3, authenticated with one API key sent as a bearer token. Site Explorer covers point-in-time overviews, seven history reports, backlinks, broken backlinks, referring domains, anchors, linked domains, organic keywords and competitors, top and paid pages and crawled pages. Keywords Explorer covers keyword metrics, volume history and volume by country plus the three keyword-idea reports. Beyond that there is SERP Overview, Batch Analysis for up to 100 targets in one request, five Rank Tracker reports, seven project and keyword-list management nodes, and two Site Audit nodes. Forty-six read and three act.

Cost is the first thing to say about this API, because a naive loop here is an expensive mistake rather than an inconvenience. Ahrefs meters in API UNITS. Its own documented formula is that a request costs the greater of a 50 unit base cost and the per-row cost multiplied by the number of rows, where the per-row cost is the sum of the costs of each unique field that appears in the returned result or in the filter and sort parameters. Most fields cost 1 unit, but some cost 5 and some cost 10. Ahrefs' own worked example is worth memorising: a backlinks request selecting title and traffic, filtering on traffic and referring domains, sorting by traffic and returning 500 rows costs 6,000 units, because traffic alone is a 10 unit field. Ahrefs also states plainly that units once consumed are non-refundable. Every metered node in this connector names the expensive columns in its description, because the column list is the part you actually control.

Seventeen of the 49 nodes consume no units at all, and Ahrefs marks them so itself. All five Rank Tracker reports are free. All seven management nodes are free, including the two that write keywords into a project. Ahrefs: Get API Limits and Usage, Ahrefs: List Locations and Languages, Ahrefs: Get Domain Rating (Free Endpoint), Ahrefs: List Crawler IP Ranges and Ahrefs: List Site Audit Projects are free. That is a substantial free half, and it is why so much useful automation here can run daily without touching the allowance: position tracking, competitor stats, project inventory and audit health scores are all in it.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can read Ahrefs: Get API Limits and Usage to see what is left, pull a Rank Tracker report for free, and only then decide whether a metered backlinks pull is worth running. The same nodes run unattended on a schedule, which is where a metered API needs the guardrail most.

Ahrefs ships its own hosted MCP server, and it deserves naming rather than ignoring: Ahrefs documents a streamable HTTP endpoint with setup guides for Claude, ChatGPT and several other clients, available on a Lite plan or higher. If you want to ask Ahrefs questions in a chat window, use it. But Ahrefs' own MCP documentation draws a line that is directly relevant here, and it is worth quoting exactly: using the external MCP endpoint via custom scripts, bridges, or standalone HTTP or JSON-RPC clients is unsupported and not permitted, and for supported programmatic access to Ahrefs data, please use the Ahrefs public API. That is precisely what this connector is. Scheduled, multi-step, unattended Ahrefs work belongs on the public API under your own workspace key, which is the path Ahrefs documents and recommends, and it is the path these 49 nodes take.

One connection, three surfaces

  • Visual automations. Drag Ahrefs nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Ahrefs node, ready to drop on the canvas

49 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 46

Ahrefs: Batch Analysis

COSTS API UNITS, and this node EXISTS TO SAVE THEM: up to 100 domains or URLs scored in ONE request, which pays the 50-unit floor once instead of a hundred times. Whenever a workflow would loop Ahrefs: Get Domain Rating or Ahrefs: Get Traffic and Keyword Metrics over a list, use this instead. Returns DR, UR, Ahrefs Rank, backlinks, referring domains and organic and paid traffic per target. org_traffic, org_cost, paid_traffic and paid_cost are 10 units each, the refdomains columns are 5, and org_traffic_top_by_country is 10 units PER COUNTRY returned. Monetary values are USD cents. Plan note: the number of targets is also bounded by the plan's Batch Analysis limit (200 on Standard, 500 on Advanced, 1,000 on Enterprise per report in the app), and Batch Analysis is not offered on Lite.

Ahrefs: Get API Limits and Usage

FREE - consumes no API units. How many API units this key and this workspace have spent this billing month, what the ceiling is, when it resets, and when the key itself expires. On a metered API this is the node to put in front of an expensive workflow: read data.limits_and_usage.units_usage_workspace against units_limit_workspace and branch rather than discovering the ceiling by hitting it. It is also the cheapest possible check that a credential works, since it needs no parameters and costs nothing.

Ahrefs: Get Backlinks Stats

COSTS API UNITS: one row of four fields, two of which are 5-unit columns, so this lands on the 50-unit minimum. Total live and all-time backlinks and referring domains for a target on a date. These are SNAPSHOT COUNTS, not activity in a period: data.metrics.live is how many links exist now, not how many were gained. Do not sum them across dates - for a series use Ahrefs: Get Referring Domains History.

Ahrefs: Get Domain Rating

COSTS 50 API UNITS per call - the flat minimum, because the endpoint returns one row of two fields and cannot be trimmed with select. Domain Rating and Ahrefs Rank for a target on a given date. If you only need TODAY'S DR, use Ahrefs: Get Domain Rating (Free Endpoint) instead and pay nothing; this node earns its cost only when you need a historical date or Ahrefs Rank. Both numbers are point-in-time scores on a relative scale - never add them up and never average them across sites or dates.

Ahrefs: Get Domain Rating (Free Endpoint)

FREE - consumes no API units, and works on a free Ahrefs account. Domain Rating for any domain, and nothing else. Use this instead of Ahrefs: Get Domain Rating whenever DR alone is what you need: that node costs the 50-unit minimum per call, this one costs nothing. It does still need an API key (Ahrefs made the key mandatory on 2026-08-10) and it cannot be dated - it always returns today's value. Using this data publicly requires the attribution Ahrefs states in data.license.

Ahrefs: Get Domain Rating History

COSTS API UNITS, priced per row: two 1-unit columns, so a monthly two-year pull is 24 rows at 2 units and lands on the 50-unit minimum, while the same range daily is 730 rows at 2 units and costs 1,460. Domain Rating over time, one row per bucket. DR IS A POINT-IN-TIME SCORE on a logarithmic scale relative to every other site in the index - it cannot be summed, and an average of DR values is not a meaningful number, so nothing here is aggregatable.

Ahrefs: Get Keyword Metrics

COSTS API UNITS, and this is the node where a naive loop hurts most: the 50-unit floor is per REQUEST, so scoring 100 keywords one at a time costs 5,000 units minimum while one call with all 100 costs the same floor plus the row cost. ALWAYS PASS THE WHOLE LIST. Volume, difficulty, CPC, clicks, traffic potential, parent topic and search intent for a set of keywords. volume, difficulty, global_volume, traffic_potential and intents are 10 units EACH. cpc is in USD cents. FREE TEST: free when the only keywords are ahrefs, yep or firehose.

Ahrefs: Get Keyword Volume By Country

COSTS API UNITS: one row per country with two 1-unit columns, so this normally lands on the 50-unit minimum. Where in the world a keyword is searched, ranked by volume - the market-selection report. Takes one keyword only. FREE TEST: free for the keywords ahrefs, yep or firehose.

Ahrefs: Get Keyword Volume History

COSTS API UNITS: one keyword, one row per month, so a five-year pull is 60 rows and lands near the 50-unit minimum. But it takes ONE keyword only - checking seasonality across twenty keywords is twenty requests and twenty 50-unit floors, so batch that decision consciously. Monthly search volume for a keyword over time, which is how you tell a seasonal term from a dying one. Unlike every other history endpoint here, the grain is fixed monthly and the volumes ARE additive: summing twelve months gives the year's searches. FREE TEST: free for the keywords ahrefs, yep or firehose.

Ahrefs: Get Metrics By Country

COSTS API UNITS, and this one can get expensive: one row per country the target has any presence in, which is often dozens, multiplied by a per-row cost that the four traffic and cost columns push to 40+ units each. Trim Columns hard. Same metrics as Ahrefs: Get Traffic and Keyword Metrics, split by country, on one date. Monetary values are USD cents.

Ahrefs: Get Outlinks Stats

COSTS API UNITS: one row of four 1-unit fields, so the 50-unit minimum applies. How many external links and unique linked domains a target points OUT to, with dofollow counts. Ahrefs marks this endpoint BETA and warns its numbers may not match the Ahrefs UI exactly. Snapshot counts with no date parameter - there is no way to ask for a past value.

Ahrefs: Get Ranking Keywords History

COSTS API UNITS, priced per row; all columns here are 1 unit, so the bill is driven purely by how many buckets Grouping produces. How many keywords the target ranks for in each position band over time (top 3, 4-10, 11-20, 21-50, 51+). This is the report that shows rankings improving rather than just traffic moving. Each row is a standing at that point, so take the last row for a window and never sum the bands across dates.

Ahrefs: Get Ranking Pages History

COSTS API UNITS, priced per row (two 1-unit columns; Grouping sets the row count). How many of the target's pages rank in the top 100 - or top 10, via Positions - over time. Each row is the count AT that point, a standing rather than an event, so the window's value is the last row.

Ahrefs: Get Referring Domains History

COSTS API UNITS, priced per row, and note the column: refdomains is a 5-UNIT field, so a daily two-year pull is 730 rows at 6 units each, about 4,400 units. Monthly is 24 rows and hits the 50-unit floor. The count of unique referring domains over time - this is the link-growth chart. Each row is a CUMULATIVE SNAPSHOT of how many domains linked at that moment, not how many were gained in that bucket, so the window's figure is the last row and summing the rows is meaningless.

Ahrefs: Get SERP Overview

COSTS API UNITS: up to 100 rows for one keyword, and traffic, value and top_keyword_volume are 10 units each while refdomains is 5. Set Top positions to 10 rather than pulling the whole hundred. Who currently ranks for a keyword, with each result's DR, UR, backlinks and estimated traffic - the can-I-rank-here report. Takes ONE keyword: a loop over keywords pays the 50-unit floor every time, so scope those runs. value is in USD cents. FREE TEST: free for the keywords ahrefs, yep or firehose.

Ahrefs: Get Total Search Volume History

COSTS API UNITS, and the metric column is a 10-UNIT field: a daily two-year pull is 730 rows at 11 units, roughly 8,000 units. Monthly is 24 rows and hits the 50-unit floor. The combined monthly search volume of every keyword the target ranks for in the top 10 (or top 100), over time - the addressable-demand chart. Each row is the total AS OF that point, so take the last row for a window rather than summing.

Ahrefs: Get Traffic Metrics History

COSTS API UNITS, priced per ROW, and the row count is set by Grouping: two years monthly is 24 rows, two years daily is 730. All four metric columns are 10-unit columns, so a daily two-year pull with everything selected is in the tens of thousands of units. Organic and paid traffic and their estimated values over time, one row per bucket, each carrying its own date. Monetary values are USD cents. THESE ARE GAUGES: each row is the estimated CURRENT monthly figure at that point, so the window's value is the last row, never the sum of the rows.

Ahrefs: Get Traffic and Keyword Metrics

COSTS API UNITS: one row, but four of its eight fields are 10-unit columns and the endpoint has no select, so the per-row cost is fixed and high - it still lands on the 50-unit minimum because it is a single row. The headline Site Explorer numbers for one target on one date: organic keywords and traffic, traffic value, paid keywords, paid traffic and paid cost. All monetary values are USD CENTS - divide by 100. Estimates of the current monthly figures on that date, not measurements of that day.

Ahrefs: Get URL Rating History

COSTS API UNITS, priced per row (two 1-unit columns; Grouping sets the row count). URL Rating for a single page over time. Point this at a URL rather than a domain - on a bare domain it reports the homepage. UR IS A POINT-IN-TIME SCORE on a logarithmic scale and must never be summed or averaged, so this series is chartable but not aggregatable.

Ahrefs: List Anchor Texts

COSTS API UNITS, priced per row against the default limit of 1,000, though anchor reports are usually short. The anchor texts pointing at a target, with how many links and pages use each. This is the over-optimisation check: a commercial keyword dominating the anchor profile is the classic penalty signal. top_domain_rating is the single highest DR among the linking domains, a maximum rather than a total.

Ahrefs: List Backlinks

COSTS API UNITS, and this is the single most expensive node in the connector if configured carelessly: cost is per-row cost times rows, the default limit is 1,000, and traffic and traffic_domain are 10-unit columns. Selecting traffic on a 1,000-row pull costs over 10,000 units by itself. Every backlink pointing at a target, with anchor text, follow status, first-seen date and the strength of the linking page. Set a small Max rows and sort by what you care about - there is no pagination, so a small sorted request IS the top-N query.

Ahrefs: List Best Pages By Backlinks

COSTS API UNITS, priced per row; only refdomains_target is above 1 unit here (5), so this is one of the cheaper link reports. Which of a target's own pages have attracted the most links, with the highest DR among their referrers. The internal-linking opportunity report: these pages hold the authority you can pass on. Formerly /site-explorer/best-by-external-links.

Ahrefs: List Broken Backlinks

COSTS API UNITS, priced per row against the default limit of 1,000 - the same arithmetic as Ahrefs: List Backlinks. Backlinks pointing at pages of yours that no longer resolve, with the target page's HTTP code. This is the link-reclamation report: every row is equity you already earned and are now throwing away on a 404. Note there is no history parameter here, unlike the main backlinks report.

Ahrefs: List Crawled Pages

COSTS API UNITS, priced per row against the default limit of 1,000 - but every column here costs 1 unit, so a full 1,000 rows with all seven columns is about 7,000 units. Every URL of a target that AhrefsBot has crawled, with its HTTP status, title, URL Rating and crawl dates. Filter on http_code to find broken or redirecting pages without running a Site Audit.

Ahrefs: List Crawler IP Ranges

FREE - consumes no API units and needs no API key at all. The IPv4 CIDR ranges AhrefsBot crawls from. This is the node for verifying that a hit in your access logs claiming to be AhrefsBot really is: user agents are trivially forged, IP ranges are not. Returns data.prefixes[].ipv4Prefix.

Ahrefs: List Keyword List Keywords

FREE - consumes no API units. The keywords saved in a Keywords Explorer list. Reading a list here is free; feeding its id into a Keywords Explorer node as Keyword list id is NOT, and makes that request billable even for the free test keywords - so pull the keywords with this node and pass them as a comma-separated Keywords value when you want the free path.

Ahrefs: List Linked Domains

COSTS API UNITS, priced per row against the default limit of 1,000. The domains a target links OUT to, with how many links and pages point at each. The outbound mirror of Ahrefs: List Referring Domains - useful for auditing who a site is endorsing, and for spotting sold links on someone else's.

Ahrefs: List Locations and Languages

FREE - consumes no API units. The location ids and language codes available for one country, which are what Ahrefs: Add Project Keywords needs to place a tracked keyword in a city or a language. Note the shape: data.location.locations and data.location.languages are arrays of two-element PAIRS ([id, name] and [code, name]), not objects, which is why no picker reads from this node.

Ahrefs: List Matching Terms

COSTS API UNITS, priced per row, and keyword-idea reports return a LOT of rows: the default limit is 1,000 and the documented maximum is 150,000. With volume and difficulty selected that is 20 units a row. Set Max rows deliberately. Keyword ideas containing your seed terms - the bread-and-butter keyword-research report. Set Terms to questions for question-shaped ideas, and Match mode to phrase to require the words in order. FREE TEST: free when the only seeds are ahrefs, yep or firehose.

Ahrefs: List Organic Competitors

COSTS API UNITS: traffic and value are 10-unit columns, though competitor lists are naturally short so a sensible Max rows keeps this cheap. The sites competing with a target for the same keywords, ranked by keyword overlap. Country is REQUIRED here, unlike most Site Explorer reports. value is in USD cents. share is each competitor's proportion of the shared keyword set.

Ahrefs: List Organic Keywords

COSTS API UNITS, and the expensive columns here are the ones everyone wants: volume, keyword_difficulty and sum_traffic are 10 units EACH, so all three on a 1,000-row pull is 30,000+ units in one call. Every keyword a target ranks for, with its best position and the URL that holds it. Set a small Max rows and sort - there is no pagination. Setting a Comparison date turns on the _prev and _diff columns, which describe the comparison date rather than this row's date.

Ahrefs: List Paid Pages

COSTS API UNITS: sum_traffic, value and top_keyword_volume are 10 units each and referring_domains is 5. The landing pages a target runs paid search ads to, with how many ads and keywords point at each. This is the competitor-ad-spend report - what someone is willing to pay for tells you which pages make them money. value is in USD cents.

Ahrefs: List Project Competitors

FREE - consumes no API units. The competitors configured on a Rank Tracker project, with the scope each is tracked at. These are the domains that appear in Ahrefs: Rank Tracker Competitors Metrics, so read this when a competitor report shows fewer rivals than expected - the answer is usually that nobody added them to the project.

Ahrefs: List Project Keywords

FREE - consumes no API units. Every keyword tracked in a Rank Tracker project, with the location and language each is tracked in and any tags on it. This is the node to read before adding keywords, so a workflow does not re-add what is already there, and it is what supplies the location ids and language codes the SERP node and the delete node need.

Ahrefs: List Projects

FREE - consumes no API units. Every project in the workspace with its id, name, target URL, scope, owner, folder and tracked-keyword count. This is the lister behind the project picker on every Rank Tracker node, so it runs whenever someone opens one of those config panels - which is safe precisely because it is free. Note data.projects[].project_id comes back as a STRING even though the parameter that consumes it is documented as an integer.

Ahrefs: List Referring Domains

COSTS API UNITS, priced per row against the default limit of 1,000. One row per DOMAIN linking to the target, with its Domain Rating, how many links it sends, and when the first one appeared. Usually the report you want instead of Ahrefs: List Backlinks - it is a fraction of the rows for the same question, and the row count is what you are billed on. domain_rating is a point-in-time score: sort and filter on it, never total it.

Ahrefs: List Related Terms

COSTS API UNITS, priced per row, default limit 1,000 and a documented maximum of 150,000 - the same spend arithmetic as Ahrefs: List Matching Terms. Keyword ideas that do NOT contain your seed: what the pages ranking for it also rank for (also_rank_for) and what they also talk about (also_talk_about). This is the topical-coverage report - it finds the subtopics a competing page covers and yours does not. FREE TEST: free when the only seeds are ahrefs, yep or firehose.

Ahrefs: List Search Suggestions

COSTS API UNITS, priced per row, default limit 1,000 and a documented maximum of 150,000. Autocomplete suggestions for your seed keywords - what the search box offers people as they type, which is the closest thing to raw unfiltered demand. FREE TEST: free when the only seeds are ahrefs, yep or firehose.

Ahrefs: List Site Audit Issues

COSTS A FLAT 50 API UNITS per request - not per row, so pulling the whole issue list costs the same as pulling one, and there is no select to trim. Every technical SEO issue found in a Site Audit crawl, with its category, severity and how many URLs it affects. Set a Comparison date and the added, new, removed, missing and change columns fill in, which turns this into a regression alarm: branch on data.issues[].new being above zero for an Error-importance issue.

Ahrefs: List Site Audit Projects

FREE - consumes no API units. Health score and crawl summary for each Site Audit project: how many URLs were crawled, how many have errors, warnings and notices, and when the last crawl finished. The health score is a proportion of clean URLs at a point in time, so track it as a line and never total it. This is also the lister behind the project picker on Ahrefs: List Site Audit Issues, and only projects with a finished crawl appear.

Ahrefs: List Top Pages

COSTS API UNITS, with the most 10-unit columns of any node here: sum_traffic, value, top_keyword_volume and all SEVEN ai_responses_* columns are 10 units each, and referring_domains is 5. Selecting the AI citation set alone adds 70 units per row. A target's best-performing pages by organic traffic, with the keyword driving each. Since 2026-07-30 the ai_responses_* columns report how often each page is cited by ChatGPT, Gemini, Perplexity, Copilot, Grok and Google's AI surfaces - which is the AI-visibility report, at ten units a column.

Ahrefs: Rank Tracker Competitors Metrics

FREE - consumes no API units. One summary row per competitor in the project: how many tracked keywords they hold in each position band, their average position, share of voice, and how many SERP features they own (AI overviews, featured snippets, image packs, video previews and the rest). Note the response region is data['competitors-metrics'] with a HYPHEN, which does not match the path's competitors-stats. average_position is an average already - do not average it again across dates without weighting.

Ahrefs: Rank Tracker Competitors Overview

FREE - consumes no API units. One row per tracked keyword, carrying a competitors_list array with where EVERY tracked competitor sits on that keyword. This is the head-to-head view: read data.overviews is wrong here, the region is data.keywords, and the per-competitor detail is nested inside each row rather than being its own row.

Ahrefs: Rank Tracker Competitors Pages

FREE - consumes no API units. Which PAGES, yours and your competitors', win the project's tracked keywords, with share of voice and share of traffic value for each. Note the response region is data['competitors-pages'] with a HYPHEN, not an underscore. Share of voice is a percentage of the tracked keyword set - a ratio, so never sum it across rows or dates.

Ahrefs: Rank Tracker Overview

FREE - the whole Rank Tracker tool consumes no API units, so this is the node to schedule daily without watching the meter. Every tracked keyword in a project with its current position, the ranking URL, volume, difficulty and SERP features. Device is required and desktop and mobile are tracked separately. Set a Comparison date to populate the _prev and _diff columns (position_diff is the movement report). Rows are per keyword per location, not per keyword.

Ahrefs: Rank Tracker SERP Overview

FREE - consumes no API units, which is the whole reason to prefer it over Ahrefs: Get SERP Overview when the keyword is already tracked in a project. The full SERP Ahrefs last captured for one tracked keyword, with each result's DR, UR, backlinks and estimated traffic. The keyword must already be in the project - this reads a stored snapshot rather than buying a new one. This endpoint takes no select: it returns its whole column set.

Action nodes 3

Ahrefs: Add Keyword List Keywords

FREE - consumes no API units. Adds keywords to an existing Keywords Explorer list, which is how a research workflow hands its findings back to a human: run Ahrefs: List Matching Terms, filter it, and write the survivors into a list someone opens in the app. The list must already exist - v3 has no create-list endpoint. Reversible by removing the keywords in the Ahrefs UI. Keyword-list count is a plan limit (50 on Lite, 100 on Standard, 200 on Advanced, 500 on Enterprise).

Ahrefs: Add Project Keywords

FREE - consumes no API units, but it does consume the project's TRACKED KEYWORD allowance, which is a plan limit (750 on Lite, 2,000 on Standard, 5,000 on Advanced). Adds keywords to a Rank Tracker project. Every keyword is added in every location given, so 10 keywords x 3 locations is 30 tracked keywords, not 10. Reversible with Ahrefs: Delete Project Keywords, though removing and re-adding restarts that keyword's position history.

Ahrefs: Delete Project Keywords

FREE - consumes no API units. DESTRUCTIVE AND IRREVERSIBLE: removing a keyword from a Rank Tracker project stops tracking it and discards its stored position history for that project. Re-adding it starts a new history from that day; the old positions do not come back. Each entry identifies ONE tracked row, so a keyword tracked in three locations needs three entries or two of them survive. Read Ahrefs: List Project Keywords first to get the exact country, location_id and language of each row.

Connecting Ahrefs takes one credential

Keys are created in Ahrefs under Account settings on the API keys page, and only workspace owners and admins can create one. A workspace can hold up to 1,000 keys, each key expires one year after it is created, and a key is invalidated if the person who created it is removed from the workspace. The single most useful thing on that page for automation is the per-key monthly unit ceiling: it is set per key, not per workspace, so an automation key can be capped well below the workspace allowance and a runaway loop hits your own limit rather than your budget. On plan access, Ahrefs' current pricing table lists direct API access on all four plans, Lite through Enterprise, so it is not Enterprise-only. What the plan does change is the maximum rows a single request can return, which the same table gives as 100 on Lite, 250 on Standard, 500 on Advanced and uncapped on Enterprise, along with the monthly unit allowance. There is no free API tier: Ahrefs Free is a limited user interface product rather than API access.

1

In Ahrefs, open Account settings and go to API keys. Create a key as a workspace owner or admin, and set that key's monthly unit limit while you are there.

2

In Mattering Automations, open Connectors, click Add Connector, choose Ahrefs, and create a credential with the key.

3

Click Test Connection. Mattering calls Ahrefs' limits and usage endpoint, which Ahrefs documents as free and consuming no API units, so retesting a credential never costs anything. A pass returns the plan, the unit ceiling, the spend so far and the key's expiry date.

4

All 49 Ahrefs nodes appear in the canvas palette. Build against the free half first, and use Ahrefs' free test targets before pointing anything metered at a real domain.

Common uses for the Ahrefs MCP

Backlink monitoring with the column list as the budget

Ahrefs: List Backlinks and Ahrefs: List Broken Backlinks are the reports most teams want on a schedule, and they are also where the unit formula bites. The per-row cost is the sum of the costs of the unique fields you select, filter on or sort by, so choosing columns is choosing a price: traffic and traffic domain are 10 unit fields and four of the referring-domain columns are 5 unit fields, while the plain link columns are 1 unit each. Select what the workflow actually reads, sort on a cheap column where you can, and set a real limit. Ahrefs: Get Backlinks Stats is the flat-cost sizing call to run first, because it answers how big the profile is for the price of one row.

Everything Rank Tracker, on a daily schedule, for nothing

Ahrefs marks all five Rank Tracker reports as consuming no API units, and that changes what is sensible to automate. Ahrefs: Rank Tracker Overview, Ahrefs: Rank Tracker Competitors Overview, Ahrefs: Rank Tracker Competitors Pages, Ahrefs: Rank Tracker Competitors Metrics and Ahrefs: Rank Tracker SERP Overview can run every morning into a Mattering database with no spend at all, which makes position tracking the natural daily job and the metered link reports the occasional one. The management nodes are free too, so Ahrefs: List Projects and Ahrefs: List Project Keywords can keep an inventory of what is being tracked without touching the allowance.

Seven history reports into a dataset you own

Ahrefs: Get Traffic Metrics History, Ahrefs: Get Domain Rating History, Ahrefs: Get URL Rating History, Ahrefs: Get Referring Domains History, Ahrefs: Get Ranking Pages History, Ahrefs: Get Ranking Keywords History and Ahrefs: Get Total Search Volume History all take a date window and a grouping of daily, weekly or monthly. Pull them on a schedule and you have your own longitudinal record rather than a chart you have to open a browser to see. One thing to carry into whatever consumes them: these rows are gauges, not flows. Each row is Ahrefs' estimate of the state at that point in time, so the honest roll-up for a window is the latest value, and Domain Rating and URL Rating should not be rolled up at all, because a rating is a position on a relative scale rather than a quantity.

Keyword research and SERP work that feeds a brief

Ahrefs: Get Keyword Metrics returns volume, difficulty, traffic potential and intent for a keyword list, Ahrefs: List Matching Terms, Ahrefs: List Related Terms and Ahrefs: List Search Suggestions expand a seed into candidates, and Ahrefs: Get SERP Overview shows who currently holds the result page. Chain them into a content brief that lands in a Productivity task so the writer sees the difficulty and the current SERP in the same card as the assignment. Cost discipline is the same discipline as everywhere else here: volume, global volume, difficulty, traffic potential and intents are all 10 unit columns, so ask for the ones the brief prints and leave the rest out.

Site audit health as a monitoring signal

Ahrefs: List Site Audit Projects is free and returns each crawled project's health score, which makes it a sensible thing to read on a schedule and alert on. Ahrefs: List Site Audit Issues is the detail view, and it is one of the flat-cost endpoints: Ahrefs documents a fixed 50 units per request rather than a per-row charge, so pulling the issue list is priced the same whether it comes back short or long. The natural shape is free polling of the health score with a metered issues pull only when the score drops, which is a workflow rather than a dashboard.

Build and test the whole workflow without spending a unit

Ahrefs publishes free test queries, and they are the difference between a cautious build and an expensive one. Site Explorer requests are free when the target is ahrefs.com, yep.com or firehose.com, or a URL on one of them. Keywords Explorer and SERP Overview requests are free when the only keywords are ahrefs, yep or firehose. The limit is capped at 100 on a free request, and mixing in any other keyword, or passing a keyword list id, makes the whole request billable again. Point a new workflow at a free target, prove every branch, then change one field to the real domain.

Example: A weekly link-change report that checks its own budget first

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a weekly schedule fires.

2

Ahrefs: Get API Limits and Usage runs first and costs nothing. It returns the plan, the monthly unit ceiling and the spend so far, and a condition stops the run and opens a task if the remaining units are below what the rest of this workflow will spend.

3

Ahrefs: Get Backlinks Stats sizes the profile for a flat cost, so the next step knows roughly what it is asking for.

4

Ahrefs: List Broken Backlinks runs with a deliberate column list and an explicit limit. The per-row cost is the sum of the unique fields selected, filtered and sorted on, so the workflow selects only the columns the report prints and sorts on a cheap one.

5

Ahrefs: Rank Tracker Overview runs for free and adds this week's tracked positions to the same report.

6

The rows land in a Mattering database beside last week's, a task opens only when a lost link crosses the authority threshold you set, and the units spent are visible next week in the same limits and usage call that opened this run.

Ahrefs MCP questions, answered

What does an Ahrefs API call actually cost?

Ahrefs meters in API units, and its documented formula is the greater of a base cost and a per-row cost multiplied by the number of rows. The base cost of any billable request is 50 units. The per-row cost is the sum of the costs of each unique field that appears in the returned result or in the filter and sort parameters, counted once even when a field appears in several of them. Most fields cost 1 unit, but certain metrics cost 5 or 10. Ahrefs' own worked example is a backlinks request selecting title and traffic, filtering on traffic and referring domains, sorting by traffic and returning 500 rows: 6,000 units, because traffic is a 10 unit field. Ahrefs also states that units once consumed are non-refundable, which is why every metered node in this connector names its expensive columns rather than leaving you to discover them. Three shapes exist beyond the standard one: 17 nodes are free outright, Ahrefs: List Site Audit Issues is a flat 50 units per request, and the historical volume column on Ahrefs: Get Keyword Metrics bills per historical month with a 50 unit minimum, which means the width of the window is priced and not only the row count.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. On a metered API the more important half is that the same nodes also run unattended on a schedule or a trigger, with the key held once in the workspace rather than in each person's client config, and with a per-key monthly unit ceiling set on the Ahrefs side as a hard backstop.

Which Ahrefs plans include API access?

More than the folklore suggests. Ahrefs' current plan comparison table lists direct API access on all four plans, Lite through Enterprise, with a value in every column rather than the three columns that features excluded from Lite show. Ahrefs' MCP documentation describes the same gate from the other direction, saying the hosted MCP server is for users on a Lite plan or higher. So API access is not Enterprise-only. What Enterprise buys is uncapped access, which is a different claim. There is no free API tier and no trial: Ahrefs Free is a limited user interface product, not API access. The plan does change one thing that will bite a workflow, and it is worth reading the next question about it.

Why did a limit of 1,000 return 100 rows?

Because your plan caps the maximum rows a single request may return, and the cap is silent rather than an error. Ahrefs' pricing table gives the maximum rows per request as 100 on Lite, 250 on Standard, 500 on Advanced and uncapped on Enterprise. A connector cannot enforce this for you, because it does not know your plan, so every limit field in this catalog warns about it and the honest defence is to compare the row count you got against the row count you asked for. This matters more than it sounds: these list endpoints are ranked and truncated, and there is no pagination anywhere in the API. A different slice comes from changing the sort and the filter, not from asking for page two, so a truncated report that looks complete is the failure to design against.

Does testing the connection spend units?

No, and that was the deciding criterion when the test was chosen. Mattering probes the credential with Ahrefs' subscription limits and usage endpoint, which Ahrefs' own documentation describes as free and consuming no API units. On an API where units are explicitly non-refundable, a probe that spent 50 units every time somebody clicked Test Connection would be a defect. A pass proves the host, the version path, the header, and that the key is live and unexpired, and it returns the plan name, the unit ceiling, the spend so far and the key's expiry date. What it does not prove is that a given data endpoint is available on your plan, or that a large request will fit under the row cap.

Can I build and test a workflow without spending anything?

Largely, yes, and this is the most practical thing on the page. Ahrefs publishes free test queries: Site Explorer requests are free when the target is ahrefs.com, yep.com or firehose.com or a URL on one of them, and Keywords Explorer and SERP Overview requests are free when the only keywords are ahrefs, yep or firehose. The limit is capped at 100 on a free request, and mixing any other keyword into the list, or passing a keyword list id, makes the whole request billable. On top of that, 17 of the 49 nodes are free outright against your own real data: all five Rank Tracker reports, all seven management nodes, Ahrefs: Get API Limits and Usage, Ahrefs: List Locations and Languages, Ahrefs: Get Domain Rating (Free Endpoint), Ahrefs: List Crawler IP Ranges and Ahrefs: List Site Audit Projects. Between the two, most of a workflow can be proved before a unit is spent.

Ahrefs publishes its own MCP server. Why use this connector?

Ahrefs does, it is properly documented, and for interactive questions in a chat client it is a good answer: a hosted streamable endpoint with setup guides for Claude, ChatGPT and other clients, available on a Lite plan or higher. But Ahrefs' own MCP documentation is unusually clear about what that endpoint is not for, and it is worth quoting rather than paraphrasing: using the external MCP endpoint via custom scripts, bridges, or standalone HTTP or JSON-RPC clients is unsupported and not permitted, the external MCP server is not a general-purpose programmatic API, and for supported programmatic access to Ahrefs data, please use the Ahrefs public API. This connector is that supported path. It calls the public v3 API under your own workspace key, which means scheduled runs, multi-step workflows, chaining with every other connector in the fleet, and a credential held once in a shared workspace store are all on the surface Ahrefs designed for them. Use their MCP server to ask; use this to build.

What Ahrefs operations are supported, and what is left out?

49 nodes: 46 read and 3 act. Site Explorer covers Ahrefs: Get Domain Rating, Ahrefs: Get Backlinks Stats, Ahrefs: Get Outlinks Stats, Ahrefs: Get Traffic and Keyword Metrics, Ahrefs: Get Metrics By Country, the seven history reports, Ahrefs: List Backlinks, Ahrefs: List Broken Backlinks, Ahrefs: List Referring Domains, Ahrefs: List Anchor Texts, Ahrefs: List Linked Domains, Ahrefs: List Organic Keywords, Ahrefs: List Organic Competitors, Ahrefs: List Top Pages, Ahrefs: List Paid Pages, Ahrefs: List Best Pages By Backlinks and Ahrefs: List Crawled Pages. Keywords Explorer covers Ahrefs: Get Keyword Metrics, Ahrefs: Get Keyword Volume History, Ahrefs: Get Keyword Volume By Country, Ahrefs: List Matching Terms, Ahrefs: List Related Terms and Ahrefs: List Search Suggestions. Beyond that are Ahrefs: Get SERP Overview, Ahrefs: Batch Analysis, five Rank Tracker reports, seven management nodes and two Site Audit nodes. Four whole Ahrefs tools are deliberately not built: Web Analytics, because it requires their script on your site and our own analytics reads that first-party; Brand Radar, which is large and new enough to deserve its own build; Google Search Console Insights, because Mattering already ships a first-party Search Console connector reading the same data from Google; and Social Media publishing, which is not SEO data. Project lifecycle writes are also excluded, so no node here creates or deletes an Ahrefs project.

49 nodes waiting on the canvas

Put Ahrefs to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Ahrefs is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products