VigIA – AI Visibility, Analytics & Control vs WinaltChat for WooCommerce

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.

WinaltChat adds a fast, intelligent chat widget to your WooCommerce store. Customers can search your product catalogue, get instant answers about shipping and returns, and — when they need a real person — connect to your support team through a built-in live chat system, all without leaving your store. AI Shopping Assistant Dual AI Modes — Use your own API key from Groq — LLaMA (Free Tier), ChatGPT (OpenAI), Claude (Anthropic), or Gemini (Google) for full conversational AI. No key? The built-in Basic AI mode runs entirely on your server with zero external calls and zero ongoing cost. Smart Product Search — Intent-aware search across your WooCommerce catalogue. Handles typos, synonyms, multilingual and mixed-language queries, and follow-up questions naturally. Product Comparisons — Customers can ask “which is better, the Sony or the Samsung?” and get a clear side-by-side comparison with prices and key specs from your own catalogue. Store Knowledge Base — Reads your shipping, returns, contact, and about pages to answer policy questions accurately and dynamically — no hardcoded answers that break for other stores. Conversation Context — Remembers context within a session so follow-up questions (“does it come in blue?”) work naturally. Amazon Affiliate Fallback — When a product is out of stock, optionally suggest an Amazon affiliate link so you still earn a commission. Live Human Chat Human Handoff — When a customer types phrases like “I want to talk to a human”, “customer service”, “live agent”, or dozens of natural variants, the plugin detects the request and connects them to a real person on your team. Admin Live Chats Dashboard — A dedicated Live Chats screen in your WordPress admin shows all active, waiting, and closed conversations in a two-panel interface. Every handoff request is queued here as soon as it happens — keep the tab open to also show as instantly online to visitors and connect in real time. Visitor Name Prompt — Before connecting, the visitor is optionally asked for their name. If skipped, they are identified as “Visitor #ID” so you can tell conversations apart. Full Conversation Context for Agents — When a customer is handed off, the admin sees the complete prior AI conversation so there is no need to ask “how can I help?” twice. Visitor Presence Dot — A green dot shows the visitor is active. It turns grey within 30 seconds if they close the tab. Two-Tier Timeout — If your team does not respond within 90 seconds, the visitor sees a friendly patience message. After 5 minutes of no reply, the chat gracefully falls back to the AI assistant with an optional email capture. Intelligent Offline Handling — When no admin is online the AI keeps helping, and the handoff request is still queued in the background so it’s waiting in your Live Chats list whenever you next check — no need to have caught it live. Visitors can also optionally leave their email for a follow-up; leads appear with a dedicated Leads section and unread badge. Session Management — Close chats when resolved, or delete them permanently. Closed and lead sessions stay visible in their own sections until manually removed. Zero External Dependencies — Live chat runs entirely within your WordPress site using secure AJAX polling over the REST API. No Pusher, no third-party service, no extra cost. Email Notifications — Get an email when a customer starts a live chat or leaves their contact details while you are offline. Privacy & Security All live chat data is stored in your own WordPress database. Nothing is sent to an external service. Session tokens are 32-character cryptographically random strings — not sequential IDs — so sessions cannot be enumerated. All endpoints enforce nonces, capability checks, input sanitization, output escaping, and rate limiting. Message content is sanitized server-side, and rich chat HTML (product cards, links, images) is additionally sanitized client-side via a bundled copy of DOMPurify before being rendered — see “Bundled Libraries” below. Bundled Libraries DOMPurify 3.1.6 — client-side HTML sanitizer, used to safely render rich chat content (product cards, links, images). Vendored locally at assets/js/vendor/purify.min.js; not loaded from a CDN. © Cure53 and other contributors. Dual-licensed under the Apache License 2.0 and Mozilla Public License 2.0, both GPL-compatible. github.com/cure53/DOMPurify Requirements WordPress 6.2 or later WooCommerce 7.0 or later (must be installed and active) PHP 7.4 or later An API key from Groq, OpenAI, Anthropic, or Google (optional — Basic AI and Live Chat both work without one) Support Support Forum: wordpress.org/support/plugin/winaltchat-for-woocommerce Email: [email protected] We aim to respond to all support requests within 48 hours. External Services This plugin connects to third-party AI providers only when you configure an external AI mode and enter your own API key. In Basic AI mode and during live human chat, no external AI service is used. AI Providers (optional — only when an API key is configured) Customer messages, recent conversation context, and relevant store and product context are sent to the AI provider you select so it can generate a response. No data is sent to these providers when using Basic AI mode. Groq — groq.com | Privacy Policy | Terms of Service OpenAI — openai.com | Privacy Policy | Terms of Use Anthropic Claude — anthropic.com | Privacy Policy | Terms of Service Google Gemini — ai.google.dev | Privacy Policy | Terms of Service Amazon Associate Program (optional — only when a tag is configured) When the Amazon fallback is enabled and no matching product is found in your store, the plugin generates an Amazon search link with your Associate tag. No customer data is transmitted to Amazon by the plugin — the link simply directs the visitor’s browser. Amazon — amazon.com | Privacy Notice Deactivation Feedback (sent on deactivation — full survey response, or a bare anonymous count if skipped) When you deactivate this plugin, an optional short survey asks why. If you respond, your site URL, the plugin/WordPress/PHP version, and whatever you entered in the survey are sent to Winalt Technologies to help improve the plugin. If you skip the survey instead, a bare deactivation count (just the plugin version — no site URL, WordPress version, or PHP version) is still sent so skipped deactivations aren’t invisible in aggregate. No personal data is collected beyond this unless you choose to type it into the free-text field yourself. Winalt Technologies — aisalesmanchatpro.com | Privacy Policy Anonymous Usage Tracking (optional — off by default, only sent if you click “Allow”) On first use, a notice asks permission to send anonymous “still active” pings to help us understand real-world installs. Nothing is sent unless you click “Allow” — you can also decline, or change your choice later from the plugin’s General Settings tab. When enabled, your site URL and the plugin/WordPress/PHP version are sent to Winalt Technologies once immediately and then roughly once a day for as long as it stays enabled. No personal or customer data is ever included. Winalt Technologies — aisalesmanchatpro.com | Privacy Policy Support Contact Form (optional — only sent if you use “Contact us directly”) The settings page includes a “Contact us directly” form. If you use it, your message and the plugin version are sent to Winalt Technologies so we can respond; your email address is included only if you choose to enter one. Nothing is sent unless you submit this form yourself. Winalt Technologies — aisalesmanchatpro.com | Privacy Policy