Failure class
Blocked by bot management
A WAF or bot-management rule returns 403, a challenge page or an empty response to an AI agent before it reaches the funnel.
Who it hits
The same site works for people but a whole agent column fails at step 1. Often a new rule shipped the same week.
How to fix it
- Allow verified, signed agents (Web Bot Auth) rather than blocking by user agent.
- Keep bot rules in “monitor” for known agent vendors while you measure.
- Treat agent traffic as customer traffic in your WAF analytics.
How alt.qa detects it
We tag a finding as “Blocked by bot management” when the trace shows this pattern at the blocking step. It only becomes a ticket once it is Confirmed (reproduced in two or more cells or by replay), and we show which personas and agents it hit.
In an Alt Matrix
Look for the pattern: a failing column usually means an agent-class problem; a failing row a persona problem; the same step failing in three or more cells a product bug.
See where agents fail on your funnel.
Run one free cell on a property you own. No sales call, no card.