{"id":2971,"date":"2024-09-29T10:19:12","date_gmt":"2024-09-29T10:19:12","guid":{"rendered":"https:\/\/www.webapex.com.au\/blog\/?p=2971"},"modified":"2024-10-16T23:54:13","modified_gmt":"2024-10-16T23:54:13","slug":"google-ads-destination-mismatch","status":"publish","type":"post","link":"https:\/\/www.webapex.com.au\/blog\/google-ads-destination-mismatch\/","title":{"rendered":"Google Ads disapproved Destination Mismatch"},"content":{"rendered":"

While Google Ads disapproval happens for various reasons, one common disapproval reason is \u201cdestination mismatch\u201d.<\/p>\n

A \u201cdestination mismatch\u201d happens when the display URL and landing page are different.<\/strong><\/p>\n

\u201cGoogle requires ads to accurately reflect which app or website the user is being directed to when they click on the ad.\u201d<\/p>\n

You must follow Google Ads policy guidelines to ensure your ads get served without interruptions.<\/p>\n

Let\u2019s talk about the destination mismatch in detail.<\/p>\n

Case 1: Completely different domain mismatch<\/h2>\n

This happens when your display URL has one domain but the actual URL where the user gets redirected is different.<\/p>\n

Example:
\nDisplay URL: google.com<\/em>
\nLanding URL: youtube.com<\/em><\/p>\n

This is a clear mismatch and your ads will get disapproved. Make sure both are the same to ensure users don\u2019t get misled.<\/p>\n

Case 2: Domain and sub-domain mismatch<\/h2>\n

This is another common domain mismatch scenario where the display and the actual URL may have the main domain vs the sub-doming.<\/p>\n

Example:
\nDisplay URL tradeonline.com<\/em>
\nLanding URL: listings.tradeonline.com<\/em><\/p>\n

If you have product listings for your users to view on your sub-domain then you must display the same subdomain in the ad and take users to the same subdomain.<\/p>\n

Case 2: The landing page redirects to a separate domain<\/h2>\n

Though you may have the display and the actual URL to be the same when the user clicks on the ad the landing URL redirects to a different domain.<\/p>\n

Example:
\nDisplay URL: example.com<\/em>
\nLanding URL: example.com >> Redirects >> example1.com<\/em><\/p>\n

This is a complete mismatch and it will result in ads disapproval.<\/p>\n

Case 4: URL shortener domain mismatch<\/h2>\n

Avoid unnecessary tracking using URL shortener, it can mislead users as the destination of a shortened URL can be changed.<\/p>\n

Example:
\nDisplay URL: ebay.com\/abc-store<\/em>
\nLanding URLL: bit.ly\/abc-store<\/em><\/p>\n

This will lead to a clear domain mismatch and it will result in a disapproved destination mismatch.<\/p>\n

Case 5: Tracking parameter domain mismatch error<\/h2>\n

\u201cA tracking parameter in the final URL can cause a destination mismatch if there is no {ignore} inserted before the tracking parameter. If you use tracking in your final URL, including a dynamic ID from a third-party tracking system, you need to include {ignore} before the tracking parameter in your final URL.\u201d Learn more: https:\/\/support.google.com\/adspolicy\/answer\/6368661?hl=en<\/a><\/p>\n