Mobile Pop-ups After Google’s Guidelines: What Still Works
What the intrusive interstitial guidance actually covers, what it exempts, and the formats that stay safe.
On this page
The short version
- The guidance covers content obscured immediately after arriving from search. Timing and coverage are what matter, not the word pop-up.
- Three things are explicitly exempted: legal notices like cookie or age consent, login dialogs for gated content, and a banner using a reasonable amount of screen space.
- A small sticky bar is the format that stays clearly safe, and it is the one most sites should use on mobile regardless.
Search guidance on intrusive interstitials is widely paraphrased as "pop-ups hurt mobile rankings", which is imprecise enough to cause both unnecessary caution and real mistakes.
What it actually describes is a pattern: a visitor arrives from search on a mobile device and the content they came for is obscured, either immediately or as a standalone interstitial they must dismiss first.
The three parts of the pattern
First, the traffic source. The concern is about arrivals from search — a reader who has been on the site for three pages is in a different situation.
Second, the timing. Immediately after arrival is the case described. An interruption later in the visit, after the reader has engaged with the content, is not the same thing.
Third, the coverage. Something obscuring the main content is the issue; a banner occupying a reasonable strip is not.
All three together are the pattern. Break any one of them and you are outside it.
What is covered and what is not
| Pattern | Covered? |
|---|---|
| Full-screen overlay on arrival from search | Yes — the central case |
| Standalone interstitial before the content | Yes |
| Layout where the top of the page is a full-screen promo | Yes |
| Cookie or age consent notice | Exempt |
| Login dialog for genuinely gated content | Exempt |
| Banner using a reasonable amount of screen | Exempt |
| Overlay after meaningful engagement | Not the described pattern |
| Exit-intent equivalent on mobile | Not the described pattern, but see below |
What to run on mobile instead
A sticky bar at the bottom, one line tall, with a button that expands into the form. It is permanently available, occupies a strip rather than a screen, never obscures the content, and sits within the exemption for a banner using a reasonable amount of space.
It converts less per impression than an overlay and is shown to everyone continuously, which closes much of the gap in practice.
The other option worth using is an in-content form placed after the section it relates to. On a phone that is not an interruption at all — it is part of the article, and it is the best-performing capture point on most mobile pages.
The mobile substitutes for exit intent
Since there is no cursor, tools offer back-button interception, scroll-up detection and inactivity timers. None of these detect a visit ending, and one of them actively hijacks a control the reader pressed.
Back-button interception is the one to rule out entirely. It overrides a deliberate action, browsers increasingly work against it, and it produces the strongest negative reaction of anything in this category. Whatever the conversion rate, it is not worth being the site that does that.
How to actually test it
Desktop emulation in developer tools does not reproduce this. It gets the viewport right and misses the two things that matter: the browser chrome that occupies part of the screen, and the arrival path from a search result.
Test it properly by searching for one of your own pages on a real phone and tapping through from the result. That is the exact sequence the guidance describes, and it is the only way to see what a visitor sees — including whether the pop-up lands on top of the content before it has finished rendering.
Do it on a small phone as well as a large one. A banner occupying a reasonable strip on a large screen can take a third of a small one, and the small screen is where the reader has least room to spare.
Mobile pop-up check
- Nothing obscures the content on arrival from search
- No full-screen overlay at any point in the visit
- A sticky bar or in-content form is the primary capture
- The bar occupies a strip, not a screen
- The back button is never intercepted
- Dismissal targets are at least 44px and clear of the form
- Tested on a real phone, arriving from a search result
Frequently asked questions
Does the guidance apply to traffic that is not from search?
The ranking consideration concerns search arrivals. The reader experience concern applies to everyone, and that is the reason not to do it regardless of where they came from.
Is a cookie consent banner safe?
Consent notices required by law are explicitly exempted. That exemption covers the consent notice itself, not a marketing offer bundled into it.
How much of the screen can a banner take?
The guidance says a reasonable amount rather than a figure. A single line that expands on tap is comfortably within any reading of it; something taking a third of a small screen is not.