A popup, also written “pop-up,” is content that appears in front of what someone is viewing. On a store website, it usually means an overlay inside the current page: a size guide, message, offer or form that opens above the products. In browser settings, “pop-up” can instead mean a separate browser window opened by a website.
PopupPopup meaning: what opens and what it changes
The distinction matters. A request to “add a popup” doesn't yet say whether shopping should pause. It also leaves open whether a new window should appear or the visitor must provide information. Those are separate choices.
4 things shoppers might call a popup
Start by asking where the content lives and what responding to it does. Form describes a way to collect information. Popup describes how content appears. A form can be embedded or placed inside an overlay; an overlay can show useful information without collecting anything.
Notification permission is separate. Chrome gives it its own settings; allowing notifications is not the same action as submitting an email field on a store's page. A site's invitation to receive alerts and the browser's permission prompt may appear in sequence, but they remain separate interactions.
| Surface | Where it appears | What the shopper is interacting with |
|---|---|---|
| Website overlay | Above content within the current page | A part of the website that can contain information, buttons or a form |
| Browser popup window | In a separate browser window; some opening requests become tabs | Another browsing surface, with its own page and browser controls |
| Embedded form | In the ordinary page layout, such as below a product description | A form reached by moving through the page, without opening an overlay |
| Browser permission prompt | In browser-controlled interface associated with a site | A request for browser permission, such as allowing site notifications |
Modal describes the restriction, not the size
A modal overlay temporarily makes the rest of the page unavailable for interaction. The shopper must deal with or close the dialog before using the page underneath. A non-modal overlay leaves the surrounding page interactive.
A small centered box can therefore be modal, while a larger side panel can be non-modal. Placement isn't decisive. Neither is animation. A dimmed background is a visual clue, not proof that the interaction has been implemented correctly.
W3C's modal-dialog guidance describes keyboard focus moving into the dialog and staying there while it is open. Focus normally returns to the opener when the dialog closes, letting a keyboard user resume the original task. The guidance includes Escape to close. A visible close control is also recommended.
For a merchant reviewing a popup, try reaching the products behind it with the keyboard. If the panel is meant to be modal but focus disappears behind it, the experience needs fixing even if the screenshot looks right.
Opening, acting and closing are separate events
A popup has an opening condition, a visible state and a way out. For example, a visitor selects “Size guide,” reads the overlay, then closes it and returns to choosing a size. Another popup might open without a click after a display rule is met. The shared label says nothing about which trigger you should use.
The main button, or call to action, also needs its own meaning. “View delivery details” should reveal information; “Save my choice” should save a choice. Opening a panel and selecting its button are interactions you can count, but neither establishes that the requested action completed. Keep those events distinct.
Closing should be equally clear. Dismissing an optional message should let the shopper continue. It doesn't, by itself, say whether earlier answers were saved or a form was submitted. If a flow has multiple steps, make that state explicit rather than expecting the visitor to infer it from the panel disappearing.
A merchant example: the size guide beside the size selector
Imagine a fictional store, Fern Thread, selling shirts with a fit that differs across styles. A shopper is choosing a size and wants the measurements for the shirt they're viewing.
The merchant could put the full measurement table directly on the product page. That keeps the information available without an interruption. Or it could place an “Open size guide” button beside the selector and reveal those measurements in an overlay. The second option keeps the initial page shorter while letting the shopper ask for detail at the relevant moment.
Suppose Fern Thread chooses a modal. The guide opens over the shirt page and carries the shirt's name. A visible close button lets the shopper leave. After closing it, the shopper returns to the size-guide button and can continue choosing. No email field is needed because the job is to answer a fit question.
Now imagine the same guide opening automatically on every product visit. The content hasn't changed, but the interruption has: shoppers who already know their size must dismiss it before continuing. That is a different store decision, not a cosmetic variation.
This is an illustrative scenario, not a measured result. The useful distinction is who initiates the interruption and whether it helps the task already underway.
Does the interruption earn its place?
Put essential information on the page. A shopper shouldn't have to catch a fleeting message to learn shipping restrictions that materially affect the purchase. Optional detail can work behind a clearly labeled button when it is easy to reopen.
An automatic interruption needs justification. Ask what the shopper needs at that moment and what they must stop doing before deciding whether a quieter placement would answer the same need. A popup's ability to attract attention is not evidence that it deserves that attention.
Google Search's guidance recommends avoiding intrusive interstitials that obstruct content and suggests compact banners as an alternative to full-page interruptions. This is guidance about access to the page, not a statement that every popup causes a search penalty.
Test on a phone. If there is a form, open the keyboard and check whether someone can still understand the request, complete it or close it. Also return to the page after dismissal. We'd treat repeatedly reopening the same optional message as a separate problem from the visual design.
Why a popup blocker may not stop it
Chrome blocks automatically opened popup windows by default. That isn't a switch for every overlay. An in-page overlay is website content, rather than a newly opened browser window. Notification permissions are another separate control.
For a support report such as “your popup won't close,” first identify the surface. Ask whether it is inside the store page, a separate window, or a browser permission message. Then reproduce the opening and dismissal path. Changing browser-window settings is unlikely to explain a close button failing inside the page. A useful request to a designer or developer names the content, trigger, modal behavior, primary action and dismissal result.
For example: “Open the product's size guide when requested. Keep it readable. Return the visitor to the selector after closing.” That describes an experience someone can test. “Add a popup” describes only the surface.
Every app on every plan. Connect your store and switch on the flows in an evening.