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.

Ayuda WordPress

Fernando Tellado

AI Content Signals lets you declare, in a machine-readable way, how AI systems may use your content: for search indexing, real-time AI answers (RAG), or model training. It started with Cloudflare’s Content Signals in robots.txt and now expresses the same preferences across several surfaces, so more crawlers and tools can read them:
<ul>
<li>robots.txt — Cloudflare Content Signals (search / ai-input / ai-train)</li>
<li>HTTP header — <code>X-Robots-Tag: noai, noimageai</code></li>
<li>HTML meta — robots <code>noai, noimageai</code></li>
<li>/.well-known/tdmrep.json — W3C Text and Data Mining Reservation Protocol</li>
<li>EU Directive 2019/790 rights reservation</li>
</ul>
Everything is opt-in and does not change your robots.txt output unless you enable it.
The signals you control
You set three preferences, and AI Content Signals expresses each one in the right format on every surface you enable:
<ul>
<li>search — allow or deny search indexing and traditional search results (links and short snippets)</li>
<li>ai-input — allow or deny using your content for real-time AI answers (RAG, grounding, AI Overviews)</li>
<li>ai-train — allow or deny using your content to train or fine-tune AI models</li>
</ul>
These three come from Cloudflare’s Content Signals vocabulary, written to your robots.txt. When you deny AI training, the same opt-out is also emitted on any other surface you enable: <code>noai, noimageai</code> in an HTML meta tag and an <code>X-Robots-Tag</code> header, plus a <code>tdm-reservation</code> in your TDMRep manifest. Declaring the same preference in several places means a crawler that ignores one signal may still honor another.
Key Features
<ul>
<li>Easy-to-use settings page in WordPress admin</li>
<li>Set global defaults for all crawlers</li>
<li>Configure specific settings for individual AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.)</li>
<li>Add custom bot User-Agents</li>
<li>Supports both physical and virtual robots.txt files</li>
<li>Option to create physical robots.txt with basic WordPress rules</li>
<li>Preview generated Content Signals before applying</li>
<li>Export and import settings as JSON for easy migration between sites</li>
<li>Optional legal text with EU Directive reference</li>
<li>Developer-friendly: filter hook to extend the predefined bots list</li>
<li>Works with existing robots.txt from SEO plugins</li>
<li>Automatic sitemap detection and inclusion</li>
<li>Optional extra output surfaces: HTML robots meta tag (noai, noimageai), X-Robots-Tag header, and a W3C TDMRep file at /.well-known/tdmrep.json</li>
</ul>
Supported Bots
The plugin includes predefined settings for 28 major AI crawlers:
<ul>
<li>OpenAI GPTBot, OAI-SearchBot, and ChatGPT-User</li>
<li>Anthropic ClaudeBot, Claude-Web, and anthropic-ai</li>
<li>Perplexity Bot and Perplexity-User</li>
<li>Google Extended (Gemini) and GoogleOther</li>
<li>Amazon Bot</li>
<li>Apple Extended</li>
<li>Meta/Facebook Bot and meta-externalagent</li>
<li>DuckDuckGo DuckAssistBot</li>
<li>Allen Institute AI2Bot</li>
<li>Mistral AI</li>
<li>ByteDance Bytespider</li>
<li>DeepSeek AI</li>
<li>xAI Grok</li>
<li>Huawei Pangu</li>
<li>Common Crawl, Cohere AI, Diffbot, You.com Bot, and more</li>
</ul>
Important Notice
Content Signals is a declarative standard – it expresses your preferences but does not technically enforce them. AI companies are not legally required to respect these signals, though the plugin includes legal text referencing EU copyright directives.
The IETF AI Preferences (AIPREF) Working Group is currently developing a formal standard based on similar concepts. This plugin implements the current Cloudflare Content Signals specification and will be updated as standards evolve.
This plugin works best when combined with other protection measures like traditional robots.txt rules and server-level bot management.
<h3>Support</h3>
Need private support or custom development?
Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just <a href="mailto:ai-content-signals@ayudawp.com" rel="nofollow ugc">contact me</a> and tell me what you need.
Need help or have suggestions?
<ul>
<li><a href="https://servicios.ayudawp.com" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/ai-content-signals/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/AyudaWordPressES" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
Love the plugin? Please leave us a <a href="https://wordpress.org/support/plugin/ai-content-signals/reviews/#new-post" rel="ugc">5-star review</a> and help spread the word!
<h3>About AyudaWP.com</h3>
We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.

AI Content Signals

Control how AI uses your content — search, AI answers or training — via robots.txt Content Signals, HTTP headers, meta tags and TDMRep.

PufferSights – AI Crawler Insights vs AI Content Signals