Classify the serving restriction before editing
Open the Ads or Assets view, add the Policy details column and record the exact status, policy name, affected campaign, asset ID and first-observed time. Distinguish disapproved from eligible (limited), under review and an account-level suspension. These states do not share the same remedy. Export a small affected-asset list so the team can track each decision independently.
Check whether the problem affects one creative, all assets pointing to a particular URL, an entire product category or the account itself. If the same landing page appears in many disapprovals, investigate the destination before editing dozens of ads. Keep the last approved copy and destination in your change log to support comparison.
Separate creative policy from destination failure
For creative issues, compare the exact headline, description, image, claims and extensions with the cited policy. Remove unsupported promises, misleading wording or prohibited content only after understanding why the decision applies. Do not evade a policy with misspellings, redirects or a superficially different domain; that can worsen the compliance situation.
For destination issues, test the final URL on mobile and desktop without relying on your logged-in browser. Check HTTP response, redirect destination, domain consistency, certificate, robots restrictions, regional availability, cookie overlays and whether the page meaningfully delivers what the ad promises. A working homepage does not prove the specific landing page works.
Build an evidence packet a reviewer can use
Create one case record per policy issue: account and campaign identifiers, affected ad IDs, policy label, original copy, landing-page URL, screenshots of the error, observed date, changes made and the person who approved them. Capture a reproducible test, such as a clean-browser load of the exact destination and a dated screenshot of the corrected claim.
For a legitimate business verification or restricted-category issue, collect only the documents the platform requests, store them securely and avoid uploading personal records into informal support threads. A useful appeal describes the specific error or correction; a long emotional complaint rarely helps a reviewer identify the relevant evidence.
Choose correction, dispute or escalation deliberately
If the ad or destination actually violated the policy, correct it and save the change so review can restart. If the decision appears mistaken, use the available appeal path and select the appropriate reason rather than falsely claiming changes were made. Google's Policy Manager shows appeal history and outcomes; track the result there instead of assuming an email reply equals reinstatement.
Google's current help documentation limits repeated appeals and says appeals directly in the account are unavailable for policy decisions more than six months old beginning July 21, 2026. Do not exhaust retries with identical submissions. When an appeal is marked duplicate or fails after a genuine fix, follow Google's documented review or support guidance.
Protect measurement while the ads are offline
Record disapproval start and end times alongside daily eligible impressions, spend, conversions and the share of campaigns affected. A decline in lead volume during the outage is not proof that a bidding strategy deteriorated. Annotate the reporting period and avoid making optimization decisions from days with materially restricted delivery.
If urgent demand must still be served, shift only to compliant, approved campaigns with appropriate intent and destinations. Do not simply duplicate the rejected ad into another account. Check the replacement's conversion action, geographic coverage and landing page before moving spend, and retain an audit trail of any temporary allocation.
Verify recovery across assets and destinations
After review, confirm the actual serving status of the affected ad and its related assets, not just the appeal's success message. Revisit mobile landing-page access, policy details and eligible impressions over the following days. If the ad remains limited under a different policy, open a separate issue rather than declaring the incident resolved.
A reusable incident checklist should include detection, classification, destination test, evidence, correction, appeal status, restored delivery and a prevention owner. Review recurring causes monthly: broken redirects, expired claims, unavailable offers, feed discrepancies or website releases that changed page access.
Connect policy QA to the wider account audit
Include policy status in launch and change-control checks, especially after website migrations, new ad assets and seasonal promotions. Link the person editing the website with the person responsible for Ads policy so changes to redirects or page content do not silently invalidate approved campaigns.
Use the Google Ads Launch Checklist to document preflight controls and the website launch QA guide to test the destination. The objective is not to maximize the number of appeals; it is to prevent the same correctable disapproval from recurring while keeping claims accurate and landing pages useful.