The ad says northstar.example. The Final URL field also says northstar.example. Yet Google Ads reports Destination mismatch. Opening the URL in a normal browser appears to confirm that everything is fine.
Do not rewrite the ad yet. Trace the click.
The practical answer is to compare the entered Final URL with every destination produced after it: the effective tracking template, each server redirect, any browser-side redirect, and the page that finally loads. The first hop that changes the advertised website—or changes the promised content even while keeping the same domain—is the place to fix. Looking only at the URL field and the last browser address can hide the responsible rule.
Google’s current Destination mismatch policy names cross-domain redirects, URL shorteners, geo-based redirects, case-sensitive server behavior, display-domain mismatches, and tracking paths that lead to different content as possible causes. A June 2026 policy update permits a different-domain redirect only in certain circumstances with prior approval; it is not blanket permission to route an ordinary ad wherever you want. See Google’s June 2026 Destination Requirements update.
This guide gives you a repeatable audit, a command-line trace, a browser trace, and three controlled examples. The examples are fictional teaching cases, not live campaigns or evidence of Google approval.
What Google Ads is actually comparing
“Destination” is not one field. It is a route assembled from several layers, some of which may be inherited from higher in the account.
| Layer | What it controls | What to verify |
|---|---|---|
| Display URL/domain | The website identity shown in the ad | Its domain should agree with the website the user reaches. On shared hosting domains, the display URL must clearly distinguish the actual subdomain. |
| Final URL | The landing page you enter for the ad, keyword, asset, or other item | It should be a direct, stable HTTPS landing page for the advertised content. |
| Mobile Final URL | An optional mobile-specific destination | It must not send mobile visitors to a different website or unrelated content. |
| Tracking template | A tracking route that can wrap the landing-page URL | It must preserve the intended Final URL and promoted content rather than substitute a different landing page. |
| Final URL suffix | Query parameters appended to the landing page | It should add measurement parameters without becoming a second routing system. |
| Server and edge rules | CDN, load balancer, CMS, locale, cookie, or device redirects | Follow every Location response. A Final URL redirect must not change the landing website without an applicable prior approval, and the completed route must preserve the intended content. |
| Browser code | JavaScript, consent logic, app/deep-link logic, or service-worker navigation | It must not switch the expected website or promoted content after the HTTP trace appears clean. |
Google’s Final URLs and tracking templates documentation explains that the Final URL is the landing page while the tracking template holds tracking information. Google’s URL tracking hierarchy documentation also makes an operationally important point: URL options can exist at several levels—including account, campaign, ad group, ad, keyword, and sitelink—and the most specific applicable setting wins.
That inheritance is why an ad can look correct when the campaign or account still contains the bad route.
First, confirm that this is a redirect problem
Before changing redirects, read the exact policy detail attached to the affected item. “Destination mismatch” is different from “Destination not working.” Google’s Destination not working policy covers conditions such as HTTP errors, DNS failures, timeouts, private IPs, malformed responses, and redirect loops; a route that lands on the wrong website or content belongs to mismatch.
Also rule out a platform-selected landing page. In eligible Search campaigns, Final URL expansion in AI Max can replace the entered Final URL with another relevant page on the same domain. Performance Max Final URL expansion can do something similar. If the address changed without an HTTP or browser redirect, inspect Final URL expansion and landing-page reporting rather than inventing a redirect that never occurred.
Once the policy detail and campaign behavior point to a route mismatch, audit the route in this order.
A ten-minute destination mismatch audit
1. Record the exact affected object
Write down the campaign, ad group, ad or asset, keyword if applicable, displayed domain, Final URL, mobile Final URL, and the full disapproval subtype. Do not start from a copied URL in a spreadsheet if the live account contains a different value.
Add columns for the tracking template, Final URL suffix, and—where available—Tracking template source. Google’s tracking-template setup guide says this column shows which template is applied and that template changes can take 24–48 hours to be reflected in ad serving. Record the time of the latest edit rather than assuming an immediate result.
2. Expand the effective click URL
Use the Test function next to the item’s URL options. Google’s landing-page test documentation lists possible messages for a landing-page URL mismatch, Final URL mismatch, an HTTP URL in the tracking chain, and a JavaScript redirect in the tracking chain.
Read those messages conservatively. The same page also says the test does not support URL redirects, is not a policy check, and does not catch every parallel-tracking problem. That limitation makes the Test result a clue rather than a full chain capture. Save what it reports, then reproduce the route independently.
3. Trace server redirects with a real GET request
The browser address bar shows the current URL, not the intermediate response history. Use a redirect-aware HTTP client to retain that history. The following one-line curl command follows up to ten redirects, saves every response header block, discards the page body, and prints the effective final URL:
curl -sS -L --max-redirs 10 -D redirect-headers.txt -o /dev/null -w 'final=%{url_effective}\ncode=%{http_code}\nredirects=%{num_redirects}\n' 'https://www.example.com/landing-page'
-L follows redirects; -D writes response headers; the write-out variables expose the effective URL, final status, and redirect count. Those behaviors are documented in the official curl manual. The HTTP mechanism itself is standard: redirect responses such as 301, 302, 307, and 308 commonly identify the next target with a Location field, as described in RFC 9110.
Use a GET, not only curl -I. -I asks for a HEAD response, and a server is allowed to handle HEAD differently from GET. Remove authorization codes, click IDs, email addresses, and other sensitive query values before sharing the trace.
Read the output from top to bottom. For every response, record:
- status code;
- full
Locationvalue, including scheme, host, path, and query; - whether the host changed;
- whether the intended product, offer, or category changed;
- which system generated the response.
The owner may be visible in headers, but often you will need to match the hop to CDN rules, server configuration, a CMS redirect plugin, locale middleware, or the click tracker’s logs.
4. Trace browser-only navigation
If curl reaches the right page but the browser does not, open Chrome DevTools before loading the URL. In Network, enable Preserve log, disable the cache for the test, and reload from the entered Final URL. Chrome’s Network features reference documents those controls and the Initiator column, which can identify a request initiated by a redirect or script.
Inspect the first document request and every later document navigation. A JavaScript locale router, consent manager, deep-link fallback, or service worker can create a mismatch without a 3xx response. Test a normal desktop and mobile browser in the countries and languages you actually target. Do not create an AdsBot-only route or serve compliant content to Google while sending people elsewhere. Google defines that behavior as cloaking in its Circumventing systems policy.
5. Compare conditions, not just URLs
A route may vary by location, device, language, cookie, authentication state, inventory, or time. Repeat the trace under the conditions relevant to the disapproved ad, keeping the offer constant. Useful comparisons include:
- fresh session versus returning session;
- desktop versus mobile;
- each country or language targeted by the affected campaign;
- tracking template enabled versus temporarily removed in a safe draft or test environment;
- authenticated versus signed-out landing page, if the offer is meant to be public.
Do not use these comparisons to disguise one destination from review. Their purpose is to remove unintended variation so Google and the user receive the same promoted product or service.
6. Mark the first meaningful divergence
The final page is the symptom. The first divergence is the cause.
If response 1 changes brand.example to retailer.example, fix the edge rule that emitted response 1. If an account-level tracker receives {lpurl} but maps a custom parameter to another product, fix that mapping. If the server trace is clean and a script changes the page, fix the script. Do not patch a later hop while leaving the earlier bad rule active.
Open the interactive redirect-chain lab or use the structured redirect-chain example data.
Three controlled redirect examples
Example 1: A same-domain canonical redirect
Entered Final URL: https://northstar.example/sale
Observed route: 301 → https://northstar.example/summer-sale/ → 200
Final domain: northstar.example
First domain-changing hop: none
This chain preserves the same website and the same sale. It is not the cross-domain problem you were looking for. Still, the shortcut creates an unnecessary variable: server behavior, parameters, or a future redirect rule could change it later.
Fix: put the canonical https://northstar.example/summer-sale/ URL directly in the ad; align any mobile, keyword, asset, and tracking settings; then rerun the Google Ads test and a fresh browser trace. If the ad remains disapproved, investigate the exact reported subtype rather than calling this same-domain hop the culprit without evidence.
Example 2: A geo router changes the domain
Entered Final URL: https://trailcase.example/shop
Observed route for Canadian traffic: 302 → https://trailcase.ca/ca/shop → 200
Final domain: trailcase.ca
First domain-changing hop: response 1
The visible destination looks correct from one location, but the edge or locale layer sends another location to a different website. Google’s mismatch page specifically lists geo-redirection applications among possible causes.
Fix: choose one deliberate architecture. Keep Canada on a path of the advertised website, such as https://trailcase.example/ca/shop; or use a direct Canadian Final URL in the localized ad so the displayed and landing domains agree. If the business genuinely falls within Google’s limited different-domain exception, obtain the required prior approval and follow its conditions. Do not assume the exception from the mere fact that the second site belongs to the same company.
Example 3: An inherited tracker changes the product
Intended Final URL: https://solaraudio.example/headphones
Effective template: https://click.measure.example/r?u={lpurl}&offer={_offer}
Expanded tracker output: 302 → https://solaraudio.example/products/air-2 → 200
Final domain: solaraudio.example
First meaningful divergence: the tracker’s response
Here, the advertiser domain still matches. The content does not. A stale fictional custom parameter—offer=air2—overrides the landing-page value and sends the click to one product while the Final URL represents a broader headphones page. Google’s policy treats a tracking template or expanded URL that leads to different content from the Final URL as a destination mismatch.
Fix: find the level that supplies the effective template; remove the stale offer mapping; and make the tracker return the intended landing-page parameter instead of substituting a different product. If you only need ordinary query parameters, a Final URL suffix may be simpler than an extra redirect. When a third-party click tracker is necessary, use one that meets Google’s requirements; Google maintains a certified click tracker list.
Parallel tracking does not make this audit optional. Google currently makes it mandatory for Search, Shopping, Display, Video, and Performance Max campaigns; hotel campaigns are the listed optional case. With parallel tracking, the user goes directly to the Final URL while tracking loads in the background. In a non-parallel route, the user passes through tracking redirects first. Either way, keep the tracking route valid and consistent. See Google’s parallel tracking overview.
Where the bad hop usually hides
| Pattern in the trace | Likely owner | Corrective action |
|---|---|---|
www or trailing-slash normalization on the same website |
Web server or CDN | Enter the canonical Final URL directly and keep one normalization rule. |
| Country, currency, or language sends traffic to another domain | Edge, geolocation app, commerce platform | Keep routing on the advertised domain, use a direct localized ad URL, or use an approved exception. |
| Short URL expands to an unexpected host | Link shortener or legacy campaign tool | Remove the shortener and enter the stable landing page. |
| Tracker receives the right landing URL but returns another page | Tracking vendor or custom parameter map | Fix the effective inherited template or mapping; retest the expanded route. |
curl is clean but DevTools shows a later document navigation |
JavaScript, consent tool, deep-link code, service worker | Repair or remove the browser-side navigation. |
| Only one capitalization variant lands correctly | Case-sensitive server or rewrite rule | Use the exact canonical casing everywhere and normalize consistently. |
| Correct today, wrong after inventory or offer state changes | Commerce middleware, promotion engine, fallback rule | Do not let a fallback change the promoted product or website; update or pause the ad when the original destination is no longer truthful. |
The best fix is usually to remove indirection. A direct Final URL is easier to review, easier to debug, and less likely to drift than a chain distributed across an ad platform, tracker, edge service, and site code.
Re-test before requesting review
After the owner changes the bad rule, repeat the same evidence path:
- confirm the live Final URL, mobile URL, effective template, suffix, and template source;
- run Google Ads’ URL Test again;
- run a fresh GET-based server trace and save the headers;
- reload in DevTools with Preserve log and cache disabled;
- repeat the relevant location, device, and session conditions;
- verify that the advertised website and promoted content remain consistent through every route;
- request review only after the corrected behavior is live.
Google’s mismatch help says edits to an ad-, keyword-, or sitelink-level tracking template trigger review automatically, while a fix at ad group, campaign, or account template level may require an appeal. Follow the current instructions shown with the affected item. Google’s policy appeal guidance recommends fixing the destination first and appealing when the issue is corrected or you believe the decision is an error.
Your review note should be factual: name the old hop, the system that owned it, the corrected route, and the conditions you retested. Do not claim “no redirects” if a canonical redirect remains, and do not submit repeated appeals while the chain still reproduces the mismatch.
Keep destination mismatches from returning
Treat destination routing as production infrastructure, not campaign copy. Before launch, export the effective URL settings at every applicable level, trace the real expanded route, and store the result with the campaign QA record. Re-run that check when a CDN rule, locale app, CMS plugin, tracker mapping, domain, promotion, or product fallback changes.
The operating rule is simple: the URL entered in Google Ads is only the start of the evidence. Follow every hop, find the first one that changes the website or the promised content, and fix that layer before asking Google to look again.
Sources
- Destination mismatch — Google Advertising Policies Help.
- Destination not working — Google Advertising Policies Help.
- Update to Destination Requirements Policy (June 2026) — Google Advertising Policies Help, posted June 23, 2026.
- Learn about final URLs and tracking templates — Google Ads Help.
- About tracking in Google Ads — Google Ads Help.
- Set up your tracking template — Google Ads Help.
- Test your landing page — Google Ads Help.
- About Final URL expansion in Search — Google Ads Help.
- About Performance Max campaigns — Google Ads Help.
- About parallel tracking — Google Ads Help.
- List of certified Google click trackers — Google Ads Help.
- Network features reference — Chrome for Developers.
- curl manual — curl project.
- RFC 9110: HTTP Semantics — RFC Editor / IETF, June 2022.
- Circumventing systems — Google Advertising Policies Help.
- Fix a disapproved ad or appeal a policy decision — Google Advertising Policies Help.
