Interstitials

Google's mobile interstitial penalty explained — which popups get a page demoted, which are exempt (legal gates, login walls, small banners), why it's page-level not site-wide, the desktop expansion, and how to audit and fix.

First published: Jun 27, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #4 in Mobile SEO#91 in Technical SEO#121 on the site

An interstitial is a full-page popup or overlay that blocks a page's main content. Google's intrusive interstitials signal demotes a page when it shows a content-blocking overlay on the transition from a search click — announced August 2016, launched January 10, 2017 (mobile), expanded to desktop in February 2022. It's page-level, not site-wide, and a soft, algorithmic signal — not a manual action. Three types are penalized (immediate full-page popups, standalone interstitials you must dismiss, above-the-fold layouts that mimic an interstitial); three are exempt (legal gates like cookie/GDPR/age, login walls for non-public content, and small easily-dismissible banners). Popups shown after the user engages (exit-intent, timed, scroll) aren't penalized. The 2024 API leak confirmed a violatesMobileInterstitialPolicy boolean. Remove the interstitial and wait for a recrawl — that clears the signal, though Google doesn't guarantee rankings return to their exact prior position.

TL;DR — The intrusive interstitialsIn SEO, interstitials are full-page popups or overlays that block the main content of a page. Google demotes pages with intrusive interstitials shown on the transition from a search click — a page-level signal, with legal gates, login walls, and small dismissible banners exempted. signal is a page-level, algorithmic ranking demotion that fires when a page blocks content on the transition from a search click. Announced August 23, 2016, launched January 10, 2017 (mobile search only), expanded to desktop in February 2022. Three patterns are penalized (immediate full-page popups, standalone interstitials you must dismiss, above-the-fold layouts that mimic an interstitial); three are exempt (legal gates, login walls for non-public content, small easily-dismissible banners). Interstitials shown after engagement (exit-intent, timed, scroll) aren’t penalized — Mueller: it’s about “the interaction between the search click and going through the page and seeing the content.” It’s a soft signal, not a manual action, and not site-wide. The 2024 API leak confirmed a violatesMobileInterstitialPolicy boolean. Remove the interstitial and get a recrawlCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial. to clear the signal — not a guarantee rankings snap back exactly.

What counts as an interstitial

The documented concern is accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all. of main content, not every modal or banner. Evidence for this claim Official or primary documentation supporting the adjacent article claim, with scope limited to the source's published description. Scope: No ranking guarantee or undisclosed system mechanics are inferred beyond the cited source. Confidence: high · Verified: Google: Avoid intrusive interstitials Whether an implementation is intrusive depends on its size, timing, purpose, and effect on access. Evidence for this claim Official or primary documentation supporting the adjacent article claim, with scope limited to the source's published description. Scope: No ranking guarantee or undisclosed system mechanics are inferred beyond the cited source. Confidence: high · Verified: Google: Avoid intrusive interstitials

Google’s definition is precise: “Intrusive interstitials and dialogs are page elements that obstruct users’ view of the content, usually for promotional purposes. Interstitials are overlays on the whole page and dialogs are overlays only on a part of the page.” The distinction between interstitial (whole page) and dialog (part of the page) is Google’s, and it matters — a small partial overlay is treated differently from a full-page block.

The key word throughout is intrusive. Not every overlay is a problem; the signal targets the ones that get between a searcher and the content they clicked for.

The timeline (and the part most articles get wrong)

This topic is muddied by people conflating two separate events, so let me lay the sequence out cleanly:

  • November 2015 — app install interstitials. Before the broader signal, Google started treating pages with an app-install interstitial that hid significant content as not mobile-friendlyWhether a page is easy to use on a mobile/touch device — legible text without zooming, tap targets sized and spaced to avoid mis-taps, content that fits the viewport with no horizontal scrolling, and no intrusive interstitials. Distinct from mobile-first indexing and Core Web Vitals.. This came out of a July 2015 case study where Google foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. its own app-download interstitial on Google+ was hurting the experience. This is a distinct, earlier action — not the 2017 penalty.
  • August 23, 2016 — announcement. Google announced the broader intrusive interstitials signal, with an effective date of January 10, 2017.
  • January 10, 2017 — launch. The signal went live for mobile search. Both John Mueller and Gary Illyes confirmed it was rolling out that day.
  • February 2022 — desktop expansion. Google extended page experienceGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. signals, including the absence of intrusive interstitials, to desktop rankings. (Mobile-friendliness was not part of the desktop signal, but interstitials were.)
  • 2023–2024 — Page Experience report retired. Google removed the standalone Page Experience report from Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. and dropped “page experience” as a named ranking system — but the interstitial signal itself keeps operating. This is the single most confused point on the topic: the report went away, the signal did not.

What actually triggers the signal

Three patterns, straight from the 2016 announcement:

  1. A popup that covers the main content — either immediately after the user navigates to the page from search, or while they’re looking through it.
  2. A standalone interstitial the user must dismiss before accessing the main content.
  3. An above-the-fold layout that appears to be a standalone interstitial, with the original content inlined underneath the fold.

That third one is the trap. You don’t need a literal JavaScript overlay — a page whose top section looks like an interstitial, pushing the real content below the fold, is treated the same way.

What’s explicitly allowed

Also from the announcement — three exemptions:

  1. Legal-obligation interstitials — cookie usage, age verification, GDPR consent.
  2. Login dialogs on sites where content isn’t publicly indexable — private content like email, or content behind a paywall.
  3. Banners that use a reasonable amount of screen space and are easily dismissible — Google cites the app-install banners provided by Safari and Chrome as the model.

And critically — timing exempts a popup. Mueller has been clear that the signal only cares about the entry transition: “What we’re looking for is, really, interstitials that show up on the interaction between the search click and going through the page and seeing the content… What you do afterwards, like if someone clicks on stuff within your website or closes the tab or something like that, then that’s kind of between you and the user.” So exit-intent popups, popups timed to appear after the user has already been engaging with the page, and scroll-depth popups are not penalized — they fire after the user has already reached the content. Google hasn’t published a specific delay or scroll-percentage threshold that guarantees safety; the test in Mueller’s quote is whether the overlay interrupted the search-click-to-content transition, not a stopwatch number, so treat any “wait 20 seconds” figure you see elsewhere as a rule of thumb, not an official one.

How severe is it, really

Lightweight. Google framed it from day one as “just one of hundreds of signals used in ranking,” and noted that “the intent of the search query remains a very strong signal, so a page may still rank highly if it has great, relevant content.” Mueller has called it “a softer factor” that “wouldn’t be applied across the whole website” — a “slight demote.” So: a ceiling, not a cliff. Sites don’t fall to page 100 over a popup, and brand and high-relevance queries are largely insulated.

It’s page-level, not site-wide — and the API leak proves it

This is the technical spine. The penalty applies per page, not to your whole domain. Mueller said as much — it “wouldn’t be applied across the whole website.” The 2024 Google Content Warehouse API leak then surfaced the implementation: a violatesMobileInterstitialPolicy boolean (a true/false flag that demotes a page when it violates the policy), alongside an adsDensityInterstitialViolationStrength integer scaled 0–1000 for severity. A per-document boolean is exactly what “page-level” looks like under the hood.

Not a manual action

There’s no manual penalty and no reconsideration request. It’s purely algorithmic. Starting in April 2022, Google did begin sending advisory GSC email notices (“Improve your page experience by removing intrusive interstitials from [domain]”) — but those are informational, not enforcement. You don’t appeal; you fix and recrawl.

The cloaking trap — don’t

A tempting “fix” is to detect GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. and hide the interstitial from it while still showing it to users. Don’t. That’s cloaking. Gary Illyes called botA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index.-detection interstitials “the last search-friendly thing you can do.” If you do serve different content to GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. for a legitimate reason, remember Mueller’s caveat that when Google crawls and indexes a page, “we don’t send a referrer” — so referrer-based logic that keys off “came from Google search” won’t behave the way you expect for the crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index..

For interstitials you genuinely need — age gates, consent screens — the rule is to overlay on top of the HTML, not replace it. Mueller: “The important part is that you’re showing this on top of the HTML page; not that you’re showing it instead of the HTML page.” Google tries to “recognize legal interstitials and ignore those.” Two corollaries:

  • For mandatory age gates, Google recommends letting Googlebot crawl the content without triggering the gate.
  • Don’t redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. every URL to a single consent page — that strips those URLs from search. Overlay the consent on each page instead.

One caveat worth being precise about: Google’s Search exception for “legal obligation” interstitials is guidance for how Search treats the overlay — it isn’t a legal determination that your gate is actually required. Whether a given consent or age gate is legally mandatory depends on your jurisdiction and business, and that’s a question for qualified legal counsel, not an SEO guide. Don’t build a gate you don’t legally need just because Google says a legal gate wouldn’t hurt you in Search.

App install interstitials

The original 2015 problem still has a clean answer: instead of a full-page app-install prompt, use Smart App Banners (Safari), Chrome’s in-app install experience, or a small HTML banner. These are the “reasonable screen space, easily dismissible” pattern Google explicitly blesses.

What about Bing

Bing has no named, dated interstitial penalty equivalent to Google’s 2017 signal. But it isn’t a free-for-all: Bing’s Webmaster Guidelines weigh ad intrusiveness as part of overall page quality — whether ads “take up prime real estate” versus being separated from content, and whether users can mentally separate content from ads. Pop-ups and “grey-overs” are flagged in Bing’s web spam filtering. Practical takeaway: no specific penalty to chase, but intrusive overlays still hurt you in Bing’s quality assessment.

How to audit for intrusive interstitials

  1. Chrome DevTools — switch to mobile emulation and visit your top landing pages as a fresh visitor. Does anything block the content on arrival?
  2. Screaming Frog / a crawler — crawl with a mobile user-agent and pull rendered-page screenshots to spot overlays at scale.
  3. Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. — check Messages for the advisory interstitial notices, and use URL Inspection to see what Googlebot renders.
  4. Manual spot-check — your highest-traffic mobile landing pages first; those are where the demotion costs the most.

How to fix and recover

  • Replace full-page overlays with top/bottom banners that use modest screen space and are easy to dismiss.
  • Move promotional popups to fire after engagement (scroll, timer, exit-intent) rather than on entry.
  • For legal gates, overlay on the HTML, don’t redirect.
  • For app installs, use Smart App Banners / small prompts.

Recovery is algorithmic — there’s nothing to appeal. Remove the interstitial and wait for Googlebot to recrawl; for important pages, request indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. via GSC URL Inspection to speed it up. Once the recrawl reflects the fix, the interstitials signal stops working against the page — that’s not the same as a guaranteed ranking bounce back to the exact prior position. Google has never published a recovery timeline, and rankings depend on “hundreds of signals,” not this one alone, so treat removal as clearing an obstacle rather than a promise of a specific result.

Where this sits

Interstitials are a page experience concern alongside Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. and HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.' — the cluster of signals about how a page feels to use rather than what it says. Because the original penalty was mobile-first and is still most consequential on mobile, it lives here in mobile SEOMobile SEO is the practice of optimizing a site so it ranks well when crawled and indexed by a mobile (smartphone) user agent and delivers a fast, usable experience on phones. Since Google completed mobile-first indexing, the mobile version is the primary version Google uses for indexing and ranking — so mobile SEO is effectively baseline SEO for every site.. For how Googlebot fetches and renders the pages it’s judging, see CrawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor..

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.