AdSense Ad Serving by Site Basics

AdSense ad serving by site means Google evaluates and controls ads per hostname on your Sites list—and may further adjust delivery with policy ad serving labels that are not the same word as Ready. Publishers with one earning blog and one blank subdomain often blame “AdSense broke” when the real story is two different site objects sitting in different serving states.

Cluster owners: Connected sites vs account status, What Requires review means, AdSense ads not showing: what to check, and Add a new site after approval. This page is not those how-tos—it is the serving literacy map so you read the right badge before you rip out ad code.

Serving is site-scoped: Sites approval status tells you whether a hostname may show ads at all; Policy center tells you whether ads are disabled, restricted, or regular on that property after approval.

Official: Check the status of your AdSense sites · Policy ad serving status breakdown · Ad serving was disabled · Site not ready to show ads

Disclosure: Educational AdSense serving guide only. No earnings, RPM, or approval guarantees. Confirm labels in live Help—UI changes. CashPilot may earn from some links at no extra cost to you.

Table of contents

1. Three layers that control whether ads appear
2. Sites approval status: the first gate per hostname
3. Policy ad serving: the second gate on a Ready site
4. Page-level vs site-level disablement
5. Decision table: which layer is blocking this URL?
6. Multi-site accounts: normal combinations
7. When Ready is true but units stay blank
8. Small-blog scenario: subdomain surprise
9. What this page deliberately skips
10. FAQ
11. Read Sites and Policy center for the same hostname

Three layers that control whether ads appear

Think in three stacked questions—each can block ads independently:

1. Account layer: Is your publisher account approved and in good standing at the program level? Payments tasks, identity verification, and account-wide policy actions live here. A hard account rejection is not fixed by deleting one Sites row.

2. Site approval layer: On Sites, what is this hostname’s approval label—Requires review, Getting ready, Needs attention, or Ready? Until a site is Ready, Google has not cleared that URL to show ads regardless of how long ago your account was approved. Map: Connected sites vs account status.

3. Policy serving layer: After a site can serve, Policy center and reporting may show disabled, restricted, at risk, or regular ad serving for that property or specific pages. Ready on Sites does not guarantee regular serving if enforcement is active.

Ad code placement, ads.txt authorization, and Auto ads toggles are a fourth practical layer—but they matter only after the site approval gate opens. That troubleshooting path lives on ads not showing, not repeated here.

Sites approval status: the first gate per hostname

Google’s Check the status of your AdSense sites defines approval labels per site:

Requires review is the label many beginners misread as “broken.” It means you have not finished the front door—see Requires review meaning. Getting ready is in-flight review, not rejection.

Critical habit: read the label on the same hostname where units are blank. www. and bare domain strings are different rows if you added both incorrectly—see add a new site for URL precision.

Policy ad serving: the second gate on a Ready site

Google’s Policy ad serving status breakdown describes serving health after inventory can theoretically run:

Reporting summarizes severity at a high level; Policy center remains where you repair violations and request reviews. Time zones and domain granularity can make reporting and Policy center look slightly different—Help documents those discrepancies.

Why this matters for “by site” literacy: Site A can show regular serving while Site B on the same account shows restricted serving because B’s content mix triggers different advertiser bids—not because your account ID is broken.

Page-level vs site-level disablement

Ad serving was disabled Help distinguishes scope:

Page-level: A specific URL violated policy; ads stop on that page while other pages may continue.

Site-level: Enforcement applies across the property; you must fix site-wide, not only the example URL Google cited.

Account-level: Program-wide risk—different repair path from a single Sites row.

Beginners often paste the example violation URL into Search Console and “fix” one post while identical templates remain live. Help explicitly requires addressing violations across the site before review—not only the sample link.

If serving disabled on one article, do not delete the entire Sites entry unless you are permanently abandoning the hostname—that is a business off switch, not a page-level repair tool (remove site basics covers intentional removal).

Decision table: which layer is blocking this URL?

Working the wrong layer wastes weeks—tweaking ad code while Sites still says Requires review, or requesting account reapply while Policy center wanted a page fix.

Multi-site accounts: normal combinations

These combinations look scary but are routine:

Approved account + site A Ready + site B Requires review. You launched a second domain without running verify/review on B. A keeps earning; B stays blank until B’s site layer clears.

Site Ready + policy restricted serving on that same site. Advertisers partially boycott sensitive content categories; RPM drops before ads disappear entirely—different symptom from “code missing.”

Page disabled on an otherwise Ready site. One viral post broke policy; other posts still monetize until patterns repeat.

Inactive site label on Sites. Help notes some properties need another review before ads resume—distinct from a fresh Requires review on a never-checked hostname.

If I were auditing a friend’s two-domain account, I would screenshot Sites and Policy center for each hostname side by side before touching WordPress plugins.

When Ready is true but units stay blank

Ready means Google cleared the site object—not that every implementation mistake is impossible:

• Ad code not on the URL variant users visit (HTTP vs HTTPS, www mismatch).
• ads.txt Not found or Unauthorized on the row Sites displays—seller file status sits beside approval status on the same page.
• Auto ads off while you forgot manual units—or vice versa.
• Caching layers serving old HTML without tags.
• Limited ads or invalid traffic signals—see limited ads vs invalid traffic when Policy center is clean but delivery feels throttled.

The ads not showing owner owns that triage sequence. This page stops at teaching which badge should send you there.

Small-blog scenario: subdomain surprise

A publisher runs blog.example.com on AdSense for a year—Ready, regular serving, modest RPM. They launch shop.example.com for digital downloads, paste the same ad snippet, and see blanks.

Sites list shows only blog.example.com Ready. The shop subdomain was never added, verified, or reviewed. Account approval did not “inherit” to the new hostname.

Fix path: Add a new site after approval for the shop host—or remove ads from shop if monetization is inappropriate there. No amount of forum “AdSense dead” panic fixes a missing site object.

Alternate branch: shop was added but sits in Getting ready while blog stays Ready—classic two-layer account story from connected sites vs account.

What this page deliberately skips

• Step-by-step verification methods (meta tag vs ads.txt file)—add a new site
• First-apply checklist content—approval checklist
• Hour-by-hour pending psychology—review time
• RPM interpretation—page RPM report basics

Skipping those keeps this URL a serving-status primer, not a clone of neighbors you already shipped.

FAQ

Frontmatter carries schema-ready pairs. Major sections above expand each theme with official Help context.

Read Sites and Policy center for the same hostname

AdSense ad serving by site is not one global on switch. Open Sites for approval status on the exact URL with blank units. Open Policy center for disabled, restricted, or at-risk serving on that property. Use connected sites vs account when you confuse account approval with site Ready, Requires review when checks never started, add a new site when the hostname is missing, and ads not showing when both badges look healthy but units are still empty. Read the layer that is actually red—then click the owner built for that layer.