內容簡介
AITooler Bot Analytics 是一款專為網站擁有者設計的外掛，能夠追蹤並分析 AI 爬蟲的訪問情況，提供有關爬蟲行為的詳細報告，並協助管理網站內容的可讀性及訪問權限。
【主要功能】
• 追蹤 16 種已知 AI 爬蟲的訪問
• 提供內容可讀性檢查的 llms.txt 檔案
• 透過 robots.txt 規則控制爬蟲訪問
• 自動更新訪問記錄，無需手動上傳
• 不會影響網站速度或傳送數據至外部
外掛標籤
開發者團隊
② 後台搜尋「AITooler Bot Analytics – AI Crawler Tracking & Visibility」→ 直接安裝（推薦）
原文外掛簡介
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.
AITooler Bot Analytics answers three questions from one screen:
1. Which AI bots are crawling my site?
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…), AI search indexing (OAI-SearchBot, PerplexityBot…) and live user requests (ChatGPT-User, Claude-User — a real person asked an assistant to open your page).
That last group matters. Those are potential readers and customers, not just crawlers.
2. Is my content readable for AI?
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.
3. Who is allowed in?
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.
What this plugin does NOT do
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.
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.
It does not nag you with upgrade banners.
Good to know
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’s the case.
robots.txt is a voluntary standard. Reputable crawlers respect it; obscure scrapers may not.
llms.txt is an emerging convention. Adoption by AI companies varies, but publishing one costs you nothing and several crawlers already fetch it.
What makes this different from the existing 150+ plugins in this space?
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.
Built and maintained by a site operator who got tired of grepping access logs to see whether AI bots had come by.
