In the first week of April, we had multiple client accounts get flagged by Google Ads for policy violations. Different industries. Different campaign types. Different policy categories. None of them had changed anything about their ads.
In one case, campaigns had been running clean for over a month before Google suddenly started disapproving them one by one. In another, an account had zero impressions for 30 days and no one had been alerted.
When one account gets flagged, that’s a one-off. When several get flagged in the same window for completely different reasons, that’s a pattern. Something changed on Google’s end. Here’s what we know, what we’re seeing, and what you should check on your own account before Google gets to it first.
Google updated its ad policies on March 31 2026. The enforcement followed immediately.
On March 31, 2026, Google published updates to its Ads Policy Help Center articles across a broad range of categories: Editorial, Healthcare and medicines, Financial products and services, Limited ad serving, Sexual content and wellness, Other restricted businesses, plus several related policies including Google Ads Terms & Conditions, API policies, and Promotional offers.
Google’s official description: “improved organization and readability” with “no change to enforcement of the policies.”
What we observed tells a different story. Within days of that update, previously compliant ads across multiple accounts started getting flagged.
This wasn’t completely out of the blue. Google had already retired legacy ad format policies on March 17 (covering text ads, form ads, responsive ads, and image quality) as part of a broader policy consolidation effort running through early 2026. The March 31 update looks like the next phase of that same effort.
Here’s the pattern we think is driving this: when Google rewrites policy documentation, the automated classifiers that enforce those policies often get recalibrated against the updated language. The policies may not have changed on paper. But the system reading and enforcing them appears to have shifted.
This lines up with what we heard directly from Google. After flagged ads on one of our accounts prompted a call with a Google Ads rep, the rep confirmed that Google had recently rolled out major updates to its ad review algorithm. Those updates are the most likely explanation for why previously compliant ads are now getting caught. Google knows the system is behaving differently. They just haven’t said so publicly.
This is part of a larger enforcement shift
The March 31 update didn’t happen in isolation. Google’s ad enforcement has been accelerating for a while, and 2026 is intensifying that trajectory.
Some context on scale: Google suspended 39.2 million advertiser accounts in 2024. That’s up from 12.7 million in 2023, a threefold increase in a single year. They blocked or removed 5.1 billion ads and restricted another 9.1 billion. Google deployed over 50 updates to its AI enforcement models in 2024 alone.
The bigger shift is how Google enforces. The platform has moved from reactive enforcement (catching violations after the fact) toward predictive enforcement. Google now flags ads based on the predicted likelihood of a violation, not just actual violations. Ads caught by the predictive model get pushed into a slower “Enhanced Review” queue that can delay launches by 24 to 72 hours, even if the ad ultimately passes.
The part that matters most for existing advertisers: previously approved ads can be retroactively disapproved after policy updates.
Google says they’ve reduced incorrect suspensions by 80% with improved AI. That sounds good until you remember the denominator. At 39.2 million suspensions, even a small error rate translates to a massive number of legitimate businesses getting caught.
Compliance is not a set-it-and-forget-it thing anymore.
The types of issues we’re seeing right now
Over the past two weeks, we’ve seen a range of policy flags hit accounts we manage. These aren’t edge cases. They’re common scenarios that a lot of Google Ads advertisers will relate to.
Factual product claims flagged as clickbait
We’ve seen ads with specific, documented performance claims get disapproved under the Clickbait/Misrepresentation policy. The ads weren’t exaggerating. The claims were real, verifiable product specifications.
The trigger: absolute language. Google’s automated classifier reads phrases like “100% accuracy” or “guaranteed results” as sensationalist, even when they describe a documented, measurable product capability. The system doesn’t understand context. It just sees the pattern and flags it.
One detail worth noting: these disapprovals rolled in sequentially, not all at once. Google’s automated review processes ads through a queue, so you might see flags trickling in over several days rather than a single batch rejection. The timing on these correlated directly with the algorithm updates Google confirmed to us.
The practical fix: prep backup headlines that convey the same message without absolute language. “Complete” instead of “100%.” “Reliably detects” instead of “guaranteed detection.” Have these ready before you need them, so you’re not scrambling if an appeal gets denied.
Content getting swept into restricted categories it doesn’t belong in
If your business is adjacent to healthcare, addiction services, financial products, or other regulated categories, your ads can get flagged under policies that don’t actually apply to you.
We’ve seen this with organizations whose content touches sensitive topics getting flagged under restricted policies for services they don’t even offer. Google’s restricted category classifiers cast a wide net. If your ad copy or landing page contains language that overlaps with a regulated category, the system may flag it regardless of what your business actually does.
The frustrating part is the inconsistency. We’ve seen nearly identical ads get different outcomes: one approved, one disapproved. The classifier isn’t making consistent calls on borderline content, which makes it hard to predict what will pass and what won’t.
The takeaway: you can’t assume that because one ad passed review, similar ones will too. Especially after a policy update, the system may evaluate the same language differently than it did a month ago.
Destination mismatches hiding behind working redirects
Your Final URLs might not be doing what you think
Across multiple accounts, we’ve found ads disapproved for destination issues, and in some cases the violations had been sitting there unnoticed for weeks.
Google checks every declared Final URL in your account. It doesn’t just confirm the page exists. It checks that the URL resolves cleanly to the expected destination without cross-domain redirects, and that the content on the landing page matches what the ad promises. When it finds a mismatch, the ad gets flagged.
We’ve seen this play out two ways.
The first: ads that are supposed to be running, but they’re quietly disapproved because of a URL problem. A domain migration where the old URLs were never updated in Google Ads. Pages that got deleted or moved during a site redesign. URL paths that changed when a CMS was updated. The campaign looks active, but the ads aren’t serving. You’re losing traffic you think you’re getting.
The second is more subtle and, in some ways, worse. Campaigns that are paused at the campaign or ad group level, so no one is monitoring them. But the individual ads inside those campaigns are still technically enabled. If those ads have policy violations (outdated URLs, destination mismatches, whatever it might be), those violations are still counted as active strikes in your account’s Policy Manager. The campaigns aren’t delivering a single impression, but they’re quietly accumulating compliance problems that affect your overall account health. We’ve seen accounts where this was happening and the advertiser had no idea, because everything looked paused from the top level.
Both situations point to the same thing: Google’s enforcement system doesn’t ignore ads just because you’re not looking at them.
Display ad CTAs triggering misleading design flags
We’ve seen display ads disapproved under Google’s Misleading Ad Design policy because of the specific word used in a CTA.
The trigger was the word “Download.” Google’s policy prohibits display ad elements that simulate functional interactions, and “Download” implies a file-download action the ad can’t actually perform. The only ads in the same set that weren’t disapproved used a different CTA word entirely.
This is a nuance most advertisers would never figure out on their own. It’s not just about the visual styling of the button. It’s about the specific word.
Words to avoid in display ad image CTAs: “Download,” “Install,” “Open,” “Launch,” “Play,” “Run,” “Click Here,” “Close.”
Safe alternatives: “Get,” “See,” “Read,” “Learn,” “Explore.”
Enforcement of this policy has ramped significantly in recent months. Plenty of existing display ads across the web still have similar CTA elements that haven’t been caught yet, but newly uploaded ads are being reviewed under the fully enforced rules. If you’re creating new display ads, this matters right now.
The compliance checklist you should run this week
You don’t need to wait for Google to flag you. Here’s what to audit proactively, based on what’s actually triggering violations right now.
Ad copy. Search your headlines and descriptions for absolute claims: “100%,” “guaranteed,” “#1,” “best,” “proven,” “instant,” “miracle.” These are the words Google’s classifier is most sensitive to. Even if the claim is factually true for your product, context doesn’t matter to the automated system. If you’re in or adjacent to healthcare, financial services, legal, addiction treatment, or any regulated category, also review your copy for terms that could get swept into restricted policy buckets that don’t apply to your business. And check for trademark terms from other brands while you’re in there.
Display ads. Review all image ad CTAs for the restricted action words listed above. Check that your CTA buttons don’t visually simulate system-level interactions (anything that looks like an operating system dialog box, a browser notification, or a software install prompt).
Destinations and URLs. Click through every Final URL in your active campaigns and confirm it loads the correct page. Not a 404. Not the homepage when it should be a product page. Not a page that’s been moved or restructured since the ad was created. If your site has gone through a domain migration, CMS change, or major redesign, pay extra attention here. URL paths that worked six months ago may not resolve correctly today. Scan for URL hygiene issues: duplicate UTM parameters, double slashes in paths, HTTP instead of HTTPS. And verify that what your ad promises actually matches what the landing page delivers. Google’s crawler is checking for this.
Account hygiene. Open your Policy Manager and look for any active warnings or strikes you might not have noticed. Then check your paused campaigns. If campaigns are paused at the campaign or ad group level but the ads inside them are still enabled, any policy violations on those ads are still counting against your account. This is easy to miss because the campaigns look inactive from the top level. Either pause the individual ads, remove the ones with violations, or set the campaign to “Ended” so nothing inside it can accumulate strikes. Also verify that your Advertiser Identity Verification and Business Operations Verification are current and complete
Already flagged? here’s the right way to respond.
If you’ve already been hit with disapprovals, here’s the short version of how to handle it.
First, read the specific policy violation. Hover over the “Disapproved” status in your Google Ads account to see the exact policy citation. The fix depends entirely on which policy was triggered, and guessing wastes time.
Fix the underlying issue before you appeal. Repeatedly appealing without making changes doesn’t just fail. It can hurt your account standing and make future appeals harder. Google tracks your compliance history.
If the disapproval seems wrong (and sometimes it is), file an appeal with specific, factual reasoning for why the ad complies with the cited policy. Be clear and concise. Don’t get emotional or write a novel.
Have backup ad copy ready. Don’t wait for the appeal outcome to start prepping alternatives. If the appeal is denied, you want to be able to swap in compliant copy the same day.
Check for related account impact. Suspensions can cascade to linked Merchant Center accounts, other accounts on the same manager, and accounts using the same payment methods. One suspension can create problems across your entire account structure.
And don’t ignore individual ad disapprovals thinking they’re minor. Patterns of violations feed into Google’s three-strikes system, which escalates from warnings to temporary suspension to permanent account loss.
We’re running compliance audits for our Google Ads clients
We’re proactively auditing ad copy, display ads, destination URLs, and account health across our managed accounts right now. The audit covers everything in the checklist above, plus deeper investigation into account-specific issues that are easy to miss without dedicated attention.
We flag potential violations before Google does and provide specific recommendations, including replacement ad copy where needed. If you want us to run one on your account, reach out.
The bottom line
Google’s enforcement system is going to keep getting more aggressive. That’s been the trajectory for years, and everything about 2026 is accelerating it. More AI model updates, tighter classifiers, broader policy consolidation, and a growing willingness to retroactively flag ads that previously passed review.
The businesses that avoid disruption are the ones treating compliance as an ongoing practice, not something they set up once and forget.
If your ads were running fine last month, that doesn’t mean they’re fine today. Worth checking.
