What counts as a pop-up or interstitial
A pop-up is any element that appears over the page content, often after a delay or an action such as scrolling. An interstitial is a full-page or near-full-page screen shown between the visitor and the content they came for, such as an app promotion, a signup request or an age gate. Banners that stick to the top or bottom of the screen are related: they do not always cover the content, but on a phone they can eat a large portion of the viewport.
On a desktop monitor, these elements are an irritation. On a phone they can be a roadblock, because the screen is small enough that a single overlay can hide nearly everything.
Why small screens make the problem worse
- Less room. An overlay that covers a quarter of a desktop screen can cover most of a phone screen.
- Tiny close controls. A small “x” in the corner is hard to hit with a thumb, and a miss may trigger the offer underneath instead.
- Awkward scrolling. Some overlays lock the page behind them, trap scrolling or are taller than the screen so the close button sits out of view.
- Slow connections. Overlays can load late, shift the layout and arrive just as someone starts to read, causing mistaps.
- Interrupted tasks. Phone use is often brief and goal-driven, so being blocked early may simply end the visit.
These problems are felt even more strongly by visitors with motor or vision difficulties. A modal that cannot be dismissed with a keyboard or that does not announce itself to a screen reader can lock them out entirely, a point examined in keyboard navigation.
How search engines are said to view it
Search engines have, in the past, stated that they may treat pages that show intrusive interstitials immediately after a visitor arrives from search results as less user-friendly. The details have changed over time so check what the major search engines publish before relying on any specific claim. The consistent idea is that content should be reasonably accessible once someone lands on it. Practices commonly described as problematic include:
- a pop-up that covers the main content right after arrival
- a standalone interstitial that must be dismissed before the content can be seen
- a layout where the above-the-fold area looks like an interstitial, with the content pushed below it
Commonly described as acceptable, because they have a legitimate purpose and use limited space, are things like legal notices such as cookie consent or age verification, a login wall on content that is genuinely private, and small, easily dismissed banners. Even these should be sized carefully. No result is guaranteed either way, and how any search engine applies its guidance can change, but the visitor experience reasoning holds regardless.
Questions to ask before adding one
- What is it for? Is it needed for legal or functional reasons, or is it a marketing request? A functional necessity deserves a little more latitude.
- Does it help the visitor at this moment? A newsletter request shown before the person has read a word is unlikely to be welcome.
- How much screen does it cover on the smallest phone you support? Test it, rather than assuming.
- Can it be closed easily? The close control should be large, clearly visible, reachable with a thumb, and operable by keyboard.
- Does it return focus properly and announce itself? For accessibility, focus should move into it when it opens and back to the page when it closes.
- When does it appear? Triggers based on time, scroll depth or exit intent behave differently on phones, where there is no cursor to detect leaving.
- How often does it return? Showing it on every page view is usually worse than remembering the dismissal.
- Is there a lighter alternative? An inline signup box within the content, a small banner or a link in the footer might serve the same goal with less disruption.
Design choices that reduce harm
If you decide a pop-up is worthwhile, some choices make it less disruptive:
- Keep it small, such as a slim bar rather than a full-screen takeover.
- Delay it until the visitor has had a chance to read or complete something.
- Make the wording honest, and make the decline option as visible as the accept option.
- Avoid stacking multiple overlays, such as a cookie notice plus a newsletter box plus a chat widget, all at once. On a phone, that combination can fill the entire screen.
- Make sure it does not cause layout shifts or push the main content down after it loads, which relates to core web vitals.
- Provide a clear way to dismiss it by touch, keyboard and assistive technology.
How to audit your own site
Visit your key pages on a real phone, preferably in a private browsing window so earlier dismissals are not remembered. Arrive from a different route, such as a search result or a shared link, and note what appears, when and how much of the screen it covers. Try to close it with a thumb. Rotate to landscape, where the available height is even smaller and close buttons are often pushed off-screen. Then repeat with the keyboard.
Consider the full journey too. If a visitor reaches a product page and the first thing they see is a discount request that hides the product, that matters for product pages as much as for articles. For online shops, extra layers near checkout can also add checkout friction.
A balanced view
Overlays are not always wrong. Some sites find them useful, and some legal situations require notices. The key is proportionality: the more the element interrupts, the stronger the justification needs to be. When in doubt, test with real people on real phones, check your analytics for clues such as quick exits after the overlay appears, and treat them with care because bounce rate has many possible explanations.