Skip to content

Google Ads destination not working: how to find and fix the cause

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.

5 minute check: in Google Ads, open Tools, then Troubleshooting, then Policy manager. Count the ads that show Destination not working and hover over one to read the details. That count is how much of your advertising is switched off right now.

Why Google Ads says destination not working when your site loads

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:

  • You are not AdsBot. Firewalls and security plugins judge visitors by user agent and IP address. You pass; a crawler may not.
  • You are not where AdsBot is. Google says AdsBot often crawls from the United States and wants a page that returns a 200 response globally.
  • You may be testing a different URL. Your ad's expanded URL "combines the Final URL with any applicable tracking templates and parameters".

What each Google Ads destination not working error means

ErrorWhat happenedLook first at
HTTP 4xx (403, 404)The server refused or couldn't find the pageA typo or deleted page (404), a firewall rule (403)
HTTP 5xxThe server returned an errorHosting, a crashing plugin
DNS errorYour domain didn't resolve to an IP addressDNS records, an expired domain
Redirect too long, empty, bad or loopingA redirect was broken or circularRedirect rules and plugins
Timeout or malformed responseThe server was too slow or sent broken dataServer resources, crashing code
Page requires authenticationA login or password blocked accessStaging 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.

Step 1: Find the exact error and the URL Google tested

  1. Open Tools, then Troubleshooting, then Policy manager, and look at the Policy issues tab. Or go to Campaigns, then Ads.
  2. In the Status column, hover over the Disapproved status for more information. Write down the error type.
  3. Copy the final URL. Note any tracking template, final URL suffix or mobile final URL on the ad, ad group, campaign or account.
  4. Count the affected ads. If every ad is hit, think site-wide: DNS, firewall, hosting. If only 1 or 2 are, think page-level: a typo, a deleted page, a bad redirect.
  5. For Performance Max, confirm the campaign has at least one asset group. Google says a missing one can cause an invalid final URL error during setup, even when the page works.

Then ask what changed in the days before: a new host, a DNS edit, a security plugin or a redesign.

Paying for clicks that do not turn into calls?

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.

Get my free video audit

Step 2: Test your landing page as Google AdsBot

In Chrome

Google publishes the steps to mimic AdsBot in Chrome DevTools:

  1. Click the 3-dot icon at the top right of Chrome, then More tools, then Developer tools.
  2. Click Network conditions and select Disable cache.
  3. Under User agent, uncheck Use browser default and paste AdsBot-Google (+http://www.google.com/adsbot.html).
  4. Load your landing page and check it looks exactly like it normally does.
  5. Repeat with the AdsBot Mobile Web string from Google's crawler documentation.

A 403 page, a "checking your browser" screen, a blank page or an odd redirect is your problem.

From the command line

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.

With Search Console

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.

In your logs

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.

Step 3: Check the website causes one by one

DNS records and your domain

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.

Firewalls, security plugins and country blocks

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:

  • WordPress security plugins such as Wordfence, which can rate limit crawlers. Check what they blocked recently.
  • Bot protection or challenge settings at your CDN, and any firewall your host runs.
  • Country blocks. AdsBot often crawls from the US, not always, and Wordfence's changelog includes an improvement to let non-US Google crawler IP addresses pass country blocking.

Redirects and redirect loops

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.

Passwords, placeholders and slow hosting

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.

Mobile-only errors

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.

Step 4: Check tracking templates and typos

If the page passes, look at the URL itself.

  • Missing final URL. Google says tracking templates at the account, campaign or ad group level must include a ValueTrack parameter that inserts your final URL, such as {lpurl}, or "your landing page URL will break". Check every level, down to the keyword, and select Test where Google offers it.
  • Suffixes and click trackers. Load the full URL with its parameters to see whether your server or firewall objects. If clicks pass through another company's tracking domain, that domain must work for AdsBot too.
  • Typos and moved pages. Google names a URL that "was incorrect or contained a typo" as the common cause of a 4xx response.
  • AI Max. Google warns that tracking templates "can sometimes lead to broken expanded landing pages with a 404 error" if they aren't set up compatibly.

Step 5: How to fix destination not working and get the ad reviewed

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:

  1. Go to Tools, then Troubleshooting, then Policy manager.
  2. On the Policy issues tab, select Appeal on the affected ad.
  3. Under Reason for appealing, choose Made changes to comply with policy or Dispute decision, then Submit.
  4. Check back in 24 hours. The status shows In progress meanwhile.

Google's appeal rules:

  • Each ad can be appealed up to 3 times; after that, contact Google Ads support.
  • Wait at least 24 hours between appeals for the same ads.
  • If an appeal fails, make a minor edit to the ad text or final URL and save it. Google says this forces a new crawl.
  • From July 21, 2026, decisions made more than 6 months earlier can't be appealed in your account.

Stop it from happening again

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:

  • Allowlist both AdsBot crawlers in your firewall, CDN and security plugin by Google's published IP ranges or reverse DNS, not the user agent alone, since anyone can claim to be AdsBot.
  • Put an uptime monitor on every landing page your ads use, not just the homepage.
  • Run Google's Link Checker script. It checks the final URLs of your ads, keywords and sitelinks for errors and can email you, but it ignores tracking templates.
  • Before a hosting move, DNS change, redesign or new security plugin, list your final URLs and retest them as AdsBot the same day.

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.

What to do next

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.

Common questions

Why does Google Ads say destination not working when my site works?

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.

How long does Google take to review an ad after I fix it?

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.

Can Destination not working get my Google Ads account suspended?

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.

Does robots.txt cause Destination not working?

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.

Get your free video audit

The 3 fixes we'd make first on your site, within 1 business day.

Send my website
Free video auditWhatsApp