A publisher can pass Core Web Vitals and still make a page difficult to read with ads. Google’s Page Experience documentation now points site owners to data that can show that gap.
In an update dated September 22, Google added CrUX ad metrics to the resources in its Page Experience guidance. The experimental measurements describe how many ads people encounter, how much screen space those ads occupy, and the processing and network resources they use.
The addition gives ad load a more visible place in Google’s SEO documentation. It does not make the new measurements ranking signals.
Google Page Experience Guidance Now Links to Ad Data
Google’s Page Experience page has long asked site owners to consider whether excessive ads distract from or interfere with the main content. The new link gives them a way to examine that question using aggregated data from Chrome users.
The resource entry names ad count, ad density and ad weight. It sits alongside links to Core Web Vitals, HTTPS information, intrusive interstitial guidance and Lighthouse. Google describes the ad measurements as a source of insight into real users’ experiences, as Chrome sees and reports them.
That placement matters because the measurements were introduced by Chrome earlier this month for a broader audience that includes publishers, advertisers and ad technology providers. As TechWyse reported when Chrome released the four experimental ad-load metrics, the data makes parts of an ad experience publicly measurable. The documentation change now puts that resource directly in front of people reviewing a site for search performance.
It also creates an easy point of confusion. A link from an SEO document does not, by itself, change how Google ranks pages.
The Ranking FAQ Draws a Clear Boundary
The same Google documentation that links to the ad metrics says Core Web Vitals are used by its ranking systems. It then draws a distinction: other page experience aspects do not directly help a website rank higher in search results.
Chrome makes a separate distinction in its ad metrics overview. Although the measurements share the CrUX data pipeline with Core Web Vitals, they are not part of the Core Web Vitals initiative. They also lack its performance categories, such as “Good,” “Needs improvement” and “Poor.”
There is no Google-provided ad density target for an SEO team to meet, and the documentation update does not announce one. Treating an ad count as a pass-or-fail search score would go beyond what Google has published.
The difference matters for reporting. Core Web Vitals measure loading, responsiveness and visual stability. The ad data answers another question: what does the advertising on a page look and feel like during a browsing session? Both can inform a review of the page, but they do different jobs.
Four Measurements Describe the Ads People Encounter
Chrome reports four dimensions of ad load. Ad count tracks the average number of distinct ad frames visible in the viewport as a person scrolls. Ad density measures the average share of the visible screen occupied by those frames during a session.
The two ad weight measurements look beyond placement. CPU weight captures processing used by ad frames and related workers; network weight records the data transferred by ad frames and resources. A page with relatively few visible ads can still place demands on a user’s device or connection.
These are field measurements drawn from eligible Chrome users, aggregated over rolling 28-day periods. Chrome’s tooling guide says the metrics are reported at the 75th percentile. Teams can inspect them in CrUX Vis, retrieve current data through the CrUX API, review historical trends through the History API, or use the DevTools Ad panel while investigating a page.
The coverage has limits. Chrome says its field data includes eligible users on Windows, macOS, Android, ChromeOS and Linux. Chrome on iOS, Android WebView applications and other Chromium-based browsers are excluded. The measurements describe the Chrome traffic represented in CrUX; they are not a census of every visit to a site.
Publishers Can Compare Ad Changes With User Experience
For marketers and SEOs, the practical use is to examine ad load alongside existing page experience data. A publisher changing its ad placements can compare later CrUX ad density and weight trends with its earlier readings, while continuing to monitor Core Web Vitals separately. An unexplained increase in ad weight gives the publisher and its ad partners a specific issue to investigate.
That work has a commercial dimension. Publishers depend on advertising revenue, and removing placements simply to lower a metric is not a conclusion supported by Google’s guidance. The data is more useful for identifying where a format takes up substantial screen space or consumes resources, then assessing that finding against how the page is used.
Chrome introduced the ad measurements on September 15 and labels all four experimental. It has said data availability should increase over the following month and that the metrics may evolve with feedback. For now, Google’s Page Experience page points to a new diagnostic resource while its ranking guidance remains explicit: the ad metrics have no published scoring threshold or direct ranking role.
