CrUX ad metrics give every buyer, seller and curious competitor a public read on how ad heavy your site feels to real Chrome users. Chrome added four experimental measurements to the Chrome User Experience Report on September 15, 2026: Ad Count, Ad Density, Ad Weight for network usage and Ad Weight for CPU usage. A week later Google listed them in its page experience documentation, and Chrome DevTools now has an Ads section to debug them locally. This guide explains what each metric measures, how Chrome collects it, whether it affects rankings and six essential checks to run before advertisers look you up.
Definitions and rules here come from Chrome for Developers documentation and Google Search Central, with a statement from Google's John Mueller verified on his Bluesky account. Chrome has not published targets for these numbers, so we do not suggest any.
Table of Contents
What Are CrUX Ad Metrics?
In its launch post, Chrome says the new metrics are "designed to describe websites' ad loads as real users encounter them." They sit in the same public CrUX dataset that already reports Core Web Vitals, which means anyone can look up an eligible origin.
Chrome's definitions are short. Ad Count is "the average number of ads in the viewport." Ad Density is "the average fraction of the viewport area occupied by ads." Ad Weight (Network Usage) is the resources consumed by ads measured in bytes, and Ad Weight (CPU Usage) is the resources consumed by ads measured in milliseconds.
In the CrUX API, the four keys are experimental_ad_density (a percent), experimental_ad_count (unitless), experimental_ad_cpu (milliseconds) and experimental_ad_kilobytes (kilobytes). All four are reported at the 75th percentile, or p75, over a 28 day rolling window.
How Chrome Measures Ad Count and Ad Density
According to Chrome's measurement methodology, collection starts when the browser receives the first response bytes for the main HTML document and ends when the page is unloaded. For Ad Count and Ad Density, Chrome samples the viewport once per second. An ad counts as visible if any of its pixels are inside the viewport at that sample point.
The two layout metrics treat overlap differently. For Ad Density, overlapping ads are counted once by taking the union of their areas, and only the part of an ad inside the viewport is measured. For Ad Count, each ad counts individually if at least one pixel is in the viewport, even when another ad covers it. Ads that are not rendered, such as those set to display: none, are left out of count and density, but their CPU and network weight still counts.
Some site behaviors change the math. Sampling pauses when a tab moves to the background. On single page applications, soft navigations do not reset the window, so samples from every view in the session are averaged together. On infinite scroll pages, Chrome notes that a user idling at the bottom keeps adding identical samples, which may skew the session average.
The p75 figure is what you will see reported. Chrome's own example: a p75 Ad Density of 23% means 75% of visits had an Ad Density of 23% or less. A p75 Ad Count of 3.00 means 75% of sessions had 3 or fewer ads in the viewport at any given sample point. Data comes from Chrome on Windows, macOS, Android, ChromeOS and Linux, while Chrome on iOS and Android WebView are excluded.
The ads.txt Rule and Ad Detection
Not every site gets reported. Chrome says it includes only sites that list at least one authorized seller in their ads.txt file. Origins with no ads.txt, or with only a placeholder record, are excluded from that reporting. The filter is applied during CrUX aggregation, so the DevTools Ads panel will still show local numbers for any page you inspect.
To decide what is an ad, Chrome uses its own ad detection. It matches requests against a filter list that Chrome describes as a condensed version of EasyList, and it labels resources or frames created while an identified ad script is on the JavaScript stack. Classification is sticky for frames, and the main frame itself will never be classified as an ad frame.
Developers can test this with a demo rule. Adding the query parameter ?ad_filterlist_demo_param=1 to a request URL makes Chrome treat that request as ad related, which is useful when checking how a new wrapper or lazy loading script is classified.
Are Chrome Ad Metrics a Ranking Factor?
Google has been careful here. Chrome says the metrics "are not part of Core Web Vitals and don't have suggested targets or thresholds," and there are no Good, Needs improvement or Poor labels. Google's page experience documentation now lists them as a resource that can help you understand your site's ad count, ad density and ad weight.
When Search Engine Roundtable asked about the addition, John Mueller replied on Bluesky: "We included them because they're available as metrics to help evaluate the state of your site. Not everything is a direct search ranking factor!" The same Google page says Core Web Vitals are used by its ranking systems, and that other page experience aspects don't directly help a site rank higher.
That does not make ads irrelevant to search. The page experience self assessment still asks whether your content avoids "an excessive amount of ads that distract from or interfere with the main content." And heavy ad code can still hurt the vitals that do count, which we cover in our guide to how ads impact Core Web Vitals and SEO.
Why Advertisers Will Look at This Data
Chrome's launch post says it expects the metrics "to be particularly useful for web advertisers and the services they use to place ads." The supporting quotes came from buyers, sellers and ad tech. Google Ads executive Bill Reardon said Display & Video 360 "supports this initiative to bring transparency to page layout quality."
Publishers who already run lighter layouts see an opening. Sara Badler, Chief Advertising Officer, North America at The Guardian, said: "As a publisher focused on independent, quality journalism, we want to be valued for the experiences we build, and these metrics provide a clear, objective ground truth to support that." Michael McNeeley of Index Exchange said "you can see the potential for an incentive shift," while adding there is "still work to be done on how best to use the data."
The flip side is that cluttered layouts become easier to spot from the outside. If your pages lean on stacked units, it is worth reading our breakdown of made for advertising sites to see how buyers already think about ad clutter.
Where to Find Your Numbers
Chrome's tooling guide lists four places. CrUX Vis is a dashboard that plots the past 40 weeks of rolling 28 day periods and updates weekly on Mondays. The CrUX API returns the latest 28 day snapshot for an origin or a URL and is updated daily. The CrUX History API returns weekly history, typically 40 data points. Chrome says it is also working on adding the metrics to the CrUX dataset on BigQuery.
For local debugging, Chrome's New in DevTools post for October 2026 describes an Ads section in the Application panel with a dashboard for the four metrics, CPU and network usage split by ad element, a table of ad scripts in the main frame and a toggle that highlights ads on the page.
6 Essential Checks for Publishers
1. Confirm your ads.txt lists an authorized seller
Without at least one authorized seller line, your origin will not appear in the public ad data at all. Check that the file is live and not a placeholder record.
2. Pull your origin and top URLs
Query the CrUX API with the four experimental keys for your origin, then repeat with the url field for your highest traffic templates. Data availability was expected to increase over the month after launch, so some URLs may still return nothing.
3. Audit layouts in the DevTools Ads panel
Turn on the highlight toggle and scroll a typical article on mobile and desktop. Compare what you see with our ad density guidelines.
4. Watch overlapping and sticky units
Overlap is counted once for density but every visible ad adds to Ad Count, so an anchor plus a sticky sidebar can raise one number more than the other.
5. Review infinite scroll and single page templates
Because idle time and soft navigations change how samples accumulate, test these templates separately from standard articles.
6. Track ad weight next to your vitals
Set alerts on experimental_ad_cpu and experimental_ad_kilobytes so a heavy new script shows up before buyers notice it.
CrUX ad metrics are labeled experimental, and Chrome says it is open to feedback and to changing them. Treat them as a public mirror of your layout today, and keep the history so you can show buyers how it improves.