Google Disapproved 1,500 Ads Over Server Errors Nobody Can Find

Multiple Google Ads accounts woke up to disapproved campaigns this week. The reason cited: "destination not working." The landing pages, in every reported case, loaded fine. No downtime, no DNS outages, nothing broken on the advertiser's end. Google's automated crawlers flagged phantom errors, and the system did what automated systems do. It turned everything off.

This is not a new phenomenon. And that's exactly why it deserves more than a shrug this time around.

1,500 Ads Down, Zero Actual Errors

Ryan Berry, managing director at Cornerhouse Media, reported more than 1,500 ads disapproved in a single account around 1:30 p.m. UTC. Charlotte Osborne, a Google Ads trainer, documented two separate client cases the same week: one flagged for a DNS error, another for an HTTP 500. Joshua Barr, another specialist, said he'd been getting "lots of emails overnight" about disapprovals and had been dealing with similar problems for weeks.

The common thread: every site was functioning normally. Internal IT teams checked DNS records. Pages loaded in browsers. Uptime monitoring showed zero incidents. The disapprovals came from Google's automated crawler encountering something it interpreted as a server error, even though real users experienced nothing wrong.

Google hasn't issued a public statement on the wave.

Google's Crawler Has a History of Seeing Ghosts

This isn't the first time. In February 2022, a remarkably similar wave hit advertisers. Forty-three client accounts at one agency were flagged for "government documents and official services" policy violations. The accounts sold HVAC equipment, beauty products, and orthopedic supplies. Nothing remotely governmental.

When asked about it, Google Ads Liaison Ginny Marvin responded: "We haven't seen any 'mass' disapprovals that would indicate a bug." The advertisers staring at dozens of paused campaigns would probably describe the situation differently.

The 2022 episode is useful context because it shows how these cycles tend to resolve. Google eventually acknowledged individual errors through support channels but never confirmed a systemic issue. One advertiser was told the fix "would take 2 days." For a campaign that's bleeding leads every hour it's paused, two days is a very long time.

The PMax Timing Makes Everything Messier

What makes this round particularly rough is the timing. Google started retroactively reviewing existing Performance Max assets on April 14, the same week the destination errors hit. New PMax campaigns have been under asset-level review since April 7, and existing campaigns entered a two-week re-review window that runs through April 28.

The asset-level system replaces Google's older campaign-level enforcement. Previously, one policy violation could pause your entire campaign across Search, Display, YouTube, and everything else PMax touches. Now individual assets get evaluated independently: approved, approved with limitations, under review, or disapproved.

On paper, that sounds like an improvement. Only the offending asset gets pulled instead of the whole campaign. In practice, the false positive rates are concerning. Healthcare imagery carries a 15-25% false positive rate under the new AI review system. Before-and-after images sit at 20-30%. Even claims using words like "best" or "guaranteed" flag at 10-15%.

Combine that with a crawler simultaneously flagging working landing pages for nonexistent server errors, and what you end up with is a week where the automated review system seems to be misfiring from two directions at once.

The Revenue Cost of a Phantom Error

When an ad gets disapproved, it stops serving immediately. Appeals typically take 24 to 72 hours. Google's recommended process: check the policy manager, verify your landing page, submit an appeal through standard channels.

What that timeline leaves out is the downstream cost. If you're running lead gen campaigns at $50 per lead and generating 40 leads a day, a two-day disapproval costs you $4,000 in lost pipeline before anyone at Google even looks at it. For e-commerce accounts running on thin margins during a promotional window, the math gets worse fast.

And there's no proactive warning. You find out when your ads stop serving or when the email arrives. By then, the damage is hours old.

Google's automated enforcement is a lot like speed cameras. It catches real violators, and at scale, it has to. Google removed 5.5 billion ads and suspended 39 million advertiser accounts in 2024 alone. But when the camera malfunctions, you still get the ticket. And the burden of proof falls entirely on you.

What to Audit Before May 12

I'm not going to pretend there's a permanent fix for Google's crawler misreading your site. If Googlebot decides your server returned a 500 error that your own monitoring never recorded, you're at the mercy of the appeal process. But there are things you can tighten up right now that reduce your exposure.

Test your landing pages from multiple geographic locations, not just your office. Google's crawlers hit from various IPs and regions. A CDN misconfiguration that serves fine from your office but returns errors from European edge nodes will trigger disapprovals you'll never catch from your desk. Tools like Uptrends or Pingdom offer free multi-location checks.

Check how your server responds to bot traffic specifically. Some WAF configurations rate-limit or block automated crawlers without anyone realizing it. If your firewall is accidentally throttling Googlebot, you're manufacturing your own disapprovals. Pull your access logs, filter for the Googlebot user agent, and verify those requests are getting clean 200 responses.

If you're running PMax campaigns, audit your asset library this week. Google recommends 8-10 text assets and 7-10 image assets per asset group. If a few get disapproved during retroactive review, you want enough remaining to keep the campaign functional without a significant CPA spike. Asset disapprovals can increase CPA by 5-40% depending on volume, with recovery taking up to three weeks in some cases.

The grace period for existing PMax assets runs through May 12. After that, enforcement is permanent.

Google Keeps Score, Runs the Appeals, and Offers No Refunds

This fits a broader pattern that's been getting harder to ignore. Google's automated systems have been on a run this year, from consent enforcement quietly eating nine months of EU conversion data to the ad review crawlers now flagging working landing pages. We've written about this structural problem before: when the same company controls the auction, the measurement, and the appeals process, accountability gets blurry.

And to be fair, I get why Google leans on automation here. You can't manually review 5.5 billion ads a year. That's not a realistic expectation. But there's a real gap between "we automate everything" and "we offer a fast-track lane for obviously false disapprovals." I'm talking about cases where the landing page plainly works and the error is on the crawler's end. That gap is where advertisers are losing real money right now, and Google hasn't shown much urgency about closing it.

Based on the false positive rates in Google's own PMax documentation, I'd estimate roughly 10-15% of active PMax accounts will see at least one asset flagged during the retroactive review window. Most of those will be fixable. But the ones that quietly crater your CPA while you wait three days for an appeal? Those are worth preparing for now, while there's still time to build in the buffer.

Notice Me Senpai Editorial