VigIA – AI Visibility, Analytics & Control vs AlmaWeb AI Visitor Analytics

Two sides of AI traffic, one powerful plugin. With the rise of AI platforms like ChatGPT, Claude, Gemini, and Perplexity, your website faces two new realities: 1. AI bots scraping your content for training and indexing 2. Real human visitors discovering your site through AI tools and clicking through to visit AlmaWeb AI Visitor Analytics is the only WordPress plugin that tracks BOTH: AI Bot Detection Identify bots from major AI companies (OpenAI, Google, Anthropic, Meta, Amazon), SEO crawlers (Ahrefs, Semrush), aggressive scrapers, and even “stealth” bots hiding behind standard User-Agents. Detect GPTBot, ClaudeBot, Google-Extended, Gemini, Bytespider, Perplexity and 200+ more. AI Referrer Tracking Track real human visitors coming FROM AI platforms! When someone asks ChatGPT a question and clicks a link to your site, you will see it. Understand which AI tools are sending you traffic, which pages they land on, and how diverse your AI traffic sources are. Why AlmaWeb AI Visitor Analytics? In a world where AIs massively consume AND distribute web content, it is crucial to know: Who’s scraping your content – Precisely identify each AI bot (GPTBot, ClaudeBot, Google-Extended, Gemini, etc.) Whether ChatGPT is training on your data – Detect OpenAI crawlers in real time and block them if needed Which pages are being targeted – Discover what content interests AI bots the most Hidden bots – Detect even bots that mask their identity with standard User-Agents (stealth detection) Which AI platforms send you traffic – Track human visitors referred by ChatGPT, Claude, Perplexity, etc. Key Features 🔍 Multi-Level Bot Detection Level 1 – User-Agent: Detects 200+ AI bot signatures (OpenAI, Anthropic, Google, Meta, Amazon, Apple, xAI, Mistral, Cohere, Perplexity, DeepSeek, and more) Level 2 – IP Range: Verifies official IP ranges from OpenAI, Anthropic, and Google to catch masked bots Level 3 – Stealth Detection: Detects invisible bots like ChatGPT Atlas that use standard browser User-Agents by cross-referencing IP addresses 📊 Comprehensive Dashboard Real-time statistics (human visits vs bots) Evolution charts with Chart.js Distribution by AI family (OpenAI, Google, Anthropic, etc.) Top 10 most active bots Top 10 most scraped pages Comparison with previous period Business KPIs: growth rate, peak hours, intent distribution 📋 Detailed Logs Advanced filtering by bot type, IP, date Real-time search Full CSV export Complete details: User-Agent, IP, URL, detection method, AI family, bot intent Special badge for “invisible” bots ⚙️ Flexible Configuration Enable/disable tracking Bad bot blocking option (disabled by default) Configurable data retention (90 days by default) Automatic daily cleanup of old data Exclude logged-in users (optional) 🔒 Privacy Respectful No data sent to third-party services All data stays in your WordPress database GDPR compliant No cookies or client-side tracking Only downloads public data (IP ranges) Detected Bots The plugin detects over 200 different bots in the following categories: AI Bots (AI Training & Inference): OpenAI (GPTBot, ChatGPT-User, OAI-SearchBot, Operator, ChatGPT Agent), Anthropic (ClaudeBot, Claude-Web, Claude-SearchBot), Google AI (Google-Extended, Gemini, NotebookLM, GoogleAgent-Mariner), Meta AI, Amazon (Amazonbot, Bedrock, Nova Act), Apple Intelligence, Perplexity, Mistral, xAI (Grok), Cohere, DeepSeek, Character.AI, Kagi, Exa, Tavily, Apify, and 150+ others. Search Engines: Google, Bing, Yahoo, DuckDuckGo, Yandex, Baidu, etc. SEO Crawlers: Ahrefs, Semrush, Moz, Majestic, etc. Scrapers & Malicious Bots: Content scrapers, email collectors, attack bots, etc. Advanced Stealth Bot Detection Some AI bots like ChatGPT Atlas use standard browser User-Agents (Chrome, Safari) to go unnoticed. AlmaWeb AI Visitor Analytics detects them by cross-referencing IP addresses against official IP ranges from OpenAI, Anthropic, and Google — all stored locally, no external calls required. Example: A visitor with User-Agent “Mozilla/5.0 Chrome/…” from an IP in the OpenAI range will be identified as “ChatGPT Atlas” and marked with an “INVISIBLE” badge in the logs. Firewall — Block Unwanted Bots Since v1.2.0, the plugin includes a built-in Firewall to block bots before they access your content: Block by intention — Stop training crawlers (GPTBot, ClaudeBot), scrapers, or inference bots Block by family — Block all bots from a specific company (ByteDance, Meta, OpenAI, etc.) Blocked bots receive a 403 response and are still logged for analysis Performance Zero external calls: IP ranges for OpenAI, Anthropic and Google are stored locally Minimal impact: Optimized to not slow down your site Optimized queries: Indexes on all important columns Automatic cleanup: Daily deletion of old data Protect your content and understand your traffic like never before. Official Plugin Page Visit the official plugin page for additional resources and support: https://almaweb.fr/ai-visitor-analytics Privacy & Data Protection AlmaWeb AI Visitor Analytics takes your privacy seriously: Data Storage All data is stored locally in your WordPress database No external services receive any data from your site You have full control over data retention (configurable from 1 to 365 days) Automatic daily cleanup removes old data based on your settings What Data is Collected The plugin collects the following information for each visit: * User-Agent string * IP address * Requested URL * HTTP referrer * Request method (GET, POST, etc.) * HTTP headers (Accept, Accept-Language, Accept-Encoding) * Timestamp This data is used solely for bot detection and traffic analysis on your own site. GDPR Compliance No cookies are set by this plugin No client-side tracking or JavaScript-based analytics IP addresses are stored for bot identification purposes only You can configure data retention to comply with your privacy policy Users can request data deletion through standard WordPress data export/erasure tools What This Plugin Does NOT Do Does NOT send your data to external servers Does NOT track end-user behavior for advertising Does NOT use third-party analytics services Does NOT set cookies Does NOT require user consent (server-side logging only) Third-Party Services This plugin may connect to the following third-party services only to download publicly available bot IP ranges: OpenAI IP Ranges GPTBot: https://openai.com/gptbot.json ChatGPT-User: https://openai.com/chatgpt-user.json SearchBot: https://openai.com/searchbot.json Purpose: Verify IP addresses to detect OpenAI bots, including stealth bots like ChatGPT Atlas Data sent: None – the plugin only downloads public IP range information Caching: IP ranges are cached for 24 hours to minimize requests Privacy Policy: https://openai.com/privacy Important Notes No data from your site is ever sent to these services The plugin only downloads publicly available IP range lists These requests happen server-side (not from visitors’ browsers) IP ranges are cached locally for 24 hours If the external service is unavailable, the plugin continues to work using User-Agent detection Bundled Libraries Chart.js v4.5.1 (bundled locally) * Used for dashboard visualizations * No external connections required * Loaded only on admin pages * License: MIT All third-party code is included in the plugin and does not require external CDN connections. Support & Documentation Getting Help If you need help with the plugin, here are your options: Documentation: Check the plugin settings page for inline help and tooltips WordPress Support Forum: Post your questions on the WordPress.org support forum Official Page: Visit https://almaweb.fr/ai-visitor-analytics for contact and support Reporting Bugs If you find a bug, please report it on the WordPress.org support forum with: * WordPress version * PHP version * Steps to reproduce the issue * Any error messages you’re seeing You can also contact us directly through our official page at https://almaweb.fr/ai-visitor-analytics Feature Requests We welcome feature suggestions! Please submit them on the WordPress.org support forum or contact us through https://almaweb.fr/ai-visitor-analytics Contributing This plugin is open source and welcomes contributions! Translation The plugin is available in French and English. To add a new language: Copy languages/almaweb-ai-visitor-analytics.pot Translate using Poedit or similar tool Save as almaweb-ai-visitor-analytics-{locale}.po and compile to .mo Contact us through https://almaweb.fr/ai-visitor-analytics to submit your translation Credits Developed by: Yohan Ziri Company: AlmaWeb (https://almaweb.fr) License: GPLv3 or later Special Thanks: * Chart.js for beautiful visualizations * The WordPress community for feedback and support * All users who help improve the bot detection library

VigIA (Spanish for “lookout” or “watchman”, incorporating “IA” – Spanish for “AI”) is a complete AI visibility toolkit for WordPress. Monitor 60+ AI crawlers, control access to your content, and optimize how AI systems discover and understand your site. What does VigIA do? Scores your AI visibility with a 100-point analyzer covering 20 checks across 5 categories Tracks AI crawlers visiting your site (GPTBot, ClaudeBot, PerplexityBot, and 60+ others) Provides detailed analytics with advanced filters, server-side pagination, and exportable reports with metadata banner Blocks unwanted crawlers via PHP (403 response) Manages robots.txt rules for AI crawlers with compliance monitoring Sends email alerts about crawler activity (daily, weekly, or monthly) Generates llms.txt files to help AI systems understand your site Serves markdown endpoints for posts, pages, taxonomy archives (categories, tags, WooCommerce product categories, custom taxonomies) and WooCommerce products with schema-like data Generates JSON-LD structured data with Site Identity and AI Discovery signals Exposes abilities for AI agents and automation tools (WordPress 6.9+) Key Features AI Visibility Analyzer * 100-point scoring system with letter grades (A+ to F) * 20 individual checks across 5 categories * Access & AI Discovery (37 pts): robots.txt, AI bot directives, Content Signals, llms.txt, sitemap, RSS feed * Structured Data & Semantic Context (25 pts): JSON-LD schemas, Open Graph, Twitter Cards, meta description, canonical URL * Content Structure & Readability (20 pts): heading hierarchy, semantic HTML5, image alt text, content/HTML ratio * AI Interaction & Distribution (8 pts): markdown delivery, AI share buttons * Access Performance (10 pts): TTFB measurement * Smart recommendations with direct links to VigIA features and plugin suggestions * Analyze any page on your site with URL autocomplete selector * Results cached for 24 hours with manual re-analyze option Analytics Dashboard * Total visits, unique crawlers, and pages crawled statistics * Timeline chart with daily breakdown * Category distribution (AI Training, AI Search, AI Assistant, Data Scraper) * Top crawlers and most crawled pages tables with paginated navigation * Share Buttons & AI-powered Summaries integration: see share button clicks per page * Recent activity log with content type and HTTP status columns (color coded by status family) * Advanced filters: multi-select crawler picker, content type, HTTP status code, and configurable date range * Server-side pagination with four-button pager (first, previous, next, last) — operates over the full database, not just the latest 500 rows * Period comparison functionality * CSV export with a metadata banner (site name, site URL, export type, date range, export timestamp, applied filters) * “Export filtered CSV” button that downloads exactly what the active filters return, with vigia-filtered-YYYY-MM-DD.csv filename * Content type detection distinguishes Home, Post, Page, Product, custom CPTs, Category archive, Tag archive, Date/Author archive, Feed, Sitemap, REST API, File, Admin / login attempts (/wp-admin, /wp-login.php), WordPress system (admin-ajax, xmlrpc, wp-cron, wp-comments-post), 404 Not found, and Other Crawler Blocking * Block crawlers via PHP with 403 Forbidden response * Quick block dropdown in analytics dashboard * Manage blocks from Extras page * Works on any server (Apache, Nginx, LiteSpeed, etc.) Robots.txt Management * Add Disallow rules for AI crawlers * Visual preview of your robots.txt * Compliance monitoring: see which crawlers ignore your rules * One-click blocking for non-compliant crawlers * Works with both physical and virtual robots.txt Email Alerts * Daily, weekly, or monthly reports * Three detail levels: Minimal, Normal, Complete * Non-compliant crawler warnings * Activity comparison with previous period Markdown for Agents * Serve posts, pages and any public post type as optimized markdown for AI agents * Serve taxonomy archive pages (categories, tags, WooCommerce product categories, custom taxonomies) as markdown — disabled by default, opt in per taxonomy * Dedicated .md URL endpoints (e.g., /your-post.md, /category/news.md, /product-category/electronics.md) * Accept: text/markdown content negotiation on posts and taxonomy archive pages * Discoverability via Link HTTP headers and HTML tags * YAML frontmatter for posts: title, date, modified, author, image, categories, tags, post type, lang * YAML frontmatter for taxonomy terms: title, description, url, type, taxonomy, parent, count, image (term meta), lang * WooCommerce product frontmatter adds schema-like fields: sku, product_type, price, regular_price, sale_price, currency, availability, stock_quantity, rating, rating_count, review_count * Taxonomy term body includes the term description (rendered through the_content), the list of direct child terms in hierarchical taxonomies, and an excerpt of the latest posts/products assigned to the term * Product listings inside product_cat archives include an inline summary with formatted price, “was X” on sale items, star rating and out-of-stock flag * Respects blocking rules (blocked crawlers get 403) and LLMs.txt exclusion filters * Per-term noindex detection from Yoast SEO, Rank Math, All in One SEO and SEOPress * Analytics integration: tracks markdown requests per crawler * X-Markdown-Tokens response header * Filters: vigia_markdown_post_eligible, vigia_markdown_term_eligible, vigia_markdown_term_posts_limit * Follows the Cloudflare Markdown for Agents standard LLMs.txt Generator * Select content by post type with one click * Filter by taxonomies (categories, tags, custom) * Manual include/exclude with AJAX search * Exclude by URL patterns (wildcards supported) * SEO plugin integration (auto-exclude noindex content) * Auto-regeneration (daily, weekly, monthly) * Robots.txt integration (add llms.txt and llms-full.txt references) * Generate llms.txt and llms-full.txt files * Full content or excerpt mode * Compatible with Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, and Native SEO NoIndexer JSON-LD Structured Data * Generate WebSite and Organization/Person schema for site identity * AI Discovery: ReadAction pointers to llms.txt, llms-full.txt, and Markdown for Agents endpoints * Social profiles and sameAs links for brand identity across the web * SearchAction for Google sitelinks search box * Media library integration for logo selection * SEO plugin conflict detection (Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework) * Choose output page (front page or any published page) * Live JSON-LD preview with real-time updates * Smart integration with LLMs.txt and Markdown for Agents features Supported AI Crawlers VigIA monitors 60+ AI crawlers including: OpenAI: GPTBot, OAI-SearchBot, OAI-AdsBot, ChatGPT-User Anthropic: ClaudeBot, Claude-SearchBot, Claude-User, Claude-Code Google: Google-Extended, GoogleOther, Gemini-Deep-Research, Google-NotebookLM Perplexity: PerplexityBot, Perplexity-User Meta: Meta-ExternalAgent, FacebookBot, Meta-WebIndexer Amazon: Amazonbot, Amzn-SearchBot, bedrockbot Mistral: MistralAI-User, MistralAI-Index Microsoft: BingBot ByteDance: Bytespider Apple: Applebot-Extended And many more… Privacy Focused VigIA stores visitor data locally in your WordPress database. No data is sent to external servers. Abilities API VigIA is one of the first WordPress plugins to implement the Abilities API introduced in WordPress 6.9. This API allows AI agents, automation tools, and external systems to discover and interact with VigIA’s functionality in a standardized, secure way. What are Abilities? Abilities are self-contained units of functionality that VigIA exposes through WordPress’s central registry. Each ability has defined inputs, outputs, and permissions, making it easy for automation tools to understand and use them. Available Abilities VigIA registers the following abilities: Analytics vigia/get-crawler-stats – Get statistics about AI crawler visits (total visits, unique crawlers, pages crawled) vigia/get-top-crawlers – Get a ranked list of most active AI crawlers vigia/get-top-pages – Get the most crawled pages on your site Blocking vigia/get-blocked-items – List all blocked crawlers and IP addresses vigia/block-crawler – Block a crawler by User-Agent pattern vigia/unblock-crawler – Remove an existing block Robots.txt vigia/get-robots-rules – Get current AI crawler rules in robots.txt vigia/add-robots-disallow – Add a Disallow directive for a crawler vigia/remove-robots-rule – Remove a robots.txt rule Use Cases Automated monitoring: AI agents can query crawler statistics and alert you to anomalies Reactive blocking: Automation tools can block crawlers that repeatedly ignore robots.txt External dashboards: Aggregate data from multiple WordPress sites with VigIA installed WP-CLI integration: Future command-line access through the Abilities API n8n / Make workflows: Build custom automation flows using VigIA’s abilities Requirements The Abilities API ships with WordPress 6.9 and later. On older WordPress versions, VigIA works normally but abilities and MCP are not available. MCP Server (Model Context Protocol) VigIA exposes its 9 abilities as native MCP tools to any MCP-compatible client (Claude Code, Cursor, Claude Desktop, Codex CLI, Antigravity, Continue, Cline, Zed and similar) using the official WordPress MCP Adapter. The adapter ships bundled with the plugin, so the MCP endpoint is active right after installation — no Composer step or terminal access required. Requirements WordPress 6.9 or later (provides the Abilities API) Quick connect (recommended) Open VigIA > Extras > MCP and click “Generate password and connection commands”. The plugin creates a dedicated Application Password named VigIA MCP and renders ready-to-paste commands for Claude Code, Cursor, Claude Desktop and a generic block (URL + Authorization header) for any other MCP client. The plain password is shown only once. If you lose it, revoke the entry from the same panel and generate a new one. Endpoint https://your-site.example/wp-json/vigia/v1/mcp The endpoint uses HTTP Basic auth with the WordPress Application Password. The user must have the manage_options capability. Connecting Claude Code Quick Connect builds the full command for you. The shape is: claude mcp add --transport http vigia https://your-site.example/wp-json/vigia/v1/mcp --header "Authorization: Basic BASE64_OF_USER_AND_APP_PASSWORD" Claude Code merges the new entry into its config file automatically — no risk of breaking other servers. Connecting Cursor Save the JSON block from Quick Connect as ~/.cursor/mcp.json. You can also reach this file from inside Cursor at Settings → Cursor Settings → MCP. If the file already exists with other content, see the FAQ. Claude Desktop and other clients Claude Desktop does not speak HTTP MCP, so it needs a small bridge and a config file of its own. Any other client (Codex CLI, Continue, Cline, Antigravity, Zed, or your own) takes the two raw values Quick Connect exposes: the server URL and the Authorization header. Both cases are covered in the FAQ, together with how to merge VigIA into a config file that already exists without losing what is in it. Read-only mode If you only want your AI to consult VigIA (not change anything), enable “Read-only mode” in the MCP tab. While on, write actions (block, unblock, robots changes) return a permission denied error. Read actions (statistics, top crawlers, blocked items, robots rules) keep working. The toggle stores a vigia_mcp_read_only option that hooks into the vigia_can_write_via_abilities filter. Developers can still force read-only from a mu-plugin: add_filter( 'vigia_can_write_via_abilities', '__return_false' ); The mu-plugin filter at the default priority takes precedence over the toggle. Who can reach the endpoint The endpoint requires the capability to manage options, the same one every tool behind it already asked for. The vigia_mcp_transport_capability filter can lower that bar; each tool keeps its own permission check. After connecting Restart your MCP client after adding the server so it picks up the new tools. Then try a few prompts to confirm everything is wired up: “Show me VigIA crawler stats for the last 7 days.” “List the top 5 most crawled pages on this site.” “Add a robots.txt Disallow rule for TestBot and then list the current AI crawler rules.” The third example exercises a read + write + read round-trip, which is the most complete sanity check. Support 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 contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.