Why does Google say my ad destination is not working?
Direct answer“Destination not working” means Google’s crawler could not open the page. Typical causes are a 403, 404, or 500, a site under construction, a DNS or redirect failure, or a login wall. “Destination experience” means the page loads and then gets in the way: a pop-up, a broken Back button, or a file download. If the page loads and the offer is simply wrong, that is a different disapproval.
Three labels that get mixed up
| What you see | Google’s label |
|---|---|
| 404, under construction, login wall, redirect loop, DNS failure | Destination not working |
| Pop-up, Back-button trap, auto-download, fake warning on the page | Destination experience |
| The page loads and the price or product does not match the ad | Landing-page mismatch |
A hacked page that injects a skimmer is a compromised site. A fake dialog drawn inside the ad, rather than on the page, is misleading ad design.
When the crawler cannot open the URL
Google’s Destination not working page, reviewed on September 27, 2026, disapproves destinations that do not function, including “you’ve reached this page in error,” “nothing to see here,” and “site under construction.” It also disapproves HTTP errors AdsBot receives on common devices, including 403, 404, and 500. The display URL is what people see. The final URL is where the click goes. The expanded URL adds tracking templates. Google says the expanded URL in the interface can differ from the destination you think you set.
Other causes on that page include a DNS failure, an unregistered or expired domain, a firewall, a redirect that is too long, empty, or invalid, a private IP, a malformed HTTP response, a timeout, a redirect loop, and a login or password wall. App engagement ads cannot use a third-party tracker. App promotion trackers have to land in the correct store, and the app can be promoted only where it is available to download. A warning comes at least 7 days before suspension. After the fix, appeal, or change the final URL. Google’s page explains how to spoof AdsBot in Chrome DevTools. Use those steps. Do not guess a user-agent string.
When the page loads and then blocks the visit
Google’s Destination experience policy disapproves pages that are unnecessarily hard to use. Named cases include pop-ups and interstitials that hide the content, a Back button that does not work, pages that load slowly or require an extra app, and links that download a file or open an email address. Timed pop-ups, pop-unders, and pop-ups that come from the ad itself are examples. An interstitial that the visitor can leave is allowed. A PDF landing page is allowed for pharmaceutical advertisers.
Abusive experiences on that page include an automatic redirect, ads that look like system warnings, fake chat or notification chrome, invisible click targets, close buttons that open another ad, and a moving mouse pointer meant to trick a click. Better Ads examples include a countdown the visitor must wait through, large sticky ads, and flashing animated ads. Google points owners to the Abusive Experience Report in Search Console for that review. This policy also warns at least 7 days before suspension.
Setup workflow
- Read the policy name. Destination not working, destination experience, and a mismatched offer are three labels.
- For a crawler error, open the disapproval detail, then check the final URL and the expanded URL with tracking. Fix typos, DNS, redirect loops, login walls, and HTTP 403, 404, or 500 responses that AdsBot receives.
- App engagement ads cannot use a third-party tracker. App ads can only run where the app is available to download.
- For destination experience, remove pop-ups that cover the page, Back-button traps, forced downloads, and fake system warnings on the page. A PDF is allowed for pharmaceutical advertisers.
- Appeal after the fix. If you cannot repair the URL, point the ad at a page that returns HTTP 200. Both policies warn at least 7 days before suspension.
Frequently asked questions
The page loads in my browser. Why is it disapproved?
Google checks the destination with AdsBot, including the expanded URL after tracking templates. A firewall, an expired domain, a login wall, or a 403 that only the crawler sees will still fail. Your own Chrome session is not the test.
Is a pop-up the same label as a 404?
No. A 404, a 500, or an under-construction page is Destination not working. A page that loads and then blocks the content with a pop-up, traps the Back button, or starts a download is Destination experience. Both warn at least 7 days before suspension.
Sources
This reading is as of September 27, 2026.
See the URL the crawler actually opens
LaunchGuarding checks the destination behind the ad, including a tracker hop that never reaches the product.