When you screen hundreds of thousands of publisher domains, you need a traffic signal you can reproduce and defend — not a single invented visitor count. This guide compares two reproducible proxy approaches: Google's Chrome UX Report presence and rank groups, and third-party traffic-estimate vendors. Both are legitimate data sources; the question is which proxy fits screening at scale.
No one outside a publisher's analytics has their true visitor count. Everyone else works from a proxy — a measurable signal that correlates with traffic. The honest move is to name your proxy, report it as a proxy, and make sure anyone could reproduce it. That is what keeps a screening deliverable auditable.
A good proxy can be re-derived by a third party from a stated source. If a number can't be reproduced, it can't be checked — and we won't ship it as fact.
At screening scale you need the same signal on every domain, so publishers rank against each other consistently — not a mix of sources per row.
A proxy is labeled as a proxy. Presence-and-rank-group framing communicates a band of confidence rather than a false-precise visitor figure.
Both are real, widely-used data sources with legitimate uses. They answer slightly different questions, and each has a place in a screening stack. Here is what each actually is.
Whether a domain's origin appears in the public Chrome UX Report — a binary signal that the site has cleared Chrome's minimum-popularity threshold. Absence is informative too, especially for filtering the very smallest sites.
The coarse popularity band Google assigns an origin (a broad magnitude bucket rather than an exact rank). It orders publishers by scale without claiming a precise visitor count.
The same domains, viewed through each proxy, for the specific job of screening a whole vertical. Neither column is "wrong" — they optimize for different things.
| CrUX presence + rank groups | Traffic-estimate vendors | |
|---|---|---|
| What it returns | Presence flag + coarse rank group (magnitude band) | A specific estimated visits figure |
| Reproducible from a public source | Yes — public Google dataset | No — proprietary modelled estimate |
| Comparable across all domains | Same signal on every origin present | Depends on coverage per site |
| Precision claimed | Deliberately coarse (a band) | Precise-looking single number |
| Best-fit use | Whole-vertical screening & ranking | Deep single-site & competitive analysis |
| Coverage of tiny sites | May be absent below the threshold | Varies; often modelled or blank |
Across a run that can screen hundreds of thousands of domains, the traffic field has to be defensible on every row. We default to CrUX presence and rank group because any client can re-derive them from a public source — and we never ship a visitor count we can't stand behind.
If your workflow needs vendor estimates as an added field, we can incorporate a licensed source alongside the reproducible proxy — clearly labeled as a modelled estimate, never presented as measured fact.
The two data sources are complements more than rivals. Match the proxy to the decision you're making.
Use CrUX presence and rank group. You get one reproducible, comparable signal on every domain, so publishers sort by scale consistently and the field survives an audit.
Bring in a traffic-estimate vendor once you're evaluating a handful of finalists. Their richer single-site tooling adds context where an exact-looking figure and trend view are worth the proprietary trade-off.
The free pilot runs the full pipeline on your category and delivers your first 20 qualified publishers — each with a reproducible traffic proxy — plus a full-run projection. No cost, no obligation.
Request a Free Pilot