Google Ads links not working?
Use this guide when a Google Ads click opens a broken page, lands on the wrong page, or Google Ads shows a "Destination not working" or "Destination mismatch" status.
Start with the exact Google Ads URL
A click may use an ad Final URL, a keyword Final URL override, a sitelink Final URL, a Final mobile URL (Mobile Final URL), or a landing URL Google Ads reports for that click. If you test a guessed URL, you can miss the broken destination.
Use this page as a Google Ads link checker: choose the URL field that belongs to the affected click, compare what should open with what actually opens, then choose the fix from that result.
For the full map of URL fields and URL options, including tracking templates and Final URL suffixes, read how Google Ads click URLs work.
Account
Campaign
Ad group
Ad
- Final URL
- Mobile Final URL
Search keyword
- Final URL
- Mobile Final URL
Sitelink asset
- Final URL
- Mobile Final URL
1. Pick the URL field that belongs to the click
Open the affected ad, keyword, sitelink, or asset in Google Ads. If Google Ads shows "Destination not working" or "Destination mismatch", open the Status column or Policy details for the same item.
Use the URL field that matches the affected click:
- Search click with a matched keyword that has its own Final URL: use that keyword Final URL.
- Search click with no keyword Final URL: use the ad Final URL.
- Non-keyword ad or headline click: use the ad Final URL.
- Sitelink click: use the sitelink asset Final URL.
- Mobile problem: use the Final mobile URL for the same ad, keyword, or sitelink asset if one exists.
- Landing URL or Expanded URL shown in Status or Policy details: test that reported URL first, because it may already include URL options or redirects.
Do not use the Display URL, a preview URL, or a guessed website URL. The Display URL is what the ad shows; it is not always the landing URL the browser opens after a click.
2. Decide what should open
Before you open the URL, name the expected destination. A Google Ads landing page checker can only tell you if the link is right when you know what right means for this click.
Use the ad or sitelink copy, offer brief, landing page plan, client instruction, or a known-good campaign to set these expectations:
- expected domain
- expected page, product, offer, or funnel step
- expected country or language, if that matters for this campaign
Use the Google Ads status or policy reason as context for the test, not as the expected destination.
3. Open the URL and compare
Paste the URL you selected in step 1 into a clean or private desktop browser window. Do not search for it in Google, and do not edit the URL before opening it.
If you have both a reported Expanded URL and a configured Final URL, test them one at a time. Treat each one as a separate test, because the reported Expanded URL may already include URL options or redirects.
After loading stops, compare three things:
- the Google Ads URL field you tested
- the final URL in the browser address bar
- the visible page: expected page, wrong page, error page, blank page, loading screen, login wall, or access block
Choose the result that matches the desktop test:
- The URL does not open or the page is unusable.
- The URL opens the wrong domain, product, offer, country, or language.
- The URL opens the right page, but Google Ads still rejects it.
- The URL opens the right page and Google Ads has no destination warning.
If the right page opens and Google Ads has no destination warning for that item, stop this destination check. Test a different affected item, or use the tracking guide if the only problem is missing click data.
If the right page loads but UTM or GCLID data is missing, this is a tracking problem, not a broken destination. Use the Google Ads tracking parameters guide.
If someone else needs to fix the issue, include only the useful handoff details: screenshot, device, exact Google Ads status, HTTP or DNS error, and redirect chain if you have them.
4. Check mobile only when it can change the answer
Run a mobile test when the affected item has a Final mobile URL, the complaint is mobile-only, desktop works but Google Ads still shows a destination issue, or the destination could vary by device.
Open the Final mobile URL if one exists. Otherwise open the same URL you tested on desktop. Compare the final mobile URL and visible page against the same expected destination.
5. Choose the fix from what happened
The Google Ads URL field is wrong before you open it:
Update the affected ad, keyword, sitelink asset, or Final mobile URL. A keyword Final URL can override the ad Final URL for that Search click, so fix the most specific field that caused the wrong landing page.
The URL does not load, or Google Ads shows "Destination not working":
Send the tested Google Ads URL, final browser URL if one loaded, visible error, device, screenshot, and any HTTP or redirect details to the website, server, DNS/CDN, firewall, or redirect owner. Ask them to check HTTP 4xx/5xx responses, DNS errors, redirect loops, bad or empty redirect URLs, private IPs, malformed responses, timeouts, and login walls.
The Google Ads URL is right, but the browser lands on the wrong domain, page, offer, country, or language:
Fix the redirect, tracking template, site rule, or page content that sends people away from the expected destination. If the URL is right but the page content no longer matches the ad, update the page or update the ad text to match the page.
Desktop works but mobile fails:
Fix the part that only failed on mobile: the Final mobile URL, the mobile redirect, the mobile page, or a mobile access rule.
Google Ads shows "Destination mismatch":
Compare the Display URL domain, the Final URL or Final mobile URL domain, and the domain where the browser finally lands. If they do not match, fix the URL or redirect that changes the domain. Also check whether a redirect, tracking template, or Expanded URL sends people to different content than the Final URL.
Google Ads shows "Destination not crawlable" or "Destination not accessible":
Ask a developer or CDN/security owner to check whether AdsBot-Google or AdsBot-Google-Mobile is blocked by robots.txt, firewall rules, bot protection, server-side access rules, geo rules, or targeted-location access limits.
6. Recheck the failed path
Fix only the part that matched step 5. Then test the same Google Ads URL, device, and status path that failed before.
- If you changed an ad, keyword, sitelink asset, or Final mobile URL, wait for automatic review and watch the status.
- If you fixed the page, redirect, DNS/CDN, firewall, or tracking template, request review or file an appeal if the Google Ads status does not clear.
- If the right page loads but UTM, GCLID, or other tracking parameters are missing, use the Google Ads tracking parameters guide instead of this checklist.
Too many places to check when a link breaks?
Kanat checks the paths for you and points out bad destinations. Leave your email for early access.
No Google Ads access needed yet.