DataForSEO: where the volume comes from, and what happened to it on the way

DataForSEO is an application programming interface that resells search data in bulk: keyword volumes, suggestions, backlinks, results pages. On volumes it measures nothing of its own. It serves the Google Ads keyword planner, one call at a time.

A search volume is not a count of last month. It is a twelve-month average, computed across a family of phrasings. Everything you do with it follows from that.

1. The problem it solves for me

A keyword plan rarely holds under 300 queries, and it has to be read market by market. On a mortgage brokerage account I had four countries to compare across a single list. A matrix that size is not built by hand: it needs a source a script can call, pour into a sheet, and replay three months later on the same list to see what moved.

That is the whole reason I went through an interface rather than a screen. Not to get a different number: to get 1,200 of them at once, traceable and repeatable.

2. What I do with it, and the figure that settled the question

On that same account, Sistrix reported 1,400 monthly searches on a mortgage calculator query. DataForSEO returned 18,100, at low competition, same country and same month. Thirteen times apart on the same query.

The gap stops being mysterious once you know where each figure is made: one comes from an in-house model built on a traffic panel, the other from Google's own planner. So I do not treat them as two opinions about one fact. When they diverge by that much I take Google's and record the other beside it, because an editorial plan built on 1,400 and a plan built on 18,100 do not produce the same page.

3. What I never ask it for

This month's figure. Google Ads help on keyword planner statistics states it plainly: average monthly searches is an average taken over twelve months, across all languages. In a seasonal trade the displayed number describes no month of the year. A market that lives from April to September shows up at half its June weight and double its January weight.

A figure per phrasing. The same Google page specifies that the statistic covers the keyword "and its close variants". Accents, plurals, word order: the whole family reports the same number. So I never sum the rows of one family in a content plan, on pain of counting the same volume three times and announcing a potential that does not exist. It is the most expensive mistake in keyword research, and it goes unnoticed because the total still looks plausible.

The corollary runs against intuition, and it can be worked. Two variants that share a volume do not share a ranking. On that brokerage account the same page came out 27th on one variant and 32nd on the other. Two pages can therefore split a family by each claiming one phrasing in its title tag, where the volume table suggested merging one into the other. That is the working principle behind a semantic cluster that lasts.

A zero. A volume of zero means "below Google's reporting threshold". It does not mean nobody searches. I write the first phrase in a deliverable and never the second: of the two, only one is accurate.

The whole search network. By default, partner sites that host Google search sit outside the figure. You have to ask for them explicitly, and in some markets the difference is not a rounding error.

What my site actually captures. DataForSEO describes demand, never my share of it. Measuring what Google truly showed a site is a different job, and I have written up its own blind spots in what I ask Search Console for.

4. What I run alongside it

Search Console first, on any family where the site already exists: real impressions are a fact, an estimated volume is a model, and the two only read well side by side. A dedicated rank tracker next, because neither of them tells you where a page sits on a given day. And a spreadsheet, plainly, because a volume only becomes a decision once it is lined up against a URL, an intent and a title tag that claims its own variant.

5. What it costs, counted in calls

The constraint is not the price, it is the shape of the billing. The documentation for the search volume endpoint is explicit: one call accepts up to 1,000 keywords, and the price does not depend on how many keywords it carries. One or a thousand, it is the same call.

That inverts the working method. With Semrush the unit is counted per row, so you ration the list and catch yourself dropping queries to protect a balance. Here you ration calls, not words. The list goes out whole, and the only ceiling I ever reach is a throughput ceiling: 12 calls per minute per account on these endpoints, with four years of history behind them.

Mistaking the refined product for the raw material

A search volume arrives averaged over twelve months, melted together with its variants, missing part of the network. It is not raw data, it is a finished product. Reading it without knowing what it went through means confusing the two, and building an editorial plan on a number you have not understood. That is exactly where the craft starts.

Want to know what your market actually searches for?

I pull the volumes, cross them with what Google already shows you, and tell you which pages are worth writing. It is the starting point of my SEO and content strategy engagements.

Request a free audit

Read next