How to Fix Intrusive Interstitials and Mobile Pop-ups

An intrusive interstitial is a pop-up or overlay that covers the main content as soon as someone lands on a page, especially on mobile. Common examples are full-screen newsletter modals, discount wheels and app-install walls. By the end of this guide you will have found every overlay on your site, replaced the blocking ones with compact banners or delayed slide-ins, and confirmed that each page shows its content immediately on a phone-sized screen.

By Updated ⏱ 1-3 hours🎯 Intermediate● High impactOn-Page
Illustration: Intrusive interstitials fix guide
ON-PAGE · FIX GUIDE Intrusive interstitials IMPACTEFFORT TIME1-3 hours LEVELIntermediate

Why it matters

Google's Search Central guidance still lists intrusive interstitials as something to avoid. They make content harder for users and Google to reach, and that can count against a page's experience compared with competing results. The bigger cost is behavioural.

Visitors arriving from search or AI answer links who hit a full-screen wall on a 390px screen often go straight back, which raises bounce and lowers conversions. Our audit reports the share of your pages that show this pattern, so one sitewide pop-up rule can flag almost every URL at once.

✕BeforeOn mobile,https://example.com/blog/guide openswith a full-screen "Get 10% off" modal✓AfterThe article loads fully visible, and a72px bottom banner reading "Get 10%off – Sign up" appears after the

What you need

Admin access to your CMS and to any pop-up or email-capture tool (e.g. Klaviyo, OptinMonster, Popup Maker, HubSpot)
Access to your tag manager (e.g. Google Tag Manager), if pop-ups are injected through it
Chrome with DevTools for mobile device emulation
A list of your site's main page templates (home, product, blog post, category)

Step-by-step fix

1

Inventory every overlay on your key templates

Open each main template in Chrome. Press F12, then Ctrl+Shift+M (Cmd+Shift+M on Mac) to emulate a phone such as iPhone 14 Pro, and reload with the cache disabled. Note every element that appears over the content and where it comes from.

Usual sources are:

  • Theme settings
  • A pop-up plugin or app
  • A Google Tag Manager tag
  • An embedded chat or review widget

In the DevTools Console, run the snippet below to list fixed or sticky elements that cover more than 30% of the viewport.

javascript
[...document.querySelectorAll('body *')].filter(el=>{const s=getComputedStyle(el);if(!['fixed','sticky'].includes(s.position)||s.display==='none'||s.visibility==='hidden')return false;const r=el.getBoundingClientRect();return (r.width*r.height)/(innerWidth*innerHeight)>0.3;}).forEach(el=>console.log(el,el.id,el.className));
Pro tip: Test in an incognito window. Most pop-up tools set a 'seen' cookie and won't show the modal to you again, which hides the problem.
2

Sort overlays into required and marketing

Some overlays are legitimately needed and Google does not treat them as intrusive when they are reasonably sized:

  • Cookie consent
  • Age verification for regulated products
  • Login prompts for content that is genuinely private or paywalled

Everything else is marketing and should not block content on arrival. That includes newsletter sign-ups, discount offers, spin-to-win wheels, app-install prompts, surveys and 'are you sure you want to leave' dialogs. Write down which tool controls each marketing overlay so you can change its settings in the next steps.

Pro tip: If a legal overlay is full-screen, it can still be flagged. Make it compact too (see step 5).
3

Turn full-screen modals into a compact banner

Change the pop-up's layout from 'modal', 'fullscreen' or 'lightbox' to a bottom bar or corner slide-in. On mobile, keep it to roughly 25% of the viewport height or less. Do not use a dark backdrop, and do not lock page scrolling.

If your tool has no banner layout, hide its mobile version and add your own banner using the HTML/CSS below.

html
<div id="promo-bar" role="region" aria-label="Newsletter offer" hidden>
  <p>Get 10% off your first order from Example Co.</p>
  <a href="/signup">Sign up</a>
  <button type="button" aria-label="Close offer" id="promo-close">×</button>
</div>
<style>
#promo-bar{position:fixed;left:0;right:0;bottom:0;max-height:25vh;display:flex;gap:12px;align-items:center;justify-content:space-between;padding:12px 16px;background:#111;color:#fff;font-size:15px;z-index:1000;box-shadow:0 -2px 8px rgba(0,0,0,.2)}
#promo-bar[hidden]{display:none}
#promo-bar a{color:#fff;font-weight:600}
#promo-close{min-width:44px;min-height:44px;background:none;border:0;color:#fff;font-size:22px}
</style>
Pro tip: Make the close button at least 44×44px. A tiny × that is hard to tap is one of the most common complaints about mobile overlays.
4

Delay the trigger and skip the landing view

Don't show anything on page load or after a short timer like 3 seconds. Use engagement triggers instead:

  • Scroll depth of 50% or more
  • A second page view in the session
  • Exit intent on desktop

Respect a dismissal cookie for at least 7–30 days. The script below shows the banner from step 3 at 50% scroll and remembers when it is closed.

html
<script>
(function(){
  var bar=document.getElementById('promo-bar');
  if(!bar||document.cookie.indexOf('promo_dismissed=1')>-1)return;
  function onScroll(){
    var depth=(scrollY+innerHeight)/document.documentElement.scrollHeight;
    if(depth>=0.5){bar.hidden=false;removeEventListener('scroll',onScroll);}
  }
  addEventListener('scroll',onScroll,{passive:true});
  document.getElementById('promo-close').addEventListener('click',function(){
    bar.hidden=true;
    document.cookie='promo_dismissed=1; max-age='+60*60*24*14+'; path=/; SameSite=Lax';
  });
})();
</script>
Pro tip: In pop-up tools, this setting is usually under 'Triggers', 'Behavior' or 'Display rules'. Look for 'scroll percentage' or 'page views in session'.
5

Shrink the cookie banner and other required overlays

Set your consent platform to a bottom bar or small corner box rather than a centred modal with a dimmed backdrop. Most consent platforms offer this, including Cookiebot, OneTrust, CookieYes and Complianz. The page content should stay visible and readable behind the banner.

Keep age gates and login walls only on the URLs that actually need them, not sitewide.

Pro tip: In Cookiebot, choose the banner layout in the admin under Configuration > Banner. In CookieYes, use Cookie Banner > Layout and pick 'Banner' instead of 'Popup'.
6

Remove leftover overlays injected by tags

In Google Tag Manager, open Tags and search for the names of your pop-up vendors and for custom HTML tags containing 'modal', 'popup' or 'overlay'. Pause or delete any that duplicate the overlays you just fixed. Then submit and publish a new container version.

Also check your theme's own settings for built-in newsletter pop-ups, which often stay enabled after a pop-up app is installed.

Pro tip: Name the published version clearly, e.g. 'Removed full-screen mobile popups', so you can roll back quickly if something breaks.
7

Retest every template on mobile

Clear your cookies or use a fresh incognito window. Load each template in DevTools mobile emulation and confirm two things. First, the main content is visible immediately on load.

Second, any banner appears only after the trigger you set and covers no more than about a quarter of the screen. Run the console snippet from step 1 again; it should list nothing on load apart from a compact cookie bar. Then re-run the audit and check that the number of flagged pages has dropped.

Pro tip: Also test on a real phone over mobile data. Slow script loading can make a delayed banner appear at an odd moment or flash on load.

Platform-specific notes

WordPress

In Popup Maker, open Popup Maker > All Popups > edit the popup. Under Popup Settings > Triggers, replace 'Auto Open' with a scroll trigger. Under Display, choose a 'Bottom' location and a small size. In Elementor Pro, go to Templates > Popups. Under Publish > Triggers, use 'On Scroll' at 50%. Under Advanced Rules, enable 'Show after X page views'. Then set a bottom-bar layout in the popup's Layout settings and hide it on mobile if needed.

Shopify

Many themes include a built-in newsletter pop-up. Find it under Online Store > Themes > Customize, in the pop-up section or Theme settings, and disable it there. For Klaviyo, open Sign-up forms, edit the form, switch the form type to 'Flyout' or 'Full-width', and under Targeting & Behavior set the display timing to 'After scroll' and 'Show on mobile' to a separate small mobile form. Also check Apps and app embeds for overlays from other apps.

Wix

Lightboxes are managed in the Editor under Pages & Menu > Lightboxes. Select the lightbox, open Settings, and turn off automatic display, or limit it to specific pages with a delay. Switch to the mobile editor to resize or hide the lightbox on mobile only. A Wix Strip pinned to the bottom of the screen is a good banner alternative.

Webflow

Pop-ups are usually a fixed div shown by a Page Load interaction. In the Interactions panel, change the trigger to Page Scroll or Scroll Into View on an element halfway down the page. In the Designer, switch to the mobile breakpoint and change the element's position from full-screen fixed to a bottom-aligned fixed bar.

Next.js / custom React

Render the banner client-side only, behind a scroll or engagement hook, and never as an initial-state modal. Avoid setting `overflow: hidden` on `<body>` for marketing banners. Read the dismissal flag from a cookie in middleware or on the server so returning visitors never see the banner flash on load.

Check that it worked

✅ How to verify

  • Use Chrome DevTools mobile emulation in a fresh incognito window: the main content is visible on load and nothing covers more than about 25% of the viewport until the visitor interacts.
  • Run the console snippet from step 1 on each template right after load and confirm it returns no large fixed overlays other than a compact cookie bar.
  • Use the URL Inspection tool in Google Search Console, choose 'Test live URL', then 'View tested page' > Screenshot. The rendered page should show your content, not a pop-up.
  • Re-run the audit and confirm the count of pages flagged for intrusive interstitials has dropped to zero, or only to pages with justified legal gates.

⚠️ Common mistakes

  • Fixing the pop-up in the plugin but leaving a duplicate copy firing from Google Tag Manager or the theme's built-in newsletter pop-up.
  • Swapping a full-screen modal for a 5-second timer modal. A delayed full-screen overlay still blocks content and still gets flagged.
  • Showing a separate 'mobile app install' interstitial when a small banner, or Safari's built-in Smart App Banner via the apple-itunes-app meta tag, would work.
  • Making the cookie consent a centred full-screen wall with a dark backdrop when a bottom bar meets the same legal requirements.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

Does Google penalize pop-ups on mobile?

Google advises against interstitials that block the main content right after someone arrives from search. They can make a page's experience compare poorly with other results and make content harder to reach. There is no manual penalty, but they hurt engagement and can reduce visibility in close rankings. Small banners and legally required notices are fine.

Are cookie consent banners considered intrusive interstitials?

Not when they are a reasonable size. Google explicitly exempts dialogs required by law, such as cookie consent and age verification. Keep them compact, for example a bottom bar, so the content stays visible behind them.

How big can a mobile pop-up be without being intrusive?

Google gives no exact pixel limit, but its guidance refers to banners that use a reasonable amount of screen space. A practical target is no more than about 25% of the viewport height. It should be easy to dismiss and should not lock scrolling.

Are exit-intent pop-ups OK?

Exit-intent pop-ups on desktop are generally acceptable because they appear when the visitor is leaving, not when they arrive. Mobile has no reliable exit-intent signal. On phones, use a scroll-depth or second-pageview trigger with a compact banner instead.