Google Ads Destination Requirements 2026: Fix Disapprovals

Your ad gets disapproved for “Destination not working” — and the page loads in half a second in your browser. Nine times out of ten the page is fine; what is not fine is what the reviewer sees. AdsBot crawls from a data center, in a different country, with no cookies, no session and a different user agent. Where you see a working landing page, it sees a geo redirect, a consent wall, or a 403 from your firewall.

Google Ads destination requirements are the policy block responsible for more disapprovals than anything except ad text rules. This guide covers all ten disapproval categories, the June 2026 change to the redirect policy, a 20-minute diagnostic, and a pre-launch checklist that removes most of the problem before you ever hit publish.

How Google actually checks your page

Review happens two ways. Automated: the AdsBot crawler visits the final URL, renders the page, compares its content against the ad, and checks technical conditions. Manual: a reviewer opens the same page, typically from a targeted country.

Three consequences explain most “inexplicable” disapprovals:

AdsBot must be allowed in robots.txt. If the crawler cannot read the page, Google cannot verify that its content matches the ad.
The page must load from every targeted region. Geo blocking at the CDN or firewall layer is the single most common hidden cause.
The whole path is reviewed, not just the endpoint. Redirect chains, tracking parameters, mobile rendering and behavior when consent is declined are all part of it.

Google Ads destination requirements: the ten disapproval categories

Category	What it means	Usual cause
Destination not working	Destinations that don’t function properly or were set up incorrectly, or return HTTP errors on common browsers and devices	404/500, a broken tracking-template parameter, forced login
Destination mismatch	Display URL must align with the actual landing page: no foreign domains, improper subdomains, or redirects to a different domain	Affiliate links, URL shorteners, domain-to-domain redirects
Destination not crawlable	AdsBot must be able to read the page to verify content matches the ad	Disallow in robots.txt, bot blocked at WAF, anti-scraping rules
Destination not accessible	Destinations that aren’t reachable in the location the campaign targets	CDN geo filter, regional redirect, missing language version
Destination experience	Pages must be easy to navigate and safe; prohibits abusive experiences, downloads initiated from ads, and formats that breach Better Ads Standards	Full-screen interstitials on load, auto-downloads
Insufficient original content	Destinations must offer unique value, not replicate content found elsewhere or exist solely to show ads or redirect users	Thin bridge pages, aggregators with no content of their own
App or web store policy violation	App and store destinations must comply with Google’s app and web store policies	App removed or restricted in the store
Unacceptable URL	Non-standard syntax, IP addresses as display URLs, unacceptable characters	Hand-built links, stray characters in UTM parameters
Unrecognized app	Apps Google cannot identify from the supplied link	Wrong app identifier
Phone number requirements	Call formats need a verified, acceptable number — no fax lines, premium numbers or virtual services	Dubious call-tracking providers

Two of these blindside advertisers most often: “insufficient original content” and “destination experience.” Both sound subjective, but in practice they reduce to one question — does the person who clicked get what the ad promised, without obstacles in the way?

What changed in June 2026: cross-domain redirects

On 23 June 2026 Google posted an update to the destination mismatch policy, effective in early July. The substance: redirecting from an ad’s final URL to a different domain is now permitted in certain circumstances, with prior approval.

Google’s own example: a consumer packaged goods manufacturer sending users to a pre-approved list of retailer destinations where the advertised product is sold.

Three things to be clear about:

It is an exception, not a default permission. Without advance authorization, cross-domain redirects still violate the policy.
Approval must be obtained before you run, not after a disapproval.
It covers a pre-agreed, finite list of destinations — not arbitrary traffic routing.

If your setup depends on redirects and you plan to use the new exception, start with the approval request and point live ads at your own domain in the meantime.

The 20-minute diagnostic

Check robots.txt. Confirm AdsBot is not blocked. Note the nuance: AdsBot has several agents (desktop and mobile), and a blanket disallow for all bots covers them too unless you write an explicit exception.
Walk the full final URL. Copy the link exactly as it appears in the ad — tracking template and parameters included — and open it in incognito. Half of “not working” disapprovals are a broken parameter.
Inspect response codes across the chain. Look at intermediate hops, not just the final code. A four- or five-hop chain is a red flag by itself.
Test from each targeted country. If the site is closed to some regions at CDN or firewall level while the campaign targets them, disapproval is guaranteed.
Open it on mobile. Look specifically at pop-ups, the consent banner, and whether the main content is reachable without extra taps.
Test the “reject cookies” path. If declining consent leaves an infinite spinner or a blank screen, that is a destination experience violation. How to keep collecting signal under rejections is covered in our guide to Consent Mode v2 and privacy.
Compare content to the ad. The product, price, offer and geography promised in the ad must literally appear on the page.

Never test in your own browser with autofill and an active session. Test in incognito, with the full URL from the ad, and from a targeted region. That is where 80% of disapproval causes reveal themselves.

Geo accessibility: the most common hidden cause

One scenario deserves its own section because it looks random in reports: you target ten countries, ads get approved, and a day later some of them flip to “destination not accessible.” The causes are almost always the same:

A WAF or CDN blocks requests from certain countries and data centers — and AdsBot crawls from a data center.
Automatic geolocation redirects send foreign visitors to a different domain, which reads as destination mismatch.
The language version for a country does not exist and returns 404 instead of falling back to the default.
Server rate limiting returns 429 when the crawler makes several requests.

The fixes are infrastructural: an explicit allow-list for AdsBot, a fallback instead of a 404, and replacing automatic geo redirects with a region selector. As a bonus, this usually improves load behavior too — see our guide to landing page speed and Core Web Vitals.

Pre-launch checklist: 16 items

Your own domain, HTTPS, a valid certificate with no warnings.
AdsBot explicitly allowed in robots.txt.
Final URL with all parameters returns 200 in incognito.
No more than one redirect in the chain, and that one stays on your domain.
Display URL matches the landing page domain.
Page reachable from every targeted region.
Contact details, legal entity information and a working contact channel.
A privacy policy and, where data is collected, a clear explanation of why.
Offer terms, pricing and limitations stated on the page itself, not only in the ad.
No automatic downloads or navigation without a user action.
Pop-ups do not cover content immediately on load.
Mobile layout readable without horizontal scrolling; buttons are thumb-sized.
Main content visible when optional cookies are declined.
Content is original — not a copy of another site, not a thin bridge page.
Call formats use a verified number: no premium lines, no fax.
Forms work and show a visible confirmation (ideally recorded as a conversion).

That last item is about money, not policy: a page that clears review but does not convert costs exactly the same per click. What to fix first is covered in our breakdown of landing page conversion for paid traffic.

Server-side: configure it once, stop firefighting

Most destination disapprovals are configuration problems, not content problems. Here is what to fix at the infrastructure layer.

1. robots.txt. If you block third-party crawlers, AdsBot needs an explicit allow. A blanket User-agent: * disallow covers it too, so the exception has to be its own block for the AdsBot agents — desktop and mobile. After editing, verify the specific directory is reachable: an accidentally blocked landing-page folder is a classic.

2. WAF and bot protection. Rules like “block data-center traffic” take out AdsBot along with scrapers. You need an explicit allow-list validated by reverse DNS, not by the user-agent string alone — otherwise you open the door to anyone claiming to be Google.

3. Response codes. How review reads the common cases:

What the server returns	How it is read
200 with real content	Fine
301/302 within your own domain	Acceptable, but shorter is better
301/302 to a different domain	Destination mismatch (unless pre-approved)
403 to the crawler	Destination not crawlable
404 in a specific country	Destination not accessible
429 under repeated requests	Can be read as a non-working destination
200 with an empty DOM before JS	Risky: the crawler may not see the match with your ad

4. Rendering. If content is assembled entirely client-side and the page is blank without JavaScript, you are betting on the crawler rendering in time. For paid-traffic landing pages, server-side rendering — or at minimum static HTML carrying the core offer — is the safer default.

5. Tracking parameters. The final URL with your tracking template must behave exactly like the clean URL. A common breakage: the server strips unknown parameters with a redirect, lengthening the chain. Handling parameters and click IDs correctly is covered in our guide to GCLID, GBRAID and tracking templates.

A repeatable launch workflow

Rather than catching disapprovals one at a time, lock a sequence for every new landing page:

A day before launch, publish on the production domain and let it settle — a brand-new domain with no history reviews worse.
Run the 16-point checklist above instead of relying on memory.
Verify accessibility from every targeted country and record response codes — that record is exactly what you attach to an appeal later.
Launch a single ad and wait for its status before building out the full structure. Bulk-uploading against an unverified destination turns one disapproval into a hundred.
After approval, avoid changing the domain or URL structure without reason: every final-URL change resubmits the ad for review.
When editing the page, preserve the match with the ad. Remove an offer from the page while the ad still promises it and you are back to destination mismatch.

What to do after a disapproval

Get the exact sub-reason. Hover the ad status — the specific category is named there. “Not working,” “mismatch” and “not crawlable” have completely different fixes.
Fix the cause, not the symptom. Swapping in a different URL without addressing the underlying issue usually earns a second disapproval.
Let the crawler see the fix. After the change, edit the ad — that resubmits it for review, which typically completes within one business day.
Appeal with evidence only. If you are confident the policy is met, attach proof: the HTTP response code, a screenshot from the targeted country, the relevant robots.txt lines.
Do not mass-duplicate ads. Cloning ads against the same destination accelerates account-level restrictions, not approval.

It is worth separating a policy disapproval from a different state entirely: an approved ad that barely serves. That is not a landing page problem — diagnostic order lives in our guides to limited ad serving and ads that aren’t showing.

Site migrations and redesigns: four recurring failures

Disapprovals spike around site changes. What usually breaks:

Final URLs never updated in campaigns. Redirects from old addresses work for users, but campaigns end up carrying long chains and some pages fall into 404. Update URLs in ads and assets instead of leaning on redirects.
The staging robots.txt shipped to production. A file with a blanket disallow, inherited from the test environment, is the single most common post-release incident. Check it first.
A new consent platform blocks content. A fresh CMP throws a full-screen modal and serves nothing until the user answers — a direct destination experience risk.
Legal pages disappear. Privacy policy, contacts and terms routinely get lost in a redesign, and without them the site reads as untrustworthy in review.

The routine that prevents all four: export every final URL from your campaigns before release, then batch-check them after release and confirm response codes. Fifteen minutes of work that saves a day of disapproval triage.

How disapprovals connect to your CPC

There is a second reason to keep destinations clean beyond passing review. Landing page quality feeds Quality Score: relevance to the query and page usability influence Ad Rank, and therefore your cost per click and position. The practical payoff usually arrives twice — disapprovals stop first, then average CPC on the same keywords drifts down as the landing page experience component improves. Treat the checklist above as account economics, not paperwork.

How this connects to the rest of the account

Destination problems rarely arrive alone. Disapprovals hit campaigns unevenly, demand shifts into whichever campaigns are still serving, and the result looks like cannibalization between PMax and Search when the root cause is purely technical. E-commerce has its own mirror of this: the same destination rules apply to shopping ads, so run the check alongside Merchant Center product disapproval diagnostics.

If what blocks your launch is the state of the ad account rather than the landing page, that is a separate track — see our advertiser verification service and Google Ads agency accounts. But note the order of operations: no account fixes a page that fails destination requirements, because those checks run at the ad level and will repeat everywhere.

FAQ: destination requirements

The page opens fine for me — why does Google say it doesn’t work?

Because you are opening it from your own country, with an active session, without tracking parameters. Test the complete final URL in incognito and, where possible, from the targeted region.

Do I have to allow AdsBot in robots.txt?

Yes. Without crawler access Google cannot confirm the page matches the ad, and that is its own disapproval reason — destination not crawlable.

Can I advertise an affiliate link?

Redirecting to a different domain falls under destination mismatch. Since July 2026 there is an exception for pre-approved cases — such as an agreed list of retailer destinations — but approval must be obtained in advance.

How many redirects are acceptable?

There is no published number, but the practical rule is short is better. One internal redirect is generally safe; a long chain through third-party services is a reliable source of trouble.

What counts as insufficient original content?

A page that offers no standalone value: it replicates content from elsewhere, exists only to display ads, or exists only to push the user somewhere else.

Does page speed affect review?

Speed is not its own disapproval category, but an extremely slow page combined with intrusive formats falls under destination experience. Speed also feeds Quality Score and therefore your CPC.

How long does re-review take after a fix?

Typically up to one business day once the ad has been edited and resubmitted. Simply waiting without editing does not trigger a new review.

Can I use different landing pages per country?

Yes — but do it with separate campaigns or ads pointing at the correct URLs, not with an automatic geo redirect from a single address, which reads as destination mismatch.

What if I believe the disapproval is wrong?

Appeal with concrete evidence: HTTP status, a screenshot from a targeted country, robots.txt lines. Repeat appeals with no changes rarely go anywhere.

Are the requirements identical for Search, PMax and Shopping?

The base requirements apply across formats. Shopping ads add product data requirements, so e-commerce diagnostics have to run in Google Ads and Merchant Center in parallel.

Does one disapproval hurt the whole account?

A single disapproval, no. Repeated violations of the same rule raise the risk of account-level restrictions, which is why fixing the cause beats recreating the ads.

Google Ads Destination Requirements in 2026: 10 Disapproval Reasons and How to Clear Them