Can mobile interstitials really be indexed by Google?

Does Google really index what's behind an interstitial?

John Mueller's statement breaks a common misconception: a mobile interstitial does not automatically prevent the indexing of the content it hides. When Googlebot crawls a page in mobile-first mode, it analyzes what is actually displayed on the screen.

If the interstitial presents structured text content and this content is technically accessible to the bot, Google may decide to include it in the index. The key criterion remains the notion of mobile-friendliness: the content must be perceived as relevant and usable on a smartphone.

What does Google mean by 'mobile-friendly content'?

Google doesn't provide a specific definition, which complicates interpretation. It can be assumed that this covers technical criteria: configured viewport, readable text without zoom, clickable buttons, absence of Flash.

But it likely also includes a UX dimension. An interstitial that takes up 90% of the screen with an invisible close button will probably be deemed unsuitable. In contrast, a discreet notification at the bottom of the screen might pass. The ambiguity is intentional on Google's part.

How does Google decide what to index during a crawl?

Googlebot executes JavaScript and takes a snapshot of the page as it appears after rendering. If an interstitial triggers instantly, the bot will see it. If the overlay hides the main content, Google will have to choose what to prioritize.

The logic seems to be: Google indexes what it sees first, or what appears most significant to it. An interstitial containing a newsletter signup with 10 words will not replace a 1500-word article located below. But an overlay presenting a detailed offer might be taken into account.

• Interstitials do not automatically block the indexing of the content they hide
• Google evaluates the mobile relevance of the visible content during the crawl
• The bot considers what it perceives after executing JavaScript
• An interstitial with structured content can be indexed if deemed suitable
• The precise evaluation criteria remain intentionally vague

Is this statement consistent with real-world observations?

Yes and no. On paper, Mueller's assertion aligns with what we observe: some sites with overlays continue to be indexed normally. Tests show that Google effectively distinguishes between primary content and secondary elements.

But in practice, unpredictability remains complete. Two sites with similar interstitials can experience radically different outcomes. One will see its content indexed without issue, while the other will suffer a drop in visibility. [To be confirmed]: Google has never provided numeric thresholds to define what is 'mobile-friendly'.

Should we conclude that interstitials are risk-free?

Absolutely not. The nuance is crucial: indexing does not equal good ranking. Google may index the content of an interstitial while penalizing the page for poor user experience. The Page Experience Update explicitly targets intrusive overlays.

Moreover, even if Google technically indexes the hidden content, there is no guarantee that it will assign weight in ranking. Text hidden behind an interstitial will always have less value than content that is immediately accessible. This makes algorithmic sense.

What practical cases invalidate this general rule?

Mandatory legal interstitials (cookies, age verification) are not penalized; Mueller has confirmed this multiple times. But be cautious: a 3-line cookie banner yes. A full-screen overlay requiring a login before accessing content, no.

Another exception: partial paywalls. Google has created specific guidelines for premium content. If you use the appropriate structured data markup and leave a visible excerpt, you can block the rest without risk. But again, the devil is in the implementation details.

What should be done with existing interstitials?

Start with a complete audit of all your overlays: newsletter, promotions, push notifications, geolocation. For each, ask yourself: does this content provide real value to the mobile user, or is it just noise?

Next, test the mobile rendering using the URL inspection tool in Search Console. Check exactly what Googlebot sees. If your interstitial covers 80% of the screen and the main content only appears after scrolling, you have a problem. Technical indexing is not enough if the user experience is degraded.

What technical errors should be avoided at all costs?

Never use cloaking techniques to hide interstitials from Googlebot. Showing an overlay to human visitors and a clean page to the bot is a blatant violation of the guidelines. Google will eventually detect this, and the penalty will be severe.

Avoid immediate-trigger overlays that cover the entire screen without a visible close option. Even if Google indexes the content, these practices negatively impact CLS and FID. Your Core Web Vitals will suffer, and with them, your ranking.

How can I ensure my implementation is compliant?

Use Google's Mobile-Friendly Test on all your pages with interstitials. If the tool reports accessibility issues, your overlay is likely problematic. Complement this with real user tests: install Hotjar or Clarity to see how mobile visitors interact with your popups.

Monitor your Search Console metrics after each change: impressions, CTR, average position. If you observe a decline correlated with the deployment of a new interstitial, you have your answer. Indexing may be maintained, but the ranking impact is negative.

• Audit all interstitials and overlays present on the mobile site
• Test Googlebot rendering via the URL inspection tool
• Measure the impact on Core Web Vitals (CLS, FID, LCP)
• Ensure each interstitial has a visible and accessible close button
• Implement a delay of 3-5 seconds before triggering non-essential overlays
• Monitor Search Console KPIs after each modification