abignu

GEO Metrics AI Traffic Monitor turns your raw server and WordPress logs into actionable intelligence about AI bot traffic. In a world where ChatGPT, Claude, Gemini, and Perplexity crawl billions of pages to power their answers, knowing whether those bots visit your site — and what they read — is a new SEO frontier.
The plugin works out of the box with zero configuration. It reads your existing <code>debug.log</code>, access logs, and PHP error logs, identifies AI crawlers by their User-Agent string, and displays a clean analytics dashboard inside your WordPress admin.
<h4>What you get</h4>
<ul>
<li>AI Bot Dashboard — KPI cards for total requests, AI bot visits, distinct bots detected, and the active date range. Visual trend chart broken down per bot per day. Donut chart of bot share.</li>
<li>Bot Details tab — per-bot breakdown with company grouping (OpenAI, Anthropic, Google, Meta…), bot type (crawler / agent / search / researcher), top pages visited, and HTTP status distribution.</li>
<li>Log Viewer tab — raw log lines with syntax highlighting, live refresh via AJAX, and per-event type/severity filtering.</li>
<li>Live Traffic capture — the plugin writes its own <code>live.log</code> (no server log access needed), capturing every frontend, REST API, and AJAX request in Combined Log Format, with automatic 5 MB rotation.</li>
<li>Date range filter — filter all dashboard data by custom date range or quick presets (Last 7 days, Last 30 days, etc.).</li>
<li>WP-Cron sync — automatic parsing on a configurable schedule (Hourly / Every 6 hours / Twice daily / Daily).</li>
<li>Data retention — configurable retention period (default 30 days) with automatic purge.</li>
<li>Proxy-aware IP detection — optional trust of <code>X-Forwarded-For</code> / <code>CF-Connecting-IP</code> headers for sites behind Cloudflare or a reverse proxy.</li>
<li>GEO Metrics — visit <a href="https://trygeometrics.com" rel="nofollow ugc">trygeometrics.com</a> for cross-site AI traffic aggregation and visibility scoring across your entire brand.</li>
</ul>
<h4>Detected bots (40+)</h4>
Organized by company:
<ul>
<li>OpenAI — GPTBot, ChatGPT-User, OAI-SearchBot, OAI-AdsBot</li>
<li>Anthropic — ClaudeBot, Claude-Web, Claude-User, Claude-SearchBot, anthropic-ai</li>
<li>Google — Googlebot, Google-Extended, Gemini, Google-Agent, Google-CloudVertexBot, GoogleOther, Google-NotebookLM</li>
<li>Microsoft — bingbot</li>
<li>Perplexity — PerplexityBot, Perplexity-User, DuckAssistBot</li>
<li>Meta — Meta-ExternalAgent, Meta-ExternalFetcher, Meta-WebIndexer</li>
<li>xAI — GrokBot</li>
<li>Mistral AI — MistralAI-User</li>
<li>ByteDance — Bytespider, TikTokSpider</li>
<li>Apple — Applebot</li>
<li>Amazon — Amazonbot</li>
<li>Cohere — cohere-ai</li>
<li>You.com — YouBot</li>
<li>DuckDuckGo — DuckDuckBot</li>
<li>Common Crawl / Research — CCBot, AI2Bot</li>
<li>SEO tools — AhrefsBot, AhrefsSiteAudit, SemrushBot, DotBot, Barkrowler, DataForSeoBot, ScreamingFrog</li>
<li>Other search engines — BaiduSpider, Yandexbot, Naverbot, ShapBot</li>
</ul>
<h4>Privacy</h4>
The plugin reads log files already stored on your server. It does not set cookies, collect personal data from visitors, or make any external HTTP requests. Raw log lines are never stored in the WordPress database — only aggregated counts and parsed metadata are persisted.
<h4>Source log support</h4>
<ul>
<li>WordPress <code>debug.log</code> (WP_DEBUG_LOG)</li>
<li>PHP <code>error_log</code> (auto-detected from <code>php.ini</code>)</li>
<li>Plugin-owned live traffic log (zero-config, works on any host)</li>
<li>Web server access log (optional path in Settings)</li>
<li>Up to 3 custom log paths</li>
</ul>

GEO Metrics AI Traffic Monitor

Know which AI crawlers visit your site, how often, and what they read. Zero-config bot detection from your existing WordPress logs.

ldesuque

Server-side, non-blocking request logging with a local queue, batched delivery, 
exponential-backoff retries, a circuit breaker, query-parameter redaction, and 
path filtering. Admin actions use the WordPress REST API.
<h3>Configuration</h3>
Settings -> nBlick Signal Agent. Set the API key (or define NBLICK_SIGNAL_API_KEY 
in wp-config.php), enable logging, and use the Status tab to send a test event.
<h3>External services</h3>
This plugin connects to the nBlick Signal API, a third-party service, to provide 
bot detection and traffic analysis. This connection is essential to the plugin’s 
purpose: request data collected on your site is transmitted to nBlick for 
analysis, and the plugin does nothing useful without it.
What is sent, and when:
<ul>
<li>The plugin sends batches of request metadata to the nBlick Signal ingest 
endpoint (default: https://api.trynblick.com/signals/wordpress) on a recurring 
background schedule (via WP-Cron) whenever logging is enabled and queued data 
exists, and once when you click “Send Test Event”.</li>
<li>Each request record may contain: the visitor’s IP address, the request method, 
host, path, HTTP status code, user agent, referer, response size, request 
duration, a timestamp, query-string parameters (with sensitive keys such as 
passwords and tokens redacted), a per-site identifier (UUID), and a schema 
version number.</li>
<li>Only public front-end traffic is sent. WordPress admin, login, REST API, AJAX, 
cron, WP-CLI, and any paths you exclude are never collected or transmitted.</li>
<li>Authentication uses an API key you provide, sent in the X-NBlick-Signal-Key 
request header.</li>
</ul>
The IP address is transmitted in full because it is required for the service’s 
bot-detection and reverse-DNS analysis.
This service is provided by nBlick. By using the plugin you are sending the data 
described above to nBlick. Please review their terms and privacy policy:
<ul>
<li>Terms of service: https://trynblick.com/terms-of-service</li>
<li>Privacy policy: https://trynblick.com/privacy-policy</li>
</ul>
<h3>Privacy</h3>
<ul>
<li>The plugin is server-side only. It sets no cookies and performs no client-side 
or browser tracking.</li>
<li>Sensitive query parameters (configurable; by default password, pass, token, 
auth, authorization, apikey, api_key, secret, card, cc, ssn and similar) are 
redacted to “[REDACTED]” before storage and transmission.</li>
<li>Captured data is queued in a local database table and removed after it is sent 
successfully, or purged after the configured retention period (default 7 days).</li>
<li>When the Sodium PHP extension is available, the API key is encrypted at rest 
using your site’s authentication salts; defining NBLICK_SIGNAL_API_KEY in 
wp-config.php avoids database storage entirely.</li>
<li>Because the plugin transmits visitor IP addresses to a third party, you may 
need to disclose this in your own site’s privacy policy depending on your 
jurisdiction (e.g. GDPR/CCPA).</li>
</ul>

nBlick Signal Agent

Captures public request metadata and ships it in batches to the nBlick Signal API for bot detection and traffic analysis.

GEO Metrics AI Traffic Monitor vs nBlick Signal Agent