Home / Fixes / Destination not working
Google Ads landing page disapproval

Google Ads disapproved your ad for "Destination not working"

A "Destination not working" or mobile landing page error stops your ad from serving, often because the page fails on a device or in an in-app browser you never tested. The page can look fine to you and still trip the check.

Signs this is happening to you

  • Google Ads shows "Destination not working" or "Mobile landing page error"
  • The ad is disapproved but the URL loads fine on your computer
  • It happens intermittently or only on mobile
  • Merchant Center flags a crawl or destination error for the same URL

What's usually causing it

  • The page fails on mobile or in an in-app browserGoogle crawls on mobile. A script error, redirect loop, or slow load that only happens on a phone or in the Instagram browser reads as a broken destination.
  • A redirect or geo rule blocks the crawlerAggressive redirects, age gates, or region blocks can stop Google from reaching the final page.
  • Intermittent timeouts under loadA page that times out some of the time will fail the check even if it usually loads.
  • Broken or missing content on the landing pageA 404, an empty page, or a blocked resource makes the destination look non-functional.

How Mimetic finds it and ships the fix

Mimetic loads your landing page the way Google does, on mobile and in-app browsers, and finds the failure that is tripping the disapproval.

  • We load the flagged URL on mobile, desktop, and in-app browsers
  • We catch script errors, redirect loops, timeouts, and blocked resources
  • We pinpoint the device or condition where the page fails
  • We open the fix as a pull request so the destination passes review
Google crawls your page on mobile

A landing page that works on your desktop can still fail on the mobile or in-app environment Google checks, which is why these disapprovals feel invisible.

Questions

Why is my ad disapproved when the page loads fine for me?

Google checks the page on mobile and can hit a script error, redirect, or timeout that you do not see on desktop. Mimetic loads the page in those exact conditions and finds the failure.

Does this also fix Merchant Center destination errors?

Often the same underlying page failure causes both. Mimetic finds the broken render or redirect behind the destination error so you can resolve the Ads and Merchant flags together.

Could the in-app browser be the problem?

Yes. Pages frequently break in the Instagram or TikTok in-app browser specifically, and a large share of paid traffic lands there. Mimetic tests those environments directly.