Google’s mobile interstitial guidance specifically exempts legally required interstitials, cookie and GDPR-style consent banners, age-verification gates for legally restricted content, along with reasonably-sized banners generally, while targeting interstitials that hide substantial content immediately upon arrival from a search result without a legal basis for doing so. The distinguishing factors Google’s documentation actually names are legal necessity, dismissibility, and how much of the viewport or underlying content gets obscured on entry, not a specific automated visual-detection algorithm scoring every popup against a numeric coverage threshold.
The exemptions Google explicitly lists
Google’s Search Central documentation on mobile popup interstitials names specific categories that are exempted from being treated as a problematic interstitial regardless of their visual presentation:
- Interstitials required by law, most notably cookie-consent and privacy-notice banners mandated by regulations such as GDPR, along with age-verification interstitials for content legally restricted by age (alcohol, tobacco, adult content categories where verification is a legal requirement rather than a business choice).
- Login dialogs on sites where content isn’t publicly indexable, since requiring login to view genuinely private or paywalled content isn’t the kind of “hide content the user came for” interstitial the guidance targets, if the underlying content itself isn’t meant to be publicly accessible in the first place.
- Reasonably-sized banners that use a reasonable amount of screen space and are easily dismissible, such as app-install banners or promotional banners that don’t obscure substantial content and can be readily closed.
What Google’s guidance actually targets
The interstitials Google’s guidance describes as problematic are ones that appear immediately or soon after a user arrives from a search result and make it difficult to access the main content the user was searching for, particularly standalone popups that must be dismissed before viewing content, interstitials that display as part of the normal page flow but push substantial content below the fold behind a popup obscuring the viewport, and app-install interstitials that use a large percentage of viewport space in a way that isn’t easily dismissed and isn’t legally required.
The core distinguishing logic in Google’s own documentation isn’t a screen-coverage percentage disclosed as a hard number; it’s a combination of factors evaluated together: whether there’s a legal basis compelling the interstitial’s existence, whether the interstitial can be easily dismissed by the user, and how much of the actual content the user was seeking gets obscured on arrival. A cookie consent banner satisfies the legal-basis exemption regardless of how much of the screen it occupies, because its existence is compelled by law rather than a business or marketing choice; a promotional popup with no legal basis, occupying a comparable amount of screen space, doesn’t have that same exemption available to it.
Why there’s no disclosed numeric coverage threshold
It’s a common misconception that Google enforces a specific screen-coverage percentage algorithmically, some fixed number above which any interstitial becomes automatically penalizable. Google’s public guidance describes categories and examples rather than a disclosed hard numeric cutoff for coverage percentage. This is consistent with how Google generally handles disclosure of guideline-enforcement specifics: providing illustrative examples and named exemption categories clear enough for site owners to reason about their own implementation, without publishing an exact algorithmic threshold that would function as a precise target to design just barely within. The honest, accurate framing is that Google evaluates interstitial patterns against the named categories and general principles (legal necessity, dismissibility, content obstruction) rather than against a specific disclosed percentage.
The practical distinguishing test for a real implementation
Applying Google’s stated categories to a real cookie-consent banner implementation, the compliance question comes down to: is the interstitial’s existence actually required by an applicable law (most cookie-consent regimes genuinely do require this, making the legal-necessity exemption straightforwardly applicable), and is it implemented in a way that’s reasonably dismissible rather than functioning as a permanent, undismissable block on all content access. A cookie banner that can be accepted, rejected, or dismissed, after which the underlying content becomes accessible, fits comfortably within the exemption. An interstitial using a cookie-consent framing as a pretext while actually functioning as a persistent, hard-to-dismiss block designed primarily to serve some other purpose (forcing engagement with a marketing prompt attached to the same dialog, for instance) moves further from the narrow legal-necessity exemption and closer to the pattern Google’s guidance actually targets.
Practical implication
Implement cookie and privacy-consent interstitials as genuinely dismissible dialogs that satisfy the actual legal requirement compelling them, rather than using the legal-consent framing to also smuggle in unrelated marketing or engagement prompts within the same undismissable interstitial. Don’t attempt to reverse-engineer a specific safe screen-coverage percentage from Google’s guidance, since no such number is published; instead, evaluate any mobile interstitial against Google’s actual named criteria, is there a genuine legal basis, can the user dismiss it easily, and how much of the content the user searched for does it obscure on arrival, as the basis for whether it falls inside or outside the documented exemptions.
