Understanding policy issues and ad serving statuses

In this article, we’ll review what types of issues affect ad serving and what the ad serving statuses mean in the Policy center.

Issues that affect ad serving

If your site or app has an issue that affects ad serving, it means that your site or app either violates our Program policies, is restricted by the Google Publisher Restrictions, or has Confirmed Click on. This includes cases when the ad requests are coming from your pages that you've embedded into the sites with issues.

There are 4 types of issues: policy violations, publisher restrictions, Confirmed Click, and consent requirement. Only policy violations are required to be fixed. You don’t have to fix publisher restrictions, but note that ad serving will continue to be restricted on your site. We recommend that you act on Confirmed Click and consent requirement issues as they may impact your revenue.

You may also receive a warning before action is taken on your ad serving. Review the table below for more information about the issue types.

Type	What it means	Ad serving status	Examples
Policy violation (Must fix)	Your site or app is not currently in compliance with the Program policies. When this occurs, you need to make changes to your site or app to bring it into compliance with our policies.	Policy violations are marked Must fix in the status column. Policy violations are enforced with either Disabled ad serving or Restricted ad serving.	Examples of policy violations include, but are not limited to: Sexually explicit content Dangerous or derogatory content Layout encourages clicks
Publisher restriction	Your site or app falls under the Google Publisher Restrictions. While you can choose to monetize this type of content, you will likely receive reduced advertising as not all ad sources want to bid on it.	Sites and apps with publisher restrictions receive Restricted ad serving.	Examples of publisher restrictions include, but are not limited to: Sexual content Shocking content Online gambling content
Warning	Some policy violations and publisher restrictions have a warning period before action is taken on your ad serving. If you receive a warning, it means that your site or app is not currently in compliance with the Program policies or contains content that falls under the Google Publisher Restrictions. To resolve this, you need to make changes to your site or app to bring it into compliance. If you don't make changes, further actions may be taken on your site, app, or account.	Sites and apps with warnings receive Ad serving at risk.	Examples of issues that cause warnings include, but are not limited to: Ads & Content Overlap
Confirmed Click	Google Ads has determined that certain ads on your site or app are generating unintended clicks. This creates a poor user experience because the user ends up on advertiser landing pages instead of their intended content. Google Ads has added Confirmed Click on its affected ads. Confirmed Click adds a second click that improves the user experience by letting the user confirm their intent to visit the advertised page.	Sites and apps with Confirmed Click added receive Confirmed Click on.	Implementation examples you should review for, include but are not limited to: Ads close to navigational elements Navigational elements overlaid on display ads Buttons on top of or close to ads Content on top of or close to ads Reflow of content causing confusion. Any violations of the ad placement policies
Consent requirement	You're not currently using a certified Consent Management Platform (CMP) registered with the IAB's Transparency and Consent Framework (TCF) when serving ads to users in the EEA, the UK, and Switzerland.	Sites with consent requirement issues receive Restricted ad personalization.	Consent requirement issues are: No CMP: Some ad requests on your inventory from the EEA, the UK, and Switzerland are missing a TCF string. CMP not certified: Some ad requests on your inventory from the EEA, the UK, and Switzerland are missing a TCF string from a certified CMP. Low coverage: A majority of ad requests on your inventory from the EEA, the UK, and Switzerland are missing a TCF string.

Tip: Check out our videos on Policy center issue notifications and how to use Policy center filters to sort your issues.

Understanding ad serving status

The status of your ad serving lets you know how your sites and apps with issues are impacted. The table below explains the statuses and what they mean.

Status	What it means	What you can do
Ads not serving in Android app	Ads on new apps may take a few hours to appear. If you still do not see ads after 24 hours, Google may need to scan the app to ensure it's safe for users.	Complete the Android Package submission form (APK) form.
Disabled ad serving	All advertising is blocked on your site or app. Your site or app isn’t serving ads due to a policy violation.	Review the issue description in the Policy center to determine the changes you need to make. After you address the policy violations on your site or app, you may request a review to enable ad serving.
Restricted ad serving	There are restrictions on the advertisers that can bid on your inventory. Your site or app is likely to have little or no buyer demand because not all ad sources can bid.	Review the issue description in the Policy center to determine the changes you need to make, if any. Reminder: Policy violations must be fixed, while publisher restrictions are optional to fix. Learn more.
Ad serving at risk	Ad serving isn’t affected yet, but you’ll need to make changes to your site or app to ensure ad serving continues. This is due to a warning on your site or app. Warnings typically include enforcement dates, when further action is taken and ad serving is affected.	Fix the issues before the enforcement date to prevent ad serving from being restricted or disabled. Review the issue description in the Policy center to determine the changes you need to make.
Limited ad serving	This affects your AdSense account. Limited ad serving means Google has placed a limit on the number of ads your AdSense account can show. Learn more about ad serving limits.	Make sure you understand your ad traffic and users. Never click on your own ads, and avoid partnering with untrusted or low-quality parties. Learn more about preventing invalid activity.
Confirmed Click on	Some ads on your inventory are creating unintended clicks so Google has added Confirmed Click on these ads.	Review your ad implementations. Learn more about disallowed implementations and recommended implementations. Our system automatically applies Confirmed Click when it detects accidental clicks. Similarly, the system automatically lifts Confirmed Click when it no longer detects accidental clicks.
Restricted ad personalization	Some sites are not using a certified CMP to ask for user consent. Sites and apps that do not adopt a Google certified CMP will not be eligible for personalized ads. Sites using a certified CMP are eligible for personalized ads, non-personalized ads (NPA), and limited ads.	No CMP: If you haven’t already, choose a certified CMP registered with the TCF. Implement your CMP solution. Learn more about certified CMP options. CMP not certified: If you have your own CMP, register for certification. If you use a third-party CMP that hasn’t been certified, encourage your CMP to register for certification. You can also see our list of certified CMPs. Note: If you recently adopted a certified CMP, it may take up to 48 hours for this issue to be resolved and removed from the Policy center. Low coverage: You’ve implemented a CMP, but you haven’t implemented it correctly across all of your inventory. You have a CMP solution, but there’s an issue with the configuration or certification.