What counts as intrusive
Google's official guidance, unchanged since 2017, identifies three patterns it considers intrusive when they show on a mobile page reached from search results.
- A pop-up that covers the main content immediately or shortly after the user lands. The user clicks a result, the page loads, and within a second a modal appears over the content. The user has to find the X to read what they came for.
- A standalone interstitial that the user has to dismiss before reaching the main content. The most aggressive pattern: a full-screen ad or sign-up form that replaces the page content entirely, with a "Continue to article" link in the corner.
- An above-the-fold layout that looks like an interstitial. A masthead promo block that consumes the entire viewport before the actual content begins. Visually indistinguishable from a real interstitial; treated the same.
The mobile focus matters. The signal originated in 2017 specifically to address mobile pop-ups, where small screens make pop-ups especially disruptive. The Page Experience update integrated it as one input among several, but mobile is still where most enforcement actually happens.
Google has also been clear that the signal is small. It is not a hard penalty like a manual action; it is one ranking input among many. Pages with strong content can still rank well even with a borderline pop-up. But the fix is so cheap that there is rarely a good reason to risk the demotion.
What is explicitly allowed
The 2017 announcement listed three categories of interstitial that are explicitly exempt, and the policy has not changed.
Legal interstitials. Cookie consent banners under GDPR, the Australian Privacy Act, or the ePrivacy Directive. Age verification gates for alcohol, gambling or adult content. Required legal disclaimers. All of these are allowed even when they cover content, because they are obligations imposed by law.
Login dialogs on content that is not publicly indexable. A paywall or login wall on a private content area is fine. The content was not in the open search index in the first place.
Reasonably-sized banners. Banners that use a reasonable amount of screen space and can be easily dismissed are allowed. A 80px sticky bar at the top of the page promoting a newsletter sign-up is fine. A 600px modal that covers the whole hero is not. The line is intentionally fuzzy. Google's own examples show a banner of roughly 15 percent of viewport height as acceptable.
By extension, all of these timing-based pop-ups are allowed:
- Scroll-triggered pop-ups. The pop-up appears after the user has scrolled 50 percent of the page. The user has clearly engaged with the content.
- Click-triggered pop-ups. The pop-up appears when the user clicks a button. The user opted in.
- Exit-intent pop-ups. The pop-up appears when the user moves their cursor toward the close-tab area. The user is leaving anyway.
- Time-delayed pop-ups (in moderation). A pop-up that appears after 30 seconds on the page is generally fine. After 1 second it is not.
A brief history of the signal
Google announced the "intrusive interstitials penalty" in August 2016 with an effective date of 10 January 2017. The original announcement framed it as a standalone mobile signal: pages with intrusive pop-ups would rank lower for mobile queries.
The signal was folded into the broader Page Experience system when that launched in June 2021. From that point on, the interstitial check became one of several Page Experience inputs alongside Core Web Vitals, HTTPS, mobile usability, and safe-browsing status. The wider Page Experience system extended to desktop in February 2022.
Since the March 2024 Helpful Content update and subsequent algorithm shifts, the Page Experience system has been less prominent in Google's public messaging, but the underlying signal still operates. Sites with aggressive pop-ups still see softer rankings on mobile than they would otherwise. Sites that cleaned up their pop-ups in 2017 are still benefiting in 2026.
How to fix offending pop-ups
The fix is almost always to change when the pop-up triggers rather than to remove it entirely.
Switch immediate pop-ups to scroll-triggered. If your newsletter pop-up currently fires on page load, change it to fire when the user has scrolled 50 percent down the page. Conversion rates typically improve, not just preserve. Users who scroll halfway are engaged users, and engaged users convert better than randomly-targeted ones. Almost every pop-up platform supports scroll triggers natively (OptinMonster, Sumo, ConvertBox, native WordPress plugins).
Switch to exit-intent on desktop. Exit-intent works on desktop because the mouse cursor approaches the top of the viewport before the user closes the tab. On mobile, exit-intent is harder to detect reliably. Most pop-up platforms fall back to a time delay or scroll trigger on mobile, which is the right behaviour.
Use click-triggered modals. A "Subscribe to our newsletter" button in the body of the article that opens a modal on click is a click-triggered pop-up. The user opted in by clicking. Conversion rates from click-triggered modals are higher than from random pop-ups anyway, because the user signalled interest.
Shrink banner ads. If you have a promotional banner above the fold that consumes too much viewport, shrink it or move it below the fold. A 40 to 60 pixel banner at the top of the page is fine. A 200 pixel hero promo that pushes the actual content off-screen is borderline. The threshold is fuzzy but the safe target is "reasonably sized" which we interpret as under 15 percent of viewport height.
Server-render legal interstitials where possible. Cookie banners and age gates that are part of the initial server response cause no layout shift and look intentional. Cookie banners injected after a 600ms delay look spammy and contribute to CLS. Most modern consent platforms (Cookiebot, OneTrust, Iubenda) support server-side rendering.
Do
- Trigger pop-ups on scroll, click, or exit-intent
- Keep cookie banners small and server-rendered
- Limit above-the-fold banners to under 15 percent of viewport height
- A/B test pop-up timing against conversion rates
- Use a close button that is at least 48 by 48 CSS pixels
Don't
- Trigger pop-ups on page load or within the first second
- Use full-screen interstitials that replace the content
- Hide the close button or make it tiny
- Ship a giant promotional hero that mimics an interstitial
- Assume the signal does not apply on desktop
Common mistakes
Confusing intrusive interstitials with all pop-ups. The signal only applies to pop-ups that fire immediately on landing from search. Exit-intent, scroll-triggered, click-triggered and time-delayed pop-ups are explicitly fine. Many sites strip out useful conversion tools out of fear when the actual fix is just to change the trigger.
Stacking a cookie banner with a newsletter pop-up. The cookie banner is exempt by itself. Add a newsletter pop-up that also fires on page load and the combination is intrusive even if each one individually would be fine. Stagger them: cookie banner first, newsletter pop-up after scroll.
Trusting a pop-up plugin's "Google-friendly" claim. Most pop-up plugins say they are Google-friendly. Few default to the safe triggers. Audit your actual configuration: what does the pop-up do for a mobile user who clicks through from a search result and lands fresh on the page?
Treating CWV as a tiebreaker boost. The intrusive interstitial signal, like the rest of Page Experience, is small. Pass the threshold and move on. Fixing the pop-up takes 20 minutes; chasing it as if it were a major ranking factor is a waste of budget.
Tools and checklist
Audit tools:
- Chrome DevTools mobile emulation. Load each major template as if you arrived from search. Watch what happens in the first 2 seconds. Anything that covers content fails.
- Real mobile device test. Use a phone and a search query that lands on your page. Check the actual behaviour, not the desktop simulation.
- Pop-up platform analytics. Most platforms (OptinMonster, ConvertBox, Sumo) show trigger events. Filter by mobile traffic and check that no trigger fires within the first 2 seconds.
- Lighthouse Page Experience section. Does not directly flag interstitials but does flag related mobile-usability issues that often co-occur.
Pre-launch checklist:
- No pop-up fires within 2 seconds of page load on mobile
- Cookie banner sized under 15 percent of viewport height
- Cookie banner has an obvious accept and reject button
- Newsletter and promotional pop-ups trigger on scroll, click, exit-intent, or a generous time delay
- Close buttons at least 48 by 48 CSS pixels
- Above-the-fold promotional banners do not visually mimic interstitials
- Tested on a real phone from a real search result
Perth and WA context
Two interstitial patterns we see locally.
Local service sites with overzealous lead-gen pop-ups. A typical Perth tradie site we audit will have a "Get a quote" modal that fires on page load. Conversion rates on a load-fire pop-up are usually 1 to 3 percent. Moving the same pop-up to a scroll trigger or click trigger typically lifts conversion to 4 to 8 percent and removes the Page Experience demotion at the same time. Trades SEO sites benefit most from this change.
E-commerce sites running aggressive welcome offers. A Perth e-commerce store offering 10 percent off in a full-screen pop-up that fires immediately on landing from search is the textbook intrusive interstitial pattern. The fix is to either delay the pop-up to a scroll trigger or to display the discount as a thin sticky bar rather than a full overlay. E-commerce SEO covers the wider trade-offs.
For broader work, the website audits service flags interstitials alongside other Page Experience issues. New sites should start with a free SEO audit. The conversion rate optimisation service rebuilds pop-up strategy around triggers that are both Google-safe and higher-converting. Related Learn Hub chapters: Core Web Vitals explained, mobile usability, CLS fixes, Lighthouse explained and the wider technical SEO pillar. For Perth and regional coverage see Perth services, Local SEO Perth, Fremantle and Joondalup.