AMDT AI Traffic Analytics

AMDT AI Traffic Analytics watches; it does not touch. It records two things your usual analytics do not show:

• The AI bots that read your pages (GPTBot, ClaudeBot, PerplexityBot, Googlebot, Bingbot and the rest), and whether each one is who it says it is. It checks the bot’s IP address against the lists its operator publishes and against its reverse DNS, and flags as an impostor any visitor that uses another bot’s name. The Bot catalog shows how big each list is and the date its operator gave it, so you can tell a list kept up to date from one left untouched for a year.
• The people who arrive from an AI assistant (ChatGPT, Claude, Perplexity, Gemini, Copilot…) after clicking a citation, and the page they land on.

With that it gives you a dashboard, a log you can filter and export, and an analysis of the addresses it could not identify, with blocking rules already written for Apache, Nginx, Cloudflare or Wordfence. You apply those rules in your firewall: the plugin does not block anyone.

It also publishes your site’s llms.txt (an index of your content for language models), counts who reads it, and lets you leave posts out of it from the editor.

A complete edition, with more modules, also serves your content to AI agents through an API and an MCP server, publishes the files that announce them, declares AI usage permissions, protects that API and analyses your content. Both editions share the same tables and settings: you can move from one to the other without losing data.

What it stores

In your own database, for the retention you choose (30, 60 or 90 days):

• For the bots in its catalogue and for whoever reads your llms.txt: the IP address, the User-Agent and the page requested.
• For people who arrive from an AI assistant: only the network of their IP address (IPv4 up to the third block, IPv6 the first 48 bits), never the full address, plus the User-Agent, the page and the address of the assistant they came from.
• For automated browsers that pretend to be an iPhone (possibly Grok): the request, with its IP address.

Nothing is stored about ordinary visitors. If you turn on the debug log (Settings → Diagnostics), its entries also contain IP addresses and User-Agents. It is written to its own folder in uploads, amdt-ai-traffic-analytics/, in a file with a random key in its name; the folder denies direct access on servers that read .htaccess, such as Apache. It is deleted on uninstall if you choose to delete the data. Settings → Privacy → Policy guide has a suggested text for your privacy policy.

What it leaves in your visitors’ browsers

Nothing: no cookies, nothing stored in the browser. Pages carry a small script that, only when the visitor comes from an AI assistant, tells your own server about it.

External services

The plugin sends nothing to its author and has no telemetry. It connects to the services below. The IP lists are off on a new install until you turn them on.

Why the IP lists. To confirm that a visit from GPTBot, OAI-SearchBot, ChatGPT-User, OAI-AdsBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot or Perplexity-User really comes from its operator, the plugin can download, once a day, the lists of IP addresses those operators publish. It is off until you turn it on: a notice asks you when you activate the plugin, and Settings has the switch.

What is sent, and when. Once a day while the switch is on, and once when you turn it on, the plugin makes a plain HTTPS GET request for each public file below. The request carries the plugin’s name and version as its user agent and nothing else: no data about your site, your visitors or you.

OpenAI (GPTBot, OAI-SearchBot, ChatGPT-User, OAI-AdsBot)

• Files downloaded: https://openai.com/gptbot.json, https://openai.com/searchbot.json, https://openai.com/chatgpt-user.json, https://openai.com/adsbot.json
• What they are: Overview of OpenAI Crawlers
• Provided by OpenAI: terms of use, privacy policy

Anthropic (ClaudeBot, Claude-User, Claude-SearchBot)

• File downloaded: https://claude.com/crawling/bots.json. claude.com is Anthropic’s domain for Claude; its own pages link Anthropic’s terms and privacy policy, below.
• What it is: Does Anthropic crawl data from the web, and how can site owners block the crawler?
• Provided by Anthropic: consumer terms, privacy policy, Anthropic Privacy Center

Perplexity (PerplexityBot, Perplexity-User)

• Files downloaded: https://www.perplexity.ai/perplexitybot.json, https://www.perplexity.ai/perplexity-user.json. These are the addresses Perplexity’s documentation gives; until 2.7.13 the plugin used www.perplexity.com, which redirects to them.
• What they are: Perplexity Crawlers
• Provided by Perplexity: terms of service, privacy notice

Reverse DNS

To tell which network a bot’s address belongs to, the plugin asks the DNS resolver your server uses for the name of the IP address of the bots and of whoever reads your llms.txt (never of the people who arrive from an assistant). This goes through your server’s own resolver, as any reverse lookup does.

Your own site

When you open the Dashboard or Settings, the plugin requests your own home page, at most twice a day, to find out whether a cache sits in front of WordPress, and your own /llms.txt, at most once a day, to check that visitors get it. Both are requests to your own server; the “Check again” buttons repeat them on demand.

Third-party library

The Dashboard charts use Chart.js 4.6.1 (MIT license), bundled in admin/js/chart.umd.min.js: the minified build its authors publish on npm, without the line that points to its source map. Its source code: https://github.com/chartjs/Chart.js