- YouTube has no separate landing-page policy. Destinations are assessed under Google Ads destination requirements — the same rules that govern Search and Display.
- The review fetches the URL and weighs five things: reachability, consistency, relevance, completeness, and stability over time.
- A page that cleared Search can still fail on YouTube — not because the rules changed but because the access conditions did: in-app webview, mobile user agent, no referrer, and a far wider geographic spread than a keyword campaign implies.
- Destination mismatch is the most misread notice: it usually means the page and the video promise different things, not that the URL is broken.
- One URL returning the same substance to every visit solves this whole class of problem: keep personalization at the presentation layer and leave the offer and the claims alone.
YouTube destinations are judged by Google Ads rules, not a YouTube rulebook
A YouTube campaign is bought inside Google Ads, and its destination is assessed under the same requirements that apply to a Search ad or a Display placement. There is no YouTube-specific landing-page policy to look up. That single fact accounts for a good deal of confusion: advertisers go looking for YouTube page rules, find nothing, and conclude the destination is not really being checked — right up to the point where a campaign is disapproved for it.
What differs is not the rulebook but the conditions under which the page gets exercised. A Search click usually arrives from a browser, within the narrow set of countries a keyword list implies, carrying a referrer and a normal cookie context. A YouTube ad can reach the same URL from an in-app webview on a low-end Android device, in a country the targeting swept in incidentally, with no referrer at all. The policy is constant; the traffic hitting the page is not. Most page-level disapprovals on YouTube live in that gap. For the detection and enforcement side, see how Google's policy and detection apply to YouTube Ads; this article stays on the page itself.
What the destination review weighs
From the destination's point of view the review is not mysterious: it issues a request, assesses what comes back, and compares that against what the video promises. What is worth knowing is which dimensions it weighs, and what a typical failure looks like on each one.
| Dimension | What is required | Typical failure |
|---|---|---|
| Reachability | The URL returns complete content with no referrer, no cookies, a mobile user agent, and from any country in the campaign | The page errors for requests without a referrer, or is only reachable from some regions |
| Consistency | One URL returns the same substance in every context | The offer, product or promise an automated fetch receives differs from what a user receives |
| Relevance | Page content matches what the video promises | The video promotes a specific product and the destination is a generic homepage or an unrelated category |
| Completeness | A complete commercial page: concrete product or service information, contact details, terms and privacy pages, operating entity | A thin intermediate page, or missing legal pages and a working contact route |
| Stability | The page keeps serving the same content after approval; redesigns are ordinary, swapping the substance of the offer is not | The destination is switched to a different product or a different class of offer once the campaign is live |
The first four can be checked at the moment of submission; the fifth is continuous. Stability is the one most often underestimated: approval is not a one-time gate, live campaigns are re-examined, and a destination whose substance is swapped after it clears is treated far more heavily than one that simply failed on the first pass.
Why a page that cleared Search can still fail on YouTube
This is the most counter-intuitive category of rejection: the same URL runs for months on Search without incident, then gets disapproved the moment it sits behind a YouTube campaign. The rules did not change and neither did the page — the way it is reached did. Three differences account for most of these cases.
- The rendering environment. YouTube destinations frequently open inside the app's webview rather than the device's default browser. That environment sends a different user agent, restricts some storage and third-party cookie behavior, and often arrives without a referrer. Any page treating those signals as prerequisites for rendering can go blank there or fall into an error branch.
- Geographic spread. A keyword list narrows a Search campaign's countries by construction; video targeting is usually much broader and sweeps in countries the page has never served. Regional branches, region-locked inventory and destinations reachable only from some markets surface here for the first time.
- Device and network profile. Video audiences skew toward lower-end devices and weaker connections. A page that renders instantly on desktop can time out under those conditions, and a timeout looks the same from the assessing side as a refusal to return.
An over-tight filtering rule cuts both ways here: it blocks invalid traffic, real users arriving from an in-app webview, and the review-stage request alike. On the environment differences see mobile traffic: webview, referrer and fingerprint differences; on calibrating what gets through, see tuning pass rates between too strict and too loose.
The page-level notices that account for most disapprovals
The generic wording of these notices is what makes them expensive: a single line rarely indicates where to look, so advertisers guess. The table below translates the common ones into what to actually inspect on the page.
| Notice | What it usually means | Where to look first |
|---|---|---|
| Destination not working | The fetch received an error, a timeout or a blank body — not necessarily a site-wide outage | Requests with no referrer, no cookies and a mobile user agent; one fetch per campaign country |
| Destination mismatch | The page offers something other than what the video promises, or one URL returns different content depending on how it is reached | Line up each promise in the video against the corresponding content on the page |
| Insufficient content | The destination is an intermediate page or a shell, missing concrete product information, terms, privacy and contact details | Footer links to legal pages, the operating entity, and a contact route that works |
| Category needs a permission | The page falls into a category requiring a permission the account does not hold — unrelated to page quality | Confirm the category call is correct, then apply for the permission rather than editing copy |
| Unsupported claims | Promises on the page run ahead of what the product supports — typically outcome, earnings or timeframe statements | Every result-shaped or numeric statement on the page, and what backs it |
| Circumventing systems | Assessed as one URL serving different substance to verification than to users — a policy matter rather than a quality defect | Every rendering branch keyed on source, user agent, IP or referrer |
The last row is not the same order of magnitude as the other five. Those are fixable quality problems: correct them and resubmit. The last one sits at the policy layer, and repeat occurrences accumulate against the account. On what it covers and how it is assessed, see the Google Ads circumventing systems policy.
Destination mismatch: the notice advertisers most often misread
The usual first reaction to this notice is to check whether the URL was entered wrongly or whether the page is down. In most cases the URL is correct and the page loads fine — the mismatch is at the content layer: the video promotes a specific product or offer, and the destination is a homepage, a category listing, or a page where that product is out of stock, discontinued or repriced. From the assessing side, a user who arrives and cannot get what the ad promised is the definition of a mismatch, regardless of how good the page is in isolation.
The second trigger is easier to overlook: one URL returning different substance depending on how it was reached. Switching currency by market, copy by browser language, or layout by screen width is ordinary commerce and is not a mismatch. The line sits at the offer and the claims — the product, price and promise an automated fetch receives should match what a user receives at that same URL. On where exactly that line falls, see routing versus compliant personalization; on what counts as unambiguously over it, see the red lines.
A pre-flight check before you submit
Running these before submitting removes most page-level rejections. Each is an action rather than a principle.
- Fetch the destination with a mobile user agent, no referrer and no cookies, and confirm a complete page comes back rather than an error, a blank body or a stripped version.
- Repeat once from every country the campaign targets. Video targeting reaches more countries than expected, and regional branches surface here.
- Open it once inside a real in-app webview on a device, not just a desktop browser's mobile emulation.
- Line up every promise in the video against the corresponding content on the page, including price, availability and any timeframe.
- Confirm terms, privacy, contact details and the operating entity are present and reachable.
- Confirm tracking parameters feed measurement and attribution only and never render decisions — the substance returned with and without them should be identical.
- Re-run the same fetches periodically after launch, so a redesign does not quietly reintroduce a branch.
On systematizing this and on judging whether a page returns the same content across contexts, see how to check a page for consistency. For the equivalent requirements on another platform, see Snapchat Ads landing page requirements — the differences are mostly environmental rather than regulatory.
After a page-level disapproval
The useful first move after a disapproval is to reproduce it, not to rewrite copy. Fetch your own destination the way the ad reaches it — mobile user agent, no referrer, no cookies, from a campaign country — and look at what comes back. Most page-level rejections are visible immediately under those conditions, without guesswork.
Isolate the specific cause, fix it, then resubmit. Repeatedly resubmitting an unchanged page is the worst available option: a single disapproval carries limited weight, while repeat occurrences accumulate into an account-level record that slows the review of everything submitted afterwards. On writing the appeal and on keeping the same cause from recurring, see the appeal template and follow-up actions.
One point is worth repeating because it resolves this entire class of problem: have one URL return the same substance to every visit. The presentation layer may vary by market, language and device; the offer and the claims should not. With that in place, most of the rows in the table above stop occurring at all.
Frequently asked questions
Does YouTube have its own landing page policy?
No. YouTube campaigns are bought inside Google Ads and their destinations are assessed under the same Google Ads requirements that apply to Search and Display; there is no separate YouTube rulebook. What changes between formats is not the policy but the conditions under which the page is reached, and most page-level disapprovals on YouTube come from that difference rather than from a rule unique to the format.
Why can a page that runs fine on Search get disapproved on YouTube?
Because the traffic conditions differ. A Search click usually comes from a browser with a referrer, within countries a keyword list implies. A YouTube destination can open inside the app's webview, on a weaker device, from a country the targeting swept in, frequently with no referrer. A page that quietly depends on any of those signals renders blank, partial or into an error branch under the second set of conditions — which reads from the other side as a page that does not work, or one that behaves inconsistently.
What does a destination mismatch notice actually mean?
It usually means the page and the video promise different things, not that the URL is broken. A video advertising a specific product that points at a generic homepage, a category listing, or a page where the product is out of stock, discontinued or repriced all read as a mismatch. The same notice is also returned when one URL serves materially different content depending on how it is reached — but that case sits at the policy layer rather than being a quality defect.
Is language or currency personalization allowed?
Yes. Currency, language, layout and stock differences are ordinary commerce and are expected on any destination serving several markets. The line sits at the offer and the claims: the product, price and promise an automated fetch receives at a URL should be what a user receives at that same URL. Presentation may vary by market; substance should not vary by visitor.
What is the first step after a page-level disapproval?
Reproduce it before changing anything. Fetch the exact destination URL the way the ad reaches it: mobile user agent, no referrer, no cookies, once per campaign country. Most page-level rejections are visible immediately under those conditions. Isolate the cause, fix it, then resubmit — repeatedly resubmitting an unchanged page is what turns one disapproval into an account-level pattern.
Make every visit accountable
The ROAS365 console breaks visit data down by source, region and device, and exports the underlying decision logs — so a question gets answered with evidence rather than explanation.