Home / Blog / Mobile Interstitial Penalty

Mobile interstitial penalty: keep your popups compliant

Google does not ban popups, but it demotes pages where a popup blocks the content a mobile visitor came to read. A fullscreen modal on page load is the risky pattern. A small dismissible bar, or a popup triggered after the visitor has engaged with the page, stays within the rules. Here is what Google actually penalizes, what stays allowed, and the setup that keeps you compliant.

Key takeaway: never cover the main content on page load for mobile visitors. Trigger after engagement (scroll, delay, or exit intent), prefer a top or bottom bar over a fullscreen modal, cap at once per session, and keep the close button visible. Legal notices like cookie consent are exempt.

GrowthTools general widget settings: trigger, frequency and display rules that keep popups compliant
General widget settings in the GrowthTools dashboard: trigger, frequency cap and display rules, the three controls that decide compliance.

What Google actually penalizes

Google introduced the intrusive interstitial signal for mobile search in January 2017, and its current guidance (updated December 2025) keeps the same line: interstitials and dialogs that obstruct the content "may lead to poor search performance". Google's wording is careful. It never uses the word "penalty" and calls the signal one of hundreds. In practice, three mobile patterns trigger it:

  • A popup covering the main content right after arrival from search. The visitor taps a result and lands on an overlay instead of the article or product page.
  • A standalone interstitial before the content. The visitor must dismiss an overlay before the content becomes visible at all.
  • A layout that mimics an interstitial. The above-the-fold area looks like a fullscreen ad while the real content is pushed below the fold.

The current guidance adds two more mistakes for all devices, unless a law requires them: do not obscure the entire page with an interstitial, and do not redirect the visitor to a separate page to collect consent or input. Keep the form on the page itself.

What stays allowed

Most everyday lead capture is untouched by these rules. Google explicitly exempts:

  • Legal notices. Cookie consent banners, age gates and privacy notices are exempt. Overlay them on the content rather than redirecting, and let search crawlers see the page behind them.
  • Login dialogs for private content. Paywalled pages that are not indexable, and login prompts on private areas like email, do not trigger the signal.
  • Small banners using a reasonable part of the screen. Banners that take up only a small fraction of the screen and are easy to dismiss are Google's recommended alternative to fullscreen interstitials. Google gives no percentage, so treat "small" as a judgment call: a slim top or bottom bar, not half the viewport.

Note what Google does not promise: no safe delay in seconds, no safe screen coverage ratio, and no credit for exit intent by name. A timed popup is safer because the visitor has already seen the content, not because a particular number of seconds is approved.

Risky versus safe patterns

PatternVerdictWhy
Fullscreen modal on page load (mobile)RiskyCovers the main content before the visitor reads anything.
Popup that must be dismissed to see contentRiskyMatches the standalone interstitial pattern exactly.
Redirect to a separate signup pageRiskyExplicitly listed in the current guidance; crawlers lose the page.
Top or bottom bar, dismissibleSafeGoogle's recommended format: small fraction of the screen.
Popup after scroll, delay or exit intentSafeContent was readable first; nothing blocked on arrival.
Cookie or age-gate overlayExemptRequired by law; keep it overlaid, not redirected.

The compliant setup in GrowthTools

  1. Pick a bar for mobile traffic. Create an email capture bar or announcement bar instead of a modal for the mobile version of the campaign. It sits at the top or bottom and leaves the content readable.
  2. Trigger after engagement, never on load. Use a scroll-depth trigger, a time delay, or exit intent (see the exit-intent popup guide for the trigger options). The visitor reads first, the offer comes second.
  3. Cap frequency at once per session. One appearance per visit is enough to convert without harassing the visitor or looking like a persistent overlay to crawlers.
  4. Keep dismissal obvious. Leave the default close button visible and large enough to tap. A hidden or tiny close control is exactly the dark pattern the guidance targets.
  5. Keep the form on the page. Collect the email inside the widget and send it to your list by webhook or integration. Never bounce the visitor to a separate signup page.

If you also worry about loading performance, read how popup scripts affect Core Web Vitals: an overlay that sits on top of the page (instead of pushing content down) and a deferred script keep your layout and paint scores intact. For the general capture strategy behind these widgets, start with how to capture more leads from the traffic you already have.

Capture emails without risking your rankings.

Bars, delayed triggers and once-per-session caps are built into every GrowthTools widget. Free plan for one site, no card.

Create your free account

Honest limits

Compliance is about configuration, not about the tool: any widget, from any vendor, becomes intrusive if you show it fullscreen on page load. GrowthTools gives you the compliant controls, but the trigger and format choices are yours on each campaign. Also note that the guidance describes ranking effects, not a fixed penalty with a recovery procedure. If traffic drops after adding a popup, check the mobile rendering first, then the usual suspects (content changes, technical issues) before blaming the widget. Browse the full widget range on the GrowthTools widget catalog.

Questions

Only if it blocks the content a visitor came to read. Google demotes pages where a popup covers the main content on arrival from search, forces dismissal before the content is visible, or pushes the real content below the fold. A small dismissible banner or a popup triggered after engagement does not create that problem.

Popups required by law (cookie consent, age gates, privacy notices), login dialogs for content that is not indexable, and banners that take up only a small fraction of the screen and are easy to dismiss. Legal notices are exempt from the interstitial guidance.

Google names no safe number of seconds and no safe screen size. The safer pattern is to trigger after engagement (scroll depth, time on page, or exit intent) instead of on page load, so the visitor has already seen the content when the popup appears.

Use a top or bottom bar instead of a fullscreen modal for mobile visitors, trigger it on scroll or delay rather than on page load, cap it at once per session, keep the close button visible, and never redirect visitors to a separate signup page.

Compliant capture, from the first visit.

Start free on one site, then scale to bars, modals and social proof that respect both visitors and search engines.

Create your free account