What size of banner does Google really accept to replace interstitials?

Why does Google avoid providing precise percentages?

Google's strategy involves intentionally leaving the acceptable threshold fuzzy for application download banners. By refusing to set a numerical limit, Google retains the freedom to evaluate each case individually. This approach reflects a reality: display context varies significantly across devices, orientations, and screen resolutions.

The absence of quantitative guidance is not new in Google's recommendations. The company has long favored qualitative formulations that prevent it from being locked into rigid rules. For an SEO practitioner, this flexibility becomes problematic: how can one objectively audit a site without a measurable benchmark?

What does "drawing inspiration from Safari" actually mean?

The reference to Safari is not incidental. Safari's native banners on iOS typically occupy 10 to 12% of the screen height in portrait mode on a standard iPhone. These banners appear at the top of the page with a height of approximately 60 to 70 pixels on a screen that is 667 to 812 pixels high.

Google thus implicitly suggests that a banner remaining within this visual range should not be penalized. However, caution is needed: Safari dynamically adjusts height according to context, and some variants occupy up to 15% of the screen. The ambiguity persists even with this reference example.

How does this guideline fit within the anti-interstitial policy?

Since the mobile update in 2017, Google penalizes intrusive interstitials that obscure the main content. Application install banners represented a gray area: technically less intrusive than a full-screen popup but potentially bothersome if oversized.

Mueller's statement partially clarifies this gray area by validating the principle of banners, as long as they remain proportionate and non-blocking. A full-screen interstitial remains prohibited, a Safari-type banner is acceptable, but in between, everyone must determine their own limit in hopes that Google will approve it.

• No official percentage is provided by Google for the maximum acceptable height
• The reference to Safari suggests an implicit range of 10-15% of screen height
• This recommendation fits within the mobile anti-interstitial policy implemented since 2017
• Evaluation remains qualitative and contextual rather than based on strict thresholds
• Publishers should prioritize perceived user experience over the optimization of a technical number

Is this lack of numbers really accidental?

No, and this is where the issue lies. Google deliberately maintains this strategic ambiguity to preserve its discretion. If a threshold of 15% were officially stated, many sites would immediately reach it, testing the limits of acceptability. The absence of a numerical benchmark forces publishers to remain conservative.

On the ground, this strategy creates a disparity in treatment. Large players have resources to test different implementations and measure impact on their organic traffic. Smaller sites, on the other hand, are groping in the dark and often choose to forgo banners altogether out of caution. [To be verified]: currently, no public study documents the actual threshold applied by Google's algorithm.

Is the reference to Safari really applicable everywhere?

Problem: Safari functions exclusively on iOS, which represents about 25-30% of the mobile market depending on regions. Native Android standards differ significantly, with banners sometimes more compact, sometimes larger, depending on the manufacturers.

Recommending Safari as a universal benchmark ignores this fragmentation of the mobile market. Should a site primarily aimed at an Android audience really align with iOS standards? Logic would dictate to draw inspiration from the majority system among its own users, but Google is obviously not going to officially recommend imitating Android implementations.

What real risks of penalties exist?

Let's be honest: documented penalties specifically for banners that are too tall remain extremely rare. Most interstitial sanctions concern blocking popups or forced redirects, not static banners at the top of the page.

The real risk is probably not a direct algorithmic penalty, but rather a deterioration of user signals (bounce rate, time on page, clicks) that indirectly influences ranking. An oversized banner hampers the experience, users leave faster, Google observes this through Chrome, and adjusts the ranking accordingly. The mechanism is indirect but just as effective.

What banner size should be implemented in practice?

The actionable recommendation is to aim for a maximum height of 60-80 pixels on standard devices (screens of 667-812px in height in portrait mode). This represents about 10-12% of the screen, aligned with Safari banners. For larger screens (tablets, phablets), this proportion can drop to 8-10%.

Always test on multiple physical devices, not just in emulation. Renderings can vary significantly based on the browsers, and what Chrome Desktop displays in responsive mode does not always faithfully reflect the actual experience on an iPhone 13 or a Samsung Galaxy.

How can you ensure that a banner will not be considered intrusive?

Unfortunately, Google Search Console does not provide any dedicated report for application banners. The mobile optimization testing tool has been deprecated. The only indirect validation comes from the absence of messages in the "Mobile Usability" section and monitoring of Core Web Vitals, particularly the CLS (Cumulative Layout Shift).

A banner that appears after the initial load and causes a content shift results in a high CLS, which is a negative signal for Google. Ensure that space for the banner is reserved from the initial render to avoid this type of degradation. Also monitor the mobile bounce rate in Analytics: a sudden spike after implementing a banner likely indicates an intrusiveness issue.

What implementation mistakes should be absolutely avoided?

The classic mistake is to implement a banner with a fixed pixel value without considering the actual screen height. A 100px banner may seem reasonable on an iPhone 14 Pro Max but takes up an excessive proportion on a compact device or in landscape mode.

Another pitfall: banners that overlay content rather than integrating with it. A fixed position banner floating above the text without pushing it down creates a permanent obstruction, exactly what Google seeks to penalize. Content must always remain accessible, even if temporarily partially obscured.

• Limit banner height to 10-12% of the viewport height in portrait mode
• Implement in vh (viewport height) rather than fixed pixels to adapt to different screens
• Reserve necessary space from the initial load to avoid CLS
• Test on multiple physical devices, not just in emulation
• Monitor the mobile bounce rate before and after implementation
• Check for the absence of alerts in Search Console > Mobile Usability