VigIA – AI Visibility, Analytics & Control vs Recomaze – AI Chat Agent, AEO & GEO

Recomaze does two things for a WordPress site, and they feed each other. An AI chat agent on the site. A conversational agent that answers visitor questions from your own catalog, policies and knowledge base – not generic AI answers – recommends the right product, and carries the visitor toward checkout. AEO and GEO. AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) are two names for the same discipline: getting a site retrieved, understood and cited by AI assistants when they generate an answer. Recomaze tracks whether AI actually mentions you, fixes the reasons it does not, and publishes the content and machine-readable signals that make you quotable. The loop between them is the point. The chat agent sees every question your visitors ask, including the ones it could not answer. Those failures become a work list for the AEO side – and content published for AEO comes back as knowledge the agent can answer from. Traditional SEO competes for a position on a page of links. AEO competes to be inside the generated answer. A page can rank well in Google and never be quoted by an AI assistant, usually because nothing on it can be parsed into a clear, checkable claim. The AI chat agent Answers from your own content – the agent replies from your catalog, knowledge base and policies, in your brand voice, instead of improvising. Recommends products in conversation – it surfaces the right item as part of the answer and links the visitor to it. Your styling – colors, placement, wording and the launcher are yours to set, so the agent looks like part of the site. Preview mode – turn the agent on for administrators only and try it on the live site before any visitor sees it. Conversation analytics – conversations, visitor journeys, KPIs and insights, so you can read what people actually ask. Campaigns – run targeted on-site campaigns through the agent. Gaps: what the agent could not answer Every conversation the agent handles badly is recorded as a gap and sorted into four buckets: information missing, feature or product missing, cannot guide, and out of scope. A gap is not a report you read and forget – each one carries a fix, and the fix is a button: Missing information becomes a knowledge base article the agent can answer from next time. A losing topic becomes an AI Visibility article drafted on that exact question. A vague product becomes a product rewrite in the Content Generator, focused on the attributes the visitor asked about. A policy question becomes a policy update in your knowledge base. You can mark a gap resolved or dismiss it. The list is filtered by period, so you can see whether last month’s holes actually got closed. AI Visibility Visibility scans – ask the buying questions that matter in your niche and record which brands the AI names in the answer. Tracked prompts – keep a set of questions under continuous tracking and watch each one trend over time. Competitor tracking – see which brands take the mentions you do not, add competitors deliberately, and exclude ones that are not really rivals. Cited sources – see which pages an AI actually pulled from when it answered. Mentioned vs cited – being named and being used as a source are different results, and they are reported separately. Funnel coverage – see which stage of the buying journey your content covers and where it stops. Scan history and wins/losses – what moved since the last scan, in both directions. Trending in your chat – questions rising in your own visitor conversations, promoted into tracked prompts. Content that answers the question Content Generator – draft articles against the questions you are losing, then publish them straight into WordPress posts. Page templates – reusable structures for the page types that earn answers, run across topics. Content Checker – check a draft against what answer engines can actually extract from it, and apply the fixes. Optimized text pages and product content – rewrite titles, descriptions and Q&A so an AI can lift a fact instead of guessing at marketing copy. Prompt templates – reusable generation prompts, so output stays consistent with how you write. Scheduling and images – schedule a publish, and get image suggestions with the draft. Multi-language – generate the same content in several languages. Catalog and context Catalog Quality – scan products, score how AI-ready each one is, and fix them individually or in bulk. Import – bulk upload products and content. Knowledge Base – the source of truth the agent answers from: policies, shipping, returns, anything a visitor asks. AI Company ID – what you sell, who you sell to and how you talk, built once and pushed to everything the agent and the content generator produce. Connectors and integrations – connect the site so Recomaze can publish back to it, and plug into the rest of your stack. Agentic Commerce Feed – publish a machine-readable product feed for AI shopping agents. llms.txt – served automatically at /llms.txt and /llm.txt, the emerging convention for telling AI crawlers what a site is and what it offers. No file to write by hand. AI crawler log – every fetch of your llms.txt is recorded, so you can see which AI crawlers came, how often, and when they started. Answer schema – Article and FAQPage JSON-LD published in the page head, so an answer engine can lift a question and its answer directly. If Yoast or Rank Math already emits the Article, Recomaze steps aside and publishes only the FAQ, so the page never carries two. SEO fields filled in for you – articles published by Recomaze arrive with the focus keyphrase, SEO title and meta description already written into Yoast SEO’s and Rank Math’s own fields. AI copilot in the admin – ask it to do the work and it runs the steps for you. Dashboard – one AI-readiness score, the setup steps still open, and the latest articles, gaps and insights. Where your site can appear Recomaze prepares content for the assistants people actually ask, including ChatGPT, Claude, Perplexity, Google Gemini, Google AI Overviews and Microsoft Copilot. These are independent services; Recomaze is not affiliated with or endorsed by any of them, and no plugin can guarantee a mention in a generated answer. What Recomaze does is remove the reasons a site gets skipped: thin content, no machine-readable summary, no structured answers, nothing published against the question being asked. How it works Install, activate, and connect the site to Recomaze from the WordPress admin. Recomaze reads your site and builds your AI Company ID: what you offer, who for, in what voice. It scans AI assistants for the questions in your niche and reports where you stand against your competitors. It fixes what it can – content, product text, knowledge base, llms.txt, schema – and drafts what is missing. The chat agent goes live, and every question it cannot answer comes back as a gap with a fix attached. WooCommerce optional Recomaze runs on any WordPress site. A content site that wants the chat agent and the AEO work installs it and never touches a product. When WooCommerce is active, the catalog features switch on as well: product scanning and scoring, bulk product rewrites, product recommendations in chat, the product feed and order tracking. External Services This plugin connects to the following external services: Recomaze API Domain(s): https://api.recomaze.ai https://stagingapi.recomaze.ai (for testing and staging environments) Purpose: The API is used to retrieve user-specific product recommendations, update user preferences, and refresh authentication tokens. Data Sent: Plugin token (used for authentication) Store domain (to identify the WooCommerce store) Interaction events such as user preferences or clicks Product details from orders, including: Product names Product characteristics (e.g., categories, attributes) Product prices Terms of Use: https://recomaze.ai/tos/ Privacy Policy: https://recomaze.ai/privacy-policy/ Recomaze Tracking UI Domain(s): https://trackui.recomaze.ai https://stagingtrackui.recomaze.ai (for testing and staging environments) Purpose: The tracking service is used to display UI components such as recommendation popups and gather anonymous usage metrics to optimize recommendations. Data Sent: Client ID associated with the WooCommerce store. Recomaze Admin Service Domain(s): https://admin.recomaze.ai Purpose: This service is used to send logs for monitoring and debugging purposes. Data Sent: Plugin events and API interaction logs. Recomaze Collector Service Domain(s): https://collector.recomaze.ai Purpose: The collector service is used to retrieve reports for analytics and recommendations. Data Received: Analytics reports and performance insights.

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.