Intrusive Interstitials: What Google Penalizes and How to Fix It

What this check flags

This check fires when our crawler detects popups, modals, or overlays that cover the main content of a page on a mobile viewport, especially ones that appear immediately on load. That includes newsletter modals, promo overlays, app install interstitials, and layouts where the above-the-fold area is effectively a standalone ad. The crawler evaluates what a first-time mobile visitor arriving from search would actually see, the exact scenario Google measures.

What Google actually penalizes

In August 2016, Google announced that pages where content is not easily accessible on the transition from mobile search results may not rank as highly. The signal went live on January 10, 2017, and was later folded into Google's page experience guidance. Three patterns are explicitly called out:

First, a popup that covers the main content immediately after the user lands from search, or while they scroll. Second, a standalone interstitial the user must dismiss before reaching any content. Third, a layout where the above-the-fold section looks like a standalone interstitial, with the actual content tucked underneath.

Two scoping details matter. The signal applies to the transition from a Google mobile search result to your page, not to popups deeper in the click path. And it is page-level, so one offending template can drag down every URL that uses it. Google has said great content can still rank despite the signal, but on competitive queries you are handing rivals an edge for nothing.

What is exempt

Google explicitly excluded three categories, when used responsibly:

Legal obligations. Interstitials the law requires, such as cookie consent notices and age verification gates, are not penalized. A GDPR consent banner will not hurt you.

Login walls. Login dialogs on sites where the content is private and not publicly indexable, like inboxes or members areas, are fine. If Googlebot cannot index the content anyway, the wall is expected.

Reasonably sized banners. Banners that use a reasonable amount of screen space and are easily dismissible get a pass. Google never published a pixel threshold, but its examples, like Safari Smart App Banners, occupy a thin strip at the top of the screen. A common rule of thumb is to stay well under a quarter of the viewport. The thinner, the safer.

The gray zone

Email capture popups are the classic borderline case. A small, dismissible slide-in after meaningful engagement is generally safe. A full-screen takeover on arrival from search is exactly what the signal was built for. We have all lived it: you tap a result, and before you can read a single sentence a damn newsletter popup smothers the article you came for. That experience is the target, and your modal is not exempt just because the offer is good.

App install interstitials are the original offender, the case Google studied before announcing the signal. Promote your app with a small install banner, not a full-screen door.

How to fix it

Delay your triggers. Never fire popups on page load. Trigger on engagement instead: scroll depth past 50 percent, 30 to 60 seconds on page, or a second pageview. By then the user has accessed the content, which is the whole point.

// Fire only after real engagement, never on load
let shown = false;
window.addEventListener('scroll', () => {
  const depth = window.scrollY / (document.body.scrollHeight - innerHeight);
  if (!shown && depth > 0.5) {
    shown = true;
    showSignupBanner(); // banner, not full-screen modal
  }
}, { passive: true });

Exit intent on desktop only. Exit-intent popups rely on cursor movement toward the browser chrome, which does not exist on touch devices. Keep them desktop-only and verify your mobile breakpoint genuinely suppresses them rather than restyling them.

Banners instead of full-screen overlays. Convert takeover modals into top or bottom banners that leave the content readable and carry an obvious close button. Inline signup forms mid-article often convert respectably without touching the signal at all.

Frequency capping. Set a cookie or localStorage flag when a popup is shown or dismissed, and respect it for at least 7 to 30 days. Nobody should see the same modal on every pageview.

How to diagnose it

Open your top organic landing pages on a real phone, arriving from an incognito Google search so no suppression cookies exist. That first paint is what matters. In Chrome DevTools, use mobile emulation with cookies cleared and watch the first few seconds of rendering. Audit every popup tool in your tag manager, since most ship with on-load triggers by default. Then prioritize: fix the templates behind your highest-impression URLs first.

Common mistakes

Assuming the cookie exemption covers a consent banner with a giant promo bolted on; the exemption is for the legal notice, not what you attach to it. Hiding the popup from Googlebot while showing it to users, which is cloaking and a far worse problem. Testing only the homepage when search traffic actually lands on articles and product pages. And shipping a banner so tall it is a full-screen modal in everything but name.

FAQ