An intrusive interstitial is a full-page or near-full-page pop-up, overlay or splash screen that stands between a visitor and the content they clicked for. Google treats the habit as a page experience problem, and an ad-heavy layout, where ads crowd out the main content, falls under the same guidance.
What counts as an intrusive interstitial?
Google’s page experience documentation asks site owners to avoid intrusive interstitials and an excessive amount of ads that distract from or interfere with the main content. In August 2016, Google’s Webmaster blog announced the original mobile rule, which applied from 10 January 2017, and listed the kinds of overlays that make content less accessible:
- a pop-up that covers the main content right after the visitor arrives from search,
- a stand-alone interstitial that must be dismissed before the content shows,
- a layout where the above-the-fold part looks like an interstitial, with the content pushed below the fold.
The 2016 announcement and its coverage in the trade press name three kinds of overlays that are fine: legal notices (a cookie consent banner or an age check), login dialogs on private content that is not indexable, and banners that use a reasonable amount of screen and are easy to dismiss, such as the app-install banners browsers show.
Does it hurt rankings?
Google states that “there is no single signal” called page experience. Its core ranking systems look at signals that line up with a good page experience, and Core Web Vitals are the only part Google says its ranking systems use directly. Intrusive interstitials sit in the wider group Google asks you to avoid, with no stated score or fixed penalty.
The practical risk comes in two ways:
- Google’s guidance: a layout that blocks the content a searcher wanted goes against the advice in the page experience guide.
- Your own numbers: a late-loading banner that pushes the page down raises cumulative layout shift (CLS), a Core Web Vital, and a pop-up that fills the screen sends people back to the results page (see engagement rate).
How do you set up pop-ups and ads without hurting your pages, step by step?
- Open your top 10 landing pages on a phone. Use real devices or Chrome DevTools device mode, and arrive the way a searcher does: from a search result, with no cookies.
- List everything that appears. Cookie banner, newsletter pop-up, app banner, chat widget, promo bar, ads. Note when each shows up and how much of the screen it covers.
- Never cover the content on arrival. Do not show a newsletter or promotion overlay in the first moments after a visitor lands from Google. Show it after the visitor has read part of the page, scrolled, or is about to leave.
- Use a banner or inline box instead of a full-screen pop-up. A slim bar at the top or bottom, or a form inside the article, uses little space and is easy to ignore or close.
- Make the close button obvious. Give it a large tap target and let Esc or a tap outside close it. Hidden or tiny close buttons also fail accessibility checks (see accessibility).
- Keep legal prompts, and make them small. A cookie notice is allowed. Use a compact banner at the bottom, not a full-page wall, unless the law you follow requires a choice before the page loads.
- Cap ad density. Keep the main content visible without scrolling past ads. Google asks that visitors can easily tell the main content from other content, and warns against an excessive amount of ads.
- Reserve space for ads and banners. Set a fixed height so they do not shift the layout when they load (see Core Web Vitals).
- Recheck after any change to a consent tool, ad network or marketing plugin. Their defaults change.
- Test the result in your analytics. Compare conversion and email sign-ups before and after, so you know what the change costs or gains.
What should you use instead of pop-ups?
- An inline sign-up box inside the article, after the first section.
- A sticky bottom bar that takes a small strip of the screen.
- An exit-intent offer on desktop, shown when the cursor leaves the window. Exit intent does not exist on phones, so use a banner there.
- A content upgrade at the end of the post, such as a checklist.
All of these ask for the email without blocking the page. See site navigation for layouts that give visitors a clear next step.
How do you measure the result?
- Search Console: the Core Web Vitals report shows URLs with poor CLS. Use Google Search Console to find them.
- PageSpeed Insights: look at field data for CLS and LCP on the pages with banners.
- Analytics: compare the engagement rate and bounce rate of landing pages before and after you move a pop-up.
- Sign-ups: track email conversions per page, because a slimmer form changes both the volume and the quality of leads.
- Real-device check: open the page on your phone once a quarter.
What mistakes should you avoid?
- A full-screen offer 2 seconds after the page opens from a search result.
- Cookie walls that block the whole page longer than the law requires.
- A close button that is the same colour as the background or sits off-screen.
- Ads above the first paragraph that push the answer below the fold.
- Auto-playing video ads with sound that follow the reader down the page.
- Banners without reserved space, which shift the layout on load.
- Hiding the problem on desktop while mobile looks worse. Test both, because Google uses the mobile page for indexing (see mobile-first indexing).
- Believing the legal exception covers marketing. A cookie consent prompt is covered, a newsletter pop-up is not.
Where can you learn more?
The free landing page module of the Fe/male Switch startup school covers how to lay out a page so the offer is clear without blocking the content. Next steps on SEO100: check layout shifts under Core Web Vitals, then review the pop-ups against your accessibility checklist.