Google Ads compromised site: how to fix it and get ads back
Your ads were disapproved for a compromised site. Confirm the hack, clean a WordPress site, request the right reviews in the right order and stop wasted spend meanwhile.
Your site loads for you, but Google's ad crawler gets an error. Here is how to test your page the way Google does, find the cause and get your ads running again.
A Google Ads destination not working disapproval means Google's crawler, AdsBot, tried to open your landing page and got an error: a 4xx or 5xx response, a DNS failure, a broken redirect, a timeout or a login screen. Your site can load fine for you and still fail for AdsBot, so test it the way Google does.
If the page works for you, look at what treats Google differently: firewalls, country blocks, DNS, redirects and tracking templates. Fix the cause, then edit the ad or appeal.
Until then, the ad is off. Google says a disapproved ad won't be able to run until the violation is fixed and the ad is reviewed again. While it waits, that ad brings you no calls.
Google's Destination not working policy disapproves destinations that are set up incorrectly or that return an HTTP error code to Google AdsBot web crawlers on common devices globally. The test isn't your laptop. It is Google's crawler, on Google's network, opening the URL your ad uses.
There are 2 active AdsBot crawlers:AdsBot-Google for desktop and AdsBot-Google-Mobile, which identifies as an Android phone. Google's crawler documentation says both ignore the global User-agent: * group in robots.txt and crawl from a different IP range than Google's common crawlers. So your own visit proves little:
| Error | What happened | Look first at |
|---|---|---|
| HTTP 4xx (403, 404) | The server refused or couldn't find the page | A typo or deleted page (404), a firewall rule (403) |
| HTTP 5xx | The server returned an error | Hosting, a crashing plugin |
| DNS error | Your domain didn't resolve to an IP address | DNS records, an expired domain |
| Redirect too long, empty, bad or looping | A redirect was broken or circular | Redirect rules and plugins |
| Timeout or malformed response | The server was too slow or sent broken data | Server resources, crashing code |
| Page requires authentication | A login or password blocked access | Staging passwords, private stores |
Google's destination requirements treat close cousins separately: Destination not crawlable (AdsBot blocked, for example by robots.txt), Destination not accessible (unreachable in your target location) and Destination mismatch. A hacked site is different again; see our guide to the Google Ads compromised site error.
Then ask what changed in the days before: a new host, a DNS edit, a security plugin or a redesign.
Send your website and we will record a free 2 minute video on where your ad traffic leaks, with the 3 fixes we would make first.
Google publishes the steps to mimic AdsBot in Chrome DevTools:
AdsBot-Google (+http://www.google.com/adsbot.html).A 403 page, a "checking your browser" screen, a blank page or an odd redirect is your problem.
In Terminal on a Mac or Command Prompt on Windows, this shows every redirect and its status code:
curl -IL -A "AdsBot-Google (+http://www.google.com/adsbot.html)" https://www.yoursite.com/landing-page
200 is good. A 301 then a 200 works, but point the ad at the final address. A 403, 404, 5xx or endless redirects means trouble. Some servers answer this header-only request differently from a full page load, so treat an odd result as a lead.
Both tests send AdsBot's name from your own IP address, and Google warns that user agent strings can be spoofed. Wordfence, for example, says its firewall can block fake Googlebots. So your test can fail while the real AdsBot gets in, or pass while an IP rule blocks it. The next 2 checks settle it.
If your site is verified in Search Console, inspect the page with the URL Inspection tool, click Test live URL, then View tested page. You get the HTTP headers, a screenshot and fetch errors such as "Invalid server SSL certificate". It uses Google's inspection crawler, not AdsBot, so a pass makes DNS, certificate and server problems unlikely but can't clear rules aimed at AdsBot.
Ask your host or developer to search the access logs and any firewall or CDN log for AdsBot-Google around the disapproval date. Genuine requests come from hostnames that start with rate-limited-proxy and end in google.com. If AdsBot shows as blocked, or never reaches your server, something in front of your site stopped it.
Google lists 3 causes of a DNS error: domain settings that don't lead to your server, a domain that isn't registered or has expired, and a firewall that stops Google Ads connecting. Type your domain into Google Public DNS and click Resolve, with and without www. No IP address means a DNS record to fix. If it started after a move, see our guide to a website down after a domain transfer.
Google says server security settings, firewalls or CMS plugins might be blocking AdsBot, and asks you to have your developer allowlist AdsBot-Google and AdsBot-Google-Mobile. Check:
Typical culprits: http to https and www rules that bounce visitors back and forth, an old redirect plugin rule, or a final URL for a page you moved in a redesign. Run the curl test and set the final URL to the address the chain ends on.
A login or password triggers "Page requires authentication", and Google also counts placeholder pages such as "Site Under Construction" as not working. Look for a staging password left on after launch, a coming soon plugin or a Shopify store still in private mode. Google says malformed responses can come from crashing code or a server low on memory. Those and timeouts can be intermittent, so ask your host for error logs from the disapproval date.
AdsBot Mobile Web identifies as an Android phone, so anything your site does differently for phones gets tested too. A plugin that sends phones to a separate mobile site, or an outdated mobile final URL, can fail on mobile only.
If the page passes, look at the URL itself.
{lpurl}, or "your landing page URL will break". Check every level, down to the keyword, and select Test where Google offers it.Edit the ad if you changed its final URL or tracking: in Campaigns, then Ads, hover over the ad, select Edit, make the change and Save. It is reviewed again automatically, and Google says most ads are reviewed within 1 business day.
Appeal if you fixed and retested the website and the URL stayed the same, or if nothing was wrong:
Google's appeal rules:
DNS, firewall and redirect causes of a Google Ads destination not working error tend to arrive with a change to your site or setup. Build a routine around them:
If AdsBot is blocked somewhere you can't reach, or the error keeps coming back, bring in your developer or host. Checking landing pages and clearing disapprovals is also part of our Google Ads management work.
Open Policy manager and write down the exact error and URL. Test the page as AdsBot, then check DNS, your firewall and your redirects. Fix the cause, then edit the ad or appeal. Once ads run again, make sure clicks turn into calls; our guide to Google Ads clicks but no calls picks up from there.
Want a second pair of eyes on the page your ads send people to? We'll record a free 2 minute video audit of your site showing the 3 fixes we'd make first.
Because Google tests with its own crawler, AdsBot, not your browser. A firewall, security plugin, bot protection setting or country block can let you in and still block AdsBot. Your ad's expanded URL, with its tracking template, can also differ from the address you tested. Test the page with an AdsBot user agent and check your logs.
Google says most ads are reviewed within 1 business day, and editing an ad sends it back for review automatically. For appeals, check back in 24 hours. If an ad stays under review for more than 2 full business days, check its status, and contact Google Ads support after a week.
Not right away. Google says these destination violations don't lead to immediate suspension and that it warns at least 7 days before suspending an account. Meanwhile, a disapproved ad doesn't run until it is fixed and reviewed again. If you can't fix the page quickly, point the ad at a working page or remove it.
A robots.txt rule that blocks AdsBot leads to a separate disapproval, Destination not crawlable. AdsBot ignores the general User-agent: * group, so only rules that name AdsBot-Google or AdsBot-Google-Mobile block it. If you see Destination not working, look for an error response, a DNS failure, a redirect problem or a firewall block.
The 3 fixes we'd make first on your site, within 1 business day.