- The display path is two optional pieces of presentation text (up to 15 characters each) appended after the domain to hint at the page's topic. They do not need to be real folders on the site.
- The domain in the display URL is not typed in; it is taken from the final URL. That is the underlying reason the shown domain and the landing domain must agree.
- The old AdWords destination URL was split into a final URL plus a tracking template and final URL suffix, so the landing page and tracking are managed separately.
- Most destination mismatch disapprovals come from the redirect chain: one hop lands on another domain, or different visitors end up in different places.
Three URLs on one search ad
Start by aligning the vocabulary. The final URL is the address of the page a user reaches after clicking, and it is the thing the platform checks as the landing page. The display URL is the line shown to users on the ad, built from the final URL's domain plus the display path. The tracking fields — tracking template, final URL suffix and custom parameters — add or record parameters during the click without changing the page the user finally sees.
| Field | What it does | Who sees it |
|---|---|---|
| Final URL | The landing page after the click, and the subject of policy checks | Users after they click |
| Display path (Path 1 / Path 2) | Presentation text after the domain that hints at the page topic | Everyone who sees the ad |
| Display URL | Domain (taken from the final URL) plus display path | Everyone who sees the ad |
| Tracking template / final URL suffix | Add or record parameters without changing landing content | Generally invisible |
We cover what the landing page itself has to satisfy in the Google Ads landing page requirements; this article focuses on how these fields relate to each other.
The display path: what it can and should not say
In responsive search ads the display path is two optional fields of up to 15 characters each. When filled in, the ad shows something like “domain/path1/path2”. The point is to give users a sense, before they click, of which kind of page they will reach — for example “example.com/shoes/running”.
A few points that come up often:
- It does not have to exist. The display path is presentation text; the final URL can have an entirely different path structure, even a long parameter string. The platform does not require a literal match.
- It should still relate to the landing content. Writing “/free-trial” for a page with no trial uses presentation text to mislead, and that kind of inconsistency is treated as a mismatch with the destination.
- It cannot change the domain. The display path only affects what comes after the domain. No field lets an ad show a domain other than the one in the final URL.
- Typical uses. Echoing the keyword theme, separating product lines within an account, or marking region or language in multilingual accounts.
Where the display URL's domain comes from
In old AdWords the display URL was a free-text box the advertiser filled in, which left room for showing one domain and landing on another; the platform could only constrain that through later checks. After the upgrade, the display URL's domain is taken directly from the final URL, and the advertiser only controls the display path after it. The design turns “the domain users see equals the domain users land on” into a default constraint at the configuration level.
So when you see a destination mismatch notice, the problem almost never lies in the display path. It lies in what happens after the final URL: whether a user who clicks it is taken to another domain.
What replaced the AdWords destination URL
Many people search for “destination url adwords” because they met the field in an old tutorial or account. In the old system a single destination URL did two jobs: pointing to the landing page and carrying tracking parameters or third-party tracking redirects. Every tracking change meant editing the ad's destination, sending it back through review and breaking its history.
Upgraded URLs separate the two. The final URL describes only the landing page; the tracking template describes how the click passes through tracking services; the final URL suffix appends parameters to the landing page. Tracking templates can be set at account, campaign or ad group level, and changing them does not send the landing page back for checks. We break down how to design the tracking path without triggering disapprovals in Google Ads tracking templates and redirects.
One more field that is easy to overlook is the mobile final URL. Use it only when mobile genuinely needs a different page; with a responsive site, leave it empty. When both versions exist, both must meet the same consistency requirements.
The consistency rules the destination is checked against
Google's destination requirements policy is broad, but the part that touches these fields reduces to three rules:
- Domain consistency. The display URL's domain matches the domain users finally reach. Passing through a tracking redirect is fine, but the endpoint must be the same domain.
- Reachable and consistent. The final URL loads, and presents substantively the same content to different visitors. Returning an error, a blank page or another version to some origins is recorded as a destination problem.
- Consistent with the ad. What the ad text and display path communicate can be found on the landing page.
The second rule deserves a note. The platform visits final URLs under different conditions. If page logic branches by visitor so that some people see another version, the setup falls under the circumventing systems policy, with consequences far more serious than a single disapproval. For how platforms generally run this kind of comparison, see how ad platforms detect pages that branch by identity.
Common sources of mismatch
- The redirect endpoint moves domain. A short link, affiliate hop or interstitial takes users to another domain.
- Mixing subdomains and root domains. Subdomains of the same root are usually fine; moving to an entirely different root domain is not.
- Region or language redirects. Redirecting users by region to a local site on another domain makes one final URL land on different domains for different people. Adapting within the same page is the safer approach.
- Protection rules misfiring. A WAF, CDN or bot-protection rule returns a block page to some origins, so the platform sees an unreachable destination.
- Split tests across multiple URLs. Tests that send visitors to different addresses give one ad several real destinations. For testing within one address, see same-URL A/B testing methodology.
Start from the final URL and follow it once from a standard browser, once from a mobile browser and once from a data-centre egress, recording the domain of every hop and the page that finally loads. If all three end on the same domain with substantively the same content, consistent with the ad and display path, the configuration holds up on consistency.
Working through a disapproval
When a destination-related disapproval arrives, work through it in order. First confirm the final URL itself loads. Then inspect the full chain once the tracking template and suffix are expanded, noting which domain each hop lands on. Next visit from different conditions to confirm no protection rule or regional redirect is producing a difference. Finally compare the page against the ad text and display path. Fix what you find, then request another review with a clear explanation. If the issue has escalated to the account level, common reasons Google Ads accounts are suspended and how to write an appeal are the natural next references.
Frequently asked questions
What is the display path in Google Ads?
The display path is two optional text fields, Path 1 and Path 2, of up to 15 characters each. They are appended after the domain in the URL shown on a search ad to indicate what the landing page is about. They are presentation text and do not have to exist as real folders on the site.
Is the Google Ads display URL the same as the final URL?
No. The final URL is where the click actually lands. The display URL is what the ad shows: the domain of the final URL plus any display path text. The domain part is taken from the final URL, which is why the two cannot point to different sites.
What happened to the destination URL field in AdWords?
The single destination URL was replaced by upgraded URLs: a final URL for the landing page, plus separate tracking fields such as the tracking template and final URL suffix. Separating them lets tracking change without the landing page itself being re-submitted.
Why was my ad disapproved for destination mismatch?
Most often the domain shown in the ad differs from the domain a visitor finally reaches, typically because a redirect in the click path lands on another domain. Check the full chain from final URL through tracking redirects to the page that loads, and make sure every visitor ends on the same domain.
One URL, the same page for every visitor
Same landing-page URL for every visitor — language and region adaptation in-page, in-page A/B testing, and invalid-traffic filtering. No cloaking, no sneaky redirects.