Chrome now publishes your ad load. Is ad density a ranking factor, and how many ads is too many?

KEY TAKEAWAYS

1. The four ad metrics are public, experimental and unscored. Google says they are not a direct ranking factor.
2. Five different rulebooks say "too many ads". Each divides by something different, so their numbers cannot be compared.
3. In 49 French press sites, ad CPU time tracked slow INP more closely than density did. Layout shift was unrelated to ad quantity.
4. If removing a unit costs 15% of page revenue, pageviews must rise 17.6% to break even.

Until last month, only a site's own team could measure how heavily it ran ads. On 15 September 2026 Chrome began publishing it. Anyone can now look up four ad figures for any eligible site. A week later Google Search linked to them from its page experience guidance, and the question arrived on schedule: is this a ranking factor?

What did Chrome release?

Four metrics, added to the Chrome User Experience Report (CrUX), the same public data set that carries Core Web Vitals. Each is labelled experimental.

Chrome samples the viewport once a second for the whole visit. Its own example: ads cover half the screen for five seconds, then none for five seconds, and Ad Density is 25. CrUX then reports the 75th percentile across page views over a rolling 28 days. A density of 23 means three quarters of visits had 23% or less.

The announcement says the metrics are not part of Core Web Vitals and have no suggested targets. It names advertisers and ad-buying services as the main audience. It does not mention Search.

Is ad density a Google ranking factor?

Not directly, on the evidence available.

On 22 September, Search Engine Roundtable reported that Google had added the ad metrics to the resources list in its page experience document. Asked about it, Google's John Mueller replied: "Not everything is a direct search ranking factor!" He said the metrics were listed because they help site owners evaluate a site.

The same Google document draws the line clearly. It says Core Web Vitals are used by its ranking systems, and that other aspects of page experience do not directly help a page rank. It also keeps a self-assessment question asking whether a page avoids an excessive amount of ads that distract from or interfere with the main content.

So there are two honest statements. No one has shown that Search reads these four fields. And Google has cared about ad-heavy layouts for a long time. In January 2012 it announced a page layout change aimed at pages that load the top of the screen with ads, which it said affected fewer than 1% of searches.

The useful reading is this. The ad metrics are not a ranking input. They are a new way to see two things that can be: interaction speed, and a layout where ads crowd out content.

Why can't you apply the 30% rule?

Because it measures something else. At least one early analysis advises keeping Ad Density under 30%, borrowing the figure from the Better Ads Standard. Chrome's tooling guide says the ad metrics have no Good, Needs improvement or Poor bands.

Five rulebooks now say "too many ads". Each divides by something different.

The Better Ads test is a property of the page. It gives the same answer whatever the reader does. CrUX density is a property of visits. A sticky unit adds to it for every second the reader stays. The two can point in opposite directions.

A hypothetical example shows how. Take a phone viewport of 390 by 800 pixels. A 320 by 50 sticky anchor covers 5.1% of it. A 300 by 250 unit covers 24% when fully in view. A small sticky video player of 256 by 144 covers 11.8%.

• Light layout, 60-second visit. The anchor is visible throughout and one 300 by 250 is in view for 20 seconds. Density is 5.1 + 24 x 20/60 = 13.
• Heavy layout, same visit. Anchor and sticky video throughout, one 300 by 250 in view for 45 seconds. Density is 5.1 + 11.8 + 24 x 45/60 = 35.

The two sticky units contribute 17 points before the reader scrolls past a single in-content ad. Sticky formats dominate this metric. On the height test, the same article could pass comfortably.

Which ad metric actually tracks Core Web Vitals?

In the one public table we could analyse, CPU weight did. Density mostly did not.

On 17 September the French firm artwaï published mobile, origin-level ad metrics and Core Web Vitals for the French press sites in its performance ranking. The table has 49 rows. Density runs from 5% to 41%. Ad CPU time runs from 1.17 seconds to 14.69 seconds a visit. The article reads the table by eye. We ran the correlations ourselves.

Three readings follow.

First, a density line would not have protected these sites. Seven of the 49 have density of 30% or more. But of the 42 below 30%, 24 still have an INP above 0.20 seconds. Split by CPU instead and the picture sharpens. Of 21 sites with ad CPU of five seconds or more, 18 have INP above 0.20 seconds. Of 28 sites under five seconds, 13 do.

Second, layout shift has nothing to do with how many ads are shown. All 11 sites with CLS above 0.10 sit below 20% density. That is a problem of reserving space for slots, not of ad quantity.

Third, this is association in one country and one vertical. One site in the table has light ads, 1.55 seconds of CPU, and a slow INP of 0.33 seconds. Another has the heaviest ad CPU in the set, 14.69 seconds, and a better INP than that light-ad site, at 0.29 seconds. DebugBear reports the same tendency on a wider set of sites, without a coefficient.

There is also a blind spot. Chrome's definition says the CPU figure covers ad frames only and excludes ad scripts running in the main frame. A low reading does not clear everything in your ad stack.

The best evidence that ad formats travel with ranking losses is older. Zyppy's 2024 study of 50 sites that won or lost through the 2023 Google updates found fixed footer ads and fixed video ads each correlated with losing at about -0.52. Its author calls the sample very small and says these are not ranking factors. They are the same sticky formats that inflate density.

What does a blank report mean?

Usually that you are not eligible. Chrome includes only sites that list at least one authorised seller in ads.txt. Sites with no file, or a placeholder, are left out. The origin must also be popular enough to be in CrUX. And only page views that showed ads are counted.

Other quirks change how a number reads:

• Ads hidden with display none are left out of count and density but still add to CPU and network weight.
• On single-page apps, soft navigations do not reset the measurement, so one long session is averaged into one score.
• Chrome on iOS is not included.

What to do with each reading

What does removing an ad unit have to earn back?

Ad revenue is pageviews times page RPM, divided by 1,000. If removing a unit cuts RPM by a share x, pageviews must rise by 1/(1 - x) - 1 to break even.

A hypothetical site has 400,000 monthly pageviews at an $18 page RPM, or $7,200. Removing a sticky video worth 15% of page revenue takes RPM to $15.30. Break-even is 470,588 pageviews, a gain of 17.6%.

No source in this research measures a ranking gain from reducing ads. So the case for removal has to rest on something you can observe on your own site: INP on that template moving from slow to fast, or more pages per visit. If neither moves in a 28-day test, the unit stays.

A seven-step check

1. Open your ads.txt and confirm at least one real seller line. Confirm the origin has CrUX data at all.
2. Pull the baseline in CrUX Vis for phone and desktop separately. Record the four ad figures and INP, LCP and CLS for the same window.
3. Go to URL level for the top landing page of each template. Where CrUX has no URL data, use the DevTools Ad panel and label it lab data.
4. Classify each template with the table above.
5. Check by hand against the rulebooks that do have lines: the Better Ads height test, ads against content per screen, and any single ad near the Heavy Ad limits.
6. Run the break-even sum for each candidate unit. Test one unit on one template.
7. Re-read after a full 28-day window. The CrUX History API returns weekly points. Judge by INP, CLS and Search Console clicks for that template, not by the density figure.

If traffic has already fallen, rule out the other causes first. Our traffic drop diagnosis for the September 2026 spam update covers the order to check them in.

What changes now that it is public?

The ranking question may turn out to be the smaller one. Chrome built these metrics for ad buyers, and a buyer can now compare your ad load with a competitor's in a minute.

Core Web Vitals already feed the organic authority pillar of digital authority. The ad metrics do not, and should not until someone shows they matter to search. They are worth a quarterly look because they explain one of the numbers that does. If you want that baseline measured alongside the rest, the waitlist is open.

Questions

Are CrUX ad metrics a Google ranking factor?

Google has not said so. Chrome's announcement does not mention Search. When Google's page experience document added the metrics on 22 September 2026, John Mueller said not everything is a direct ranking factor. Core Web Vitals are used in ranking, and one ad metric tends to move with one of them.

What is a good Ad Density score?

There is none. Chrome says the ad metrics have no suggested targets and no Good, Needs improvement or Poor bands. The 30% figure some guides quote comes from the Better Ads Standard, which divides ad height by content height. CrUX divides ad area by viewport area over time.

Why does my site have no CrUX ad metrics?

Chrome reports them only for sites that list at least one authorised seller in ads.txt, and only for origins popular enough to be in CrUX at all. A site monetised by affiliate links or house promotions may show nothing. A blank report does not mean zero ads.

Should I remove ads to improve rankings?

Not on these numbers alone. No source we found measures a ranking gain from cutting ads. Test one unit on one template, and judge it by interaction speed and clicks on that template after a full 28-day window. Run the break-even sum first.

Sources

1. Chrome for Developers, New ad metrics in Chrome User Experience Report developer.chrome.com
2. Chrome for Developers, CrUX ad metrics overview developer.chrome.com
3. Chrome for Developers, Ad Density developer.chrome.com
4. Chrome for Developers, Ad Count developer.chrome.com
5. Chrome for Developers, Ad Weight: CPU developer.chrome.com
6. Chrome for Developers, Ad measurement: methodology developer.chrome.com
7. Chrome for Developers, CrUX ad metrics tooling guide developer.chrome.com
8. Chrome for Developers, Understand Chrome's Heavy Ad Interventions developer.chrome.com
9. Google Search Central, Understanding page experience in Google Search results developers.google.com
10. Google Web Tools Help, Mobile ad experiences support.google.com
11. Google Publisher Policies Help, More ads or paid promotional material than publisher-content support.google.com
12. Google Webmaster Central Blog, Page layout algorithm improvement webmasters.googleblog.com
13. Search Engine Roundtable, Google Page Experience Docs Adds CrUX Ad Metrics seroundtable.com
14. artwaï, CrUX Ads Metrics : la réalité des pubs enfin visible ! artwai.com
15. Zyppy, Winning and Losing Big Google Updates: 50-Site Case Study zyppy.com
16. DebugBear, New Data From Google: See How Ads Impact Web Performance debugbear.com

NEXT STEP

See where your brand stands.

Your Digital Authority Score, who AI recommends for your target questions, and the placements that close each gap. Your first report is free.

Get your free report →