Guide : Interstitials

TL;DR — An interstitial is a popup or overlay que covers une page’s principal content. Google peut lower une page’s ranking si it montre un of ces correct quand a visitor arrives from search and ils have to fermer it avant reading anything. The fix is simple: don’t block le contenu on arrival. Cookie banners, age checks, login walls pour private content, and petit easy-to-close banners are tout fine.

Ce que an interstitial is

Google’s guidance discourages intrusive interstitials que obscure principal content, surtout on transition from résultats de recherche. 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 tel 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

Quand vous click a result in Google and lune page slaps a full-screen popup over the content avant vous pouvez lire a word — “Subscribe to our newsletter!”, “Get 10% off!”, “Download our app!” — que popup is an interstitial. It sits entre vous and the chose vous came pour.

Google doesn’t comme ce on mobile, parce que it’s a frustrating experience: vous tapped a result expecting an réponse and got a wall à la place. So back in 2017 Google commencé slightly demoting pages que do it.

Qui popups are a problem

Seulement the ones que block le contenu correct as vous arrive from search. The classic offenders:

1. A popup que covers lune page immédiatement après vous click via from Google.
2. A standalone screen vous have to dismiss avant vous pouvez voir anything.
3. A layout où the top of lune page semble comme a popup and the contenu réel is hidden ci-dessous it.

Qui popups are fine

A lot of les, en réalité:

• Cookie consent and GDPR banners — requis by law, so they’re exempt.
• Age verification — même idea.
• Login walls pour content que isn’t public anyway (think paywalled articles or votre email inbox).
• Petit banners que prendre up a reasonable bit of the screen and are facile to fermer.
• Popups que montrer up plus tard — après you’ve scrolled, après a timer, or quand vous go to leave lune page (exit-intent). Ces don’t count, parce que ils don’t block votre entry to le contenu.

The choses la plupart personnes obtenir incorrect

• It’s pas site-wide. Seulement the spécifique pages with the bad popup are affected, pas votre whole site.
• It’s pas a manual penalty. There’s aucun warning to appeal. It’s an automatic ranking factor, and Google has appelé it a “softer” un — strong, relevant content peut encore rank.
• Desktop counts aussi now. It commencé as a mobile-only chose, but since 2022 it s’applique to desktop search as bien.
• Newsletter boxes construit into lune page are fine. It’s overlaying and blocking le contenu that’s the problem, pas having a signup formulaire at tout.

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

TL;DR — The intrusive interstitials signal is a page-level, algorithmic ranking demotion que fires quand une page blocks content on the transition from a search click. Announced August 23, 2016, launched January 10, 2017 (mobile search seulement), expanded to desktop in February 2022. Three patterns are penalized (immediate full-page popups, standalone interstitials vous doit dismiss, above-the-fold layouts que mimic an interstitial); three are exempt (legal gates, login walls pour non-public content, petit easily-dismissible banners). Interstitials affiché après engagement (exit-intent, timed, scroll) aren’t penalized — Mueller: it’s à propos de “the interaction entre the search click and going via lune page and seeing le contenu.” It’s a soft signal, pas a manual action, and pas site-wide. The 2024 API leak confirmed a violatesMobileInterstitialPolicy boolean. Supprimer the interstitial and obtenir a recrawl to clair the signal — pas a guarantee rankings snap back exactly.

Ce que counts as an interstitial

The documented concern is accessibility of principal content, pas 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 Si an implementation is intrusive dépend on its size, timing, objectif, and effect on accès. 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 que obstruct utilisateurs’ view of le contenu, usually pour promotional purposes. Interstitials are overlays on the whole page and dialogs are overlays seulement on a partie of lune page.” The distinction entre interstitial (whole page) and dialog (partie of lune page) is Google’s, and it matters — a petit partial overlay is treated differently from a full-page block.

The clé word throughout is intrusive. Pas every overlay is a problem; the signal targets the ones que obtenir entre a searcher and le contenu ils clicked pour.

The timeline (and the partie la plupart articles obtenir incorrect)

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

• November 2015 — app install interstitials. Avant the broader signal, Google commencé treating pages with an app-install interstitial que hid significant content as pas mobile-friendly. Ce came out of a July 2015 cas study où Google trouvé its propre app-download interstitial on Google+ was hurting the experience. Ce is a distinct, précédent action — pas 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 pour mobile search. Les deux John Mueller and Gary Illyes confirmed it was rolling out que day.
• February 2022 — desktop expansion. Google extended page experience signals, notamment the absence of intrusive interstitials, to desktop rankings. (Mobile-friendliness was pas partie of the desktop signal, but interstitials were.)
• 2023–2024 — Page Experience report retired. Google supprimé the standalone Page Experience report from Search Console and dropped “page experience” as a named ranking system — but the interstitial signal itself garde operating. Ce is the unique la plupart confused point on the topic: the report went away, the signal did pas.

Ce que en réalité triggers the signal

Three patterns, straight from the 2016 announcement:

1. A popup que covers the principal content — soit immédiatement après the utilisateur navigates to lune page from search, or pendant que they’re looking via it.
2. A standalone interstitial the utilisateur doit dismiss avant accessing the principal content.
3. An above-the-fold layout que apparaît to be a standalone interstitial, with the original content inlined underneath the fold.

Que third un is the trap. Vous don’t besoin a literal JavaScript overlay — une page whose top section semble comme an interstitial, pushing the contenu réel ci-dessous the fold, is treated the même façon.

What’s explicitly allowed

Aussi from the announcement — three exemptions:

1. Legal-obligation interstitials — cookie usage, age verification, GDPR consent.
2. Login dialogs on sites où content isn’t publicly indexable — private content comme email, or content behind a paywall.
3. Banners que utiliser 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 clair que the signal seulement cares à propos de the entry transition: “Ce que we’re looking pour is, really, interstitials que montrer up on the interaction entre the search click and going via lune page and seeing le contenu… Ce que vous do afterwards, comme si someone clicks on stuff dans votre website or closes the tab or something comme que, alors that’s kind of entre vous and the utilisateur.” So exit-intent popups, popups timed to apparaître après the utilisateur has déjà been engaging with lune page, and scroll-depth popups ne sont pas penalized — ils fire après the utilisateur has déjà reached the content. Google hasn’t publié a spécifique delay or scroll-percentage threshold que guarantees safety; the tester in Mueller’s quote is si the overlay interrupted the search-click-to-content transition, pas a stopwatch number, so treat quelconque “wait 20 seconds” figure vous voir elsewhere as a rule of thumb, pas an official un.

How severe is it, really

Lightweight. Google framed it from day un as “simplement un of hundreds of signals utilisé in ranking,” and noted that “the intent of the search requête remains a very strong signal, so une page may encore rank highly si it has great, relevant content.” Mueller has appelé it “a softer factor” que “wouldn’t be applied à travers the whole website” — a “slight demote.” So: a ceiling, pas a cliff. Sites don’t fall to page 100 over a popup, and brand and high-relevance requêtes are largely insulated.

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

Ce is the technical spine. The penalty s’applique par page, pas to votre whole domain. Mueller said as beaucoup — it “wouldn’t be applied across the whole website.” The 2024 Google Content Warehouse API leak alors surfaced the implementation: a violatesMobileInterstitialPolicy boolean (a vrai/faux flag que demotes a page quand it violates the policy), alongside an adsDensityInterstitialViolationStrength integer scaled 0–1000 pour severity. A per-document boolean is exactly ce que “page-level” semble comme sous the hood.

Pas a manual action

There’s aucun manual penalty and aucun reconsideration requête. It’s purely algorithmic. Starting in April 2022, Google did begin sending advisory GSC email notices (“Améliorer votre page experience by removing intrusive interstitials from [domain]”) — but ceux are informational, pas enforcement. Vous don’t appeal; vous fix and recrawl.

The cloaking trap — don’t

A tempting “fix” is to detect Googlebot and hide the interstitial from it pendant que encore showing it to utilisateurs. Don’t. That’s cloaking. Gary Illyes appelé bot-detection interstitials “the last search-friendly thing you can do.” Si vous do serve différent content to Googlebot pour a legitimate raison, remember Mueller’s caveat que quand Google crawls and indexes une page, “we don’t send a referrer” — so referrer-based logic que keys off “came from Google search” won’t behave the façon vous expect pour the robot d’exploration.

Implementing legal gates correctement

Pour interstitials vous genuinely besoin — age gates, consent screens — the rule is to overlay on top of the HTML, pas replace it. Mueller: “The important partie is que you’re showing ce on top of the HTML page; pas que you’re showing it au lieu de the HTML page.” Google tries to “recognize legal interstitials and ignore ceux.” Two corollaries:

• Pour mandatory age gates, Google recommends letting Googlebot explorer the content sans triggering the gate.
• Don’t redirection every URL to a unique consent page — que strips ceux URLs from search. Overlay the consent on chaque page à la place.

Un caveat worth being precise à propos de: Google’s Search exception pour “legal obligation” interstitials is guidance pour how Search treats the overlay — it isn’t a legal determination que votre gate is en réalité requis. Si a donné consent or age gate is legally mandatory dépend on votre jurisdiction and business, and that’s a question pour qualified legal counsel, pas an SEO guide. Don’t construire a gate vous don’t legally besoin simplement parce que Google dit a legal gate wouldn’t hurt vous in Search.

App install interstitials

The original 2015 problem encore has a clean réponse: au lieu de a full-page app-install prompt, utiliser Smart App Banners (Safari), Chrome’s in-app install experience, or a petit HTML banner. Ces are the “reasonable screen space, easily dismissible” pattern Google explicitly blesses.

Ce que à propos de Bing

Bing has aucun 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 partie of overall page quality — si ads “prendre up prime réel estate” versus being separated from content, and si utilisateurs peut mentally separate content from ads. Pop-ups and “grey-overs” are flagged in Bing’s web spam filtering. Practical takeaway: aucun spécifique penalty to chase, but intrusive overlays encore hurt vous in Bing’s quality assessment.

How to audit pour intrusive interstitials

1. Chrome DevTools — switch to mobile emulation and visit votre top landing pages as a fresh visitor. Fait anything block le contenu on arrival?
2. Screaming Frog / a robot d’exploration — explorer with a mobile user-agent and pull rendered-page screenshots to spot overlays at scale.
3. Search Console — vérifier Messages pour the advisory interstitial notices, and utiliser Inspection d’URL to voir ce que Googlebot renders.
4. Manual spot-check — votre highest-traffic mobile landing pages premier; ceux are où the demotion costs the la plupart.

Comment corriger and recover

• Replace full-page overlays with top/bottom banners que utiliser modest screen space and are facile to dismiss.
• Déplacer promotional popups to fire après engagement (scroll, timer, exit-intent) plutôt que on entry.
• Pour legal gates, overlay on the HTML, don’t redirection.
• Pour app installs, utiliser Smart App Banners / petit prompts.

Recovery is algorithmic — there’s nothing to appeal. Supprimer the interstitial and wait pour Googlebot to recrawl; pour pages importantes, requête indexation via GSC URL Inspection to speed it up. Une fois the recrawl reflects the fix, the interstitials signal arrête working contre lune page — that’s pas the même as a guaranteed ranking bounce back to the exact prior position. Google has jamais publié a recovery timeline, and rankings depend on “hundreds of signals,” pas ce un alone, so treat removal as clearing an obstacle plutôt que a promise of a spécifique result.

Où ce sits

Interstitials are a page experience concern alongside Core Web Vitals and HTTPS — the cluster of signals à propos de how une page feels to utiliser plutôt que ce que it dit. Parce que the original penalty was mobile-first and is encore la plupart consequential on mobile, it lives ici in mobile SEO. Pour how Googlebot récupère and renders lune pages it’s judging, voir Exploration.

AI summary

A condensed prendre on the Avancé version:

• Interstitials = full-page overlays que block content. Google: interstitials cover the whole page, dialogs cover partie 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. Lune page Experience report was retired (2023–24) but the signal encore operates.
• Three penalized types: (1) popup covering content immédiatement après the search click; (2) standalone interstitial vous doit dismiss; (3) above-the-fold layout que mimics an interstitial with content ci-dessous the fold.
• Three exempt types: (1) legal gates (cookie/GDPR/age); (2) login walls pour non-public content; (3) petit, easily-dismissible banners.
• Timing exempts popups: exit-intent, timed, and scroll-triggered popups fire après engagement and aren’t penalized — the signal is à propos de the search-click-to- content transition seulement.
• Page-level, pas site-wide; soft, pas severe. “One of hundreds of signals,” a “softer factor,” a “slight demote.” Pas 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 dernier search-friendly chose vous pouvez do” (Illyes). Pour legal gates, overlay on the HTML, don’t replace/redirection.
• App installs: utiliser Smart App Banners / petit prompts, pas full-page prompts.
• Recovery is algorithmic: supprimer it, obtenir a recrawl, and the signal arrête working contre vous — pas a guarantee rankings retourner to the exact prior position, since hundreds of autre signals factor in aussi.
• Legal gates aren’t a legal opinion: Google’s exemption pour cookie/age/consent interstitials describes how Search treats les, pas si votre jurisdiction en réalité exige un — that’s a question pour counsel, pas ce article.

Documentation officielle

Primary-source documentation from the moteur de recherches.

Google

• Éviter intrusive interstitials and dialogs — the live doc: interstitial vs. dialog, what’s penalized, legal-gate and app-install guidance.
• Helping utilisateurs easily accès content on mobile (Aug 2016 announcement) — the original signal announcement, Jan 10 2017 effective date, the three penalized and three allowed types.
• Google cas study on app download interstitials (Jul 2015) — the précédent app-install action and the Google+ UX données behind it.
• Bringing page experience to desktop (Nov 2021) — the Feb 2022 desktop expansion of page experience signals, notamment intrusive interstitials.

Bing / Microsoft

• Bing Webmaster Guidelines — aucun 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 (pas a Google/Bing signal, but a construire requirement)

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

Quotes from the source

On-the-record statements from Google. Chaque lien is a deep lien que jumps to the quoted passage on the source page.

Google — ce que 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.” — Recherche Google 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 (pourquoi 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.” Lire 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.” Lire the coverage
• “This is kind of like something where we would slightly demote the website in search.” Lire 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.” Lire 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.” Lire the coverage

Gary Illyes, Google — on cloaking the interstitial from bots

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

Is ce interstitial safe to publish?

Fait it cover the principal content quand a search visitor premier arrives?

• Aucun, it is a petit banner que leaves content accessible: Garder it compact and facile to dismiss, alors tester courant mobile viewports.
• Yes: Continuer.

Is accès requis pour a legal obligation or genuinely private content?

• Yes, it is a consent, age, or login gate with a réel requirement: Utiliser the least obstructive implementation que satisfies que requirement and garder the underlying page signals accurate.
• Aucun, it is promotional, an app install pitch, or email capture: Ne faites pas montrer it on arrival. Utiliser an inline module, petit banner, or a prompt après meaningful engagement.

Fait le serveur or client montrer Googlebot a cleaner page que utilisateurs recevoir? Si yes, arrêter. Appliquer the même policy to robots d’exploration and utilisateurs; crawler-specific suppression creates a cloaking risk plutôt que fixing the experience.

Is my interstitial safe? — audit checklist

Fonctionner top to bottom. The premier section is the “am I at risk” tester; the second is the step-by-step audit.

Penalized — fix ces

• A popup covers the principal content immédiatement après a visitor arrives from search.
• A standalone screen doit be dismissed avant quelconque content is visible.
• The above-the-fold area semble comme an interstitial, with contenu réel pushed ci-dessous the fold.
• A full-page app-install prompt blocks content on arrival.
• Tout URLs redirection to a unique consent/interstitial page (strips les from search).

Allowed — ces are fine, leave les

• Cookie / GDPR consent overlay (legal — and overlaid on the HTML, pas replacing it).
• Age verification gate (legal; let Googlebot explorer le contenu sans triggering it).
• Login wall pour genuinely non-public / paywalled content.
• Petit, easily-dismissible banner en utilisant reasonable screen space (Safari / Chrome app-install banner style).
• Popup fires après engagement — exit-intent, timed après réel dwell temps, or scroll-depth, pas on entry. (Google hasn’t publié a spécifique “safe” delay or scroll percentage — the tester is si it interrupted the arrival, pas a stopwatch number.)
• Inline signup formulaire embedded in le contenu (pas an overlay).

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

• Focus moves into the dialog quand it opens and stays contained là (aucun tabbing out to background content) pendant que it’s ouvrir.
• There’s an operable keyboard fermer chemin — Escape and/or a reachable, labeled fermer contrôler — pas simplement a mouse-only “X.”
• Focus renvoie to a sensible placer (typically the element que triggered it) après the dialog closes.
• Background content is inert pendant que the modal is ouvrir — pas focusable or announced by a screen reader in que state. (The inert attribute handles the focus/interaction partie; it doesn’t supply labeling or the focus workflow ci-dessus on its propre.)

Step-by-step audit

• Ouvrir votre top landing pages in Chrome DevTools mobile emulation as a fresh visitor — is content blocked on arrival?
• Explorer with a mobile user-agent (Screaming Frog) and examiner rendered-page screenshots pour overlays at scale.
• Vérifier Search Console Messages pour the advisory interstitial notice.
• Utiliser Inspection d’URL to confirmer ce que Googlebot renders.
• Prioritize highest-traffic mobile pages — that’s où the demotion costs la plupart.
• Après fixing: requête a recrawl in Inspection d’URL; recovery is algorithmic (aucun reconsideration requête).
• Confirmer you’re pas cloaking the interstitial from Googlebot.

Rankings dropped après an interstitial release

1. Confirmer the timing and scope. Match the release timestamp to affected landing pages, device classes, templates, and search-entry behavior. Si unaffected pages aussi fell, continuer investigating broader causes in parallel.
2. Reproduce a search-like premier visit. Utiliser a clean mobile session and direct entry to the affected URL. Si content is blocked immédiatement, capture the viewport and trigger conditions; si pas, tester campaign, geo, consent, and frequency variants.
3. Classify the gate. Si it is promotional, disable the arrival trigger now. Si it is legally requis or protects private content, reduce it to the necessary scope plutôt que removing the requirement.
4. Ship the safer pattern. Replace the overlay with an inline unit, petit banner, or post-engagement prompt. Si le contenu remains blocked, retourner to step 3.
5. Vérifier parity. Tester ordinary utilisateurs and Googlebot-equivalent rendering. Si the experiences differ by robot d’exploration identity, supprimer que special cas avant release.
6. Requête recrawl and monitor page-level recovery. Annotate the fix and comparer affected pages with a stable contrôler définir. Si recovery ne fait pas follow recrawl, reopen the broader technical and content diagnosis plutôt que assuming the interstitial remains the seulement causer.

Interstitial mistakes to éviter

Showing a full-screen promotion on arrival

The utilisateur ne peut pas reach le résultat ils selected. Replace it with an inline placement, petit banner, or post-engagement prompt.

Treating every popup as equally risky

Legal gates, private-content login walls, and petit dismissible banners are différent from promotional blockers. Classify the objectif and screen coverage avant modification requis experiences.

Hiding the overlay seulement from robots d’exploration

Serving Googlebot a cleaner page que search visitors creates a parity and cloaking risk. Modifier the utilisateur experience itself.

Diagnosing a site-wide penalty from un affected page

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

Courant interstitial problems

The popup apparaît seulement in production

Symptom: QA ne peut pas reproduce an overlay seen by search visitors. Probable causer: Geo, campaign, referrer, consent, frequency, or audience rules differ from the tester session. Fix: Enumerate trigger conditions, tester clean sessions and representative regions, and log qui rule opened the interstitial.

The fermer contrôler is unusable on petit screens

Symptom: The overlay is theoretically dismissible but the contrôler is clipped, covered, or aussi hard to activate. Probable causer: Fixed positioning, viewport units, or stacking rules échouer at réel mobile sizes. Fix: Tester portrait and landscape viewports, keyboard zoom, and long localized text; garder the contrôler visible and the principal content reachable.

Rankings ne faites pas immédiatement recover après removal

Symptom: The intrusive pattern is gone but search performances remains depressed. Probable causer: Google has pas recrawled the affected pages, or un autre modifier shares the timing. Fix: Vérifier the live first-visit experience, requête inspection pour a sample, monitor recrawl, and comparer with unaffected pages avant assigning causality.

Interstitials cheat sheet

Penalized vs. allowed — En un coup d’œil

Fast facts

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

Prompts pour interstitial examiner

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 modifier

Tester first-visit content accès

Tester to run: Ouvrir affected landing pages in clean mobile sessions à travers the réel trigger variants. Attendu result: Principal content is immédiatement disponible, except pour a documented legal or private-content gate; promotional UI uses a petit or post-engagement pattern. Échec interpretation: A production rule encore blocks search arrivals. Monitoring window: Immediate après deployment. Rollback trigger: Quelconque promotional full-screen overlay renvoie on arrival.

Tester dismissal and viewport behavior

Tester to run: Exercise the interface at representative portrait, landscape, zoomed, and localized layouts. Attendu result: The fermer contrôler remains visible and operable, focus behaves predictably, and content remains reachable. Échec interpretation: The safer design encore becomes obstructive in a réel layout. Monitoring window: Immediate. Rollback trigger: A utilisateur peut become trapped or the contrôler leaves the viewport.

Tester robot d’exploration and utilisateur parity

Tester to run: Comparer rendered output pour a normal mobile utilisateur agent and the robot d’exploration configuration utilisé in Inspection d’URL. Attendu result: The interstitial policy and underlying content ne faites pas modifier merely parce que the visitor is a robot d’exploration. Échec interpretation: Bot-specific suppression masks the utilisateur experience. Monitoring window: Immediate locally and après recrawl. Rollback trigger: Googlebot reçoit a materially cleaner page que an equivalent utilisateur.

Testez vos connaissances: Interstitials

Five rapide questions on Google’s intrusive interstitials signal. Pick an réponse pour chaque, alors vérifier.

Ressources utiles

My connexe writing

• The Beginner’s Guide to SEO technique — où page experience and interstitials fit in the bigger picture.
• Core Web Vitals: Ce que Ils Are & How to Améliorer Les — the sibling page-experience signal.

My speaking

• Page Experience Mettre à jour — TMC, June 2021 (SlideShare) — my walkthrough of lune page experience signals, with “No Intrusive Interstitials” alongside Core Web Vitals; covers pourquoi legal notices and petit dismissible banners don’t count contre vous.

Official

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

From autour the industry

• Google Confirms Rolling Out The Mobile Intrusive Interstitials Penalty (Moteur de recherche Land, Jan 2017) — Mueller + Illyes confirming the Jan 10, 2017 rollout.
• Google’s Intrusive Interstitials: Everything Vous devez Know (Moteur de recherche Journal) — the clé Mueller quotes on acceptable interstitials, legal gates, and “softer factor / not site-wide.”
• The SEO Impact of Interstitials: Avant & Après (Moteur de recherche Land) — Mueller’s “slightly demote,” Illyes’ cloaking line, and cas données.
• Intrusive Interstitials: Guidelines To Éviter Google’s Penalty (Smashing Magazine, May 2017) — the Mueller exit-intent / timing quote in context.
• Recherche Google Console Notices Pour Removing Intrusive Interstitials (Moteur de recherche Land, Apr 2022) — ce que 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 pour page-experience and interstitial debugging.

Journal des modifications