Policy
Google-served ads on screens without publisher-content
Older guides, ours included, call it "No content" under "Valuable inventory." It reads like an insult and usually is not one. It is a placement rule, not a verdict on your writing: Google found ad code on a screen that had no publisher content for the ad to sit beside.
By Mario Bailey · Published · Updated
Google's Publisher Policies now group this rule under "Inventory value." It does not allow Google-served ads on screens "without publisher-content or with low-value content," on screens "that are under construction," or on screens "used for alerts, navigation or other behavioral purposes." A site made mostly of those screens gets this verdict even when its real pages are excellent.
The screens Google names
- Under-construction or coming-soon pages with the ad code already in place.
- Dead-end screens. Google's own examples are Thank You, Exit, and Error pages. Confirmation and logout screens work the same way.
- Screens whose job is navigation or alerts rather than content: menus, notices, pop-up prompts.
- Automatically generated content that went up without manual review or curation, which Google calls out by name.
- In apps, screens where the user is meant to look away, such as a flashlight app (Google's example).
The usual real causes
Most cases are timing or placement, not quality. People apply before the site has real pages, or they paste the ad code site-wide so it also loads on error pages and post-form screens, or the site is mostly gated so the part Google can see is thin. Google's help text says it may limit or disable ad serving on pages like these "until changes are made," so the fix is to make sure every screen where an ad can appear actually has content for it to appear beside.
Two neighbors are easy to confuse with it. If the screen has content but the content is copied from somewhere else, that is replicated content. If the content is there but the ads outweigh it, that is more ads than publisher-content. Same policy family, different fix.
How to fix it
- Apply with a finished site. Have a real set of substantial, published pages before you turn ads on, not a shell with a homepage and a contact form.
- Keep ad code off content-free screens. Do not let ads load on error, thank-you, exit, confirmation, or under-construction pages. If your setup injects ads everywhere, scope it to real content pages only.
- Review anything generated automatically. Pages produced by a feed, a template, or a tool need a human pass that adds something before they carry ads.
- Make gated content visible enough. If most of the site sits behind a login, give the crawler real, public content to assess. A site that shows only a gate reads as no content.
- Fix the flagged screens, then request one review. The Policy center names the affected pages. Correct those specific screens, confirm the fix, and request the review once.
Staying clear of it
- Every page that can show an ad has real, substantial content on it.
- No ad code on error, thank-you, exit, alert, or placeholder screens.
- No ads on automatically generated pages nobody has reviewed.
- Public, crawlable content even if part of the site is gated.
- You apply with a finished site, not a stub.
Scan your site Every violation, by name
Source: Google Publisher Policies, Google-served ads on screens without publisher-content. Quotations are Google's. Current as of October 2026.