Interstitial Popup

An interstitial popup is a full-screen or near-full-screen overlay that appears between the user and the content they expected to see. Think of it as a gate you have to walk through before you enter the room. Sometimes that gate is necessary — a bouncer checking ID at a bar, or a cookie banner on a site that must obtain consent. But if the gate is too wide, appears every time someone knocks, or has a tiny latch that is hard to find, people turn around and leave.

I draw the line at screen coverage. On a mobile viewport, if the overlay covers more than 50% of the visible area and appears before the user has scrolled or interacted, I flag it as intrusive. Google’s guidelines are less precise but the pattern is clear: content must remain accessible. I saw a client lose 18% of their organic traffic after a redesign added a 30-second-delayed newsletter overlay that covered the entire screen. Reverting to a small slide-in at the bottom recovered most of the loss within three weeks.

The counter-argument I hear is “but our email list grew by 40%”. That might be true in the short term, but the SEO cost — lost rankings, higher bounce rate, lower click-through rate — often outweighs the direct conversion gain. I would rather run an inline signup form inside the content than any form of interstitial, and reserve full-screen overlays for genuinely mandatory interactions such as age verification. Even then, a small bar with a “Proceed” button is better than a gate that hides the whole page.

Mobile traffic is where the penalty bites. Google’s mobile-first indexing means the crawler sees the same page a human does on a phone. If that page has a full-screen promo that covers the main content, Google can apply the intrusive interstitials penalty, which effectively lowers rankings for that query. I check for this in every [technical SEO](/technical-seo/) audit — the Mobile Usability report in Search Console surfaces any pages where “Intrusive interstitials” are flagged.

Lead-generation popups are the most common offender on ecommerce sites. I once audited a fashion retailer whose product page had a 10% signup conversion rate from an immediate popup, but their organic traffic from Google dropped 22% over the same period. When I delayed the popup by 8 seconds and shrunk it to a bottom banner, the signup rate fell to 7% but organic traffic recovered to the previous level within six weeks. The net gain was actually higher because they kept their ranking for the head terms.

Compliance contexts are a special case. Age-verification gates for alcohol or gambling sites, and cookie consent prompts under GDPR, are generally exempt from the intrusive-interstitial rule. However, I still implement them as small overlays rather than full-page takeovers. A [mobile SEO](/mobile-seo/) best practice I follow: load the consent layer asynchronously so the content is already visible underneath. If the user dismisses it quickly, the page feels instant. If they need to interact, the friction is minimal.

Edge case: single-page apps that use JavaScript to show a modal on initial load. These can run afoul of the guidelines even if the modal is not technically a popup, because the user lands on a page where the content is hidden. I treat any overlay triggered on DOMContentLoaded as high-risk and refactor it to trigger on scroll or after a timer. The [core web vitals](/core-web-vitals/) impact also matters — a large overlay that loads late can cause layout shift (CLS).

I used to think that any popup with a visible close button was safe. I was wrong. Google’s guidelines explicitly call out “dialogs that obscure the main content” even when they can be dismissed. The close button has to be prominent and tappable — at least 48x48 pixels. I had a site where the close was a small X in the top-right corner on a white background. It was technically visible, but users on a 320px-wide screen struggled to hit it. That site saw a manual action warning for intrusive interstitials. I fixed it by making the close button a solid-coloured circle with a white X, 54x54 pixels.

Another mistake: I assumed only ad interstitials were penalised. But Google treats newsletter signups, discount overlays, and social share prompts the same way if they block content on mobile. A client in the travel niche had a “Get 10% off” popup that appeared immediately on landing. Organic traffic from mobile dropped 15% after a core update. I argued it wasn’t an ad, but Google’s policy is about behaviour, not intent. Any overlay that makes content harder to reach is a risk.

I also originally thought that interstitials were fine on desktop because Google’s guidelines are mobile-specific. While that is technically true, user behaviour still suffers: I measured a 25% higher bounce rate on desktop for a page with a full-screen popup versus one with a small banner. And with user experience signals becoming ranking factors, I now apply the same rules to both viewports. The only difference is the screen coverage threshold — on desktop I tolerate up to 60% coverage as long as the underlying page is still scrolled and readable around the overlay.

Finally, I underestimated how [JavaScript SEO](/javascript-seo/) interacts with popups. If the popup content is inserted via JavaScript and Google has trouble rendering it, the popup might not be seen by the crawler, but the user who lands on the page still sees a gate. That inconsistency can hurt rankings. I now pre-render critical content server-side and load the overlay only after interaction or a delay.