zicygp

<p>Zicy AI Access Monitor helps site owners understand when known AI crawlers and AI assistant retrieval agents access their WordPress content.</p>
<p>The plugin logs self-identifying AI-related User-Agents, summarizes raw visits into daily totals, and provides an admin dashboard for reviewing AI access patterns across your site. It is designed for AI visibility, AI search optimization, and content monitoring workflows.</p>
<p><strong>What it tracks:</strong></p>
<ul>
<li>Search crawlers — AI systems that may crawl content for search or answer retrieval workflows, such as OAI-SearchBot and PerplexityBot</li>
<li>Training crawlers — AI-related crawlers that may access content for model training or dataset-building workflows, such as GPTBot, ClaudeBot, CCBot, Amazonbot, Bytespider, CohereBot, Mistral-ai, and Meta-WebIndexer</li>
<li>User proxies — AI assistant fetchers that retrieve pages when responding to user requests, such as ChatGPT-User, Claude-User, Perplexity-User, Gemini-Deep-Research, Google-Agent, and BingPreview</li>
<li>AI control agents — AI-related User-Agents such as Google-Extended that may represent AI data-use control behavior rather than ordinary search crawling</li>
</ul>
<p><strong>How it works:</strong></p>
<ol>
<li>Matching visits are recorded as temporary raw logs.</li>
<li>URLs are normalized to reduce duplicates caused by common tracking parameters.</li>
<li>IP addresses are anonymized by default before being stored.</li>
<li>Each night at 02:15 site time, raw logs older than today are summarized into daily totals.</li>
<li>Raw logs that have been rolled up are deleted.</li>
<li>Daily summary records are retained so you can review historical AI access activity.</li>
</ol>
<p><strong>In your WordPress admin dashboard:</strong></p>
<ul>
<li>View daily summaries of known AI bot and AI assistant access</li>
<li>See today’s raw logs before the next rollup</li>
<li>Filter by date, bot, type, or signature</li>
<li>Review top pages accessed by AI assistant user proxies</li>
<li>Compare week-over-week activity for top pages</li>
<li>See vendor diversity indicators for accessed pages</li>
<li>Export daily summary data as CSV</li>
<li>Receive weekly email summaries with top accessed pages</li>
<li>Generate copy-ready AI Tracking Briefs for selected pages</li>
</ul>
<p><strong>Why it matters:</strong></p>
<ul>
<li>See which known AI systems are accessing your content</li>
<li>Identify which pages AI assistants retrieve most often</li>
<li>Support AI search optimization and AI visibility reporting</li>
<li>Understand differences between crawler, training, control, and user-triggered AI access</li>
<li>Build structured page briefs that can be used in AI visibility workflows</li>
</ul>
<p><strong>Bot allowlist includes:</strong></p>
<ul>
<li>OpenAI: GPTBot, OAI-SearchBot, ChatGPT-User</li>
<li>Anthropic: ClaudeBot, Claude-User, Claude-SearchBot</li>
<li>Perplexity: PerplexityBot, Perplexity-User</li>
<li>Google: Google-Extended, Gemini-Deep-Research, Google-Agent</li>
<li>Microsoft: BingPreview</li>
<li>Amazon: Amazonbot</li>
<li>Common Crawl: CCBot</li>
<li>ByteDance: Bytespider</li>
<li>Cohere: CohereBot</li>
<li>Mistral: Mistral-ai</li>
<li>Meta: Meta-WebIndexer</li>
</ul>
<p>Developers can extend or modify the allowlist with the <code>gp_aibal_ai_bots</code> filter.</p>
<p><strong>Important detection note:</strong></p>
<p>This plugin detects only self-identifying User-Agents. It does not guarantee that every visit is from the claimed company or system, because User-Agent headers can be spoofed. The plugin should be used as a visibility and reporting aid, not as a security or access-control tool.</p>
<h3>Privacy</h3>
<p>Zicy AI Access Monitor is designed to keep raw request-level data temporary.</p>
<p>The plugin stores matching AI-related access events in your WordPress database, anonymizes IP addresses by default, rolls raw logs into daily summaries, and deletes rolled-up raw logs. Daily summaries are retained for reporting. The plugin does not send logged access data to Zicy or any third-party service.</p>
<p>Site owners are responsible for ensuring that their use of access logging complies with applicable privacy laws and their own privacy policy.</p>


Zicy AI Access Monitor

Monitor known AI crawlers and AI assistant fetches, with daily rollups, CSV exports, weekly summaries, and page briefs.

Freemius

Sajjad Ali

Pagup

<p>Better Robots.txt replaces the default WordPress robots.txt workflow with a smarter, structured version you can configure and preview before publishing.</p>
<p>Instead of a blank textarea, you get a guided wizard with presets, plain-language explanations, and a final Review & Save step so you can inspect the generated robots.txt before it goes live.</p>
<p>Built for beginners and advanced users alike, Better Robots.txt helps you control how search engines, AI crawlers, SEO tools, archive bots, bad bots, social preview bots, and other automated agents interact with your site.</p>
<p>Trusted by thousands of WordPress sites, Better Robots.txt is designed for the AI era without resorting to hype, vague promises, or hidden rules.</p>
<p>Better Robots.txt is available in Free, Pro, and Premium editions. The free plugin covers the guided workflow and essential crawl control features, while Pro and Premium unlock additional governance, protection, and AI-ready modules. Some screenshots on the plugin page show features from all three editions.</p>
<h3>A quick overview</h3>
<p><iframe loading="lazy" title="Better robots.txt Video — AI-Ready Crawl Control for WordPress" src="https://player.vimeo.com/video/1169756981?dnt=1&app_id=122963" width="750" height="372" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share" referrerpolicy="strict-origin-when-cross-origin"></iframe></p>
<h3>Why Better Robots.txt is different</h3>
<p>Most robots.txt plugins fall into one of three categories:</p>
<ul>
<li>Simple text editor</li>
<li>Virtual robots.txt manager</li>
<li>Single-purpose AI or policy add-on</li>
</ul>
<p>Better Robots.txt goes further.</p>
<p>It gives you a complete, guided crawl control workflow so you can:</p>
<ul>
<li>Choose a preset that matches your goals</li>
<li>Control major crawler categories without writing everything by hand</li>
<li>Keep core WordPress protection rules visible and editable</li>
<li>Clean up low-value crawl paths that waste crawl budget</li>
<li>Generate a cleaner robots.txt output</li>
<li>Preview the final result before saving</li>
</ul>
<h3>What you can control</h3>
<p>Better Robots.txt helps you manage:</p>
<ul>
<li>Search engine visibility</li>
<li>AI and LLM crawler behavior</li>
<li>AI usage signals such as search, ai-input, and ai-train preferences</li>
<li>SEO tool crawlers</li>
<li>Bad bots and abusive crawlers</li>
<li>Archive and Wayback access</li>
<li>Feed crawlers and crawl traps</li>
<li>WooCommerce crawl cleanup</li>
<li>CSS, JavaScript, and image crawling rules</li>
<li>Social media preview crawlers</li>
<li>ads.txt and app-ads.txt allowance</li>
<li>llms.txt generation</li>
<li>Advanced directives such as crawl-delay and custom rules</li>
<li>Final review before publishing</li>
</ul>
<h3>Editions</h3>
<p>Better Robots.txt is available in three editions:</p>
<ul>
<li>Free – Includes the guided setup, the Essential preset, core crawl control features, and the final Review & Save workflow.</li>
<li>Pro – Adds more advanced governance and protection modules, including additional AI, crawler, and cleanup controls.</li>
<li>Premium – Unlocks the most restrictive and advanced protection options, including the Fortress preset and additional high-control modules.</li>
</ul>
<p>Some options shown in the interface are marked Free, Pro, or Premium so users can immediately understand which modules belong to each edition.</p>
<h3>Presets</h3>
<p>Setup starts with four modes:</p>
<ul>
<li>Essential – A clean, practical configuration for most websites that want a better robots.txt without complexity.</li>
<li>AI-First – For publishers and content sites that want AI-ready governance without shutting down discovery.</li>
<li>Fortress – For websites that want stronger protection against scraping, archive capture, and unnecessary crawl activity.</li>
<li>Custom – For users who prefer to configure each module manually.</li>
</ul>
<p>For many sites, one preset plus a quick review is enough.</p>
<h3>Built for beginners and experts</h3>
<p>Beginners get:</p>
<ul>
<li>A guided setup instead of a raw robots.txt box</li>
<li>Preset-based configuration</li>
<li>Plain-language explanations for important choices</li>
<li>A safer workflow with a final preview step</li>
</ul>
<p>Advanced users get:</p>
<ul>
<li>Editable core WordPress protection rules</li>
<li>Fine-grained crawler controls by category</li>
<li>WooCommerce-oriented cleanup options</li>
<li>Consolidated output options</li>
<li>Advanced directives and custom rules</li>
<li>A final output they can inspect before publishing</li>
</ul>
<h3>AI-ready, without hype</h3>
<p>Better Robots.txt includes features for modern AI-related crawl governance, including:</p>
<ul>
<li>AI crawler handling</li>
<li>Optional llms.txt support</li>
<li>AI usage signals for compliant systems</li>
<li>Optional machine-readable governance signals for advanced use cases</li>
</ul>
<p>These features help you express how you want automated systems to use your content.</p>
<p>However, Better Robots.txt does not claim to control AI by force. Like robots.txt itself, these signals are most useful with compliant systems and good-faith crawlers.</p>
<h3>What Better Robots.txt is</h3>
<p>Better Robots.txt is:</p>
<ul>
<li>A robots.txt governance plugin for WordPress</li>
<li>A guided configuration workflow instead of a raw text editor</li>
<li>A crawl control layer to reduce wasteful crawling</li>
<li>A practical bridge between SEO, crawl hygiene, and AI-era policy signaling</li>
<li>A way to keep your crawl policy clearer for humans and machines</li>
</ul>
<p>Technical reference for advanced users: Better Robots.txt also maintains a public <a href="https://github.com/GautierDorval/better-robots-txt" rel="nofollow noopener noreferrer ugc">GitHub repository</a> with product definition, governance notes, and machine-readable artefacts.</p>
<h3>What Better Robots.txt is not</h3>
<p>Better Robots.txt is not:</p>
<ul>
<li>A firewall or Web Application Firewall (WAF)</li>
<li>An anti-scraping enforcement engine</li>
<li>A legal compliance engine</li>
<li>A guarantee that every bot will obey your rules</li>
<li>A replacement for server-level security or access control</li>
</ul>
<p>It helps you publish a clearer crawl policy.</p>
<p>It does not replace infrastructure-level protection.</p>
<h3>Typical use cases</h3>
<p>Use Better Robots.txt if you want to:</p>
<ul>
<li>Clean up a weak or noisy default robots.txt</li>
<li>Reduce crawl waste on WordPress or WooCommerce</li>
<li>Keep major search engines allowed while restricting other bots</li>
<li>Control whether archive bots can snapshot your site</li>
<li>Publish AI usage preferences more clearly</li>
<li>Keep social preview bots allowed while limiting scrapers</li>
<li>Review the final file before making it live</li>
</ul>
<h3>Key Features</h3>
<ul>
<li>Guided step-by-step wizard</li>
<li>Preset-based setup: Essential, AI-First, Fortress, Custom</li>
<li>Search engine visibility controls</li>
<li>AI and LLM crawler governance</li>
<li>AI usage signals support</li>
<li>SEO tool crawler controls</li>
<li>Bad bot and abusive crawler options</li>
<li>Archive and Wayback access controls</li>
<li>Spam, feed, and crawl trap cleanup</li>
<li>WooCommerce crawl cleanup options</li>
<li>CSS, JavaScript, and image crawling rules</li>
<li>Social media preview crawler controls</li>
<li>ads.txt and app-ads.txt allowance</li>
<li>Optional llms.txt generation</li>
<li>Consolidated output option</li>
<li>Core WordPress protection rules remain visible and editable</li>
<li>Final Review & Save preview screen</li>
</ul>
<h4>About the publisher</h4>
<p>Better Robots.txt is developed and maintained by <a href="https://pagup.com/" rel="nofollow ugc">Pagup</a>, a digital readability firm based in Quebec, Canada. Pagup helps organizations become correctly understood by search engines, generative AI systems, and autonomous agents.</p>
<p>The robots.txt file is the first surface that AI crawlers read when they discover a site. A well-structured robots.txt that references governance files such as llms.txt, ai-manifest.json, and interpretation policies helps AI systems understand your site faster and more accurately.</p>
<p>Better Robots.txt is one component of a broader digital readability practice that includes <a href="https://pagup.com/en/services/semantic-content-architecture/" rel="nofollow ugc">semantic content architecture</a>, <a href="https://pagup.com/en/services/ai-governance-and-machine-readability/" rel="nofollow ugc">AI governance and machine readability</a>, and <a href="https://pagup.com/en/glossary/interpretive-seo/" rel="nofollow ugc">interpretive SEO</a>.</p>
<h4>Part of the Pagup ecosystem</h4>
<ul>
<li><a href="https://pagup.com/" rel="nofollow ugc">pagup.com</a> — Digital readability firm. Diagnostic, semantic architecture, AI governance.</li>
<li><a href="https://gautierdorval.com/" rel="nofollow ugc">gautierdorval.com</a> — Doctrine, canonical definitions, interpretive governance research.</li>
<li><a href="https://interpretive-governance.org/" rel="nofollow ugc">interpretive-governance.org</a> — Formal versioned standard for interpretive governance.</li>
<li><a href="https://better-robots.com/" rel="nofollow ugc">better-robots.com</a> — Documentation and resources for Better Robots.txt.</li>
</ul>


Better Robots.txt – AI-Ready Crawl Control & Bot Governance

Replace the default WordPress robots.txt workflow with a smarter, structured version you can preview before publishing, with Free, Pro, and Premium ed …

Zicy AI Access Monitor vs Better Robots.txt – AI-Ready Crawl Control & Bot Governance