Google Ads Destination Not Working: How to Fix It and Get Your Ads Approved

Short answer: “Destination not working” in Google Ads means your ad was disapproved because the landing page it points to cannot be reached or does not work properly when Google checks it. It is not a judgment on your product or your ad copy — it is a plumbing problem between the ad and the page. The page may be down, deleted, redirecting in a loop, blocked to Google’s crawler, or broken on mobile while it looks fine on your desktop. This guide covers how to find the exact fault, fix it in the right order, and get the ad approved again.

What “Destination not working” actually means

Google checks that every ad leads somewhere real. When you submit an ad, Google’s systems visit the final URL — the page the ad actually sends people to. If that visit fails, the ad is disapproved with a destination error. The ad itself can be perfectly written and fully policy-compliant; it still will not run until the destination works.

It helps to separate this from two nearby errors, because the fix is different for each. Destination mismatch means the page works, but it does not match what the ad promised — a different product, a different offer, a different domain. Destination experience means the page loads, but Google judges the experience itself as poor — hard to navigate, misleading, or difficult to use. Destination not working is simpler and more mechanical: the page cannot be reached or cannot be used at all.

The seven faults that cause it, in order of likelihood

Work through these in this order. Most cases are fixed by the first three.

1. The page is gone. The product was removed, the page slug changed after a redesign, or the URL in the ad has a typo. The result is a 404, or a redirect to a generic homepage that no longer contains the offer.
2. The site is down or erroring. A server error (a 500 error), a database failure, or a hosting outage means Google’s check gets nothing back. The site may come back a minute later, but the disapproval stands until the ad is re-checked.
3. A redirect loop or a long redirect chain. Page A sends visitors to page B, which sends them back to A — or a chain of five or six redirects where one link in the middle is broken. Browsers sometimes tolerate this; Google’s check does not.
4. The URL breaks after tracking is added. A tracking template or a hand-built UTM string can corrupt the final URL — a missing slash, a doubled question mark, an unencoded character. The base page works; the ad’s exact URL does not.
5. Google’s crawler is blocked. A robots.txt rule, a firewall rule, a password gate, or a country block can stop Google’s ad crawler (AdsBot-Google) even while normal visitors get through. If the crawler cannot see the page, the destination is treated as not working.
6. SSL or security failure. An expired certificate, a certificate for the wrong domain, or mixed secure/insecure content can stop the page loading cleanly, especially on the secure connection Google expects.
7. It works on desktop but not on mobile. Most ad clicks are mobile. A page that loads on your office computer but times out, breaks, or shows a blank screen on a phone will fail the check that matters.

The free Destination Requirement checklist turns all of this into tick-off items. If your problem turns out to be a mismatch rather than a broken page, the Destination Mismatch checklist covers that case, and the Destination Experience checklist covers page-quality problems. Everything else — checklists for every Google policy — is in the free tools hub.

Diagnose it in five minutes

First, open the exact final URL yourself — not the page you think the ad points to, but the URL shown in the ad’s settings, in a private browser window. If it does not load for you, that is the fault, and no policy appeal will fix it.

Second, check what the page returns. A 404 means the page is gone or the URL is wrong. A 500 error means the server is failing. A redirect that never lands means a loop. Note the exact result before changing anything — guessing wastes review cycles.

Third, test it on a phone, on a mobile connection rather than office Wi-Fi if you can. Mobile-only failures are common and easy to miss from a desk.

Fourth, check the tracking. Strip the tracking parameters off the URL and test the clean page, then test with them back on. If the clean page works and the tracked one does not, the fault is in the tracking template, not the website.

Fifth, check access. Look at robots.txt and any firewall or security plugin rules for blocks on Google’s crawlers, and confirm the page is not behind a login, a password, or a country block.

Fix order: restore, simplify, then re-check

First, restore a working page. Fix the typo, restore the deleted page, or point the ad at the correct live URL. If the product is genuinely gone, point the ad at a real replacement — never at a dead page or a generic homepage that does not contain the offer.

Second, fix the server and security faults. Resolve the 500 error with your host, renew or correct the SSL certificate, and remove any password gate from the landing page.

Third, simplify the journey. Cut the redirect chain down to one hop at most, fix the broken tracking template, and unblock Google’s crawler. Every extra hop is another place the check can fail.

Only then, request a review. In Google Ads, fix the ad and resubmit it, or request a review from the policy manager for the disapproved ad. Describe nothing fancy — the fix is the page working. Most ad reviews complete within one business day, but do not change the URL again while the review is running, or the reviewer will check a different destination from the one you fixed.

If the ad is rejected again after a genuine fix, re-run the five-minute diagnosis before appealing. A second rejection usually means the fault is still there in a form you have not tested — most often the mobile version, or the tracked URL rather than the clean one.

How to stop it happening again

Three habits prevent almost every recurrence. First, never change a page URL without updating every ad that points to it in the same session — a redesign that renames pages silently disapproves ads. Second, keep redirect chains short and tested: one hop, to a live page, with no surprises. Third, re-check destination URLs after any site change, hosting move, or SSL renewal, before Google finds the break for you. A destination that works today and breaks tomorrow costs you the days the ad sits disapproved while nobody notices.

And one distinction worth keeping: if your ad is disapproved for a policy reason rather than a broken page — a suspension, a misrepresentation flag, a trademark problem — the fix is a different process entirely. The companion guide on appealing a Google Ads account suspension covers that side, and the suspension guides for Merchant Center cover the shopping side.

Frequently asked questions

What does “Destination not working” mean in Google Ads?

It means Google disapproved your ad because the landing page it points to cannot be reached or does not work when Google checks it — the page may be deleted, down, redirecting in a loop, blocked to Google’s crawler, or broken on mobile. The ad will not run until the destination itself is fixed.

Why is my ad disapproved when my website works fine?

Because the ad’s exact final URL may differ from the page you tested. Check the URL in the ad’s settings, including any tracking template, in a private window and on a phone. Common hidden faults are a typo in the ad URL, a broken tracking string, a redirect loop, or a block on Google’s crawler that does not affect normal visitors.

How do I fix a Destination not working disapproval?

Diagnose first: open the exact final URL, note whether it returns a 404, a server error, or a redirect loop, test it on mobile, and test it with and without tracking parameters. Then fix the fault in order — restore or correct the page, fix server and SSL problems, shorten redirect chains, unblock Google’s crawler — and only then resubmit the ad or request a review.

How long does a Destination not working review take?

Most ad reviews complete within one business day. Do not change the URL again while the review is running, or the reviewer may check a different destination from the one you fixed. If it is rejected again, re-diagnose before appealing — the fault is usually still present on mobile or on the tracked URL.

Is Destination not working the same as Destination mismatch?

No. Destination not working means the page cannot be reached or used at all. Destination mismatch means the page works but does not match what the ad promised — a different product, offer, or domain. The two errors need different fixes, so confirm which one your ad actually shows before changing anything.