How accurate are SEO tool traffic estimates? 15 sites against Search Console

1. Why I ran this

A business owner asked on Reddit why Semrush and Ahrefs showed about a tenth of the traffic Search Console reported, and whether that meant their SEO agency was doing something wrong. The replies agreed the tools were unreliable, but nobody showed how unreliable, or in which direction.

The site had 20,000 to 30,000 monthly visits in GA4, Semrush estimated about one tenth of the Search Console figure, and neither tool showed keywords the owner could see ranking near the top (r/SEO, also posted in r/bigseo). The best reply explained the mechanism: the tools only know the queries in their own database and multiply volume by a modelled click rate. That is also how DataForSEO defines its metric: estimated traffic is the product of CTR and search volume across all the keywords a domain ranks for (DataForSEO, vendor).

So I measured it. I took 15 sites I work on, mostly in Bulgarian search, with some Slovak, Romanian, UK and U.S. traffic, and compared October 2026 Search Console clicks in each site's main country with the estimate for the same country from DataForSEO Labs. I keep the sites anonymous. The per-site file labels them Site A to Site O, from the most underestimated to the most overestimated.

2. What earlier studies found

The published tests are mostly English-language and several years old. They found typical errors of roughly 20% to 70%, and the one that tested small sites found them estimated worse.

Two of these come from tool vendors. Ahrefs notes that its error depends heavily on the site and industry, from under 5% to more than 1,000% (Ahrefs, vendor). Screaming Frog found that for its three sites with under 10,000 organic visits, almost every tool's estimate was at least 40% wrong, and that one site living on long-tail local phrases was underestimated by all three (Screaming Frog, vendor). I found no published test for small-language markets like Bulgarian or Slovak, which is where most of my sample sits.

3. How far off were the estimates?

Far. The median site was estimated at 35% of its real clicks. Nine of the 15 sites were below half, six landed within 25% of reality, and only two were overestimated.

The worst case is the Reddit question in extreme form. Site A had 5,025 clicks in Bulgaria in October, from 258 different queries with at least one click. The tool listed one ranking keyword for it and estimated 92 visits, less than 2% of reality. Site B was estimated at 142 visits against 2,420 clicks.

All nine of the lowest ratios belong to Bulgarian sites. Five non-Bulgarian sites are too few to call a pattern, but the direction fits what earlier tests suspected: a keyword database is thinner where fewer people search, so the estimate falls short. The next section shows why the near-perfect totals for the other markets should not reassure you.

4. Why an accurate total can still be wrong

Because the tool overestimated the keywords it knew and missed most of the others. On the 3,318 keywords both sources had, it estimated 2.4 times the real clicks. Every site whose total landed within 25% shows the same pattern.

Take Site L. Its total estimate was 18,014 visits against 19,022 real clicks, 95% of reality, the kind of number that makes a tool look trustworthy. But 17,434 of those estimated visits sat on keywords that brought 4,559 real clicks in October. The other three quarters of its traffic came from searches the tool did not list. Site M, estimated at exactly 100%, follows the same pattern: 8,551 estimated visits on keywords that earned 3,178 clicks.

My data does not show why the per-keyword estimates run high, and part of it is how I matched them: clicks on a spelling variant of a keyword do not count toward it here. Two likely causes are inflated volumes for small markets and a click curve that assumes a clean results page. Real pages carry ads, maps, forums and AI Overviews; I measured how much an AI Overview alone takes in my study of the same queries a year apart. The positions also differed: on keywords in both sources, the tool's rank and the Search Console average position had a median gap of under 1 to 8 places, depending on the site.

5. What the tool cannot see

Most of the traffic. Across the 15 sites, 81% of real clicks came from keywords the tool did not list. Half of that is anonymized queries that Google hides from every tool, the other half named queries missing from the tool's database.

Anonymized queries are searches not issued by more than a few dozen users over two to three months. Google leaves them out of the query table to protect privacy but keeps them in the totals (Google Search Central). A keyword database built from search volumes cannot contain them, so any tool will miss this part of a site, and it was large here: a median 48% of clicks per site. The same hidden share distorts CTR analysis, as I showed in why site-wide CTR is low.

The named queries the tool missed are its own gap. On the median site, the tool listed 40% as many ranking keywords as the site had queries with at least one click, and the keywords it did list carried 37% of the clicks on named queries. Site E is a clear case: 1,917 queries with clicks in October and 100 keywords in the tool.

6. Can you still compare sites with it?

Roughly, and only within one market and one tool. The rank correlation between estimate and real clicks across my 15 sites was 0.71, near the 0.76 Pearson correlation Ahrefs reported for U.S. sites (a different measure). Single comparisons can be badly wrong.

A correlation of 0.71 means that a bigger site usually gets a bigger estimate. It does not mean any two sites will be ordered correctly. Site A, with 5,025 real clicks, was estimated at 92 visits; Site I, with 216 clicks, was estimated at 88. On the tool's numbers they were the same size. In reality, one had 23 times the other's traffic. Ahrefs makes the same point, framed in its own favor: the estimates are more consistent than they are accurate, especially within one industry (Ahrefs, vendor).

That is enough for a quick look at who leads a market. It is not enough to value a site you want to buy, to forecast what a client will get, or to judge whether an agency delivered. For those, ask for the Search Console data.

7. How to check a tool against your own data

Compare the tool's estimate for your own domain with your Search Console clicks for the same country and month. The ratio tells you how far to trust that tool in your market.

1. Take 30 days of Search Console clicks for your main country, web search only. Do not use GA4 all channels: as replies in the r/bigseo thread pointed out, Search Console counts only Google organic clicks, so compare it with the Organic Search channel in GA4.
2. Look up your domain in the tool for the same country and note its estimated monthly organic traffic and the number of keywords it says you rank for.
3. Divide the estimate by your clicks. Under 0.5 means the tool estimates less than half of your real clicks; that was 9 of my 15 sites.
4. Count your queries with at least one click in Search Console and compare with the tool's keyword count. A low share means it misses your long tail.
5. Before trusting a "good" total, open the tool's top keywords and compare each with Search Console clicks. If they are overestimated two or three times, the total is right by accident, as on Sites L and M.
6. Use the ratio on competitors in the same market and tool, as a rough correction, not a measurement.

If you are judging an agency, the tool gap is not evidence either way. Search Console clicks, the pages they land on, and the enquiries they bring are. An SEO audit should start from that data, not from a third-party estimate.

9. Methodology and limitations

Search Console clicks for October 1 to 30, 2026, in each site's main country, against DataForSEO Labs estimates for the same country, collected on November 2, 2026.

• Sites: 15 small business, ecommerce and information sites I work on, with at least 100 clicks in their main country in October. Two more properties had too little data and were left out. Names, verticals and query text are withheld.
• Real traffic: Search Console clicks, web search, all devices, filtered to the country with the most clicks (Bulgaria for 10 sites, Slovakia for 2, Romania, the UK and the U.S. for one each). Country totals include anonymized queries; query rows do not, and no site reached the 25,000-row limit.
• Estimates: DataForSEO Labs (Google) domain overview for estimated monthly organic traffic and keyword counts, and ranked keywords for per-keyword estimates, using the same country and its main language. Ranked keywords were capped at the 1,000 keywords with the highest estimate, which affects two sites. Cost: 0.89 USD.
• One provider: I did not test Semrush or Ahrefs directly. Their databases and click models differ, so their errors will differ in size, though the earlier studies point the same way.
• Matching: keywords were matched by exact text after lowercasing and trimming spaces. Spelling variants and word-order changes do not match, which makes the keyword-level overestimate somewhat larger than it is.
• Not like for like: a tool estimate is a modelled monthly figure from a database snapshot; Search Console clicks are counted for a fixed window. Clicks are not sessions. Seasonality between the snapshot and October can move the ratio.
• Limits: 15 sites is a small, non-random sample, heavy on Bulgarian. Only five sites come from other markets, so the market comparison is a hint, not a finding.
• Data: data-sites.csv (one anonymized row per site) and data-summary.json (every number on this page), CC BY 4.0.

10. Frequently asked questions

Sources

1. r/SEO. "GA4 and GSC show traffic, but Semrush and Ahrefs report much lower organic traffic. Is my SEO agency doing something wrong?" October 29, 2026. reddit.com/r/SEO/comments/1xigrrm/ga4_and_gsc_show_traffic_but_semrush_and_ahrefs/. Accessed November 2, 2026.
2. r/bigseo. Same question posted the same day, October 29, 2026. reddit.com/r/bigseo/comments/1xigstu/ga4_and_gsc_show_traffic_but_semrush_and_ahrefs/. Accessed November 2, 2026.
3. Tim Soulo, Ahrefs. "How Accurate Are the Search Traffic Estimations in Ahrefs? (New Research)." 1,635 websites, U.S. traffic. May 3, 2022. Vendor: sells SEO or analytics products. ahrefs.com/blog/traffic-estimations-accuracy/. Accessed November 2, 2026.
4. Patrick Langridge, Screaming Frog. "How Accurate Are Website Traffic Estimators?" 25 websites, mainly UK, Google Analytics data for February to April 2016. June 13, 2016. Vendor: sells SEO or analytics products. screamingfrog.co.uk/how-accurate-are-website-traffic-estimators/. Accessed November 2, 2026.
5. Daniel Waisberg, Google Search Central Blog. "A deep dive into Search Console performance data filtering and limits." October 19, 2022. developers.google.com/search/blog/2022/10/performance-data-deep-dive. Accessed November 2, 2026.
6. DataForSEO. "dataforseo_labs/google/domain_rank_overview/live" API documentation (definition of estimated traffic volume). Vendor: sells SEO or analytics products. docs.dataforseo.com/v3/dataforseo_labs/google/domain_rank_overview/live/. Accessed November 2, 2026.

Last updated: November 2, 2026. Related research: all studies.