SEO Data Bench/Guides/pay-per-lookup-seo-audit

Pay per lookup for occasional SEO audits: what one client audit cost through DataForSEO and Serpstat, measured

Field guidecohort v1US · enrun 2026-09-15includes a Treg route

One client audit (rankings for 50 queries, volumes for the same 50, the domain's ranked keywords, its backlink profile and a 100-page on-page crawl) run through two pay-per-call routes on 29 October 2026, with the settled cost per step and what the API did not return that a suite's screens do.

Written for people asking: Is anyone paying per lookup for occasional SEO client audits instead of keeping an Ahrefs plan for the API?How much would a single SEO audit cost through DataForSEO?What do you lose moving client audits from Ahrefs to a pay-per-call SEO API?

The question comes from an agency owner on a $139 Ahrefs plan doing four client audits a year who runs everything through Claude: “I have no idea what a single audit would cost me” on a pay-per-lookup route, and did clients notice the move (r/Agentic_SEO, 23 October 2026). This page prices one audit by running it.

What “one audit” was defined as

Five jobs on one domain, every one a job an audit deliverable usually opens with:

1. Rankings. Where the domain sits in Google for a fixed list of 50 queries. The list is this site’s cohort v1 (50 US-English buyer queries for data APIs, frozen on 15 September 2026); the domain is hunter.io, a cohort domain that competes on some of them.
2. Volumes. Monthly search volume for the same 50 queries.
3. Ranked keywords. Everything the domain already ranks for, first 1,000 rows.
4. Backlinks. A profile summary and the top 100 referring domains.
5. On-page crawl. 100 pages checked for the usual technical issues.

Two routes ran the same five jobs on 29 October 2026 (Sydney time): DataForSEO, whose SERP and crawl endpoints fetch live, and Serpstat, which answers from a stored index. Both were called through the Treg CLI, which injects the provider key and settles each call on a ledger, so the cost column below is what was billed, not a list price. Every call, its latency and the ledger are on the evidence page.

What it cost, per step

Two billing facts matter more than the totals. Serpstat meters per returned row: a 10-result SERP request returned 17 to 20 rows and cost 17 to 20 credits, about $0.0095 a call, and its ranked-keyword call consumed 1,000 credits by the provider’s own left_lines counter while the ledger settled it at $0; a direct Serpstat account would pay the $0.50. DataForSEO bills a failed live fetch: the one SERP call that returned status 40101 still cost $0.002. The whole run, both routes, moved the balance by $0.60.

Four audits a year against a seat

Ahrefs’ figure is the list price read on 26 October 2026 and detailed on what SEO data you can get for free; its 200,000 monthly units are more than four audits of this size need, so the seat’s cost is the subscription, not the units. The poster’s $139 is their own plan’s price and is quoted as written.

What the API returned, and what the suite’s screens show that it did not

Rankings disagreed between live and stored. On the 50 live Google pages hunter.io appeared in the top 10 for one query (“email finder api”, position 1). Serpstat’s stored index had it on three of its 20 held queries (positions 4, 5 and 14), and on the one query both returned it, the positions differed. The September run showed live routes returning different lists for the same query; a stored index is a third list again. An audit should name its route.

Volumes disagreed too. Both routes returned a number for 22 queries, and the number was the same on 5. “serp api” was 12,100 on both; “enrichment api” was 70 on DataForSEO and 1 on Serpstat; “keyword research api” 50 against 140. DataForSEO’s numbers are Google Ads Keyword Planner’s, which the coverage benchmark matched to the digit; Serpstat’s come from its own model. Nineteen of the 50 queries had no volume on DataForSEO, returned as null, not zero.

Ranked keywords and backlinks are index sizes. 8,045 against 12,042 keywords, 75,544 against 32,731 backlinks, for the same domain on the same day. Neither is wrong; each is the size of that provider’s crawl. The backlink benchmark measured the same spread across three indexes.

The crawl is counts, not a to-do list. DataForSEO’s 100-page crawl fired 21 of its 57 check types: 93 pages without image alt text, 20 titles too long and 34 too short, 2 duplicate titles, 0 broken links, 96 pages with render-blocking resources. That is the raw material of a technical audit section. What it is not is the ranked, explained issue list a suite’s site-audit screen shows, with a chart of the score over time; those come from the person or the agent reading the counts.

What was not available at all on either route: a historical series (the stored index returns the current snapshot; a series is yours to build by storing each run), screenshots of anything, Semrush or Ahrefs data as such (they do not sell per call; see the access-cost section), and a ranked issue list.

Who this fits

• Four audits a year, the API idle in between. Pay per call, and keep the seat only if a client is paying for a suite’s report format. The data cost is under $2 a year on these numbers; the real cost is the template you build once.
• An agent that runs the audit. The five calls above are the whole audit; an agent given the runner script and the domain can produce the dataset in about five minutes, most of it waiting on the crawl. Pin one SERP route and store its name with each run.
• Clients who read the suite’s screens. The API will not reproduce them. Run one audit this way first and look at what you would send.
• A stored index is fine for ranked keywords and backlink order, not for the current position of a query it does not hold.

What this page cannot tell you

One domain, one day, 50 queries in one niche, two routes. A larger domain costs more on the two lines that scale with rows and pages; a site with 50,000 pages is a different crawl bill. Ahrefs’ per-request unit costs beyond its 50-unit minimum depend on rows and fields and were not published on the help page read, so the seat is compared on its subscription, not on units an audit would use. Whether a client notices the move is not something a run can measure; the output format is, and it is a dataset. The Serpstat ranked-keyword call settling at $0 on the ledger is one observation on one day and may be a metering gap that closes.

Reproduce it

treg auth login
scripts/run-audit-cost.py evidence/fixtures/seo-cohort-v1.json evidence/audit-cost/$(date +%F) --domain example.com
scripts/score-audit-cost.py evidence/fixtures/seo-cohort-v1.json evidence/audit-cost/$(date +%F)

• summary.json with every count above; tables as CSV: positions (the audited domain’s position per query and route), volumes, cost per endpoint from the ledger, Serpstat credits per call.
• Scripts: runner, scorer; the cohort is on the dataset page. Raw responses are kept locally and not published, because full result lists and ranked-keyword rows are the providers’ data; the tables carry only the audited domain’s own positions and the counts.

Next step

• Run it on your own client domain before the renewal: the runner takes a domain and the query list and returns the dataset for under a dollar. Per-call rates and the route headers are in the Treg docs: treg.to/docs, treg.to/pricing.
• What each route returns beyond the ten links: SERP completeness. What a month of regular calls costs: latency and cost. What the free tiers cover before any of this: free SEO data APIs.

Relationship: the people who run this site also work on Treg, one of the routes compared on this page. Every Treg figure here is a call we paid for, with the raw response downloadable, and the same fixture is run against the alternatives where their terms allow.

Spotted an error or a changed price? Email corrections@seodatabench.com with the page URL and a source. Corrections are logged on the corrections page.