Chrome Now Publishes Sites' Ad Loads: What the New CrUX Ad Metrics Mean for Buyers and Publishers

If you sell advertising on a content site, your ad load used to be something you described to buyers. If you buy open-web media, it was something you took on trust or paid a verification vendor to check. Since September 15, 2026, Chrome publishes it. Four experimental ad metrics now sit in the Chrome User Experience Report (CrUX), the public dataset of field measurements from real Chrome users, and anyone can look up an eligible site.

What the four metrics measure

The metrics were announced on the Chrome for Developers blog by Alex Cone, and the definitions sit in Chrome's ad measurement documentation. For Ad Count and Ad Density, Chrome samples the viewport once per second during a visit and averages the samples across the session, which runs from the first bytes of the page until it unloads. The two Ad Weight metrics are cumulative totals for the same visit.

As with the existing Web Vitals in CrUX, the published figure is the 75th percentile: three quarters of sessions on the page experienced that value or better. Density is weighted by time, so a visit in which ads fill half the viewport for five seconds and none of it for the next five records a density of 25%.

Two details matter before anyone quotes these numbers. First, only sites that list at least one authorised seller in their ads.txt file are measured. An origin with no ads.txt, or only placeholder records, gets no ad metrics. Second, Chrome identifies ads with a filter list condensed from EasyList, the open-source blocking ruleset, plus any resource or frame requested by a script already identified as an ad. The main frame itself is never classified as an ad, and the CPU metric counts ad frames only, excluding CPU time for ad scripts running in the main frame. PPC Land points out that on many sites the header bidding wrapper and the ad server library run there, so the CPU figure can understate what ads actually cost a page.

Not a Core Web Vital, and not a ranking signal

Chrome is explicit that the ad metrics are not part of Core Web Vitals and do not have suggested targets or thresholds. There is no good, needs-improvement or poor band. The announcement says nothing about Google Search, and neither does the documentation we read. Nothing Google has published links these numbers to rankings, and a publisher should not reorganise a site on the assumption that it will.

That is not the same as saying the numbers carry no weight. Chrome says it expects them to be particularly useful for web advertisers and the services they use to place ads. The primary audience Chrome names is the buy side.

Why a public number changes the conversation

Ad load has always been negotiated with uneven information. The publisher knows its layouts; the buyer sees a media kit and whatever its verification vendor measures on its own impressions. A browser-measured figure that either side can pull gives both parties the same starting point. It will not settle arguments on its own, and it sits alongside other pressure for auction transparency, such as the remedies in the Google ad tech case. Chrome's announcement carried supporting quotes from publishers, ad tech firms and agencies, including this one.

For publishers, the upside is the one Badler describes: a site that has held back on ad density can now show it with a number it did not produce itself. The downside is symmetrical. A site that stacked sticky units and in-content slots to lift short-term revenue now has that choice on the public record, next to its Core Web Vitals, for any buyer who looks. Ad weight also lands on the same pages your visitors are trying to use, and speed and design affect conversions as much as they affect a buyer's view of your inventory.

For advertisers and agencies, the metrics are a free, independent screen for inventory. In the same announcement, Google's Bill Reardon said Display & Video 360 supports the initiative and looks forward to exploring with the industry how the signals can improve quality. That is support, not a product feature, so do not expect a density filter in the buying platform yet. Until one arrives, the checks happen outside whichever DSP you choose.

How to look up a site, and what to do this quarter

The data is available now in CrUX Vis, the web dashboard, and through the CrUX API, which returns a rolling 28-day aggregation, and the CrUX History API, which holds weekly time series for the past six months. Chrome DevTools also shows a local measurement of the same metrics for any page you inspect, in the Ads tab of the Application panel. That reflects your own session, not the CrUX figure, and it can differ from what CrUX reports. They are not yet in the CrUX dataset on BigQuery; Chrome says it is working on that. Coverage is still filling in, and Chrome expects data availability to increase over the coming month, so a missing value today does not necessarily mean a site is ineligible.

• Publishers: pull your own origin and the URLs of your main page templates before a buyer does. Compare Ad Weight: Network with the rest of the page, and confirm your ads.txt is live and lists real sellers, or you will not appear at all.
• Publishers: watch mobile density most closely. A mobile viewport is smaller, so the same ad unit covers a larger share of it, and that is the figure most likely to come up in a negotiation.
• Buyers: pull the metrics for the top domains on your open-web inclusion lists and look for outliers, sites with density well above their peers. Treat an outlier as a reason for a closer look, not an automatic exclusion.
• Buyers: when a seller pitches premium placements, ask for the site's CrUX ad metrics alongside the rate card. If the site is eligible, the data is public anyway.
• Both: record a baseline now. While the metrics are experimental, the trend across several weekly readings tells you more than a single value.

Once a quality measure is public and free, it tends to become a buying criterion whether or not anyone mandates it. Index Exchange's Michael McNeeley added a fair caveat in Chrome's announcement: there is still work to be done on how best to use the data. Publishers who check their own figures now will be having that conversation on their own terms.