Click & destination
Destination URL not declared
What Google's rule says
Google's stated rule is that the ad's declared click-through URL does not match the actual landing page URL. Declaring the click-through URL is a standing requirement for third-party-served ads, so this reason is about a declaration that exists and is wrong, rather than one that is absent.
What actually causes it
- A click tracker inserted between the ad and the destination, so the declared URL is the tracker's.
- An affiliate or shortener redirect that hides the real landing page.
- Geo or device routing that sends users somewhere other than the declared page.
- A landing page updated mid-campaign without the declaration being updated with it.
How to fix it
Make the declared URL name the page the user actually ends on, not the first hop of the chain. Where routing genuinely varies, declare it so that every branch is covered rather than only the one you tested.
The part that is not obvious
The check is on where the user ends up, not on where the click is sent first, which is why adding a tracking redirect to a previously approved creative is enough to trigger this on its own. It is also the reason that reads worst in an appeal: an undeclared destination is exactly what a cloaking setup looks like from Google's side, so a benign routing rule and a deliberate deception are indistinguishable in the data. Declaring every branch is cheaper than explaining one.
Related reasons
Reason name verified against Troubleshoot creatives rejected by Display & Video 360 or Google Ad Manager on 30 July 2026. The causes and fix above are practitioner guidance, not Google policy text.