Start by understanding exactly what was flagged, which ads are affected, and what "Destination Mismatch" actually means in Google's terms.
Check the inbox of the email address linked to your Google Ads account. Google sends a message naming the specific policy — in this case, "Destination Mismatch" — and listing the disapproved ads. Also log in to Google Ads and go to Tools → Policy Manager to see every affected ad. Keep the notice open as you work through this checklist, as you will need specific ad names and URLs from it when writing your appeal.
A Destination Mismatch violation occurs when the web address (URL) shown in your ad does not lead to the same website as the actual page the user is taken to after clicking. In simpler terms: your ad shows one address in the visible URL (called the "display URL"), but the real page the user lands on belongs to a different domain or subdomain. For example, your ad displays "yoursite.com" but clicking it takes the user to "differentsite.com" or "subdomain.differentsite.com." Google requires complete consistency between what your ad shows and where it actually takes people.
Every Google ad has two types of URL. The "Display URL" is the web address shown visually inside the ad (for example, "yourshop.com/sale") — this is what the user sees before clicking. The "Final URL" is the actual address the user is taken to after clicking the ad. These two must share exactly the same domain. The path after the domain name (the part after the first forward slash) can be different — for example, the display URL might show "/shoes" while the final URL goes to "/shoes/womens-trainers-2024" — but the main domain must be identical. Any difference in the domain is a mismatch.
Go to Policy Manager in your Google Ads account and open every disapproved ad. For each one, write down: the ad name, the campaign it belongs to, the Display URL shown in the ad, and the Final URL (the actual destination). Place them side by side so you can see at a glance where the mismatch is. This comparison is essential because it tells you whether the issue is in the display URL (which you are showing), the final URL (where you are actually sending people), or both. Without this comparison, you cannot fix the right thing.
Visit support.google.com/google-ads/answer/6305261 and read the full policy on Destination Mismatch. This page explains all the scenarios Google considers a mismatch — including domain differences, subdomain mismatches, redirect destinations, and mobile URL discrepancies. Understanding the full policy helps you spot additional mismatches in your account that were not explicitly listed in the violation notice but that could still cause future disapprovals if left unaddressed.
Before making any changes, do a complete audit of your entire account to find every mismatch — not just the ones flagged in the violation notice.
Go through every active ad in every campaign and every ad group. For each ad, compare just the domain part of the Display URL (the part before the first slash after "https://") with the domain part of the Final URL. They must be exactly the same. For example: Display URL domain = "mystore.com" and Final URL domain = "mystore.com" is correct. Display URL domain = "mystore.com" and Final URL domain = "checkout.differentprovider.com" is a mismatch. Write down every ad where these domains differ — these are all violations that need to be fixed, even if only some were listed in the original notice.
Do not assume a Final URL goes where you think it goes. Open an incognito or private browser window (Chrome: Ctrl+Shift+N / Mac: Cmd+Shift+N) and type or paste each Final URL into the address bar. Watch the address bar closely as the page loads — if the URL changes during loading (which means you were redirected), the final address shown is the real destination. If this final destination domain differs from your Display URL domain, you have a redirect-caused mismatch. Note down the actual final destination for every ad URL you test.
A redirect chain occurs when clicking a URL sends the user through one or more intermediate web addresses before reaching the final page. For example, your Final URL might be "yoursite.com/offer" but that page immediately redirects to "thirdpartyplatform.com/youroffer." Even though your Final URL domain was correct, the actual destination is a different domain — and Google checks where the user ultimately lands, not just where the Final URL points initially. Use a free redirect checker tool (such as redirectdetective.com or httpstatus.io) to check every Final URL for redirects that cross domain boundaries.
A subdomain is the part of a web address that comes before the main domain name. For example, in "shop.yoursite.com," the subdomain is "shop" and the main domain is "yoursite.com." Google generally requires that the domain shown in the Display URL and the domain of the Final URL match at the registered domain level (the "yoursite.com" part). Displaying "yoursite.com" but sending users to "app.differentsite.com" is a mismatch even if both seem related to your business. Check all your ads for subdomain issues and confirm the root domain is consistent.
Many advertisers add tracking parameters to their Final URLs to measure clicks and conversions — for example, UTM parameters from Google Analytics or click-tracking parameters from third-party marketing tools. Some tracking systems work by inserting a redirect through their own domain before sending the user to your actual landing page. If your click-tracking tool routes the click through its own domain (for example, "clicks.trackingservice.com/redirect?to=yoursite.com"), this may create a destination mismatch if the tracking domain differs from your Display URL domain. Check all tracking parameters and verify they do not introduce a different domain as a pass-through destination.
Google Ads allows you to set a separate "Mobile Final URL" for each ad — this sends mobile users to a different page than desktop users. If you have set mobile-specific URLs, check them separately against your Display URL domain. It is a common oversight to update desktop Final URLs to fix a mismatch while forgetting that mobile Final URLs still point to the old, mismatched destination. Go into each ad's advanced URL settings and check whether a mobile final URL has been set, and if so, confirm it shares the same domain as your Display URL.
The Display URL is what users see in your ad before clicking. It must accurately represent where they will actually be taken.
The simplest way to fix a Display URL mismatch is to change the Display URL so its domain matches the domain of the Final URL. In your Google Ads account, edit each affected ad. The domain portion of the Display URL is taken automatically from the Final URL in most modern ad formats — but in some ad types or older ad setups, you can edit it manually. If your Display URL currently shows a domain that is different from your Final URL's domain, change it to use the correct domain. The Display URL domain must be the same root domain that actually serves your landing page content to users.
The Display URL often includes optional "path" text after the domain (for example, "yoursite.com/shoes/sale"). While the path does not need to exactly match the final URL path, it must accurately represent the content of the landing page. Showing "yoursite.com/shoes" in the Display URL but landing the user on a page about handbags or a completely unrelated product is misleading and may trigger a mismatch or a Misleading Content violation alongside the Destination Mismatch. Ensure every Display URL path gives users an accurate preview of where they are going.
Some advertisers include a well-known brand name or company name in their Display URL path even when the actual landing page is on a different platform or domain. For example, displaying "AmazonProducts.com" in the Display URL when the actual landing page is on a marketplace partner site, or displaying "YourBrand.com" when the user is actually taken to a white-label platform at "whitelabelprovider.com/yourbrand." Any brand name in the Display URL must either be the actual domain of the Final URL or be part of the path text that accurately describes the landing page content.
When fixing destination mismatch violations, only fixing the specific ads listed in the violation notice and leaving others unchanged is a very common mistake. Review every active ad in your entire account. In Google Ads, you can use the account-level Reports or the Campaigns view to export all ads and their URLs into a spreadsheet. Review the display URL and final URL for every row. Any mismatch found during this audit should be fixed now, even if that ad was not yet flagged. Google's automated systems continuously review ads, and an unfixed mismatch elsewhere in your account will trigger another violation shortly after your appeal succeeds.
Dynamic Search Ads automatically generate ad headlines and Display URLs based on your website content. If your website has pages that redirect to a different domain, or if your DSA target pages contain links to external platforms, DSA campaigns can generate ads with mismatched destinations automatically. Review any DSA campaigns in your account: check the website domain used as the DSA source, confirm it matches your Display URL domain, and check whether any auto-generated ad destinations are landing on a different domain. Add URL exclusions for any pages in your DSA source that could create destination mismatches.
In responsive search ads (RSAs), the Display URL domain is pulled automatically from the Final URL, which greatly reduces the risk of a domain mismatch in the main URL. However, the customisable path fields (Path 1 and Path 2) in RSAs can still create a misleading representation if they do not reflect the landing page content. Review the Path 1 and Path 2 text in every RSA and confirm they describe the content of the actual landing page accurately. Path text like "/offers" or "/sale" is fine as long as the landing page genuinely features offers or a sale — but using paths that have nothing to do with the page content can trigger related editorial violations.
The Final URL is where users actually land. It must resolve to the same domain shown in your Display URL and must load the correct, relevant content.
If the simplest fix for your violation is to update the Final URL rather than the Display URL, update every mismatched Final URL to a page on the same domain as your Display URL. For example, if your Display URL shows "yoursite.com" and your current Final URL points to "thirdpartyhost.com/yourpage," either create an equivalent page on "yoursite.com" and update the Final URL, or update the Display URL to accurately show "thirdpartyhost.com." Whichever approach you choose, the domain in the Display URL and the domain where the user ultimately lands must be the same.
If your landing pages use redirect chains that route users through a third-party domain — even temporarily — before arriving at your actual page, you must fix the redirect. The best solution is to update your Final URL to skip the intermediate redirect entirely and point directly to the final destination page. If you cannot remove the redirect (for example, because it is managed by a third-party platform), you have two options: either host the landing page content directly on your own domain, or update the Display URL to match the domain the user actually lands on at the end of the redirect chain.
Sometimes destination mismatches arise not because of an error in the original ad setup, but because the business has migrated its website to a new domain since the ads were created. The ads still have the old domain in the Final URL, but the website now redirects all traffic to the new domain. To fix this, update every Final URL in every ad to use the new domain directly. Do not rely on the old domain's redirect to forward traffic indefinitely — redirects can break, and relying on them creates a permanent mismatch risk. Update all URLs to point directly to the current correct domain.
Third-party click-tracking and affiliate tracking systems often work by placing a redirect through their own domain in the URL chain. For example, your Final URL might be "tracker.affiliatenetwork.com/click?merchant=yoursite&page=offer" which then redirects to "yoursite.com/offer." Google checks where the user ultimately arrives — but the Display URL must match the first domain in the chain that the user is actually taken to upon clicking. Use Google's Tracking Template feature instead of embedding cross-domain redirects in the Final URL. With Tracking Templates, the tracking redirect happens transparently and the Final URL domain remains clean and consistent with the Display URL.
Even if the domain in the Display URL and the Final URL match, if the landing page displays completely different products, services, or topics from what the ad describes, this creates a content mismatch — which can overlap with both the Destination Mismatch policy and the Misleading Content policy. For example, an ad for "Men's Running Shoes" that links to a homepage showing baby clothing is a content mismatch. Update each Final URL to point directly to the specific page that features the exact product or service described in the ad.
If you have set mobile-specific Final URLs in your ads, check that they share the same domain as both the desktop Final URL and the Display URL. A common scenario causing mobile destination mismatches is when a business uses a mobile app deep link (such as a link that opens a smartphone app) or a mobile-specific subdomain (such as "m.yoursite.com") as the mobile Final URL, while the Display URL shows only "yoursite.com." Review every ad that has a mobile Final URL set and confirm the root domain is consistent across desktop URL, mobile URL, and display URL.
Cloaking means showing Google's automated review systems different content than what real users see when they visit the same URL. For example, showing a compliant landing page to Google's bots but redirecting human visitors to a different domain or a different page with different content. Cloaking is a severe violation that can result in permanent account suspension rather than just a simple ad disapproval. If any form of cloaking exists on your landing pages, remove it immediately. Google's systems are specifically designed to detect cloaking, and it is treated as an intentional attempt to deceive rather than an accidental policy violation.
Beyond URL consistency, the products, offers, and content described in your ads must match what users actually find on the landing page.
Your ad headline is the promise you make to the user. The landing page is where that promise must be fulfilled. If your headline says "Buy Designer Handbags" but the landing page is your general homepage with no handbags visible, or worse, a completely unrelated page, this is a content destination mismatch. Go through each disapproved ad and open its landing page. Confirm the headline's main subject is prominently featured on the landing page. If the landing page does not match the headline, either update the Final URL to point to the correct product/service page or rewrite the headline to accurately reflect what is on the landing page it links to.
If your ad promotes a specific discount, product model, or offer that is not visible on the landing page, this creates a content mismatch. For example, an ad saying "50% Off All Trainers This Weekend" that links to a landing page with no mention of a 50% discount is misleading. Either update the landing page to prominently feature the promotion mentioned in the ad, or remove the specific claim from the ad copy. Every specific claim, product name, price point, or offer mentioned in your ad must be verifiable on the landing page within a reasonable number of clicks from where the user lands.
If your ad says "Plumbers in Manchester" but the landing page is a generic national homepage with no mention of Manchester or any location-specific content, this creates a geographic content mismatch. Users who click an ad for a specific location expect to land on a page relevant to their location. Either create a location-specific landing page (for example, a "Manchester" page with local contact details, local testimonials, and locally relevant content) or adjust your ad copy to reflect what the general landing page actually offers, removing the specific geographic claim if the landing page does not support it.
If your ad is written in English and targets English-speaking users, but the landing page content is primarily in a different language, this creates a language-based destination mismatch. Users who click an English ad and land on a page in German or French will be confused and frustrated. Check every campaign's language targeting settings and confirm the landing pages used in those campaigns are written in the same language. If you are advertising to multiple language markets, create separate landing pages in each language and assign them to the appropriate language-targeted campaigns.
A Final URL that returns a 404 "Page Not Found" error, a 500 server error, a blank page, or an "Under Construction" page is treated as a destination mismatch because the user is taken somewhere other than the advertised destination. Check every Final URL and confirm each one loads a complete, functional page with relevant content. Use an HTTP status code checker tool (such as httpstatus.io) to batch-test all your Final URLs and identify any returning error codes. Fix all errors by either restoring the missing page, creating a redirect from the old URL to the correct current page, or updating the Final URL in the ad to the correct working address.
Sitelink extensions, promotion extensions, and location extensions each have their own destination URLs. These must also follow the destination matching rules. Check every active extension in your account and confirm that each extension's destination URL shares the same root domain as the main ad's Display URL. An extension linking to a different domain than the main ad creates an inconsistent user experience and can contribute to destination mismatch flags at the account level. Fix any extension URLs that point to domains different from the main ad's Display URL.
After fixing all mismatches, confirm every change works correctly, submit your ads for review, and put processes in place to catch URL issues before they become violations.
Open an incognito or private browser window and manually test each fixed Final URL. As the page loads, watch the address bar to confirm the URL does not change to a different domain during loading. The domain that appears in the address bar when the page finishes loading must match the domain shown in the Display URL of the associated ad. Also confirm the page content is relevant to the ad. Check both the desktop version and the mobile version (use your phone for mobile testing, not just a desktop browser's mobile simulation mode). Document the results of your testing as evidence for your appeal.
Before contacting Google, document every fix with specific details and dates. Example: "1. Updated Final URL of ad [name] from 'thirdparty.com/page' to 'oursite.com/page' on [date]. 2. Removed cross-domain tracking redirect from 6 ads — replaced with Google Tracking Template. 3. Fixed 3 mobile Final URLs that pointed to old domain 'oldsite.com' — updated to 'newsite.com'. 4. Removed redirect from 'oursite.com/landing' that forwarded to 'externalhost.com/ourpage'. 5. Updated Display URL path from '/promo' to '/offers' to accurately reflect landing page content." Specific, dated evidence demonstrates genuine fixes and significantly improves appeal success rates.
In your Google Ads account, go to Tools → Policy Manager. Find every ad still showing a "Disapproved" status due to Destination Mismatch. For each one, click "Appeal" and briefly describe the specific change you made: "Updated Final URL from [old domain] to [correct domain] to match Display URL." Submit once per ad and wait. Google's review for Destination Mismatch violations is typically completed within 1 to 3 business days. Do not submit the same appeal multiple times — wait for the result. If an appeal is rejected, read the feedback carefully, address any remaining issue, then appeal again.
Google Ads has a built-in "Disapproved Ads" email notification you can enable to alert you whenever an ad is disapproved. Turn this on to catch any future destination mismatches quickly. Additionally, consider using a third-party URL monitoring tool (such as UptimeRobot or a dedicated SEO crawler) to monitor your key landing pages and alert you when a URL returns an error or redirects to a new domain. Catching a broken or changed URL within hours rather than days or weeks means you can fix and appeal before the violation affects significant ad spend.
Prevent future destination mismatches by building a URL consistency check into your standard process for creating new ads. Before any new ad is submitted, require the creator to complete these five checks: (1) Does the Display URL domain match the Final URL domain? (2) Does the Final URL load a working page with no errors? (3) Does the page the Final URL loads stay on the same domain without redirecting? (4) Does the landing page content match what the ad describes? (5) If a mobile Final URL is set, does it share the same root domain? Making these five checks standard practice for every new ad prevents the vast majority of destination mismatch violations before they ever reach Google's review systems.
Need Help Fixing Your Ad URLs?
Tracking down destination mismatches across a full Google Ads account can be complex and time-consuming. Our team at UmairConsult identifies every URL issue, fixes them correctly the first time, and gets your ads approved and running again.
Book Your Spot