Google Ads Destination Not Working: Why It Happens and How to Fix It

Last checked 3 October 2026 against Google's documentation. By Muhammed Abdul Kalam. Blocks some ads

Quick fix

Google Ads destination not working means Google AdsBot couldn't load your landing page: it got an HTTP error, a DNS failure, a redirect problem or a login screen. Read the reason in the Status column, fix the URL or server problem, then file an appeal so the ad and page are reviewed again.

Hover over the disapproval reason in the Status column to see which error Google got.
Check the final URL, keyword URLs and tracking URLs for typos.
Test the page with Chrome DevTools set to the Google AdsBot user agent.
Make sure the page has no login screen or password in front of it.

Can't fix it yourself? Send me the details

What this error means

Google's crawler, AdsBot, visits your landing page before your ad can run. If AdsBot gets an error instead of the page, or the page is set up incorrectly, the ad is disapproved for Destination not working.

Google requires your ad content and destinations to work on common browsers and devices.

What Google shows

HTTP 4xx response

Why it happens

1The URL is wrong or the page returns an HTTP error

A mistyped or wrong URL returns a "Page not found (404)" error to AdsBot. Server errors such as 403 or 500 have the same effect, even if the page loads for you.

How to tell if this is you: The disapproval reason says HTTP 4xx or 5xx response, or the URL in the ad has a typo.

2The domain doesn't resolve

Google couldn't match your server's hostname to an IP address. That happens when the domain's settings point to the wrong IP, the domain isn't registered or has expired, or a firewall blocks Google Ads.

How to tell if this is you: The disapproval reason says DNS error, or your domain renewal has lapsed.

3Your redirects are broken

The server sent AdsBot through too many redirects (a loop), an empty or bad redirect, or a redirect URL that is too long. Content management systems can build overlong redirect URLs.

How to tell if this is you: The disapproval reason mentions a redirect, or the URL changes several times as it loads.

4The page is behind a login, firewall or router

If the page needs a login or password, or the site is hosted behind a firewall or router, Google Ads can't reach the content.

How to tell if this is you: The page asks for a login, or it only opens from your office network.

5The server is slow or crashing

If the server takes too long to send the page, Google stops waiting. Crashed application code or a server short of memory can also send a broken response.

How to tell if this is you: The disapproval reason says Timeout reading page or Malformed HTTP response.

6The page isn't finished

Pages that don't function properly or are set up incorrectly are disapproved, including placeholder pages such as "Site Under Construction".

How to tell if this is you: The landing page shows a placeholder or error message instead of your content.

How to fix it

Find the exact error

Open your ads.Campaigns then Ads
In the Status column, hover over the disapproval reason to read the error Google got.
Test the URL as AdsBot sees it: use Chrome DevTools with the user agent set to Google AdsBot.
Remember the expanded URL combines your final URL with any tracking template and parameters, so test that too.

Fix the URL or the page

For: The URL is wrong or the page returns an HTTP error, The page isn't finished

Check landing page URLs, keyword URLs, tracking URLs and deep-link URLs for typos.
Make sure the page returns an HTTP 200 response globally, not an error.
If you can't fix the page, edit the ad to send people to a different, working landing page.

Fix the server, domain or redirects

For: The domain doesn't resolve, Your redirects are broken, The page is behind a login, firewall or router, The server is slow or crashing

Check the domain is registered, not expired, and points to the right IP address, and that no firewall blocks Google Ads.
Remove redirect loops and broken or overlong redirects.
Take the landing page out from behind any login or password.
If you can't fix the server yourself, work with your web developer so the site doesn't return an error when crawled.

Get the ad reviewed again

After fixing the destination, file an appeal so Google reviews the ad and landing page.
If you pointed the ad at a different page instead, select Edit on the ad, save it, and it is reviewed again automatically.

How to appeal or request a review

Appeal once you've fixed the problem, or if you believe the review got it wrong.

Open Policy manager.Tools then Troubleshooting then Policy manager
On the Policy issues tab, select Appeal on the affected ad.
Under Reason for appealing, choose Dispute decision or Made changes to comply with policy, then submit.

What to include

Pick the reason that matches what happened: you're disputing the decision, or you've made changes to comply.

What not to do

Don't keep resubmitting an appeal that failed or was marked as a duplicate. Make a small edit to the ad text or final URL and save it instead, which makes Google crawl the page again.
Don't appeal the same ads again within 24 hours. Appeals inside that window are marked as duplicates.
Don't waste attempts. After 3 unsuccessful appeals on one ad, you can't appeal it again until you contact Google Ads support.

Open Google's review page

How long it takes

Google reviews most ads within one business day, though some take longer. If an ad is still under review after more than 2 full business days, check its status; after more than a week, contact Google Ads support.

How to stop it happening again

Keep your domain registered and renewed so it never expires.
Before ads go live, check every final URL returns an HTTP 200 response.
Don't put landing pages behind a login or password.
Fix disapprovals promptly. This policy doesn't suspend accounts without warning, but a warning comes at least 7 days before any suspension.

From my desk

Testing the exact final URL from another network and device, thinking about Google's crawler rather than the client's browser. Firewalls, geo-blocks, slow servers and bot protection can block Google while the page looks fine. I also check for a normal response and no redirect loops.

Muhammed Abdul Kalam

When to get help

The page loads for you but AdsBot keeps getting an error and you can't see why.
The problem is on your server, hosting or firewall and you don't have access to change it.
You've appealed after a fix and the ad is still disapproved.

Stuck on this? Send me the details.Tell me what the platform shows and what you've tried so far.

Send me the details

FAQs

Why does Google say my destination is not working when the page loads for me?

Google checks the page with its AdsBot crawler. If AdsBot gets an HTTP error, a DNS failure or a login screen, the ad is disapproved even if the page opens in your browser. Test it with Chrome DevTools set to the Google AdsBot user agent.

What does "HTTP 4xx response" mean in Google Ads?

The server hosting your site returned an HTTP error that stopped Google Ads reaching the content. A wrong or mistyped URL is one cause: it returns a "Page not found (404)" error.

Do I need to appeal after fixing a destination not working error?

Yes. After you fix the destination, Google says you need to file an appeal so the ad and landing page are reviewed. If you edit the ad to use a different landing page instead, it is reviewed again automatically.

Can destination not working suspend my Google Ads account?

Not without warning. Google says violations of this policy won't lead to immediate suspension, and a warning is issued at least 7 days before any suspension.

What is a DNS error in Google Ads?

It means Google couldn't match your server's hostname to an IP address. The domain may point to the wrong IP, may not be registered or may have expired, or a firewall may be blocking Google Ads.