Not reviewed
The site has not been reviewed yet. Google recommends fixing problems before the review happens.
Use case · Ad experience
The Search Console Ad Experience Report tells you whether the site has ads that bother visitors according to the Better Ads Standards. If the status is Failing for too long, Chrome starts filtering the ads. Here is how to read the report, fix issues and request a review.
What it is
The Ad Experience Report is in Search Console. It shows whether Google found experiences on the site that violate the Better Ads Standards, such as pop-ups that cover the content or sticky ads that are too large.
The review looks at a sample of pages, not all of them. Mobile and desktop are evaluated separately, so the site can be fine on one and bad on the other. Pages that require login are left out of the report.
When there is a failure, the report may include videos or screenshots from the review and a history with the date of the last review and the status changes. That is where you find out what the reviewer saw.
The statuses
The current Help Center describes four statuses. Here we use the English names, as they appear in the Help Center.
The site has not been reviewed yet. Google recommends fixing problems before the review happens.
Google reviewed it and did not find a significant number of annoying experiences in the sample. Chrome does not filter.
Several experiences that violate the Better Ads Standards were found. If the status continues, Chrome filters the ads.
The requested review is in progress. You cannot request another until this one finishes.
On mobile
Examples taken from the Help Center page on mobile ad experiences.
Review requests
Help Center rules for a site in Failing. Only owners and users with full access in Search Console can request.
Owners and users receive an email at least 30 days before filtering starts, on the first failure.
During the review, filtering is paused. If the site stays in Failing, you can request the second right away.
Filtering also pauses. If it fails again, the third request is only available after 30 days and filtering starts on the report date.
A new request only after 30 days from the previous one, or when the status changes from Failing to Passing.
How to get out of Failing
Common errors
It is almost always a setting that nobody checked on mobile.
A tall sticky unit in the footer can look discreet on a large phone and go over 30% of the screen on a small one.
The same number of units on a long post and on a short one. On the short one, the ads go over 30% of the content height.
A signup or offer window that covers the page right after it loads falls into the pop-up category.
Mobile and desktop have separate statuses. Fixing one does not change the other.
In ConsentMode
The current Help Center describes four statuses: Not reviewed, Passing, Failing and Review pending. No intermediate warning status is described there.
Google counts the failures in the last 365 days. On the second, filtering starts in 7 days. On the third, it starts immediately and the new request is only available after 24 hours. From the fourth onward, it also starts immediately and the request is only available after 30 days.
No. The Help Center states that filtering affects all visitors to the site, from anywhere.
The change can take up to 8 hours to reach all Chrome users.
Google says publishers without Search Console can also see warnings in the Chrome developer console. Even so, it is worth verifying the site in Search Console.
Library
This guide was written from these official pages. Read them directly at the source:
The audit measures each format on mobile and desktop, without clicking on ads, and shows where to fix it.