Are interstitials directly embedded in the page as penalizing as traditional pop-ups?

What is the difference between a popup interstitial and an embedded interstitial?

A popup interstitial typically displays via JavaScript above the content, often with a semi-transparent overlay that blocks access to the page. These popups have been under Google's scrutiny since the mobile update in January 2017.

An embedded interstitial is part of the page's DOM from the initial load. This can be a massive promotional banner, a newsletter block pushing the main content out of the first screen, or a large advertisement strategically placed at the top of the page. Technically, it is not an overlaid layer, but the result is the same: the mobile user does not see the content they are looking for immediately.

Why is Google now expanding its definition of interstitials?

The reason is simple: publishers have been circumventing the popup penalty by embedding the same intrusive elements directly into the HTML markup. From a user experience standpoint, an 800px tall block that monopolizes the mobile screen is just as annoying as a modal popup, regardless of whether it is technically “in the page.”

Google is refining its ability to detect visual obstruction of the main content, regardless of the technical implementation. The algorithm now analyzes the surface area occupied by these elements at the time of the first render, not just their JavaScript or CSS nature.

What coverage triggers the penalty?

Google refers to “a large part of the page” without providing a specific threshold. Based on field tests and observations of penalized sites, an element that occupies more than 50-60% of the mobile viewport height above the main content is at risk.

This approximation remains frustrating. Google does not provide a dedicated PageSpeed Insights metric nor an official percentage. SEO teams must therefore test under real conditions on mobile devices with different screen sizes to assess risk.

• HTML Embedded Interstitials: now treated like traditional popups if they cover a large part of the screen
• Approximate Threshold: 50-60% of viewport height occupied = observed penalty risk
• Algorithmic Detection: Google analyzes visual obstruction at first render, not the technical implementation method
• No Official Metric: no PageSpeed or Search Console indicator to accurately measure risk
• Broad Scope: large ad banners, bulky newsletter blocks, promotional inserts above the main content are all affected

Is this statement consistent with field observations?

Yes, and it confirms what many of us have been noticing for several months. Sites with oversized cookie consent banners or massive promotional blocks have seen their positions drop on mobile, even without using traditional JavaScript popups.

The problem is that Google remains vague about the exact threshold. Penalties have been observed on sites with elements covering 70% of the viewport, but others with 40% seem unaffected. The overall quality of the site and user engagement likely play a moderating role in the application of this rule. [To be verified]: the impact appears to be more severe on sites with already low engagement metrics (high bounce rate, short time on page).

What nuances should be applied to this rule?

Google has mentioned exceptions since 2017: legally required interstitials (age verification, strictly necessary cookie consent) and login banners on private content are not penalized. But the line is thin.

A minimal 150px cookie banner is not an issue. A cookie module that occupies 600px with five tabs of detailed preferences starts to resemble an interstitial, even if it is technically required by GDPR. Google provides no guidance on where to draw the line between legal compliance and UX abuse.

Similarly, a contextual newsletter block of 200px in the middle of the page after three paragraphs of content has never triggered an observable penalty. In contrast, the same block placed first, before any substantial content, poses a problem. The position in the reading flow matters as much as the absolute size.

In what cases does this rule not really apply?

On desktop, Google is much more lenient. Wide screens allow for complex layouts without obstructing the main content. An advertising sidebar of 300px wide does not hinder reading an article that is 800px wide.

E-commerce sites with promotional banners (“-20% today”) also seem to benefit from some leniency, probably because Google detects transactional intent and better tolerates certain commercial elements. [To be verified]: this tolerance could vary depending on verticality and the overall market quality of the site.

What should be audited first on your site?

First step: test the actual mobile display of your strategic pages using Chrome DevTools in device mode, especially on viewports of 375x667px (iPhone SE) and 360x640px (compact Android). Note the height in pixels occupied by each element before the main content.

Then, use Google Search Console to filter mobile pages and check if certain URLs show drops in clicks or impressions correlated to layout changes. Cross-check with your Analytics data to identify pages with abnormally high bounce rates on mobile.

How can you fix problematic elements without sacrificing conversions?

Reduce the height of promotional banners to no more than 25-30% of the mobile viewport. A newsletter block can remain effective with 200px in height instead of 500px if the wording is catchy and the CTA is visible.

For cookie banners, adopt a minimalist design with a well-visible “Accept All” button and a discreet “Settings” link that opens a secondary modal. The initial banner should never exceed 120-150px in height. Some sites have gained positions simply by moving from a full-height cookie banner to a sticky footer of 80px.

What tools should you use to measure the real impact?

Lighthouse and PageSpeed Insights do not provide a metric dedicated to interstitials, but watch the Cumulative Layout Shift (CLS) that can reveal elements pushing the content. A high CLS combined with a delayed First Contentful Paint often indicates an obstruction issue.

Use tools like Screaming Frog in JavaScript rendering mode to automatically capture screenshots of your pages and visually identify problematic elements at scale. Hotjar or Microsoft Clarity can show how real users interact with these elements (do they scroll immediately to avoid them? Do they click close without reading?).

• Audit all pages with banners, newsletter blocks, or large promotional inserts at the top of the page
• Measure the height in pixels of each element on mobile viewport 375x667px
• Reduce any element exceeding 30% of the viewport height, or move it after the first paragraph of content
• Test cookie banners: maximum height 150px, minimalist design, sticky footer preferred over a static block at the top
• Monitor CLS and FCP in PageSpeed Insights to detect elements delaying content display
• Cross-check Search Console data (mobile drop) and Analytics (high mobile bounce) to identify impacted pages