Fix Intrusive Interstitials & Popups on Mobile

What this means

Why it matters

How to fix it

1. 1

   Confirm which popup is flagged and how it behaves

   Open the flagged URL at a mobile width (Chrome DevTools device mode, 390px) in a fresh session, ideally by clicking through from a search result rather than from your own homepage, since many popups fire only on first visit. Watch whether the overlay covers content on arrival or after a delay or scroll. Inspect the element and note its position (fixed or absolute), z-index, and how much of the viewport it covers. That tells you whether it is a genuine intrusive interstitial or an exempt case like a slim banner or cookie bar.

2. 2

   Replace full-screen overlays with a non-blocking banner

   The safest pattern is a small bar pinned to the top or bottom that leaves the article readable behind it. Swap out any modal that covers the whole viewport on load. A slim promo bar or an inline call-to-action inside the content sells without tripping the signal. Reserve full-screen modals for actions the user explicitly starts, like tapping a Subscribe button.

3. 3

   Delay, scroll-trigger, or exit-intent your promos

   Do not fire a promotional popup on the initial landing view. Trigger it after the visitor scrolls part of the page, after a time delay, or on exit intent, so the first thing a search visitor sees is content. Suppress it on the first pageview of a session and cap frequency with a cookie so returning visitors are not hit repeatedly. This keeps the marketing function while keeping the arrival clean.

4. 4

   Keep required consent dialogs proportionate

   Cookie consent (GDPR), age gates, and similar legally required dialogs are exempt, but only when used reasonably. Do not pad them with newsletter signups or ads, and do not let them consume the whole screen. A banner-style consent bar is both compliant and safe. If you must use a full-screen consent modal, keep it to the minimum needed for compliance.

5. 5

   Keep the content in the server-rendered HTML

   Whatever you change visually, make sure the primary content is present in the initial HTML and not injected only after a popup is dismissed. For soft paywalls or read-more gates, keep the article body in the DOM and truncate it with CSS rather than removing it. This is what protects AI extraction: GPTBot, ClaudeBot, PerplexityBot, and Google's AI systems read the initial HTML, so text that appears only after JavaScript reveals a hidden modal is invisible to them. Confirm with View Source or curl that the text is there before any script runs.

6. 6

   Re-test and validate

   After the change, re-crawl the page and re-check it at a mobile width from a cold session. Use the DevTools device toolbar to confirm the content is visible above the fold on arrival. For a Google-eye view, run URL Inspection in Search Console to fetch and render the page. Then re-run this audit to confirm the intrusive_interstitial flag clears.

Example

// Non-intrusive popup: skip first view, trigger on scroll, cap with a cookie
(function () {
  var KEY = 'promo_seen';
  function hasCookie() { return document.cookie.indexOf(KEY + '=1') !== -1; }
  function setCookie() {
    var d = new Date();
    d.setDate(d.getDate() + 7); // don't show again for 7 days
    document.cookie = KEY + '=1; path=/; expires=' + d.toUTCString();
  }

  if (hasCookie()) return; // returning visitor -> stay silent

  var fired = false;
  window.addEventListener('scroll', function onScroll() {
    var scrollable = document.documentElement.scrollHeight - window.innerHeight;
    if (scrollable <= 0) return; // page fits the screen: never interrupt
    // fire only after the user has read ~40% of the page
    var scrolled = window.scrollY / scrollable;
    if (!fired && scrolled > 0.4) {
      fired = true;
      showPopup(); // your existing modal open function
      setCookie();
      window.removeEventListener('scroll', onScroll);
    }
  }, { passive: true });
})();

Skip the popup on the first landing view and fire it only after the visitor scrolls partway, so search arrivals see content first. A short-page guard prevents it firing instantly, and a cookie stops returning visitors being hit again.

Platform-specific steps

Frequently asked