Name: AITooler Bot Analytics – AI Crawler Tracking & Visibility
Availability: InStock
Author: aitooler

See which AI crawlers visit your site, serve llms.txt automatically, and manage AI bot access. Everything stays in your own database.

AITooler Bot Analytics – AI Crawler Tracking & Visibility

<p>AI assistants send real traffic now, but most site owners have no idea whether GPTBot, ClaudeBot or PerplexityBot ever visit their pages. Analytics tools ignore them. Server logs are a pain to read.</p>
<p>AITooler Bot Analytics answers three questions from one screen:</p>
<p><strong>1. Which AI bots are crawling my site?</strong></p>
<p>The plugin recognizes 16 known AI crawlers and logs their visits into a table in your own WordPress database. You get a report showing visits per bot, the pages they hit most, and when each bot was last seen. Bots are grouped by what they actually do: model training (GPTBot, ClaudeBot, CCBot&#8230;), AI search indexing (OAI-SearchBot, PerplexityBot&#8230;) and live user requests (ChatGPT-User, Claude-User — a real person asked an assistant to open your page).</p>
<p>That last group matters. Those are potential readers and customers, not just crawlers.</p>
<p><strong>2. Is my content readable for AI?</strong></p>
<p>The plugin serves llms.txt and llms-full.txt at your site root — a structured index of your content following the llmstxt.org convention. No files are written to disk, nothing to upload over FTP. The output refreshes automatically when you publish or update content.</p>
<p><strong>3. Who is allowed in?</strong></p>
<p>A simple table lets you block individual bots via robots.txt rules. Maybe you want AI search engines to index you but prefer to keep training crawlers out. One checkbox per bot.</p>
<h4>What this plugin does NOT do</h4>
<ul>
<li>It does not send your data anywhere. There is no external service, no account, no API key, no telemetry. Visit logs live in your database and are pruned automatically after a retention period you choose.</li>
<li>It does not slow your site down. Logging is a single indexed insert with a deduplication check against the same table. There is no JavaScript on the front end.</li>
<li>It does not nag you with upgrade banners.</li>
</ul>
<h4>Good to know</h4>
<ul>
<li>The robots.txt controls work when WordPress generates robots.txt dynamically. If a physical robots.txt file exists in your site root, it takes precedence — the settings page tells you if that&#8217;s the case.</li>
<li>robots.txt is a voluntary standard. Reputable crawlers respect it; obscure scrapers may not.</li>
<li>llms.txt is an emerging convention. Adoption by AI companies varies, but publishing one costs you nothing and several crawlers already fetch it.</li>
</ul>
<h4>What makes this different from the existing 150+ plugins in this space?</h4>
<p>Most existing plugins only generate the llms.txt file. This one combines three things that are typically separate: crawler visit analytics (so you know what is actually happening), content exposure (llms.txt), and access control (robots.txt rules) — all local, all in one screen, no accounts or external services.</p>
<p>Built and maintained by a site operator who got tired of grepping access logs to see whether AI bots had come by.</p>


Alternative Plugins for

Discover the Lists with AITooler Bot Analytics – AI Crawler Tracking & Visibility