Google Ads says “Destination not working” and then gives you a policy page that does little to explain what broke. If you just want to get your ad running again, that is frustrating. Here is what the warning actually means, how to find the bad link, and what to fix first.
Short answer: Google tried to open the page connected to your ad and ran into an error. Check the exact URL shown in the policy details, open it on a phone and computer, fix the page or point the ad to a working page, then save the change. If the warning stays, request a review.
What “Destination not working” means
Your ad sends people to a webpage. Google checks that destination before it lets the ad run. If the page cannot be reached or returns an error to Google's AdsBot crawler, the ad may be disapproved. A 404 means the page was not found; a 403 can mean access is blocked; a 500 can point to a server problem.
In the example above, the important clue is HTTP error: 404. That narrows the job down: find out why that exact page is missing. The warning may also say desktop or mobile, which tells you which version Google checked.
How to fix it: start with the exact URL
1. Find the affected ad or asset
In Google Ads, open Campaigns → Ads and look for the item marked Disapproved. Hover over its status or open Policy details. If the warning is tied to a sitelink or another asset, check Campaigns → Assets as well. You can also open Tools → Troubleshooting → Policy manager to see policy issues in one place.
Write down the error code and the URLs shown. The Final URL is the landing page set on the ad. The Expanded URL includes any tracking template or URL parameters. If those two addresses differ, test both: the landing page may work while the tracked version fails.
2. Open the link on a computer and phone
Copy the full URL from Google Ads and open it in a private browser window. Check it again on your phone. Does the right page appear? Can you see the content without logging in? Try the link with its tracking parameters too.
A page that looks fine in your browser can still return an error to Google. If you have a developer, ask them to check the HTTP response for the exact URL and Google AdsBot. A working page should return a normal success response rather than 403, 404, or 500.
3. Fix the page or replace the Final URL
If the page was deleted, restore it or send the ad to a relevant live page. If the address has a typo, correct it in the ad. If a page moved, use its final working address directly when possible.
For example, if https://example.com/old-service now returns a 404 but https://example.com/service works, update the ad's Final URL to the second address. Then save the ad. Do not send a collision-repair ad to an unrelated homepage just to clear a warning; the replacement page should still match the ad's offer.
4. Check other links in the campaign
Open your sitelinks and other URL-bearing assets. An older sitelink can still point to a deleted page even after the main ad has been fixed. Also check a mobile Final URL, keyword-level URL, or tracking template if your account uses one.
5. Let Google review the change
Saving an edited ad can trigger another review. If the policy issue remains after you have fixed the destination, open Tools → Troubleshooting → Policy manager, choose Appeal for the affected ad, select Made changes to comply with policy, and submit. If you believe Google's decision was wrong, the appeal screen also offers Dispute decision.
The page works for you. Why is Google still seeing an error?
This is the point where you need to check what Google receives, not only what you see. Send your developer the exact Final URL, Expanded URL, device shown in the warning, error code, and time of the disapproval. Ask them to check:
- Redirects: Does the link send Google through a loop, an invalid address, or a chain that ends on an error?
- Firewall and bot rules: Is a security plugin, hosting firewall, or bot protection blocking Google AdsBot?
- Server and DNS: Was the site down, too slow, or unable to resolve when Google checked?
- HTTPS: Does the secure version of the page load without a certificate error?
- Login and location rules: Is the page asking for a password or blocking visitors in some regions?
Google documents separate policies for destinations that are not crawlable, not accessible, or mismatched. Read the exact policy label on your ad before changing settings: the right fix depends on the error you were actually given.
What the most common clues mean
| What you see | What to check first |
|---|---|
| 404 Not Found | Typo, deleted page, wrong path, or a redirect to a missing page. |
| 403 Forbidden | Firewall, bot protection, or access rules that block AdsBot. |
| 500 server error | Hosting, application errors, or server logs. |
| Redirect error | The final destination and each step of the redirect chain. |
| Works in browser, fails in Ads | Expanded URL, tracking template, AdsBot access, device, and region. |
Before you request another review
- The exact Final URL opens the intended page.
- The Expanded URL works with its tracking parameters.
- The page loads on desktop and mobile without a login.
- The page does not return a 403, 404, or 500 response to AdsBot.
- Any sitelinks and other linked assets point to live pages.
- The landing page matches the ad people clicked.
If the appeal fails after these checks, look at the result in Policy manager and send the error details to your developer or Google Ads support. Repeatedly filing the same appeal without fixing the cause is unlikely to help.
Frequently asked questions
Can a redirect cause this error?
Yes. A redirect that loops, points to an invalid address, or ends on a broken page can stop Google from reaching your destination. A normal working redirect is not automatically a violation, but using the final page URL directly often makes troubleshooting simpler.
Do I need to create a new ad?
Usually you can edit the URL on the existing ad or asset. If the website is what is failing, a new ad that points to the same broken page will not solve the problem.
How long does the review take?
Check the ad status or Appeal history in Policy manager for the current result. Review time can vary. Google advises waiting at least 24 hours between appeals for the same ads or campaigns.
Get the link working before you spend another dollar
Start with the error code and exact URL in the warning. Fix that destination, test the tracked version, then request a review if needed. Once the ad is approved, click through it yourself: a technically available page still needs to make it easy for a real customer to call, book, or request a quote.
Sources: Google Ads Destination not working policy and Google's guide to fixing or appealing disapproved ads.
