A policy warning email from AdSense is a clock. When the status reads Ad serving at risk, you are in a warning period: fix the cited issue before it expires or AdSense flips affected pages to Restricted ad serving or Disabled ad serving. The email is terse — a URL, a category (e.g., Valuable inventory: No content), and a vague “review and fix.” This page decodes what each category actually means and what change actually clears it.
Fastest path: open the Policy center, read the exact category and the exact affected URLs (the email under-reports), fix only those URLs, wait a day for the change to go live, then click Fix → Start review process. Don’t request review until the fix is verifiably live — each rejected review pushes back when you’re allowed to try again.
First 30 minutes: triage
- Open AdSense → Policy center. The email is incomplete; the console lists every affected site and URL, sortable by site, status, issue type, and date reported.
- Read the status on each row. As of June 2026 the real labels are: Ad serving at risk (warning, you still have time), Restricted ad serving (some ads blocked), Disabled ad serving (all ads blocked on those pages), Limited ad serving (an account-level cap, usually new/unverified publishers — not a content violation), and Restricted ad personalization (a consent/CMP problem, covered below).
- Identify the scope: a single URL, a pattern of URLs (e.g., all your tag pages), or site-wide. This is a page-level enforcement if it names specific URLs, and an account/site-level one if it doesn’t.
- Know the difference between a policy and a restriction. A Google Publisher Policy violation (illegal, dangerous/derogatory, sexually explicit) means those pages will never serve ads until fixed. A Google Publisher Restriction (e.g., some health, alcohol, or shocking content) means limited or no monetization but is not a violation — you can leave the page up and just accept reduced fill.
- Do not click Start review process yet. After a site is reviewed and rejected several times recently, the button goes inactive and the console shows a date before you can try again. Spend your reviews carefully.
Which bucket are you in?
| Policy center status | What it means | First move |
|---|---|---|
Ad serving at risk | Warning period; nothing blocked yet | Fix the cited URL before the deadline, then request review |
Restricted ad serving | Some ad demand blocked on cited pages | Fix content/layout, verify live, request review |
Disabled ad serving | All ads off on cited pages | Same — but expect closer scrutiny |
Limited ad serving | Account-level ad cap (often new publishers) | Usually time/verification, not a content fix — don’t request review for content |
Restricted ad personalization | Consent/CMP not detected for EEA/UK/CH traffic | Install a Google-certified CMP (see below) |
The categories you’ll actually see
1. Valuable inventory: No content or Low value content
How to spot it: The cited URL has thin or templated content — tag pages, empty category pages, redirect/landing pages, internal search-result pages, or stub articles.
Why it happens: The page is monetized but has little original value for a user. As of June 2026 Google’s reviewers explicitly weigh originality and “information gain” — a 300-word article that repeats what 100 other sites say still reads as low value.
Fix:
- Tag/category page: either
noindexit or expand it with a genuine intro paragraph plus curated, described content (not just a link list). - Search-result or filter URL: exclude it from ad serving in AdSense → Sites → Manage → Page exclusions, or
noindexit. - A real but thin article: expand it with original analysis (aim well past ~800 words of substance, not padding), then request review.
See thin pages and AdSense review for the depth definition.
2. Sexually explicit content / Shocking content / Adult themed
How to spot it: A specific URL flagged for imagery, language, or topic. False positives happen — the classifier catches medical, history, art, or news pages.
Fix:
- False positive (medical, news, history, art): request review and explain the context briefly in the reason dropdown/notes.
- Legitimate match under a Restriction (e.g., shocking but newsworthy): you may keep it up and accept limited monetization — it is not a violation.
- Legitimate match under a Policy (sexually explicit): remove the page, or strip ads from that URL. Don’t argue — even one ambiguous page can put the account at risk.
3. Dangerous or derogatory content
How to spot it: Content about weapons, illegal activity, hate speech against protected groups, or harassment. Note: this is a hard Publisher Policy, not a soft restriction.
Fix: Most cases here are not misclassification. Edit or remove the page. Add an editorial review step before publishing anything adjacent to this territory.
4. Copyright / Misrepresentation
How to spot it: Copied content, fake reviews, deceptive claims, or undisclosed sponsored/affiliate content.
Fix:
- Copied content: rewrite originally or remove.
- Fake or AI-spun reviews of products you’ve never used: remove entirely.
- Sponsored posts: add a clear “Sponsored” or “Paid partnership” disclosure at the top of the article.
5. Privacy policy / Consent (and Restricted ad personalization)
How to spot it: Usually fires site-wide. A missing privacy policy is a content issue; a missing consent signal for EEA/UK/Switzerland traffic shows up as Restricted ad personalization (you still serve non-personalized ads, but earn less).
Fix: See privacy policy missing for AdSense and cookie consent basics. Short version:
- Privacy policy must name Google AdSense and explain third-party cookies; link it from the footer.
- For EEA, UK, and Switzerland traffic you must use a Google-certified CMP that integrates IAB TCF — required for personalized ads since January 16, 2024 (EEA/UK) and July 31, 2024 (Switzerland). The TCF v2.3 migration deadline was February 28, 2026, so confirm your CMP is on v2.3.
- Verify your CMP actually fires: Google’s list of certified CMPs is the authoritative source.
6. Better ads standards / “too many ads” / “sticky ads obscure content”
How to spot it: Specific URLs flagged, usually mobile, often tied to the Better Ads Standards.
Fix: See ad density violating policy and auto ads poor placement. Keep density reasonable (roughly 2–4 units on a 1500-word article); never let a sticky/anchor ad cover the first paragraph, a heading, or a CTA.
7. Invalid traffic / clicks
How to spot it: A sudden 20–50% earnings drop with no content change, plus a warning about “invalid activity.” Severe cases can disable the whole account.
Fix: See AdSense invalid traffic warning. Common causes: a bot scraping pages, a referral source sending click-baited traffic, or — rarely — a friend repeatedly clicking “to support you.” Do not ask people to click; never click your own ads.
Shortest fix path (any category)
- Open Policy center; read the exact category and affected URLs. Don’t act on the email summary alone.
- Fix the cited issue on the cited URLs only. Don’t “audit the whole site” before requesting review — scope creep delays the fix.
- Verify the fix is live. Wait ~24 hours, then check in an incognito window with cache cleared and confirm via
view-source:that the change (e.g., thenoindextag, removed ad, new content) is actually served. - Request review. In Policy center click Fix next to the site → under “Issues found” click Start review process → pick a reason from the dropdown → tick the confirmation box → Request review.
- Wait. Reviews typically take about a week and can take longer. Checking daily does nothing; the status changes silently.
How to confirm it’s fixed
- The Policy center row moves from
Restricted/Disabled/Ad serving at riskto Ready (or the issue drops off the list). There is no email — check the console. - Live ads return to the affected URLs (test logged-out, not in your own ad-suppressed session).
- The account-level summary at the top of Policy center shows a higher “percentage of ad requests serving without restrictions.”
What NOT to do
- Don’t delete the URL just to dodge the warning. AdSense then flags it “not accessible” and the warning persists. Fix the content, or
noindexand remove ads from it. - Don’t open multiple reviews in parallel or re-request immediately after a rejection — repeated rejections lock the Start review process button behind a wait date.
- Don’t reply to the email. It comes from a no-reply address. Everything happens in Policy center.
- Don’t argue with the classification. State the context once (“medical education content, not promotional”) and stop; reviewers don’t read long appeals.
- Don’t panic-disable ads site-wide. The enforcement is usually page-level; blanket disabling just loses revenue without speeding the review.
Prevention
- Read the Google Publisher Policies at launch, then skim the change log every few months — they update.
- Audit every new page against the policy list before publishing — especially anything touching health, finance, politics, or adult-adjacent topics.
- Keep tag, category, and search-result pages out of the indexable surface (
noindex, or disable ads via Page exclusions). - Put a standard disclosure block in your post template for sponsored/affiliate content so you can’t forget it.
- Maintain a written “no-go list” of topics you won’t cover — faster than re-reading the policy for every article.
FAQ
Q: I requested review and got the same warning back — what now?
A: The fix wasn’t enough, or wasn’t live when the reviewer looked. Re-read the Policy center notes carefully; a second URL or sub-issue is often listed. Fix that specifically, confirm it’s live in view-source:, wait for a re-crawl, then request review again — but note the button may now be locked behind a wait date.
Q: Will one policy warning hurt my whole account?
A: A single page-level enforcement (Ad serving at risk or Restricted ad serving on specific URLs) usually won’t. Repeated warnings, or any site/account-level Disabled ad serving, can. Treat the first one as a fire alarm even if only one room is burning.
Q: How long does a review take? A: Officially about a week, sometimes longer. The status flips silently in Policy center — there’s no notification, so check there, not your inbox.
Q: My site has 2000 articles and the warning lists 1 URL. Do I have to audit all 2000? A: No, but ask why that URL was flagged. If it’s a pattern (e.g., all your “interview” or auto-generated pages), the rest are likely next in line — fix the template, not just the one page.
Q: What’s the difference between “Restricted ad serving” and “Restricted ad personalization”? A: Restricted ad serving is a content/layout enforcement that blocks some ad demand on cited pages. Restricted ad personalization means EEA/UK/Switzerland visitors lack a valid consent signal, so you serve only non-personalized (lower-paying) ads — fix it with a Google-certified IAB TCF CMP, not by editing content.
Q: How long until the warning disappears after fixing? A: Roughly 1–4 weeks after the URL is re-crawled and re-classified. The Policy center entry moves to Ready or drops off the list silently.