Better Ads Standards and the Ad Experience Report
Why a Standard About "Annoying Ads" Can Switch Off Your Revenue
The Better Ads Standards were written by the Coalition for Better Ads, an industry group, based on research into which ad formats people find most annoying. Google gives them teeth in two ways. Chrome can filter ads on sites that keep breaking them, and the Google Publisher Policies, which AdSense publishers agree to, require compliance. The AdSense Help Center says so in its article on fixing ad experience issues.
So this isn't just a concern for big news sites. And because Chrome filtering applies to the whole site, one aggressive format from one ad partner can cost you revenue from every partner. Here's what the standards rule out, how Google's Ad Experience Report works, and how to get from "Failing" back to clean.
The Experiences the Standards Rule Out
The Coalition publishes its list at betterads.org/standards. For web pages there are two lists, one for desktop and one for mobile. Mobile is stricter, because a small screen gives an intrusive ad nowhere to hide.
Desktop web
- Pop-up ads. Ads that appear over the content after the page starts loading and block some or all of it.
- Auto-playing video ads with sound. Video that starts playing with audio on, without the visitor choosing to play it.
- Prestitial ads with a countdown. A full-page ad shown before the content loads that makes the visitor wait a number of seconds before they can close it. The Coalition notes that a desktop prestitial the visitor can dismiss straight away doesn't fall below the standard. The forced wait is the problem.
- Large sticky ads. An ad that stays fixed to the page, typically along the bottom edge, while the visitor scrolls and takes up more than 30% of the screen.
- Ad density above 50%, and ad density above 30% combined with a sticky video ad.
Mobile web
- Pop-up ads, with or without a countdown.
- Prestitial ads. On mobile, the Coalition lists prestitials with and without a countdown as tested experiences, so don't count on a close button to make one acceptable.
- Ad density above 30%. More on how this is measured below.
- Flashing animated ads. Ads with rapidly changing background, text or colours. Animation that doesn't flash is fine. The Coalition doesn't publish a flashes-per-second limit, so treat anything strobe-like as out.
- Auto-playing video ads with sound.
- Postitial ads with a countdown. An ad that appears after the visitor follows a link and makes them wait before they can dismiss it. If they can dismiss it immediately, it doesn't fall below the standard.
- Full-screen scrollover ads. An ad that floats over the content and makes the visitor scroll through it to get back to the page.
- Large sticky ads covering more than 30% of the screen.
- Sticky, pop-out video ads and a sticky video ad combined with a large inline ad.
The Coalition also has standards for short-form video and mobile apps. They don't feed into the web Ad Experience Report, so they're out of scope here.
What gets flagged, and what to use instead
| Experience | Desktop | Mobile | Compliant alternative |
|---|---|---|---|
| Pop-up ad | Violates | Violates | Inline unit between paragraphs |
| Prestitial ad | Only with countdown | Violates | No pre-content ad; first unit after the intro |
| Postitial with countdown | Not listed | Violates | Allow instant dismissal, or drop it |
| Auto-play video with sound | Violates | Violates | Muted auto-play or click-to-play |
| Large sticky ad (>30% of screen) | Violates | Violates | Small anchor, such as a 320x50 bar |
| Flashing animated ad | Not listed | Violates | Static or gently animated creative |
| Full-screen scrollover | Not listed | Violates | Inline unit that scrolls with content |
| Ad density | Over 50% (or 30% with sticky video) | Over 30% of main content | Space units with real content between them |
How mobile ad density is measured
This is the rule most likely to catch an ordinary content site. The Coalition adds up the heights of all ads within the page's main content and divides by the height of that main content, not the screen. Sticky ads count, but only once. Headers, footers, navigation, related-article sections and ads below the main content aren't included, and neither are pre-roll or mid-roll ads playing with relevant video content.
A hypothetical example: a mobile recipe page's main content is about 6,000 pixels tall, with a 50-pixel sticky anchor and eight 250-pixel in-content units. That's 2,050 pixels of ads, about 34%, so it fails even though no single unit looks excessive. Drop two units and it's about 26%. Short posts are the danger zone, so if your ad stack inserts units automatically, make sure the count scales with article length.
How Google's Ad Experience Report Works
The Ad Experience Report lives in Google Search Console. Google describes it as a report that lists ad experiences on your site identified as violating the Better Ads Standards. You need to be a verified owner or user of the property in Search Console to see it. In the report you choose Desktop or Mobile in the left-hand panel, and you'll find any issues split across a "Site design issues" tab and a "Creative issues" tab. Google's help page on accessing and using the report walks through the screens.
Desktop and mobile are judged separately. A site can be Failing on mobile and fine on desktop, in which case only mobile Chrome users would have ads filtered.
The statuses
Google's help article on review status lists these:
- Not reviewed. Google hasn't reviewed the ad experiences on your site yet. That isn't a problem. Google's FAQ says there's no fixed schedule for first reviews.
- Passing. Google reviewed the site and didn't find a significant number of annoying ad experiences.
- Failing. Google found numerous experiences that violate the standards.
- Review pending. You've submitted the site for another review and it's in progress.
The AdSense Help Center also refers to sites marked "Warning". That status isn't defined in the current Search Console review-status article, so if you see it, treat it the way AdSense does: a sign that some of your ad experiences don't meet the standards and need fixing before things escalate.
What a review actually looks at
Reviews use a mix of manual and automated checks on a sample of your pages. Google's FAQ says Chrome looks for repeated instances of violating experiences before acting, rather than reacting to one stray ad, and that it follows the Coalition's thresholds. Some findings come with screenshots or short videos in the report, which makes it much easier to track down a creative you've never seen yourself.
Two consequences follow from sampling. First, the report may not list every problem. Google says plainly that other violations may exist on pages it didn't sample. Second, Passing today doesn't guarantee Passing next month. Google reviews passing sites periodically too. Reviews also cover the whole domain, not just the subdomain you verified, unless the subdomain is on the Public Suffix List.
What Happens When You're Failing
A Failing status doesn't switch your ads off on the spot. According to Google's Chrome ad filtering help page, owners and users of a Failing site get an email at least 30 calendar days before filtering starts. The AdSense help article puts it the same way: if a site stays Failing for more than 30 days, Chrome filters ads on it. The date filtering would begin appears in the "Ad filtering" area at the top of the report.
Once filtering is on, Chrome stops loading ads on the site for all visitors using Chrome, wherever they are. Chrome identifies ad requests using a filter list. Its developer documentation describes that list as a condensed version of EasyList, a widely used open-source set of ad-blocking rules. When Google launched the feature in 2018 it said filtering would include ads Google itself serves, so don't assume AdSense units are exempt. Visitors may see blank gaps where ads were, or your content may close up around them, depending on how your layout handles empty slots.
When filtering is lifted, Google says the change can take up to 8 hours to reach every Chrome user, though most see ads again almost immediately.
The review request and its limits
You get two chances that pause the clock. Google's FAQ says ad filtering is paused while your first or second review request is being processed. After the second request, though, a 30-day period begins in which you can't submit another one. If the site is still Failing when that period ends, filtering starts on the date shown in the report, and Google says no further extensions are given.
So don't fire off a request after removing only the ad in the screenshot. Treat each one as your last.
From "Failing" back to clean
- Status: FailingEmail sent at least 30 days before Chrome filtering starts
- Read the reportDesktop and Mobile, Site design and Creative tabs, videos
- Fix the whole siteNot just sampled URLs; check every template and ad partner
- Request reviewDescribe each fix, tick "I have fixed all the issues"
- Filtering pausedFor the 1st and 2nd request only
- PassingFiltering off; can take up to 8 hours to reach all users
How to Fix Violations
Google's fixing issues and submitting for review page lays out the formal steps. Open the report, choose Desktop or Mobile, work through the issues on both tabs, fix them, then describe what you changed in the "Request review" area and submit. Here's how to make that work in practice.
1. Separate site design issues from creative issues
Site design issues come from your layout: too many slots, an oversized sticky unit, a prestitial your theme or a plugin inserts. Fix those in templates or ad settings. Creative issues come from the ads themselves, such as a flashing banner or a video with sound. Fix those by blocking the creative or advertiser, or by asking the ad partner to remove it. Google suggests involving your ad ops team for creatives and your designers for layout.
2. Audit every ad source and template
Many sites run more than one ad script: AdSense plus a native widget, a video player, maybe a pop-under someone added years ago. List every tag and the formats it can serve, including "engagement" extras like interstitials on navigation. The report shows example URLs, but Google reviews a sample, so fix the template behind each one rather than the URL itself.
3. Check density yourself
Open your shortest post at phone width in your browser's developer tools. Measure the main content area and each ad slot inside it, count the sticky anchor once, and do the arithmetic. If you're near 30%, remove a unit. Our guide to ad placement best practices covers spacing units without crowding the content.
4. Write a useful review request
Your description goes to the site's webmaster and to the owners and users in Search Console, and Google asks for it in English. Be specific: "Removed the prestitial inserted by our popup plugin on all mobile pages", "Reduced in-content ads on posts under 800 words from six to three", "Blocked the flashing creative from advertiser X and disabled animated ads in our network settings." Only tick "I have fixed all the issues" when that's true across the whole site.
Staying Off the Report in the First Place
Every format in the standards gets between the visitor and what they came for. Avoid that and you're unlikely to have a problem. Keep sticky units small, since a standard mobile anchor bar is nowhere near 30% of the screen but a sticky video player stacked on an anchor might be. Make video muted or click-to-play. Keep anything that blocks the article off mobile entirely. And ask new ad partners which formats they serve before their tags go live.
The same habits help elsewhere. Crowded, interruptive layouts hurt Core Web Vitals, covered in why your site gets slow after adding ads, and approval reviewers notice them too. The AdSense approval guide covers what Google looks for before it lets you run ads at all.
Your Next Step
Open Search Console today and check the Ad Experience Report for both Desktop and Mobile. "Not reviewed" or "Passing" means you're fine for now, so note the date and check again after any change to your ad setup. If you see "Failing", look at the "Ad filtering" date first, then fix every issue across the site before you send the first review request. You have two paused reviews, and you want to need only one.
If you're preparing a site to apply to an ad network rather than fixing one that already runs ads, run an AdGateScore check to see how your site scores on content, policy, performance and structure first. If a network has already turned you down, the rejection decoder explains what the wording in the rejection email usually points to.
We build AdGateScore, the ad network readiness scanner. Our articles draw on the requirements each network publishes and on what our scans find.