AdSense Ad Serving by Site or Coverage: Which Report?
Sites serving status and the Coverage column answer different questions. Route to the right AdSense owner—this page is not a second Coverage or Sites guide.
AdSense ad serving by site and the Coverage column in Reports sit in different menus and answer different questions. Beginners merge them because both appear when “ads feel broken.” One is eligibility and policy per hostname; the other is request-matching statistics for periods when serving was already allowed.
Cluster owners (early-link):
- AdSense ad serving by site basics
- AdSense Coverage report basics for small blogs
- AdSense Coverage or Fill Rate: which metric?
- AdSense ads not showing: what to check
Direct answer: Blank or site-specific serving → Sites + ad serving by site owner, then ads-not-showing. Account-wide “are requests filling?” → Coverage report owner after you confirm the hostname is allowed to serve. This URL only routes—it does not re-teach either report.
Official: Check the status of your AdSense sites · Coverage · Troubleshoot ad coverage issues · Troubleshoot common AdSense earnings issues.
Disclosure: Educational router only. No RPM targets, fill benchmarks, or approval guarantees.
Table of contents
- Two menus, two failure stories
- What ad serving by site is measuring
- What the Coverage report is measuring
- Which owner to open first
- How Reports splits interact with Sites
- Scenario: subdomain earns, root stays blank
- When metric routers beat this page
- FAQ
- Pick one report job and leave
Two menus, two failure stories
Sites (and Policy center serving labels) answer: May this hostname show AdSense ads right now? Statuses like Requires review, Getting ready, Ready, Needs attention, and policy disabled or restricted serving describe permission and enforcement on a site object.
Reports → Coverage answers: Of the ad requests sent in this date range, how often did Google return an ad? That is a match rate on requests after the serving stack is already attempting to fill units—not a substitute for reading whether the site passed review.
Why the confusion hurts: a publisher sees Coverage at 92% in Reports, feels successful, while site B shows Requires review and displays no units. Coverage aggregated at account level hid a site gate problem. The opposite also happens—Ready on Sites, Coverage soft, and the publisher assumes “Google banned me” when the issue is demand, ad blockers, unfilled requests, or unit placement—not Sites rejection.
What ad serving by site is measuring
Open ad serving by site basics when your sentence starts with:
- “This domain has no ads but my other domain earns.”
- “Sites says Needs attention or not ready.”
- “Policy says disabled on this property.”
- “I added a new hostname and only that URL is blank.”
Mechanism in plain language: AdSense attaches approval and policy state to listed hostnames. Account approval does not teleport to every future URL. Ready means that site object passed the gates to attempt serving; policy ad serving can still throttle or stop ads afterward.
That layer must be green enough for Coverage math to mean anything on traffic from that hostname. Reading Coverage first on a site that cannot serve is like tuning CTR on a 404.
What the Coverage report is measuring
Open Coverage report basics when your sentence starts with:
- “Units render but earnings wobble.”
- “Help told me to check pageviews, then coverage, then impressions.”
- “I want the column and formula for request fill.”
- “Unmatched ad requests show up in troubleshooting.”
Google documents Coverage roughly as: ad requests that returned ads divided by total ad requests, expressed as a percentage. It explains auction and inventory matching, not whether you finished site verification yesterday.
Coverage does not replace Page RPM reading. You can fill requests yet earn modestly if bids are soft. It also does not replace Sites when the browser shows empty ad slots because serving never started on that hostname.
If I were reviewing a friend’s first monthly AdSense habit, I would confirm Sites Ready (and policy regular) on the URL that earns traffic before I argued about Coverage vocabulary.
Which owner to open first
Use this order:
- Visual blank slots on a specific site? → Sites row + ad serving by site → ads not showing if Ready yet blank.
- Ads load; question is fill / unmatched requests? → Coverage report basics.
- Searched fill rate vs Coverage column names? → Coverage vs fill rate which metric.
- Multi-site account with mixed behavior? → Sites per hostname before account-wide Coverage trends.
Do not open Coverage and Sites guides alternately every hour—pick the layer that matches the symptom, finish that checklist, then revisit Reports.
How Reports splits interact with Sites
When Reports allows site or domain breakdowns, use them to separate hostnames after Sites literacy. A healthy Coverage line on blog.example.com does not prove shop.example.com is Ready.
Policy page-level disablement can produce odd splits: some URLs serve, one article does not. That is still policy serving, not a Coverage tutorial—though Coverage on the affected URL may dip once requests stop returning ads.
Date range discipline matters for Coverage (noise on small blogs). Sites status can change mid-range; a 28-day Coverage chart may span a week when the site was not Ready. Note when you fixed Sites before declaring victory on Coverage alone.
Scenario: subdomain earns, root stays blank
Imagine www passed review and shows Ready, while bare domain or a new subdomain was never added to Sites. Traffic splits across both hostnames in analytics, but only one object serves ads.
Wrong move: stare at Coverage and rewrite ad unit sizes account-wide.
Right move: list both hostnames in Sites, read status per row on the ad serving owner, add or verify the missing property, then re-check blank URLs with the ads-not-showing owner.
Coverage might look “fine” on aggregated Reports while the broken hostname contributes zero impressions—a site object problem, not a metric formula problem.
When metric routers beat this page
This router compares Sites serving literacy to Coverage report literacy. It is not:
- Fill rate vs match rate synonym routing → coverage vs fill rate owner.
- Ad requests vs impressions chain confusion → ad requests vs impressions owner.
- Connected sites vs account status → that account literacy owner.
Stay on one router per search session.
FAQ
Should I fix Coverage before Sites?
Fix Sites and policy serving when eligibility is in doubt. Coverage optimization on a hostname that is not Ready wastes time.
Does Requires review mean Coverage will be zero?
Serving may not behave like a fully Ready site during review states. Treat Requires review as a Sites job, not a Coverage tweak.
Can I use this page for ads.txt errors?
Ads.txt belongs in ads-not-showing and policy troubleshooting paths once Sites is Ready enough to attempt serving.
Pick one report job and leave
Hostname permission and policy labels → ad serving by site basics. Request fill in Reports → Coverage report basics. Fill vocabulary → Coverage vs fill rate. Blank units after Ready → ads not showing. This page routed you—finish one owner before opening the other.
Keep learning
More guides in the same topic lane.
Merge Word or Word to PDF: Which Job First?
Combine chapter DOCX files or export one read-only PDF? Pick merge Word versus Word to PDF by deliverable count and format before upload, with live tool links.
PDF to Text or PDF OCR: Which Job?
Copy plain text from a digital PDF or add search to a scan? Compare PDF to Text and PDF OCR before upload, with CashPilot live links and proof steps for freelancers.
Merge PDF or Word to PDF: Which Job First?
Stack existing PDFs or export a Word draft first? Route merge PDF versus Word to PDF by file type and deliverable before upload, with CashPilot live tool links.