Description
Anyone can put “GPTBot” or “ClaudeBot” in a request. On real servers a large share of “AI bot” traffic is vulnerability scanners in disguise. This plugin checks every AI-bot visit against the IP ranges that OpenAI, Anthropic, Perplexity, Google, Microsoft, Apple, Common Crawl, DuckDuckGo and Mistral publish, and shows you:
- Real vs fake visits per AI bot (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, Amazonbot, Meta and more)
- Which pages verified AI crawlers read
- Visitors sent to you by AI assistants (ChatGPT, Perplexity, Claude, Gemini, Copilot…)
- Signed AI agents: verifies Web Bot Auth (IETF draft, HTTP Message Signatures) signatures from agents that sign their requests
- Optional: block fake AI bots (safe — a genuine request from the operator can’t fail the IP check)
Crawlers don’t run JavaScript, so script-based analytics can’t see them. This plugin runs on your server and stores only daily counts in your own database.
External services
Nothing is downloaded until you switch it on in Tools AI Bot Analytics Settings. There are two separate options, both off by default:
-
“Download the bot list”: once a day, the bot list (
https://botledger.website/data/v1/ranges.json): bot names, user-agent patterns and the operators’ official IP ranges. No visitor data is sent; it’s a plain download. The request shows your server’s IP address and the user-agentBotLedger/<version>(not your site address or WordPress version). Privacy policy, terms.
The same file also contains Cloudflare’s published edge IP ranges, so the real visitor IP can be read safely when your site is behind Cloudflare. -
“Check signed AI agents”: when a request carries a Web Bot Auth signature, the plugin downloads that agent’s public key directory from the HTTPS address the agent names (
https://<agent host>/.well-known/http-message-signatures-directory) to check the signature. Because the address comes from the incoming request, any visitor can make your server look up a host they choose; only that public file is requested, with the user-agentBotLedger/<version>(no site address, WordPress version or visitor data), and the host sees your server’s IP address. Requests to private/internal addresses are refused, results are cached for a day, and at most 20 new agents are looked up per hour.
Screenshots

FAQ
Does it slow my site down?
Normal visitors only cost one string check. AI-bot requests add one small database write.
My bots all show as “can’t verify”
Your site is behind a proxy or CDN that hides the visitor IP. Make sure it forwards the client IP (CF-Connecting-IP or X-Forwarded-For).
Is Google-Extended a crawler?
No. Google documents it as a robots.txt token without its own user agent, so requests claiming it are counted as fake.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“BotLedger – Verified AI Bot Analytics” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “BotLedger – Verified AI Bot Analytics” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.3.2
- Bot list and links now use the project’s own domain, botledger.website.
0.3.1
- Shorter primary key for the stats table (works on older MySQL with the 767-byte index limit).
- Own downloads send the user-agent BotLedger/ instead of WordPress’s default (no site address).
- Agent key lookups are a separate opt-in setting; stricter validation of request headers.
0.3.0
- Renamed to BotLedger – Verified AI Bot Analytics.
- Remote downloads (bot list, agent key directories) only after the admin switches them on in Settings.
0.2.0
- Verify Web Bot Auth signatures (Ed25519) from signed AI agents; new dashboard section.
0.1.1
- All admin strings translatable.
0.1.0
- First release.
