Questions · Evaluate

Why does the product page open for me but not for the agent?

Most rules that refuse a page look at who is asking: a new browser with no cookies, a network your store has not seen, several requests close together. You arrive as a customer the store knows. The agent arrives as a stranger, which is exactly how a shopper’s assistant arrives too.

Why it happens

An agent opens a product the way a shopper does, in a browser with no account and no history on the store. Rules in front of a storefront often treat that visitor differently from a returning customer: a firewall rule that refuses an unfamiliar browser, a rate limit set for a person rather than an assistant comparing several products, a country block, or a rule that answers 503 on the origin’s behalf.

Nothing on the page says which rule fired, so the agent has nothing to work around. It does not wait and retry for minutes the way a determined person might. It moves on to a store that answered.

A refusal is not a bot wall. A bot wall shows a challenge an agent cannot solve, and names itself in its markup or its headers. A refused page names nothing, which is why we look twice before reporting it: a single refusal can be a moment of load, and only a refusal that comes back the same later is reported as the store’s.

This comes up at the Evaluate stage. The full treatment, including how to reproduce it and what to change, is on The store refused the product page to the agent.

Related questions

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