Most AdSense publishers think about where ads should go. Fewer think about where they should not, until a Policy Center notice says ad serving has been limited on some pages. The rule behind a lot of those notices is short and easy to trip by accident: Google does not want its ads on screens that have nothing of value on them. This post covers what the policy says, which pages on an ordinary site are at risk, and a small audit that is worth doing before a warning arrives.
What the policy says
Google's publisher policy on Google-served ads on screens without publisher-content says the content you provide should be of value to the user and be the focal point of the visit. Ads should not appear on pages with little or no content, on pages that are still under construction, or on pages that exist mainly for alerts, navigation or other behavioral purposes. Google can limit or disable ad serving on pages like these until they are fixed.
The wording turns on the idea of publisher-content. A related Google policy, more ads or paid promotional material than publisher-content, defines it as the images, videos, games, article text and user-generated content you create or manage. It does not include whitespace, header or footer content, or links to other pages on your site. A page that is mostly menu, footer and ad slots has very little publisher-content, however polished it looks.
The pages that usually trip it
Google's page gives the pattern as "dead end" screens, and the examples map neatly onto a typical website:
Thank-you and confirmation pages. The visitor has finished what they came to do. There is nothing to read, and an ad is the only thing on the screen.
Login, account and exit pages. Functional screens, not content.
Error pages. A 404 or "no results" page is the classic case, and a site-wide ad snippet will happily load on it unless something stops it.
Auto-generated or templated pages. Google's guidance says not to place ads on automatically generated content that has not had manual review or curation. Thin tag, archive and search-results pages created by a CMS fit this description, and third-party write-ups such as MonetizeMore's account of the "templated page" variant of the violation describe the same cause.
Pages that are mostly copied. A separate Google policy covers screens with replicated content, so a page that mirrors content from elsewhere without adding anything is a risk for a different reason.
What Google asks you to do about it
Accounts of the notification text agree on two remedies: fix or remove the content on the flagged pages and request a review, or remove the ad code from those pages. In either case, ad serving is limited on the affected pages until the problem is resolved. Google's pages do not set a minimum word count or article count, and a third-party knowledge-base article on the topic says the same, so do not trust anyone who quotes you a magic number.
A five-step audit
1. List your non-article templates. Thank-you pages, login, cart or account screens, 404, internal search results, tag and date archives. If a template exists mainly to move someone to the next step, it is a candidate.
2. Check whether the ad code loads there. View the source or use your ad plugin's page-level controls. A site-wide header snippet is the usual culprit, because it fires everywhere unless told otherwise.
3. Exclude, don't just hope. Turn off ads on those templates, or use a no-ads setting for specific URLs. If you use Auto ads, review the page-level exclusions rather than assuming they match your intent.
4. Thicken or remove thin pages. Short placeholder posts and empty category pages are the easiest to forget. Either give them real content or noindex and de-ad them.
5. Review the Policy Center on a schedule. A monthly look catches a limited-ads notice while it affects a handful of URLs rather than a whole section.
The takeaway
The policy comes down to one question per page: is there something here a reader came for? Where the answer is no, the ad is a liability rather than revenue. Spending an hour to keep ads off thank-you pages, error screens and thin auto-generated pages is cheaper than waiting for a notice, and it sits well beside the housekeeping in our guides to adding the AdSense ads.txt file to WordPress and fixing the "Earnings at Risk" ads.txt warning.
Sources: Google Publisher Policies: screens without publisher-content, Google Publisher Policies: more ads than publisher-content, Google Publisher Policies: replicated content, MonetizeMore.