Domain Traffic Stats: Where the Numbers Come From and How to Read Them Properly

Domain traffic stats come in two kinds, and mixing them up causes most of the arguments. For a domain you own, you have counted data: your analytics tags, your server logs and Google Search Console tell you what actually happened. For any other domain, every public number is an estimate built from panels, clickstream data, DNS queries or search rankings, which means you read it as a range and only ever compare it with a number built the same way. Both kinds are useful. Only one of them is a measurement.

This page covers where each number comes from, the five questions that make any estimate readable, and a triangulation method that gets you close enough to make a decision.

Your own domain, where the numbers are counted

• Analytics. A tag in the page records sessions, users and pageviews for visitors whose browser loaded and allowed it. This is your best view of behaviour on the site and your weakest view of total visits, because blocked tags and declined consent simply do not appear.
• Search Console. Clicks, impressions, click through rate and average position for Google search, counted by Google rather than by your tag. Start with Google's own Search Console documentation, and our report by report guide explains what each number means.
• Server logs or edge logs. Every request, including the ones no tag saw, plus every bot. The most complete source and the one that needs the most filtering.

These three will disagree, and each is right about a different thing. Write down which one your reporting uses, and keep using that one, because a change of source looks exactly like a change in traffic.

Somebody else's domain, where the numbers are modelled

Source	Built from	Good for	Not built to tell you
Panel and clickstream estimators	Device panels, anonymised clickstream feeds and modelling, scaled to a population	Direction of travel, channel mix, country split, relative size of two competitors	An exact visit count for one month
Search based estimators	A keyword index plus each domain's ranking positions and a click curve	Which pages and queries earn a rival's search traffic	Anything outside organic search, such as email or app traffic
DNS resolver popularity	Query volume seen by a public resolver. Cloudflare Radar domain rankings publishes free ranked lists built from 1.1.1.1 resolver traffic, by category and as trending domains	Whether a domain is genuinely popular, and whether interest is rising	Visits, because a DNS query is not a pageview
Real user performance data	The Chrome UX Report, a public dataset of how real Chrome users experience popular destinations, available through BigQuery, the CrUX API and PageSpeed Insights	Confirming a site has a real audience, since inclusion needs enough visitors for a statistically significant dataset	A traffic figure, since it reports experience rather than volume
Stated figures	Annual reports, investor decks, press releases, advertising media kits	A company's own number, which is the only first party figure you will get	Comparability, because every company defines a visit to suit itself

Two of our tool specific walkthroughs go deeper on the first two rows: Similarweb traffic analysis and the Semrush traffic checker. For search volume estimates rather than site traffic, see building a traffic estimate you can defend.

Five questions that make any traffic number readable

1. Visits, users or pageviews? The same site can honestly be described with three numbers that differ by a factor of several. Note the unit before you note the figure.
2. Which geography? Many free views default to one country or to worldwide. A rival that looks half your size may be twice your size in your own market.
3. Which date range, and is it complete? A part finished month reads as a collapse.
4. Domain, subdomain or path? A shop on a subdomain, a help centre on another and a blog on a subfolder are often reported separately. Decide what you are counting and apply it to both sides.
5. How are bots handled? Server logs include them, tags mostly exclude them, estimators model them out. This single difference explains most mismatches between two sources.

Triangulate, then calibrate against a domain you own

Three steps give you a figure you can defend in a meeting.

1. Take three readings of the target domain, one from a panel estimator, one from a search based estimator and one popularity signal such as a resolver ranking. Record them with their date and geography.
2. Calibrate. Run the same three readings on your own domain, where you know the real answer, and work out how far each source sits from truth and in which direction. Most people find one source consistently high and another consistently low, and that correction factor travels reasonably well across similar sites.
3. Report a range, not a point. "Between 40,000 and 70,000 monthly visits, mostly organic, concentrated in the UK" is a sentence that survives scrutiny. A single number invites an argument about the number instead of a decision.

Re-run the exercise monthly if you are tracking a competitor, and keep the readings in one sheet with the date, so you are reading a trend you built rather than a figure a tool refreshed.

Four decisions these stats are already good enough for

• Judging a link or guest post prospect. A site selling placements on the strength of its traffic is easy to check: look for a plausible search footprint and real audience signals rather than a single large number in a media kit.
• Reading a competitor's channel mix. The split between search, direct, social, referral and paid tells you where a rival is actually strong, and that shape is more reliable than the absolute volume.
• Sizing a market or a partnership. Relative size between several domains built from one source is a sound basis for a decision about where to spend.
• Diligence on a site you may buy. Use public estimates to sanity check what the seller shows you, then insist on read access to analytics and Search Console before money moves.

If your reason for checking competitors is that your own numbers are falling, our guide to diagnosing traffic by channel is the better starting point.

Questions about domain traffic statistics

How accurate are public domain traffic estimates?

Accurate enough for comparison, and loose for absolutes. Treat them as a range, calibrate against a domain where you know the truth, and compare sites only within the same source.

Can I see exactly how much traffic a competitor gets?

Exact figures come from inside a business, through analytics access, a published report or an advertising media kit. From outside you build a well supported range, which is enough for nearly every decision you need to make.

Which free sources are worth using?

Resolver based popularity rankings, the Chrome UX Report for confirming a real audience, the free views offered by the main paid tools, and any figure the company has published itself. Four free readings beat one paid reading taken without context.

Why do two tools report very different numbers for the same domain?

Because they are built from different data: one from a panel, one from search rankings and a click model. Different inputs give different outputs, which is why you compare within a source rather than across sources.

Do these tools measure traffic from AI assistants?

Assistant referrals are a small and new line in most reports, and public estimators are built on surfaces that predate them. For your own site, isolate the referral sources in your analytics and watch that line directly.

A recommendation that leaves no row in any report

One gap sits outside every method on this page. When somebody asks ChatGPT, Gemini or Perplexity which supplier to use and the reply names three companies, the deal has effectively been shortlisted, and no estimator anywhere recorded it. The winner may never receive a visit from it, the losers have nothing to see. After a decade of treating visits as the measure of visibility that is an odd blind spot, and it means "how much traffic does this domain get" now needs a second question beside it: how often is this business the name that gets given. AI Knows Us treats the answer itself as the unit of measurement, recording who was named, in what order, and from which pages. Put that next to the estimates you just collected: aiknowsus.com.