Questions · Evaluate

Could this be a fault in the scan rather than in my store?

That is why we check twice. A refused page is held, not reported, and opened again at least ten minutes later. We report it only when the second answer matches the first, and never when the refusal came from our own network.

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.

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