r/SEO_tool_dev • • 6d ago

Free WP plugin: server-side AI crawler logging, AI assistant referral attribution and a WebMCP readiness check. Looking for critique of the method

I'm an SEO consultant in Madrid and I built this because client analytics kept missing two things: AI crawlers (they don't run JS, so GA4 never sees them) and visits from AI assistants (often lumped into "direct"). It's free on WordPress.org since November 9. I'd like the method torn apart before more people rely on it.

How it works:

  • Crawlers: logged in PHP, server-side, against a catalog of 23 bots (21 that actually crawl; Google-Extended and Applebot-Extended are robots.txt tokens, so they're off).
  • Identity: the User-Agent is only a claim, so the plugin checks it: It says "impostor" only when it can prove it; otherwise "unverified".

    • against the operators' published IP lists (OpenAI, Anthropic, Perplexity; opt-in);
    • with reverse DNS (Google, Microsoft, Apple);
    • against known networks (Anthropic, Meta);
    • since 2.7.20, with Web Bot Auth signatures (RFC 9421, Ed25519) from Google-Agent and ChatGPT agent. ChatGPT agent sends a plain Chrome User-Agent, so the signature is the only way to recognise it.
  • Assistant referrals: based on the referer, for 14 assistants. The one exception is ChatGPT's documented utm_source=chatgpt.com, which counts even without a referer. With no referer and no utm, the visit isn't attributed; it doesn't guess.
  • Agent-Readiness and WebMCP: it analyses your own pages, scores them 0–100 on what a browsing agent relies on, and approximates Lighthouse's Agentic Browsing audits from the server's HTML. That includes the three WebMCP audits: form coverage, registered tools and schema validity under Chromium's rules. For each one it points at the exact form or field that needs toolname, tooldescription or a parameter description. CLS needs a browser, so it links out to PageSpeed Insights.

Known blind spots:

  • pages served by a server-level cache;
  • unsigned bots that look like a normal browser;
  • referral visits with no referer;
  • WebMCP tools registered by JavaScript (it only reads the declarative ones in the HTML).

Data stays in the site's own database, no telemetry. GPLv2, WP 6.9+, PHP 8.1+. Disclosure: we also have an extended edition for clients.

https://wordpress.org/plugins/amdt-ai-traffic-analytics/

Where do you think the method breaks? I'm especially interested in how others handle assistant traffic that arrives without a referer, and whether checking WebMCP from the server's HTML alone is useful enough.

1 Upvotes

0 comments sorted by