Questions · Discover

Why does my store block agents when I never chose to?

Bot management ships with category defaults, and an automated browser from a data centre falls into a category most defaults treat as unwanted. The setting that blocks a shopping agent is usually one nobody at the store selected deliberately.

Why it happens

Bot management assigns a score to the request before your theme is involved. An agent driving a headless browser from a data centre address looks, on every one of those signals, like the scraping traffic the product was bought to stop. The challenge that follows expects a human interaction the agent cannot perform.

The loss is invisible in analytics, and that is the property that makes this stall dangerous. A request that is challenged before the page loads produces no session, no pageview and no add to cart, so it never appears in your conversion rate. It appears as an absence.

This comes up at the Discover stage. The full treatment, including how to reproduce it and what to change, is on Bot protection blocks the agent before the storefront loads.

Related questions

Run a free scan and find out which of these your store actually hits.