Title: Zicy AI Access Monitor
Author: zicygp
Published: <strong>21 May 2026</strong>
Last modified: 28 May 2026

---

Search plugins

![](https://ps.w.org/zicy-ai-bot-logger/assets/icon-256x256.png?rev=3551547)

# Zicy AI Access Monitor

 By [zicygp](https://profiles.wordpress.org/zicygp/)

[Download](https://downloads.wordpress.org/plugin/zicy-ai-bot-logger.1.8.8.zip)

 * [Details](https://en-gb.wordpress.org/plugins/zicy-ai-bot-logger/#description)
 * [Reviews](https://en-gb.wordpress.org/plugins/zicy-ai-bot-logger/#reviews)
 *  [Installation](https://en-gb.wordpress.org/plugins/zicy-ai-bot-logger/#installation)
 * [Development](https://en-gb.wordpress.org/plugins/zicy-ai-bot-logger/#developers)

 [Support](https://wordpress.org/support/plugin/zicy-ai-bot-logger/)

## Description

Zicy AI Access Monitor helps site owners understand when known AI crawlers and AI
assistant retrieval agents access their WordPress content.

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.

**What it tracks:**

 * Search crawlers — AI systems that may crawl content for search or answer retrieval
   workflows, such as OAI-SearchBot and PerplexityBot
 * 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
 * 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
 * AI control agents — AI-related User-Agents such as Google-Extended that may represent
   AI data-use control behavior rather than ordinary search crawling

**How it works:**

 1. Matching visits are recorded as temporary raw logs.
 2. URLs are normalized to reduce duplicates caused by common tracking parameters.
 3. IP addresses are anonymized by default before being stored.
 4. Each night at 02:15 site time, raw logs older than today are summarized into daily
    totals.
 5. Raw logs that have been rolled up are deleted.
 6. Daily summary records are retained so you can review historical AI access activity.

**In your WordPress admin dashboard:**

 * View daily summaries of known AI bot and AI assistant access
 * See today’s raw logs before the next rollup
 * Filter by date, bot, type, or signature
 * Review top pages accessed by AI assistant user proxies
 * Compare week-over-week activity for top pages
 * See vendor diversity indicators for accessed pages
 * Export daily summary data as CSV
 * Receive weekly email summaries with top accessed pages
 * Generate copy-ready AI Tracking Briefs for selected pages

**Why it matters:**

 * See which known AI systems are accessing your content
 * Identify which pages AI assistants retrieve most often
 * Support AI search optimization and AI visibility reporting
 * Understand differences between crawler, training, control, and user-triggered
   AI access
 * Build structured page briefs that can be used in AI visibility workflows

**Bot allowlist includes:**

 * OpenAI: GPTBot, OAI-SearchBot, ChatGPT-User
 * Anthropic: ClaudeBot, Claude-User, Claude-SearchBot
 * Perplexity: PerplexityBot, Perplexity-User
 * Google: Google-Extended, Gemini-Deep-Research, Google-Agent
 * Microsoft: BingPreview
 * Amazon: Amazonbot
 * Common Crawl: CCBot
 * ByteDance: Bytespider
 * Cohere: CohereBot
 * Mistral: Mistral-ai
 * Meta: Meta-WebIndexer

Developers can extend or modify the allowlist with the `gp_aibal_ai_bots` filter.

**Important detection note:**

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.

### Privacy

Zicy AI Access Monitor is designed to keep raw request-level data temporary.

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.

Site owners are responsible for ensuring that their use of access logging complies
with applicable privacy laws and their own privacy policy.

## Installation

 1. Upload the `zicy-ai-access-monitor` folder to `/wp-content/plugins/`, or install
    it from the WordPress Plugins screen.
 2. Activate the plugin through the Plugins menu in WordPress.
 3. Go to **WP Admin  Zicy AI Access** to view AI access activity.
 4. Optional: add an email address in the plugin admin screen to receive weekly summaries.

## FAQ

### Does this block AI bots?

No. Zicy AI Access Monitor logs activity only. It does not block, allow, redirect,
challenge, or modify any traffic. To control AI bot access, use robots.txt, server
rules, a firewall, or CDN rules.

### Does it detect AI assistants browsing through proxies?

Only self-identifying proxies. AI assistants or browsers that use ordinary User-
Agents such as `Mozilla/5.0` cannot be reliably detected by this plugin.

### Can User-Agent detection be spoofed?

Yes. User-Agent headers can be spoofed. This plugin records matching User-Agents
for monitoring and reporting purposes, but it does not verify bot identity by IP
range or reverse DNS.

### When are raw logs deleted?

Raw logs are kept temporarily. During the nightly rollup at 02:15 site time, all
raw logs older than today are summarized into daily totals and then deleted. This
catch-up behavior helps prevent older raw logs from staying behind if WP-Cron does
not run on a previous day.

### Are IP addresses stored?

The plugin stores a best-effort client IP value, anonymized by default. IPv4 addresses
are masked by replacing the final octet with `0`. IPv6 addresses are masked to a
broader network prefix. Developers can change this behavior with the `gp_aibal_anonymize_ip`
filter.

### Does the plugin trust forwarded IP headers?

Not by default. Forwarded headers such as `X-Forwarded-For` can be spoofed unless
they come from a trusted proxy. The plugin defaults to `REMOTE_ADDR`. Developers
may enable Cloudflare or forwarded header handling with filters when their server/
CDN setup is trusted.

### What data does the plugin store?

For matching AI-related User-Agents, the plugin may store the bot/vendor label, 
matched signature, access type, normalized page URL, URL hash, timestamp, full User-
Agent, anonymized IP address, IP source, and verification status. After rollup, 
raw rows are deleted and daily summary rows are retained.

### Does the plugin send data to Zicy or any external service?

No. The plugin does not send logged access data to Zicy or to any third-party service.
Data is stored in your WordPress database. Weekly summaries are sent only through
your WordPress site’s configured email system if you add a recipient email address.

### What is the “Copy Brief” button?

The Copy Brief feature generates a structured JSON brief for a page, including the
page title, headings, detected FAQ questions, and recent AI access stats. You can
copy this brief into a Custom GPT, AI assistant, or internal workflow to provide
context about that page.

### Does it work with WP-Cron?

Yes. The nightly rollup and weekly email summary use WP-Cron. On low-traffic sites,
WP-Cron may not run at the exact scheduled time. A normal server cron or uptime 
ping can help trigger scheduled WordPress tasks reliably.

### Where are weekly CSV attachments stored?

Weekly CSV files are generated temporarily in the WordPress uploads directory, attached
to the summary email, and then deleted after the email function runs. The plugin
also adds basic directory protection files to the report folder.

### Can developers extend the bot list?

Yes. Use the `gp_aibal_ai_bots` filter to add, remove, or adjust User-Agent signatures
and their labels.

Example:

    ```
    add_filter('gp_aibal_ai_bots', function ($bots) {
        $bots['ExampleBot'] = [
            'bot'  => 'Example',
            'type' => 'search_crawler',
        ];
        return $bots;
    });
    ```

## Reviews

There are no reviews for this plugin.

## Contributors and Developers

“Zicy AI Access Monitor” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ zicygp ](https://profiles.wordpress.org/zicygp/)

[Translate “Zicy AI Access Monitor” into your language.](https://translate.wordpress.org/projects/wp-plugins/zicy-ai-bot-logger)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/zicy-ai-bot-logger/),
check out the [SVN repository](https://plugins.svn.wordpress.org/zicy-ai-bot-logger/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/zicy-ai-bot-logger/)
by [RSS](https://plugins.trac.wordpress.org/log/zicy-ai-bot-logger/?limit=100&mode=stop_on_copy&format=rss).

## Change Log

#### 1.8.6

 * Removed minimum-hit threshold from Daily summaries and Daily CSV export.
 * Kept 10+ threshold only for the 30-day Top user-initiated pages table.

#### 1.8.5

 * Fixed WordPress.org review issues: replaced inline script/style output with proper`
   wp_enqueue_*` usage.
 * Sanitized `HTTP_USER_AGENT` before storage.
 * Improved daily rollup safety and catch-up behavior.
 * Updated daily summary grain to preserve per-signature page hit counts per day.
 * Simplified daily reporting to hit-focused summaries.

#### 1.8.1

 * Fixed WordPress Plugin Check errors for prepared SQL, direct filesystem usage,
   temporary CSV cleanup, and escaped admin output.

#### 1.8.0

 * Renamed plugin to Zicy AI Access Monitor
 * Updated author branding to Zicy
 * Added clearer AI access types: search_crawler, training_crawler, user_proxy, 
   and ai_control_agent
 * Removed broad standard Bingbot tracking from the AI-specific allowlist
 * Corrected Bytespider vendor categorisation to ByteDance
 * Added URL normalization to reduce duplicate reporting caused by common tracking
   parameters
 * Added URL hash support to improve uniqueness and avoid long URL index collisions
 * Updated nightly rollup to process all raw logs older than today, improving WP-
   Cron catch-up behavior
 * Added IP anonymization by default
 * Stopped trusting forwarded IP headers by default; added developer filters for
   trusted proxy/CDN setups
 * Added static asset and low-value route exclusions to reduce unnecessary logging
 * Added cleanup for temporary weekly CSV attachments after email sending
 * Added basic directory protection files for generated report storage
 * Improved admin copy and Zicy-branded dashboard labels

#### 1.7.3

 * Added WoW (Week over Week) change indicators in top pages table
 * Added vendor diversity badges (OA, P, A, G, M, Me)
 * Improved UI clarity in admin dashboard

#### 1.7.2

 * Added 30-day proxy hits tracking per URL
 * Added “Copy Brief” feature for AI Tracking Briefs
 * Added AJAX endpoint for on-demand brief generation

#### 1.7.1

 * Added weekly email summary with CSV attachment
 * Added email configuration in admin settings
 * Added “Test email” button

#### 1.7.0

 * Full admin UI rewrite: daily summaries, filters, pagination
 * CSV export for daily data
 * Raw log preview for today
 * Manual rollup trigger

#### 1.6.0

 * Added Perplexity-User proxy detection
 * Added Bytespider detection
 * Improved IP detection for Cloudflare/proxy setups

#### 1.5.0

 * Added Claude-User and Claude-SearchBot detection
 * Added Meta-WebIndexer detection
 * Added CDN/proxy IP detection

#### 1.4.0

 * Added Google-Extended and Gemini-Deep-Research detection
 * Added database indexes for performance

#### 1.3.0

 * Added ClaudeBot and ChatGPT-User detection
 * Initial public release

## Meta

 *  Version **1.8.8**
 *  Last updated **5 months ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **7.0.7**
 *  PHP version ** 7.4 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/zicy-ai-bot-logger/)
 * Tags
 * [AI](https://en-gb.wordpress.org/plugins/tags/ai/)[analytics](https://en-gb.wordpress.org/plugins/tags/analytics/)
   [bot](https://en-gb.wordpress.org/plugins/tags/bot/)[crawler](https://en-gb.wordpress.org/plugins/tags/crawler/)
   [logs](https://en-gb.wordpress.org/plugins/tags/logs/)
 *  [Advanced View](https://en-gb.wordpress.org/plugins/zicy-ai-bot-logger/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/zicy-ai-bot-logger/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/zicy-ai-bot-logger/reviews/)

## Contributors

 *   [ zicygp ](https://profiles.wordpress.org/zicygp/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/zicy-ai-bot-logger/)