Monthly report · Verity Score exclusive dataset
AI Traffic Report · verityscore.io
First public measurement of AI bot hits across the 28 /.well-known/ endpoints published on verityscore.io. Refreshed on every deploy, continuous capture since April 2026.
- Period
- 2026-11-06 → 2026-11-06
- AI hits
- 0
- Files tracked
- 0 / 28
- Distinct bots
- 0
- Days measured
- 0
Data is being captured
Data is not yet available for this period. The aggregation backend may have been unreachable at build time, or capture just started. The page is regenerated on every deploy.
Methodology
Every GET request on one of the 28 tracked endpoints is recorded by the site's edge Worker (Cloudflare) before the static file is returned. For discovery files, the payload contains the User-Agent, the Web Bot Auth Signature-Agent and Signature-Input headers (the signature itself is reported as present only), Accept header, referrer, cookie presence only, Cache-Control header and query parameters, with no IP address. It is sent fire-and-forget to verity-server, which aggregates into MongoDB as daily buckets (file × date).
Bot attribution uses the canonical User-Agent regex (GPTBot, ClaudeBot, Bytespider, etc.). Operators (OpenAI, Anthropic, Perplexity, Meta, Microsoft, Google, Apple, ByteDance) are mapped from each operator's officially documented bot list. No IP-range cross-check is shown publicly : the User-Agent is the only attribution source displayed.
The 'human' bucket (visitors without a bot signature) is excluded: this report covers AI traffic only. Unidentified bots fall into 'other-bot' or 'unknown'.
The report is rebuilt on every deploy of verityscore.io (Astro static + build-time fetch). Typical cadence: 1 to 4 deploys per month.
Measure your own Agent Readiness
Our free audit checks whether the 11 /.well-known/ files recommended by Cloudflare Agent Readiness are published on your store, in under 60 seconds.
Install free