A policy center is the section of Google's publisher monetisation products, AdSense, Ad Manager and AdMob, where a publisher sees which of its pages, sites or apps break Google's rules, what that does to ad serving, and how to ask for a review once the problem is fixed. It exists because enforcement on the sell side used to be blunt and hard to read. Before 2017, a single content violation typically switched off ads across an entire AdSense site, and the publisher learned about it mostly by email. Google built the Policy center, as it styles the name in its help pages, to put the violation, its scope and the route back to full monetisation in one place.

How the Policy center works

Google's systems crawl publisher pages and app content and compare them against two rulebooks. The Google Publisher Policies list content that cannot carry Google ads at all, such as sexually explicit material, malware or intellectual property abuse. The Google Publisher Restrictions cover content that is allowed but that many advertisers avoid, such as alcohol, gambling or tobacco. When a crawler or reviewer finds a problem, the result appears as a row in the Policy center, attached to a site, a page or an app.

Since an April 2025 redesign, first reported for AdMob, each row carries one of three issue types. Policy issues are violations of the program policies, and according to AdSense documentation, repeated violations can lead to account suspension. Regulatory issues stem from laws such as the General Data Protection Regulation (GDPR) or US state privacy statutes. Advertiser preferences flag content some buyers choose not to bid on, which, according to Google, "will likely receive less advertising." Only the first category must be fixed. The other two cost money without breaking a rule.

Each row also shows an ad serving status, which is where the commercial consequences sit. AdSense help pages list six:

  • Disabled ad serving - no ads on the affected site until it passes review.
  • Restricted ad serving - only some advertisers may bid on the inventory, which cuts demand.
  • Ad serving at risk - a warning with a "fix by" date; ads still run.
  • Limited ad serving - an account-wide cap on the number of ads, usually linked to invalid traffic concerns.
  • Confirmed Click on - an extra tap is added to ads judged to cause accidental clicks, applied and lifted automatically at site or ad unit level.
  • Restricted ad personalization - for European Economic Area (EEA), UK and Swiss traffic where no certified consent management platform (CMP) is in place, the CMP is uncertified, or too few requests carry a consent string.

Enforcement works at three levels. A page-level action strips ads from individual URLs, a site-level action from a whole domain, and an account-level action, such as limited ad serving, from everything the publisher owns. Google made page-level enforcement the default for content violations in 2017.

Fixing an issue and requesting review

The workflow is the same across the three products. A publisher clicks Fix in the Action column, which opens an Issue details page. A "View issue" column shows screenshots of offending pages where Google has them. The publisher then selects "Start review process" and picks one of three reasons: the ad code was removed, the violations were fixed, or the publisher believes no violation exists. For apps in Ad Manager, the options differ, including releasing a new app version or making a server-side change.

Reviews are rationed. Ad Manager help pages say publishers may request "a certain number of page-level reviews during a 30 day period," a limit that refreshes daily, though Google does not publish the number. The review button turns inactive when a site has been rejected several times recently. Google's own estimate of timing has not moved much in nine years: the 2017 launch post said reviews "typically take one week but can sometimes take longer," and the AdMob documentation cited in April 2025 used almost the same words. A publisher can skip review entirely by removing the ad code; the issue then drops off the Policy center within 7 to 10 days, though, according to Ad Manager documentation, it stays in Google's systems.

The Policy center has also become the appeal channel for newer enforcement systems. When Google introduced Restricted Access Features for AdSense for Search in June 2025, five in-scope violations made one strike, with three strikes in two years revoking access to premium search features. Strikes themselves could not be appealed. Only the underlying violations could, through the Policy center, and account managers were barred from filing on a publisher's behalf.

Origin and evolution

Google announced the AdSense Policy center on May 15, 2017, after piloting it with "thousands of AdSense publishers," according to Scott Spencer, then Google's director of sustainable ads. A May 31 post by product managers Richard Zippel and Nick Radicevic and policy transparency lead John Brown called it "a one-stop shop" for policy actions. The same post introduced page-level enforcement, under which a violation "affects individual pages where violations of the AdSense Program Policies are found" rather than the whole site.

The concept then spread across Google's publisher stack. On May 2, 2019, Google launched an App Policy Center on AdMob and Ad Manager, which Brown described as "a single centralized hub to review and monitor policy violations and appeals." It allowed appeals of certain warnings within 30 days. In August 2019, Google split its content rules into the Publisher Policies and Publisher Restrictions that still structure the Policy center today, saying 734,000 publishers and app developers had been removed from its network the previous year.

A redesign on November 2, 2021 merged site and app issues in Ad Manager into one table, added an "Ad requests - last 7 days" column so publishers could see which issues cost the most, and allowed CSV exports. Issues marked "Must fix" were highlighted in an account health summary. Screenshots arrived in May 2022 for some issue types. In November 2023, AdSense for Search publishers gained their own Policy center, with Google saying no action was required.

Why it matters

For publishers, the Policy center is the nearest thing to a revenue early-warning system. A restricted or disabled status removes demand before any report shows the drop, and the "fix by" date on an at-risk warning is often the only notice before enforcement. The scale is large. Google's 2025 Ads Safety Report, published in April 2026, said Google actioned more than 480 million web pages and 245,000 publisher sites during 2025, with AI systems contributing to detection on more than 467 million of those pages. Sexual content accounted for 409 million pages, about 85 per cent, a category that is restricted rather than banned, as coverage of a September 2026 Video Advertising Bureau deck noted.

For advertisers and agencies, the tool matters indirectly. Restrictions and advertiser-preference labels determine which inventory reaches Google Ads and Display & Video 360 buyers, so the Policy center is one of the filters shaping the open web supply that programmatic campaigns buy.

Limitations and criticisms

The main complaint is opacity. Google publishes neither the page-level review quota nor how many rejections lock the review button. Kean Graham, chief executive of the monetisation vendor MonetizeMore, said in an October 2026 webinar that "Google doesn't give actual reasons why they rejected a certain publisher," though he was speaking about Ad Exchange applications rather than Policy center decisions, and his company sells compliance tools.

Coverage is also incomplete. When Google added policy breakdowns to AdSense reporting, it excluded low-volume restrictions, consent requirements, crawler issues, intellectual property violations and malware, and warned that Policy center data uses Mountain View time. Consent failures under the Transparency and Consent Framework (TCF) appear in a separate error report, not the Policy center. And ad serving limits, introduced in late 2020, cut fill rates without Google disclosing reduction percentages. Because enforcement relies heavily on machine learning, a misclassified page can lose ads before any person has looked at it.

What it is not

  • Google Ads Policy manager. The advertiser-side tool, under Tools then Troubleshooting, where ad and asset disapprovals are appealed. Each ad is limited to three appeals, and since July 21, 2026, decisions older than six months cannot be appealed from the account.
  • Google Advertising Policies Center. The name Google gives its advertiser policy help site, a reference library rather than an account tool.
  • Merchant Center diagnostics. Item and account issues for shopping feeds sit in Google Merchant Center's Needs attention tab and produce a product disapproval or account suspension, not a Policy center entry.
  • Play Console Policy status and Meta Account Quality. Google Play's Policy status page reports app rejections, removals and suspensions in the store, regardless of ads. Meta's Account Quality tool shows advertiser account restrictions. Neither touches publisher ad serving. Search Console's manual actions report is likewise a search ranking tool.

Recent developments

On April 22, 2025, Google replaced AdMob's "Must fix" label with the three issue types, renamed the Screenshots column "View issue" and let publishers flag issues they believed were applied incorrectly. On November 25, 2025, AdSense added a policy ad serving status breakdown to reports, with data back to June 27, 2025, sorting traffic into Regular, At risk, Restricted and Disabled. Reports show the highest-severity status per domain. On the advertiser side, Google said in April 2026 that Ads Advisor would check campaigns against policy while they are being edited,, a pre-emptive check with no announced publisher equivalent.

Timeline

  • May 15, 2017 - Google announces the AdSense Policy center and page-level enforcement after a pilot with thousands of publishers.
  • May 31, 2017 - Google details page-level enforcement as the default for content violations.
  • May 2, 2019 - App Policy Center launches on AdMob and Ad Manager, with 30-day appeals for certain warnings.
  • August 2019 - Google Publisher Policies and Google Publisher Restrictions introduced across AdSense, AdMob and Ad Manager, effective September 2019.
  • Late 2020 - AdSense ad serving limits introduced.
  • November 2, 2021 - Policy center redesign with unified site and app table, ad request impact column and CSV export.
  • May 2022 - Screenshots added to Ad Manager and AdSense Policy centers.
  • November 2023 - AdSense for Search publishers get a Policy center.
  • April 22, 2025 - Policy issues, regulatory issues and advertiser preferences replace "Must fix" in AdMob.
  • June 24, 2025 - Restricted Access Features announced for AdSense for Search, effective August 25, 2025.
  • November 25, 2025 - Policy ad serving status breakdown added to AdSense reporting, data from June 27, 2025.
  • April 16, 2026 - 2025 Ads Safety Report: 480 million pages and 245,000 sites actioned.

Summary

Who: Publishers and app developers using Google AdSense, AdSense for Search, Ad Manager and AdMob, and Google, which detects violations and decides reviews.

What: A dashboard listing policy issues, regulatory issues and advertiser preferences by page, site or app, with the resulting ad serving status and a workflow to request review.

When: Launched for AdSense in May 2017, extended to apps in May 2019, redesigned in November 2021 and reclassified in April 2025.

Where: Inside the AdSense, Ad Manager (under Admin) and AdMob interfaces, with policy status also surfaced in AdSense reports since November 2025.

Why: To replace blunt, site-wide enforcement with targeted actions publishers can see and fix, while keeping ads off content that breaks Google's rules or that advertisers avoid.