Why overlays stop AI agents
Agents that browse for a shopper are built to leave consent to the shopper. Google's Gemini computer use model hands control back for cookie banners and privacy prompts. Gemini in Chrome pauses for cookies, sign-in and CAPTCHAs until the person clicks Take over task. Anthropic tells developers to ask a person before accepting cookies. If the banner covers the product, the agent can't read the price until someone answers it, and often nobody is watching.
OpenAI's help page for ChatGPT's cloud browser says each website ultimately decides whether to allow its traffic. To the shopper, a store that blocks the agent and a store that hides behind an overlay look the same: the assistant couldn't get the answer.
| Overlay | What happens to an agent | Fix |
|---|---|---|
| Cookie wall that hides the page until you choose | Hands consent back to the person and waits | A banner that leaves the page readable behind it |
| Newsletter or discount pop-up on the first page | Has to find and close it before reading anything | Show it later, never before the price is visible |
| Country or currency selector as a full-screen modal | May not know which country to pick | Default to a country, offer the switch inline |
| Age gate | May need the person to confirm | Keep it only where the law requires it, as an overlay |
| Chat widget that covers Add to cart or the price | Reads or clicks the wrong element | Keep it collapsed and clear of the buy box |
| CAPTCHA or bot challenge on product pages | Stops: agents are told not to solve CAPTCHAs | Keep challenges for login, checkout and forms |
Fix the overlays
Step 1: Let the page stay readable behind the cookie banner
Keep whatever consent choices your legal team requires. The change is the layout: a banner at the bottom or side, with Accept and Reject as equal buttons, and the product, price and stock still in the page and not hidden behind a full-screen layer. Google's Search guidance asks for the same: banners that take up a small part of the screen.
Step 2: Make every pop-up a real dialog
W3C's modal dialog pattern: the dialog has
role="dialog"and a name, focus moves into it, Tab stays inside, Escape closes it, and focus returns to where it was. A labeled close button gives an agent something it can find by name.HTML: a dialog an agent can close <div role="dialog" aria-modal="true" aria-labelledby="signup-title"> <h2 id="signup-title">Join our newsletter</h2> <!-- form --> <button type="button" aria-label="Close">×</button> </div> <script> document.addEventListener("keydown", (event) => { if (event.key === "Escape") closeSignupDialog(); }); </script>Step 3: Delay marketing pop-ups
Don't open a newsletter or discount pop-up on the first page a visitor lands on. Show it after a second page view, on exit, or after a scroll, and never on top of a product's price.
JavaScript: open the pop-up from the second page view const views = Number(sessionStorage.getItem("pageViews") ?? 0) + 1; sessionStorage.setItem("pageViews", String(views)); if (views >= 2) openSignupDialog();Step 4: Don't block prices behind a country picker
Pick a default country and currency from the domain or the visitor's location, show prices straight away, and offer the switch as a menu, not a modal that must be answered first.
Step 5: Keep bot challenges off browsing pages
A CAPTCHA on a product or collection page stops agents completely. Google's sample instructions forbid its model from solving them, and Anthropic says its crawlers won't try to bypass them. Use challenges where they protect something: login, checkout and forms. See does Cloudflare block AI agents.
Test it like an agent
Step 1: Open a product page in a private window
No cookies, no history: the way an agent's fresh browser arrives. Use a phone-sized window too, where overlays cover the most.
Step 2: Answer three questions without clicking
Can you read the product name, the price and the stock state? If an overlay hides any of them, an agent has to deal with it first.
Step 3: Close everything with the keyboard
Press Tab to reach each close button and Escape to close each dialog. If you can't, neither can an agent that works through the accessibility tree.
In Aiscovery's AI agent test runs, named AI agents try key shopping tasks on your store in a read-only browser, and the masked step screenshots show the overlay an agent met and what it did next. See how a test run works.
Keep going
- Variants and stockOnce the overlay is gone: can the agent read the size and stock?
- Accessibility for AI agentsAccessibility-tree signals, keyboard behavior and dynamic states.
- Product tourThe site check, AI agent test runs and the ranked fix list.
- Request a demoSee where named AI agents stop on your own product pages.