Separate reader traffic
Verified bot or crawler requests can be explained in a support context and kept out of high-intent decision copy.
Keep technical interpretation visible and prevent confusion between monitoring and reader intent pages.
Requests are not readers
The useful question is not whether traffic looks busy; it is which activity represents readers, monitoring, crawlers, retries, or system errors.
Check the logs first
- Keep verified bots documentation as a diagnostic companion linked from issue entry points only
- Keep the test narrow: one service scenario with clear inputs, deliverables, acceptance rules, and human review
What still needs proof
Misleading readers with raw bot context can reduce confidence. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.