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.

apasionados

<p>This plugin adds lines to the virtual robots.txt file that WordPress creates automagically if the file is not present physically on the server to block some WooCommerce assets and Search pages that should not be indexed.</p>
<blockquote>
<p>Please be aware of what this plugin does exactly: If you activate the plugin it will add some lines to the robots.txt file to tell search engine bots to <strong>not to crawl and index</strong> parts of this website.</p>
</blockquote>
<p>This plugin blocks certain pages from WooCommerce (“add-to-cart”, “orderby”, “filter”, cart, account, checkout, …) from being crawled by search engines. Crawling these links normally requires a lot of CPU, memory and bandwidth because they are not cacheable and/or create crawling loops (while they are useless). Optimizing your robots.txt when running a WooCommerce online store allocates more processing power for pages that really matter.</p>
<p>This plugin also blocks the search pages from WordPress from getting indexed.</p>
<p><strong>Please only activate this plugin if you know what you’re doing</strong>.</p>
<h4>What can I do with this plugin?</h4>
<p>This plugin adds the necessary lines to the virtual robots.txt file that WordPress creates automagically to block to block WooCommerce assets that should not be indexed and the Search pages.</p>
<h4>What ideas is this plugin based on?</h4>
<p>None. We needed a fast solution to add these lines to the robots.txt file and this was the solution we coded.</p>
<h4>What is the robots.txt file?</h4>
<p>The robots.txt file is a plain text file located at the root folder of a domain (or subdomain) which tells web crawlers (like Googlebot) what parts of the website they should access and index.</p>
<p>The first thing a search engine crawler looks at when it is visiting a page is the robots.txt file and it controls how search engine spiders see and interact with the web pages.</p>
<h4>System requirements</h4>
<p>PHP version 7.1 or greater.<br />
We require 7.1 or higher because we believe that everybody should be running a modern PHP version. When releasing this plugin <a href="https://wordpress.org/about/requirements/" rel="ugc">WordPress recommends PHP 7.4 or higher</a>.</p>
<h4>How to get this plugin in your Language!</h4>
<p>The first release is avaliable in English and Spanish. In the “languages” folder we have included the necessary files to translate this plugin.</p>
<p>If you would like the plugin in your language and you’re good at translating, please use the <a href="https://translate.wordpress.org/projects/wp-plugins/block-ecommerce-assets-via-robots-txt/" rel="nofollow ugc">native WordPress Translation</a> functionality.</p>
<p>New to Translating a plugin? First read through the <a href="https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/" rel="nofollow ugc">Translator Handbook</a>, then select your locale at <a href="https://translate.wordpress.org/" rel="nofollow ugc">Translating WordPress</a> and finally go to the <a href="https://translate.wordpress.org/projects/wp-plugins/block-ecommerce-assets-via-robots-txt/" rel="nofollow ugc">translation page for this plugin</a> to translate it.</p>
<h4>Further Reading</h4>
<p>You can access the description of the plugin in Spanish at: <a href="https://apasionados.es/blog/" rel="nofollow ugc">Block WooCommerce Assets via robots.txt en español</a>.</p>
<h3>Contact</h3>
<p>For further information please send us an <a href="https://apasionados.es/contacto/index.php?desde=wordpress-org-block-woocommerce-assets-robots-txt" rel="nofollow ugc">email</a>.</p>


Block eCommerce Assets via robots.txt

Blocks some WooCommerce assets and Search pages that should not be indexed through robots.txt

Zicy AI Access Monitor vs Block eCommerce Assets via robots.txt