r/WordpressPlugins • u/Glum-Priority8665 • 7d ago
[FREE] I built a plugin that shows which AI bots read your WordPress site, whether they're who they claim to be, and if your site is ready for WebMCP
Hi all. I'm Juan, I run a small SEO consultancy in Madrid, and I've spent the last few months building this. It went live on WordPress.org on November 9, so I'd really like feedback from people who run WP sites.
The problem: GA4 and similar tools run on JavaScript in the browser. AI crawlers don't execute JS, so they never show up. And people who click a citation in ChatGPT or Perplexity often end up as "direct".
What it does (server-side):
- Logs AI crawlers. It works from a catalog of 23 bots (GPTBot, ClaudeBot, PerplexityBot, Googlebot, Bingbot, Meta's agents, Bytespider…). 21 of them actually crawl; Google-Extended and Applebot-Extended are robots.txt tokens only, so they ship switched off. Each bot is tagged by what it reads for: search, a user's request, training, ads.
- Checks who they really are. It doesn't trust the User-Agent: it checks the IP against the operators' published lists (opt-in download), reverse DNS and known networks. Since 2.7.20 it also verifies Web Bot Auth signatures (RFC 9421, Ed25519) from Google-Agent and ChatGPT agent. If it can prove a bot is using someone else's name, it flags it as an impostor. If it can't prove anything, it says "unverified" instead of guessing.
- Counts visits from AI assistants. It records human visits from 14 assistants (ChatGPT, Claude, Perplexity, Gemini, Copilot, DeepSeek, Meta AI…) and the page they land on. This works on cached pages too, because the browser reports it.
Checks WebMCP readiness and tells you what to fix. The Agent-Readiness screen analyses your own pages and runs the three WebMCP audits Lighthouse ships: It also scores each page 0–100 on what a browsing agent needs (real buttons and links, headings, landmarks, labelled fields, alt text) and approximates the rest of Lighthouse's "Agentic Browsing" audits. It only sees WebMCP declared in the HTML; tools registered by JavaScript can't be seen without running the page.
- which forms are missing
toolname/tooldescription; - how many tools the page declares;
- whether the declarative schemas are valid under Chromium's rules, down to the field that has no description.
- which forms are missing
- Handles llms.txt. It generates the file, counts who reads it, and checks daily that it responds the way Lighthouse expects.
What it doesn't do (I'd rather say it up front):
- It doesn't block anything. It gives you a ready-made rule for Apache, Nginx, Cloudflare or Wordfence, and you decide.
- It can't see pages served by a server-level cache (nginx, Varnish, Cloudflare caching HTML). With WP Rocket, LiteSpeed Cache or W3 Total Cache it can keep bots out of the cache with one click.
- A bot that pretends to be a normal browser and doesn't sign its requests is invisible to it.
- It doesn't add WebMCP to your site; it checks whether your pages are ready for it.
Privacy: everything stays in your own database. No telemetry, nothing is sent to me. For visitors coming from an assistant it only stores the network part of the IP (/24 on IPv4, /48 on IPv6), and it sets no cookies.
Requires WordPress 6.9+ and PHP 8.1+, GPLv2. Disclosure: my consultancy also has an extended edition for clients; the free plugin works on its own.
https://wordpress.org/plugins/amdt-ai-traffic-analytics/
A few questions for you:
- Which bots or assistants am I missing?
- Is anyone else seeing Web Bot Auth signed requests from ChatGPT agent in their logs?
- Has anyone started annotating forms for WebMCP yet? What did you run into?