senols

PufferSights monitors 100+ known AI crawler and AI agent user agents, hashes IP addresses, groups traffic by bot, provider, crawl purpose, content type, and response status, tracks human referrals from AI surfaces, and can publish a dynamic llms.txt content map for public site content.
The dashboard summarizes:
<ul>
<li>HTTP traffic by bot.</li>
<li>Crawl purpose.</li>
<li>Content type.</li>
<li>Response status.</li>
<li>AI referrals and crawl-to-refer ratio.</li>
<li>Top crawled content.</li>
<li>Tracked agent count.</li>
<li>Dynamic llms.txt content map.</li>
<li>robots.txt audit and policy snippets.</li>
</ul>
The crawler registry is based on current public operator documentation and industry references for OpenAI, Anthropic, Perplexity, Google, Apple, Common Crawl, Meta, ByteDance, Microsoft, Amazon, and related AI crawler operators.
The plugin does not contact any external service. All analytics data is stored in your own WordPress database.
robots.txt publishing is off by default. The plugin can generate and optionally publish policies for:
<ul>
<li>Monitor only.</li>
<li>Block training crawlers.</li>
<li>Allow AI search/user-action bots while blocking training crawlers.</li>
<li>Block all known AI bots.</li>
</ul>
llms.txt publishing is on by default and can be disabled in the PufferSights settings. The generated <code>/llms.txt</code> file lists selected published public pages and posts in Markdown so AI assistants can find the site’s main public content more easily.
<h3>Important Notes</h3>
User-agent detection is not bot verification. User agents can be spoofed. Raw IP addresses are not stored; the plugin stores a salted hash for rough uniqueness.
robots.txt is voluntary. Use a WAF, CDN, or server-level controls when technical enforcement is required.
Google-Extended and Applebot-Extended are robots.txt control tokens rather than normal request user agents, so they appear in robots.txt audits and policy snippets but usually do not appear in request logs.
llms.txt is a content map, not an access-control policy. It does not replace robots.txt and does not force AI systems to use or cite your content.
<h3>Privacy</h3>
PufferSights stores local analytics for public, logged-out requests only. It does not track wp-admin pages, logged-in users, AJAX requests, or WP-Cron requests.
The plugin stores:
<ul>
<li>Request time and date.</li>
<li>Event type, such as AI crawler request or AI referral.</li>
<li>HTTP method.</li>
<li>Request path without query string.</li>
<li>HTTP response status.</li>
<li>MIME/content group.</li>
<li>Matched crawler or AI referral provider.</li>
<li>User-agent string and user-agent hash.</li>
<li>Salted one-way hash of the request IP address.</li>
<li>Referrer origin only, such as <code>https://chatgpt.com</code>, without referrer path or query string.</li>
</ul>
The plugin does not store raw IP addresses, cookies, browser local storage, or complete referrer URLs. It does not send analytics, telemetry, crawler records, or site data to third-party services.
If llms.txt publishing is enabled, the plugin serves a Markdown overview of selected published public posts and pages at <code>/llms.txt</code>. Drafts, private posts, and password-protected posts are not included.
Administrators can disable tracking, clear captured events, and configure retention from the PufferSights admin page. The default retention period is 90 days. On uninstall, the plugin removes its custom analytics table, saved options, and scheduled cleanup hook.
The plugin also adds suggested disclosure text to WordPress’ Privacy Policy Guide.

PufferSights – AI Crawler Insights

Monitor 100+ known AI crawler and AI agent user agents with local analytics, AI referrals, llms.txt, and opt-in robots.txt policy tools.

Temso AI

Temso captures every request your WordPress origin serves over HTTP and sends it to Temso in the background. No DNS changes, no extra infrastructure — install, paste two values, done.
<ul>
<li>Captures all server-side requests — front-end, wp-admin, REST, AJAX, login, xmlrpc. Bot classification happens in Temso.</li>
<li>Non-blocking, batched delivery — adds no perceptible latency to your pages.</li>
<li>No cookies, no JavaScript, no client-side tracking.</li>
<li>Visitor IPs are sent over TLS and hashed in Temso before storage; raw IPs are never retained.</li>
<li>WordPress Multisite supported (activate and connect per site).</li>
</ul>
Learn more at <a href="https://temso.ai/" rel="nofollow ugc">temso.ai</a>.
Requests served from full-page cache never reach PHP and therefore can’t be captured by any origin plugin — this is expected and matches the documented CDN-cache limitation.
<h3>Privacy</h3>
This plugin sends the following per HTTP request that WordPress serves (front-end, wp-admin, REST, AJAX, login, xmlrpc) to the Temso API endpoint you configure: timestamp, request URL, HTTP method, response status, user agent, referer, and the visitor IP address. The IP address is transmitted over TLS and hashed by Temso before storage — it is never stored in raw form, and the plugin sets no cookies and adds no client-side tracking.

Stream front-end request logs from your WordPress origin to Temso so AI-crawler and bot traffic shows up in your dashboard.

PufferSights – AI Crawler Insights vs Temso AI