Google Ads 'Destination not working': Check Your Landing Pages

You open your account and an ad is marked Disapproved. The reason says Google Ads destination not working, and your landing page loads fine every time you click it. Meanwhile the ad is not serving, so the calls and form fills that used to come from it are slowing down. The good news is that this disapproval has a short list of causes, and most of them can be checked in about ten minutes from your own phone and laptop. The check below starts at the disapproved ad, follows the final URL, and ends with the fix and the appeal. If you have not seen a disapproval yet, run the same check anyway after your next website change, because a page can start failing without any sign on your end.

Start with the disapproved ad and its final URL

Everything else depends on knowing which ad, which URL and which reason. In Google Ads, open Campaigns, select Ads, and hover over Disapproved in the Status column. Select Read the policy to see the reason Google gave. If you want the reason visible for every ad at once, add the Policy details column through Columns, then Attributes, then Policy details.

Now copy two addresses for each affected ad: the final URL and the expanded URL. The final URL is the page you chose. The expanded URL is what Google actually requests after a tracking template and any parameters are added, and Google says it can differ from the final URL. A broken tracking template can fail a page that works perfectly when you type the address yourself. So, write down both before you touch anything.

If several ads share one landing page, one broken page can disapprove all of them. Make a short list of the distinct URLs, because you only need to fix and test each one once.

Open the page on a phone and a laptop in a private window

Google tells advertisers to test destinations on common browsers and devices, so test the way a visitor arrives. Use a private window so your saved logins, cookies and cached pages do not hide a problem. Do it once on your phone and once on a laptop, and if you can, once from a different network such as mobile data instead of your office Wi-Fi.

Watch for these things as the page loads:

• An error page, a blank page or a message such as "Page not found" or "Service unavailable"
• A login, password or "members only" screen standing between the click and the landing page
• A redirect that ends somewhere other than the page you meant, or one that keeps bouncing between addresses
• A "coming soon" or "under construction" page left over from a site change
• A page that works with www in front of the domain but not without it, or the other way around

Test both versions of the address, with and without www, if your site answers on both. Then open the expanded URL, with the tracking parts included, and see whether it behaves the same as the clean final URL.

If everything loads for you, do not stop there. The next sections cover why Google can still see a failure, and the order to work through it.

Google names these failures as a broken destination

Search Engine Land reported on October 1, 2026 that Google clarified its Destination not working policy with more examples. The wording that matters comes from Google's own Destination not working policy, which covers "Destinations that don't function properly or have been set up incorrectly." The examples include "You've reached this page in error," "Whoops! Nothing to see here!" and "Site Under Construction," along with HTTP 403, 404 and 500 responses returned to Google's AdsBot on common devices around the world. You can read the Search Engine Land report for the news, but the policy page is the rule.

Google's expanded troubleshooting table goes further. Use it as your checklist, and note who normally fixes each problem.

Read the table from the top. The first two rows are the cheapest to rule out, so check a typo or a deleted page before you open a ticket with your host. This is an order of effort. It is not a ranking of what happens most often.

A page that loads for you can still fail for Google's crawler

Google checks ad destinations with AdsBot, a crawler Google documents as a special-case crawler used for Google Ads. Its user agent token is AdsBot-Google. Because AdsBot is a robot arriving from Google's servers, a page can behave differently for it than for you:

• A firewall, CDN or security plugin can refuse the request and return a 403, even though real visitors get through.
• A rule that blocks traffic from certain countries can reject the check.
• A login or cookie requirement can send the crawler to a gate you never see in your own logged-in browser.
• Google's crawler documentation says special-case crawlers may not follow the same robots.txt rules as Google's common crawlers, so a rule written for Googlebot is not the whole story.

If the page loads normally for you and the disapproval stays, ask your host or developer to look at the server and firewall logs for requests from AdsBot and see what response each one got. Google also documents how to verify requests that claim to be from Google, so a developer can confirm that a logged request really came from Google before changing a security rule. Google recommends testing with Chrome DevTools using the AdsBot user agent, which a developer can do in a couple of minutes.

A slow page is a separate matter. Google's list covers timeouts, which means the server fails to answer, and a low speed score is not on the list. Fix a timeout, and do not chase a score.

Fix the cause at the right layer, then appeal

Change the thing that is actually broken, in this order:

1. A typo or deleted page: correct the final URL in the ad, or restore the page.
2. A 404 after a site restructure: add a valid page or set up a careful redirect to the right one.
3. A 403 or a 5xx response: ask your host or developer to adjust the firewall, CDN or security rule, or repair the server or plugin failure.
4. A DNS error: renew the domain or correct the DNS records.
5. A redirect problem: remove the conflicting rules so each address ends on one working page.
6. A login screen: send the ad to a public page.
7. A tracking template problem: correct the template syntax and parameters.

If the page cannot be repaired quickly, you can edit the ad to use another landing page that works and save it. Google allows that as a fix.

Once the destination loads cleanly on every test above, appeal. In Google Ads, open Tools, then Troubleshooting, then Policy manager, and select the Policy issues tab. Choose Appeal. Pick Made changes to comply with policy if you fixed something, or Dispute decision if you believe nothing was wrong, then submit. Google asks you to wait at least 24 hours between appeals for the same ads, and each ad is limited to three unsuccessful appeals before you have to contact support. That limit is why you fix first and appeal second. Google's Google Ads Help page has the same steps if your menus look different.

Changing the ad headline will not repair a landing page that returns an error. If you used up an appeal without changing the page, the test above has not been done yet.

Check every ad's page after any website change

After a redesign, a hosting move, a domain or DNS change, a plugin update or a new security tool, test each ad's page again:

• Open every final URL and expanded URL on a phone and a laptop in a private window.
• Confirm each one ends on the intended page with no login, error or loop.
• Test from a second network.
• Recheck after any caching, CDN or bot-protection change.
• Look at your tracking templates and keyword URLs, since a changed address structure can break them even when the pages exist.

This is routine upkeep, the sort of recurring check that website maintenance covers: uptime, redirects, plugin updates and broken links. If a different final URL error is what you are seeing in your asset groups, our post on the Google Ads invalid final URL error covers that one separately. If the account itself is suspended, start with what to do first when a Google Ads account is suspended. Google also treats a destination that does not match the ad as a different policy from a destination that does not work, so read the exact label in Policy manager before you pick a fix.

Some fixes cost nothing, and some need a specialist

A typo in the final URL, a domain that lapsed or one redirect that points to a deleted page is something you or your host can often repair at no cost beyond a few minutes. Try those first. Nobody needs a campaign-management contract to fix a typo.

Paid help starts to make sense in other situations:

• The page loads for people but returns a different response to AdsBot.
• The problem comes and goes, or shows up only in certain locations.
• Several campaigns use different tracking paths and more than one is failing.
• A migration, firewall, CDN or security plugin is involved and the cause is unclear after the basic tests.
• You have used appeals and the ad is still disapproved.

In those cases, the useful work is diagnosis first: which layer is failing, the ad, the URL, the server, the DNS, the firewall, the tracking template or Google's review. Then the smallest repair that fixes it, followed by a properly documented appeal. Nobody can promise that Google approves an ad, so be wary of anyone who does.

Frequently Asked Questions About google ads destination not working

What does "Destination not working" mean in Google Ads?

Google could not reach or properly load the landing page tied to your ad. Its policy covers destinations that do not function properly or were set up incorrectly, such as 403, 404 and 500 errors, DNS problems, redirect loops and login screens.

Why does my page work for me but Google says the destination is not working?

Google checks the page with its AdsBot crawler across common devices and locations. A firewall, location rule, redirect or login gate can block AdsBot while letting you through.

What should I check first?

Check the final URL and the expanded URL. Open both on a phone and a laptop in a private window, and look for errors, redirects and login screens.

How do I appeal the disapproval?

Fix the page first. Then open Tools, Troubleshooting, Policy manager, select the Policy issues tab, choose Appeal, and pick Made changes to comply with policy or Dispute decision.

How many times can I appeal?

Wait at least 24 hours between appeals for the same ads. Each ad is limited to three unsuccessful appeals before you need to contact support.

Can I just send the ad to a different page?

Yes. If the page cannot be fixed quickly, edit the ad to use another landing page that complies with the policy, and save it.

Wrapping Up

A Destination not working disapproval comes down to one question: what does Google's crawler get when it asks for your final URL? Start at the Disapproved status, copy the final and expanded URLs, test them on a phone and a laptop in a private window, and match what you see to Google's list of failures. Fix the layer that is broken, then appeal once with Made changes to comply with policy.

With the fix made, build a small habit around it. Every time the website changes, whether a redesign, a hosting move or a plugin update, test each ad's page again before the ad runs into a disapproval. A short test right after the change is the cheapest moment to catch a broken page.

If the page loads for you and the ad stays disapproved, Web Leveling can trace it with you, from the ad's URL settings to the firewall and the server response. Our Google Ads management work includes finding the failing layer and documenting the appeal, and you can contact us about a Google Ads disapproval to get started. We work with small and medium businesses across the country and overseas.

Terms