Interstitials

TL;DR — An interstitial is a popup or overlay that covers a page’s main content. Google can lower a page’s ranking if it shows one of these right when a visitor arrives from search and they have to close it before reading anything. The fix is simple: don’t block the content on arrival. Cookie banners, age checks, login walls for private content, and small easy-to-close banners are all fine.

What an interstitial is

Google’s guidance discourages intrusive interstitials that obscure main content, especially on transition from search results. 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: 2026-07-14 Google: Avoid intrusive interstitials It explicitly recognizes exceptions such as legal notices and appropriately sized banners. 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: 2026-07-14 Google: Avoid intrusive interstitials

When you click a result in Google and the page slaps a full-screen popup over the content before you can read a word — “Subscribe to our newsletter!”, “Get 10% off!”, “Download our app!” — that popup is an interstitial. It sits between you and the thing you came for.

Google doesn’t like this on mobile, because it’s a frustrating experience: you tapped a result expecting an answer and got a wall instead. So back in 2017 Google started slightly demoting pages that do it.

Which popups are a problem

Only the ones that block the content right as you arrive from search. The classic offenders:

1. A popup that covers the page immediately after you click through from Google.
2. A standalone screen you have to dismiss before you can see anything.
3. A layout where the top of the page looks like a popup and the real content is hidden below it.

Which popups are fine

A lot of them, actually:

• Cookie consent and GDPR banners — required by law, so they’re exempt.
• Age verification — same idea.
• Login walls for content that isn’t public anyway (think paywalled articles or your email inbox).
• Small banners that take up a reasonable bit of the screen and are easy to close.
• Popups that show up later — after you’ve scrolled, after a timer, or when you go to leave the page (exit-intent). These don’t count, because they don’t block your entry to the content.

The things most people get wrong

• It’s not site-wide. Only the specific pages with the bad popup are affected, not your whole site.
• It’s not a manual penalty. There’s no warning to appeal. It’s an automatic ranking factor, and Google has called it a “softer” one — strong, relevant content can still rank.
• Desktop counts too now. It started as a mobile-only thing, but since 2022 it applies to desktop search as well.
• Newsletter boxes built into the page are fine. It’s overlaying and blocking the content that’s the problem, not having a signup form at all.

Want the timeline, the exact Google quotes, the 2024 API leak detail, and how to audit and fix it? Switch to the Advanced tab.

TL;DR — The intrusive interstitials 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 recrawl to clear the signal — not a guarantee rankings snap back exactly.

What counts as an interstitial

The documented concern is accessibility 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: 2026-07-14 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: 2026-07-14 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-friendly. This came out of a July 2015 case study where Google found 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 experience 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 Console 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 Googlebot and hide the interstitial from it while still showing it to users. Don’t. That’s cloaking. Gary Illyes called bot-detection interstitials “the last search-friendly thing you can do.” If you do serve different content to Googlebot 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 crawler.

Implementing legal gates correctly

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 redirect 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 Console — 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 indexing 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 Vitals and HTTPS — 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 SEO. For how Googlebot fetches and renders the pages it’s judging, see Crawling.

AI summary

A condensed take on the Advanced version:

• Interstitials = full-page overlays that block content. Google: interstitials cover the whole page, dialogs cover part of it. The signal targets the intrusive ones.
• Timeline: app-install interstitials penalized Nov 2015 (separate event) → broader signal announced Aug 23, 2016 → launched Jan 10, 2017 (mobile) → expanded to desktop Feb 2022. The Page Experience report was retired (2023–24) but the signal still operates.
• Three penalized types: (1) popup covering content immediately after the search click; (2) standalone interstitial you must dismiss; (3) above-the-fold layout that mimics an interstitial with content below the fold.
• Three exempt types: (1) legal gates (cookie/GDPR/age); (2) login walls for non-public content; (3) small, easily-dismissible banners.
• Timing exempts popups: exit-intent, timed, and scroll-triggered popups fire after engagement and aren’t penalized — the signal is about the search-click-to- content transition only.
• Page-level, not site-wide; soft, not severe. “One of hundreds of signals,” a “softer factor,” a “slight demote.” Not a manual action — GSC notices (2022+) are advisory.
• 2024 API leak confirmed a violatesMobileInterstitialPolicy boolean (per-page) plus an adsDensityInterstitialViolationStrength 0–1000 severity score.
• Don’t cloak the interstitial from Googlebot — “the last search-friendly thing you can do” (Illyes). For legal gates, overlay on the HTML, don’t replace/redirect.
• App installs: use Smart App Banners / small prompts, not full-page prompts.
• Recovery is algorithmic: remove it, get a recrawl, and the signal stops working against you — not a guarantee rankings return to the exact prior position, since hundreds of other signals factor in too.
• Legal gates aren’t a legal opinion: Google’s exemption for cookie/age/consent interstitials describes how Search treats them, not whether your jurisdiction actually requires one — that’s a question for counsel, not this article.

Official documentation

Primary-source documentation from the search engines.

Google

• Avoid intrusive interstitials and dialogs — the live doc: interstitial vs. dialog, what’s penalized, legal-gate and app-install guidance.
• Helping users easily access content on mobile (Aug 2016 announcement) — the original signal announcement, Jan 10 2017 effective date, the three penalized and three allowed types.
• Google case study on app download interstitials (Jul 2015) — the earlier app-install action and the Google+ UX data behind it.
• Bringing page experience to desktop (Nov 2021) — the Feb 2022 desktop expansion of page experience signals, including intrusive interstitials.

Bing / Microsoft

• Bing Webmaster Guidelines — no named interstitial penalty, but ad intrusiveness factors into page quality.
• Web Spam Filtering (Aug 2014) — pop-ups and “grey-overs” among the ad-quality signals Bing flags.

Accessibility standards (not a Google/Bing signal, but a build requirement)

• WAI-ARIA APG: Dialog (Modal) Pattern — the focus-containment, keyboard, and labeling requirements for a modal overlay.
• web.dev: The inert attribute — how to make background content non-interactive and unannounced while a modal is open.

Quotes from the source

On-the-record statements from Google. Each link is a deep link that jumps to the quoted passage on the source page.

Google — what an interstitial is

• “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.” — Google Search Central docs. Jump to quote

Google — the original announcement (the accuracy spine)

• “Pages where content is not easily accessible to a user on the transition from the mobile search results may not rank as highly.” — Doantam Phan, Google. Jump to quote
• “Showing a popup that covers the main content, either immediately after the user navigates to a page from the search results, or while they are looking through the page.” Jump to quote
• “This new signal is just one of hundreds of signals used in ranking, and the intent of the search query remains a very strong signal, so a page may still rank highly if it has great, relevant content.” Jump to quote

John Mueller, Google — on timing (why exit-intent/timed popups are fine)

• “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.” Read the coverage

John Mueller, Google — on severity and scope

• “That’s something that is more probably a softer factor. And it’s something that wouldn’t be applied across the whole website.” Read the coverage
• “This is kind of like something where we would slightly demote the website in search.” Read the coverage

John Mueller, Google — on legal interstitials

• “We try to recognize legal interstitials and ignore those. So things like privacy policy, the data protection interstitials, those things we try to recognize and skip over.” Read the coverage
• “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.” Read the coverage

Gary Illyes, Google — on cloaking the interstitial from bots

• Bot-detection interstitials are “the last search-friendly thing you can do.” Read the coverage

Is this interstitial safe to publish?

Does it cover the main content when a search visitor first arrives?

• No, it is a small banner that leaves content accessible: Keep it compact and easy to dismiss, then test common mobile viewports.
• Yes: Continue.

Is access required for a legal obligation or genuinely private content?

• Yes, it is a consent, age, or login gate with a real requirement: Use the least obstructive implementation that satisfies that requirement and keep the underlying page signals accurate.
• No, it is promotional, an app install pitch, or email capture: Do not show it on arrival. Use an inline module, small banner, or a prompt after meaningful engagement.

Does the server or client show Googlebot a cleaner page than users receive? If yes, stop. Apply the same policy to crawlers and users; crawler-specific suppression creates a cloaking risk rather than fixing the experience.

Is my interstitial safe? — audit checklist

Work top to bottom. The first section is the “am I at risk” test; the second is the step-by-step audit.

Penalized — fix these

• A popup covers the main content immediately after a visitor arrives from search.
• A standalone screen must be dismissed before any content is visible.
• The above-the-fold area looks like an interstitial, with real content pushed below the fold.
• A full-page app-install prompt blocks content on arrival.
• All URLs redirect to a single consent/interstitial page (strips them from search).

Allowed — these are fine, leave them

• Cookie / GDPR consent overlay (legal — and overlaid on the HTML, not replacing it).
• Age verification gate (legal; let Googlebot crawl the content without triggering it).
• Login wall for genuinely non-public / paywalled content.
• Small, easily-dismissible banner using reasonable screen space (Safari / Chrome app-install banner style).
• Popup fires after engagement — exit-intent, timed after real dwell time, or scroll-depth, not on entry. (Google hasn’t published a specific “safe” delay or scroll percentage — the test is whether it interrupted the arrival, not a stopwatch number.)
• Inline signup form embedded in the content (not an overlay).

Accessibility — a dismissible overlay isn’t automatically an accessible one

• Focus moves into the dialog when it opens and stays contained there (no tabbing out to background content) while it’s open.
• There’s an operable keyboard close path — Escape and/or a reachable, labeled close control — not just a mouse-only “X.”
• Focus returns to a sensible place (typically the element that triggered it) after the dialog closes.
• Background content is inert while the modal is open — not focusable or announced by a screen reader in that state. (The inert attribute handles the focus/interaction part; it doesn’t supply labeling or the focus workflow above on its own.)

Step-by-step audit

• Open your top landing pages in Chrome DevTools mobile emulation as a fresh visitor — is content blocked on arrival?
• Crawl with a mobile user-agent (Screaming Frog) and review rendered-page screenshots for overlays at scale.
• Check Search Console Messages for the advisory interstitial notice.
• Use URL Inspection to confirm what Googlebot renders.
• Prioritize highest-traffic mobile pages — that’s where the demotion costs most.
• After fixing: request a recrawl in URL Inspection; recovery is algorithmic (no reconsideration request).
• Confirm you’re not cloaking the interstitial from Googlebot.

Rankings dropped after an interstitial release

1. Confirm the timing and scope. Match the release timestamp to affected landing pages, device classes, templates, and search-entry behavior. If unaffected pages also fell, continue investigating broader causes in parallel.
2. Reproduce a search-like first visit. Use a clean mobile session and direct entry to the affected URL. If content is blocked immediately, capture the viewport and trigger conditions; if not, test campaign, geo, consent, and frequency variants.
3. Classify the gate. If it is promotional, disable the arrival trigger now. If it is legally required or protects private content, reduce it to the necessary scope rather than removing the requirement.
4. Ship the safer pattern. Replace the overlay with an inline unit, small banner, or post-engagement prompt. If the content remains blocked, return to step 3.
5. Verify parity. Test ordinary users and Googlebot-equivalent rendering. If the experiences differ by crawler identity, remove that special case before release.
6. Request recrawl and monitor page-level recovery. Annotate the fix and compare affected pages with a stable control set. If recovery does not follow recrawl, reopen the broader technical and content diagnosis rather than assuming the interstitial remains the only cause.

Interstitial mistakes to avoid

Showing a full-screen promotion on arrival

The user cannot reach the result they selected. Replace it with an inline placement, small banner, or post-engagement prompt.

Treating every popup as equally risky

Legal gates, private-content login walls, and small dismissible banners are different from promotional blockers. Classify the purpose and screen coverage before changing required experiences.

Hiding the overlay only from crawlers

Serving Googlebot a cleaner page than search visitors creates a parity and cloaking risk. Change the user experience itself.

Diagnosing a site-wide penalty from one affected page

The signal is page-level and algorithmic. Scope the implementation and the decline by template and landing page before claiming a manual or site-wide action.

Common interstitial problems

The popup appears only in production

Symptom: QA cannot reproduce an overlay seen by search visitors. Likely cause: Geo, campaign, referrer, consent, frequency, or audience rules differ from the test session. Fix: Enumerate trigger conditions, test clean sessions and representative regions, and log which rule opened the interstitial.

The close control is unusable on small screens

Symptom: The overlay is theoretically dismissible but the control is clipped, covered, or too hard to activate. Likely cause: Fixed positioning, viewport units, or stacking rules fail at real mobile sizes. Fix: Test portrait and landscape viewports, keyboard zoom, and long localized text; keep the control visible and the main content reachable.

Rankings do not immediately recover after removal

Symptom: The intrusive pattern is gone but search performance remains depressed. Likely cause: Google has not recrawled the affected pages, or another change shares the timing. Fix: Verify the live first-visit experience, request inspection for a sample, monitor recrawl, and compare with unaffected pages before assigning causality.

Interstitials cheat sheet

Penalized vs. allowed — at a glance

Fast facts

• Announced Aug 23, 2016; launched Jan 10, 2017 (mobile); desktop Feb 2022.
• Page-level, not site-wide. Algorithmic, not a manual action.
• Severity: “a softer factor,” a “slight demote” — strong content still ranks.
• 2024 API leak: violatesMobileInterstitialPolicy (boolean) + adsDensityInterstitialViolationStrength (0–1000).
• GSC interstitial emails (2022+) are advisory, not enforcement.
• Recovery: remove → recrawl → the signal stops applying (not a guaranteed ranking bounce back). No reconsideration request.
• Don’t cloak the popup from Googlebot — that’s a worse problem than the popup.
• Bing has no named interstitial penalty, but ad/overlay intrusiveness factors into its quality assessment.

Prompts for interstitial review

Classify an interstitial specification

Review this interstitial specification as a mobile search-entry experience. Classify
its purpose (promotional, legal, login/private content, or navigation), arrival timing,
viewport coverage, dismissal behavior, and crawler/user parity. Return: likely-safe
elements, likely-intrusive elements, missing facts, and the smallest design change that
keeps the business requirement without blocking primary content. Do not assume a legal
requirement that is not stated.

[paste specification and trigger rules]

Turn QA observations into a trigger matrix

Convert these interstitial QA notes into a test matrix by device, viewport, entry
source, consent state, geography, session freshness, and engagement timing. Include an
expected result and evidence to capture for every row. Flag any case where Googlebot
would receive a different experience solely because it is Googlebot.

[paste QA notes]

Validate an interstitial change

Test first-visit content access

Test to run: Open affected landing pages in clean mobile sessions across the actual trigger variants. Expected result: Primary content is immediately available, except for a documented legal or private-content gate; promotional UI uses a small or post-engagement pattern. Failure interpretation: A production rule still blocks search arrivals. Monitoring window: Immediate after deployment. Rollback trigger: Any promotional full-screen overlay returns on arrival.

Test dismissal and viewport behavior

Test to run: Exercise the interface at representative portrait, landscape, zoomed, and localized layouts. Expected result: The close control remains visible and operable, focus behaves predictably, and content remains reachable. Failure interpretation: The safer design still becomes obstructive in a real layout. Monitoring window: Immediate. Rollback trigger: A user can become trapped or the control leaves the viewport.

Test crawler and user parity

Test to run: Compare rendered output for a normal mobile user agent and the crawler configuration used in URL Inspection. Expected result: The interstitial policy and underlying content do not change merely because the visitor is a crawler. Failure interpretation: Bot-specific suppression masks the user experience. Monitoring window: Immediate locally and after recrawl. Rollback trigger: Googlebot receives a materially cleaner page than an equivalent user.

Test yourself: Interstitials

Five quick questions on Google’s intrusive interstitials signal. Pick an answer for each, then check.

Resources worth your time

My related writing

• The Beginner’s Guide to Technical SEO — where page experience and interstitials fit in the bigger picture.
• Core Web Vitals: What They Are & How to Improve Them — the sibling page-experience signal.

My speaking

• Page Experience Update — TMC, June 2021 (SlideShare) — my walkthrough of the page experience signals, with “No Intrusive Interstitials” alongside Core Web Vitals; covers why legal notices and small dismissible banners don’t count against you.

Official

• Google — Avoid intrusive interstitials and dialogs and the Aug 2016 announcement.
• Google — Bringing page experience to desktop (Feb 2022 expansion).

From around the industry

• Google Confirms Rolling Out The Mobile Intrusive Interstitials Penalty (Search Engine Land, Jan 2017) — Mueller + Illyes confirming the Jan 10, 2017 rollout.
• Google’s Intrusive Interstitials: Everything You Need to Know (Search Engine Journal) — the key Mueller quotes on acceptable interstitials, legal gates, and “softer factor / not site-wide.”
• The SEO Impact of Interstitials: Before & After (Search Engine Land) — Mueller’s “slightly demote,” Illyes’ cloaking line, and case data.
• Intrusive Interstitials: Guidelines To Avoid Google’s Penalty (Smashing Magazine, May 2017) — the Mueller exit-intent / timing quote in context.
• Google Search Console Notices For Removing Intrusive Interstitials (Search Engine Land, Apr 2022) — what the advisory GSC emails are (and aren’t).
• The Google Content Warehouse Leak 2024 (Hobo-Web) — analysis of the violatesMobileInterstitialPolicy attribute.
• r/TechSEO — the community for page-experience and interstitial debugging.

Interstitials

In 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.

Related: Core Web Vitals, Mobile SEO

Interstitials

An interstitial is a page or overlay that sits between a user’s click and the content they came for, blocking access until they interact with or dismiss it. In Google’s words, “intrusive interstitials and dialogs are page elements that obstruct users’ view of the content, usually for promotional purposes” — interstitials cover the whole page; dialogs cover only part of it.

In the SEO sense, the term is shorthand for the mobile interstitial penalty Google announced in August 2016 and launched on January 10, 2017. It’s a page-level ranking demotion (not a site-wide or manual penalty) that fires when a page shows a content-blocking overlay on the transition from a mobile search result to the page. In February 2022 the signal was extended to desktop search too.

Three kinds of interstitial trigger the signal: a popup that covers the main content immediately after the search click; a standalone interstitial you must dismiss before seeing content; and an above-the-fold layout that looks like an interstitial with the real content pushed below the fold.

Three kinds are explicitly exempt: interstitials required by law (cookie consent, GDPR, age verification); login walls for genuinely non-public content; and small, easily-dismissible banners that use a reasonable amount of screen space. Interstitials shown after the user has already engaged with the page — exit-intent, timed, or scroll-triggered popups — are not penalized.

The 2024 Google Content Warehouse API leak surfaced a violatesMobileInterstitialPolicy boolean, confirming the penalty operates per-document. The fix is algorithmic — remove the interstitial and wait for a recrawl, no reconsideration request needed — but that clears the signal rather than guaranteeing rankings return to their exact prior position.

Related: Core Web Vitals, Mobile SEO

Changelog