The AdSense Policy center explained: issue types, ad serving statuses and review requests
Key takeaways
- The AdSense Policy center lists three types of issues: policy issues, regulatory issues and advertiser preferences.
- Only policy issues are required fixes; regulatory issues and advertiser preferences are optional but usually reduce advertising and revenue.
- "Disabled ad serving" blocks all ads on a site, while "Restricted ad serving" limits which advertisers can bid on your inventory.
- After fixing a policy issue you request a review from the Policy center with "Start review process"; each site with an enforcement needs its own review.
- If you remove the ad code instead of fixing the issue, Google says the issue disappears from the Policy center within 7 to 10 days but remains in its system.

The AdSense Policy center is the page in your account that lists every issue affecting ad serving on your sites, the enforcement applied, and the review button. It sorts issues into three types: policy issues (you must fix them), regulatory issues and advertiser preferences (optional, but they cost revenue). Each issue carries an ad serving status, such as “Disabled ad serving” or “Restricted ad serving”.
What does the Policy center show?
To open it, sign in to AdSense and click “Policy center”. According to Google’s Overview of the Policy center, you get:
- An account health summary at the top: how many sites are affected, how many issues are policy issues, regulatory issues or advertiser preferences, and what percentage of your ad requests are restricted or disabled. It also shows the percentage of account traffic serving without restrictions.
- A list of affected sites, sorted by default by the number of ad requests each issue affects. You can sort by site name, status, type of issue or date reported.
- A “Fix” link in the “Action” column that opens the Issue details page, and screenshots (when available) in the “View issue” column.
- A “Download CSV” button with “Download all items” or “Download filtered view”.
Issues also cover ad requests coming from your pages that are embedded into other sites with issues. If someone frames or embeds your pages, their problems can show up in your Policy center.
What are the three types of issues?
| Issue type | What causes it | Must you fix it? | Typical status |
|---|---|---|---|
| Policy issue | Your site does not follow the AdSense Program policies or the Google Publisher Policies | Yes. You will not receive advertising where policy issues apply | “Disabled ad serving” or “Restricted ad serving” |
| Regulatory issue | A country or regional requirement, for example GDPR or US state privacy laws | No, but you will likely receive less advertising | “Restricted ad personalization” |
| Advertiser preference | Content under the Google Publisher Restrictions, or treatments such as Confirmed Click | No, but fixing it is recommended because it affects revenue | “Restricted ad serving” or “Confirmed Click on” |
Google gives concrete examples in Understand policy issues, regulatory issues, advertiser preferences, and ad serving statuses: “Sexually explicit content” is a policy issue enforced with “Disabled ad serving”, while “Google-served ads on screens without publisher-content” is a policy issue enforced with “Restricted ad serving”. “Consent requirement: No CMP” is a regulatory issue. “Sexual content” under the Google Publisher Restrictions is an advertiser preference.
Google also warns that repeated policy violations may lead to an account suspension. Treat the Policy center as something to check regularly, not only when revenue drops.
What about “Must fix” and “Should fix”?
You will see “Must fix” and “Should fix” in many forum threads and older screenshots. The current Help Center pages do not use those terms. They classify issues as “Policy issue” (required) versus regulatory issues and “Advertiser preference” (optional). In the “Issues” column, an enforcement caused by a policy violation carries a “Policy issue” label, and one caused by a publisher restriction carries an “Advertiser preference” label, as explained in Understand the Google Publisher Policies and Google Publisher Restrictions. The practical meaning is the same: fix policy issues first, then decide whether optional issues are worth addressing.
What does each ad serving status mean?
| Status | What Google says it means | What to do |
|---|---|---|
| “Disabled ad serving” | All advertising is blocked on your site because of a policy violation | Fix the violation, then request a review |
| “Restricted ad serving” | There are restrictions on the advertisers that can bid on your inventory; little or no buyer demand is likely | Read the issue description and make changes, if any are needed |
| “Ad serving at risk” | Ad serving is not affected yet, but a warning applies and usually includes an enforcement date | Fix before the “fix by” date to avoid restriction or disabling |
| “Limited ad serving” | Account-level: Google has placed a limit on the number of ads your account can show | Understand your traffic, never click your own ads, avoid low-quality partners |
| “Confirmed Click on” | Some ads are generating unintended clicks, so a second confirmation click was added | Review your ad implementations; Google lifts it automatically when accidental clicks stop |
| “Restricted ad personalization” | Ad serving is limited in the EEA, the UK and Switzerland, for example because no certified CMP is used or TCF errors were detected | Implement a certified CMP correctly across all pages |
Two notes on wording. First, one Google page writes “Ad serving disabled” while the status table writes “Disabled ad serving”; both refer to the same full block. Second, “Limited ad serving” is an account-level status covered in detail in our guide to ad serving limits, and it is unrelated to “limited ads”, which is a privacy setting.
Warnings come before some enforcements
Some issues have a warning period. Google’s example is a warning for the “Ads & Content Overlap” Program policy: the site gets “Ad serving at risk” and the Policy center shows a “fix by” date. If you do not make changes, further action may be taken on the site or account. A warning is your cheapest moment to fix things.
Site-level vs page-level issues: what is the difference?
Enforcement can apply to a page, a site section or a whole site. Google explains the logic: when action is taken on a page, that page violates policy. When action is taken on a site or site section, multiple pages within it violate policy, and you need to check the entire site or section.
This explains a common frustration. The URL in a notification email is only an example. Google’s AdSense policy FAQs state that the same violation may exist on other pages, so fixing only the example page often leads to a rejected review.
To see only page-level issues: click “Add filter”, choose “Issue location”, check “Sites: Page-level issues”, then click “Apply”.
| Scope | What it tells you | How to approach the fix |
|---|---|---|
| Page-level | One URL violates a policy | Fix or remove that page’s content, or remove the ad code from it |
| Site section | Several pages in a directory or section violate policy | Audit every page in that section, including archives and tag pages |
| Site-level | The pattern is widespread | Audit templates, plugins, user comments and old content site-wide |
How do I request a review?
From Fix policy issues that affect ad serving, for a single site:
- Sign in to AdSense and click “Policy center”.
- Click “Fix” next to the site.
- In the “Issues found” section, click “Start review process”.
- In the dialog, choose a reason: “Removed the ad code”, “Fixed the violations” or “I don’t think these violations are present on this page”.
- Check the confirmation checkbox and click “Request review”.
For several page-level issues at once, select them in the list, click “Start review process” in the banner at the top, then pick a reason and confirm.
Limits to know:
- You must request a review for each site with policy enforcement for ad serving to continue on that site.
- You can request a certain number of page-level reviews during a 30-day period, refreshed daily. Google does not publish the number.
- After several recent rejections, “Start review process” becomes inactive and a date tells you when you can try again.
- Google does not publish a review turnaround time.
Removing the ad code instead
If a page is not worth fixing, remove the ad code from it. You do not need a review. Google says the issue stops being displayed within 7 to 10 days but remains in its system. This is often the best choice for a handful of thin or off-topic pages. Google also recommends that when you remove non-compliant content, you remove the related ad code too, so ads are not served next to a blank space (otherwise you can trigger the no content policy).
How do I prioritize a long list of issues?
Google suggests using filters: sort by the number of affected ad requests, or filter for sites with “Disabled ad serving”, which is the most severe enforcement. A practical order:
- “Disabled ad serving” on any site that earns money.
- Warnings with a “fix by” date (“Ad serving at risk”).
- “Restricted ad serving” caused by policy issues (for example, no publisher content).
- “Restricted ad personalization” from consent issues, which can affect a large share of European traffic. See the certified CMP requirement.
- Advertiser preferences, where you decide whether the content is worth keeping as it is. Our guide to prohibited and restricted content covers that trade-off.
Can I see Policy center data in reports?
Yes, partly. AdSense reports have a “Policy ad serving status” breakdown, available only for reports starting on or after June 27, 2025, with the values “Disabled ad serving”, “Restricted ad serving”, “Ad serving at risk” and “Regular ad serving”. Google lists reasons the numbers can differ from the Policy center:
- The Policy center uses the Mountain View time zone; Google recommends setting your reporting time zone to it when comparing.
- Some enforcements are not captured in reporting: low-traffic enforcements, consent requirements, crawler issues, “Intellectual property abuse” and “Malware or unwanted software”.
- Reporting shows the highest severity per site, and may list
www.example.comandexample.comseparately.
Common mistakes
- Fixing only the example URL. Audit the whole site or section before requesting a review.
- Requesting reviews too quickly. Rejections can lock the button until a set date.
- Ignoring advertiser preferences forever. They are optional, but “Restricted ad serving” can mean little or no demand.
- Deleting content but keeping the ad slot. You can swap one violation for a no-content violation.
- Confusing account-level and site-level problems. “Limited ad serving” is about traffic quality across the account, not a page to fix. If your whole account is closed rather than a site restricted, see account disabled appeals.
Frequently asked questions
Do I have to fix every issue in the AdSense Policy center?
No. Google says you are required to fix policy issues, because you will not receive advertising where they apply. Regulatory issues (such as a missing certified CMP) and advertiser preferences (Google Publisher Restrictions, Confirmed Click) are not mandatory, but Google warns they will likely reduce the advertising you receive and therefore your revenue.
How long does a Policy center review take?
Google does not publish a review time for Policy center reviews. While the review runs, the "Status" column shows "Under review". You are notified by email of the outcome, and a successful review removes the enforcement from the Policy center. A rejected review shows its details in the "Issues found" section.
Why is the Start review process button greyed out?
Google states the "Start review process" button becomes inactive when a site has been reviewed and rejected several times recently. The Policy center shows a date after which you can request another review. Use that time to audit the whole site, not just the example URL, because the same violation is often present on other pages.
What happens if I just remove the ad code from a flagged page?
Removing the ad code is an accepted alternative to fixing. You do not need to request a review in that case. Google says the issue stops being displayed in the Policy center within 7 to 10 days of removal but remains in its system, and you can request a review later if you reinstate the code.
Sources
- Overview of the Policy center · Google AdSense Help
- Understand policy issues, regulatory issues, advertiser preferences, and ad serving statuses · Google AdSense Help
- Fix policy issues that affect ad serving · Google AdSense Help
- Understand the Google Publisher Policies and Google Publisher Restrictions · Google AdSense Help
- Policy ad serving status breakdown · Google AdSense Help
Related guides
- "Ad serving has been limited": how AdSense ad serving limits work and what you can do
"Ad serving has been limited" explained: the two causes Google lists, why new accounts see it, typical duration, and what you can and cannot do while it lasts.
- "Valuable inventory: No content" and ads on screens without publisher content: causes and fixes
Why AdSense flags "Google-served ads on screens without publisher-content" (the no content issue), which pages trigger it, and how to fix it before a review.
- Prohibited vs restricted content in AdSense: Google Publisher Policies, Restrictions and restricted ad serving
Google Publisher Policies vs Google Publisher Restrictions: every category, what "Restricted ad serving" means for revenue, and when to fix, remove ads or accept.
- AdSense account disabled for invalid traffic: the appeal form, what to include and what happens to your earnings
AdSense account closed for invalid traffic: what the appeal form asks, how to answer each field, response times Google states, and what happens to unpaid earnings.
- Google's certified CMP requirement: what AdSense publishers need for EEA, UK and Swiss traffic
Since 2024 AdSense needs a Google-certified TCF CMP for personalized ads in the EEA, UK and Switzerland. Dates, what happens without one, how to check yours.