Served vs rejected: see how, who and where your site turns bots away
The Bots page now has a served-vs-rejected table for every bot, showing the status codes used, whether the real bot or impersonators are being blocked, and the paths where it happens.
The old "% allowed / % blocked" pills told you that a bot was being turned away. The new Served vs rejected section on the Bots page tells you the three things you actually need to decide anything:
- How — the status codes your site used (403, 429, 401, 451), with counts.
- Who — whether the rejected requests came from the verified bot or from impersonators wearing its name. Blocking only impersonators is the healthy pattern. Blocking the verified bot is either a decision or a firewall accident, and now you can tell which.
- Where — the top paths where the rejections happened, each linking to the URL page.
Bots that are mixed — served on some requests, rejected on others — sort to the top, because those are the ones worth a look. Filter to mixed, rejected outright, served only or not judged, and export the table as CSV. Bots that publish no identity to verify against are labelled "not verifiable" rather than guessed at.
Each row in the bot list below also swaps the pills for a served/rejected bar with counts.
Available everywhere: GET /public/v1/websites/{id}/bots/access in the API, get_bot_access in the MCP server and loglens bots-access in the CLI.