Rooster One vs VigIA – AI Visibility, Analytics & Control

One plugin instead of dozens. 554 tools, and they agree with each other. Rooster One does the work that would otherwise take dozens of separate plugins, and it does it from one place, on one set of numbers. Dozens of plugins means dozens of different vendors, dozens of renewal dates to keep track of, dozens of update cycles that have to keep working alongside each other, and a different support desk to write to depending on which part has gone wrong. One plugin means one licence, one update, one place to ask, and one thing for WordPress to load on every request instead of dozens. What is actually in it: a full SEO engine that replaces Yoast or AIOSEO. Product recommendations built from your real sales. Role, wholesale and tiered pricing. Meta, Google Ads, GA4 and TikTok measurement, sent server-side so an ad blocker cannot silence it. Sixteen couriers with vouchers, labels, tracking and daily closings. Marketplace feeds and order import for Skroutz, Shopflix, eMAG, Etsy, Amazon and more. Side cart, wishlist, back-in-stock waitlist, quote requests for catalogue shops, swatches, trust badges. Popups and scheduled announcements. Abandoned-cart recovery, email and web push campaigns, audiences. Surveys, competitions and events. Invoices, packing slips and credit notes. A GDPR consent banner with a cookie scanner. The EU withdrawal button that Directive 2023/2673 now requires. And an AI assistant that answers from your own catalogue rather than making things up. That is 188 pages and the 554 tools inside them, and there is a written description of what every one of them is for. Why one plugin rather than dozens Because separate plugins cannot see what the others know, so they disagree, and each one works the same thing out again while your customer waits. Rooster One measures your whole business on a schedule instead: every product, page, customer, order and session, written into flat tables. Which products sell and which never do, which pages are read, who bought and who nearly did. The SEO engine, the recommendations, the audiences, the ad ROI report and the AI assistant then all read those same tables. That is why they agree, and why the plugin gets faster to use as you switch more of it on: the heavy work already happened, before the request arrived. The trade-off is timing and we would rather say so plainly. A figure is only as new as its last run. And it is one plugin to load, not dozens This part has nothing to do with how well any plugin is written. WordPress loads every active plugin on every request, before it knows whether that request needs it: a file to read from disk, hooks to register, options to fetch, a translation catalogue to load. That toll is paid on the home page, on every admin screen and on every REST call, by every plugin, including the ones that will do nothing at all on that particular request. A site carrying a hundred of them pays it a hundred times before a single line of useful work happens. Rooster One is one plugin, and the parts you have not switched on register nothing. On Pro, the storefront is served by a separate lightweight runtime rather than the admin half, so your customer’s page load carries the code that draws the page and not the code that runs the shop. Everything is off by default. It installs beside your current SEO plugin, pixel manager and consent tool and changes nothing until you switch a piece on. Rooster One runs on your own server. Everything it ever sends to an outside service, and what triggers it, is listed under “What does Rooster One send to an outside service, and when?” in the FAQ below. The free version is a complete product, not a demo: 754 of the 1,268 screens, tools and actions are in it. Pro adds the operational half and the separate front-end runtime plugin. Who builds it Rooster One is built by Oxford Metadata Ltd, whose organisation is approved under Anthropic’s Cyber Verification Program for dual-use security work such as penetration testing and vulnerability research. That is the same discipline the plugin’s own defensive features come out of: the bot filtering, the form captcha, the consent and proof-of-consent log, and the login hardening. The AI features run on Anthropic Claude for chat and reasoning and Voyage AI for embeddings. It reads your site for what it is Shop — sales and add-to-carts are the measure. Catalogue — products published but not sold; engagement is the measure. Content — no WooCommerce; visits, engagement and forms are the measure. Auto-detected, overridable in one click. Scoring, cornerstones and applicable signals all follow from it. You can find all of it Ctrl+K reaches 742 places: 188 pages and the 554 tools inside them, each one openable directly. All Features lists every one, with pinnable favourites, and prints the figure for your own install. Every page carries a written description of what you can do there, and that text feeds the search. What gets measured Computed on a schedule, stored flat. Everything below reads these. Product vitals — velocity, out-of-stock history, price history, basket role, returns, and a 0–100 demand score. Content vitals — reach, engagement, freshness and a content-demand score for every post, page and custom type. Customer vitals — an omnichannel profile: purchases, affinities, lifecycle stage, survey answers, return risk. Session and attribution rollups — engagement joined to conversion on one session id, with landing page, campaign and five UTMs. Effective prices — every price rule resolved ahead of time into one row per product per audience. The features AI chat & semantic search Chat widget on Anthropic Claude, grounded in your catalogue — only real, in-stock items with exact links. Semantic search on Voyage AI embeddings across products, posts, pages and terms. A knowledge base you control, with identity guardrails so it cannot mis-describe you. Chat analytics — what was asked, how it was rated, which questions found nothing, which chats ended in an order. Related content on articles, guides, listings and products, from the same index. Added automatically to the content types you choose, or placed by hand with the AIEO Related content block or the [aieo_semantic_related] shortcode; either can be narrowed to one kind of content, so a listing recommends listings rather than products. SEO engine A drop-in replacement for AIOSEO, Yoast or Rank Math. Stays gated behind your current SEO plugin until you switch over; a read-only importer for all three and a head-parity check are included. Head, canonical, robots, Open Graph, Twitter and JSON-LD, assembled once into a cache. Commerce schema from the same tables — ProductGroup + hasVariant, per-variant colour, gtin, brand, shipping and return policy. AI titles and descriptions written against the live SERP. Drafts await approval, or run on Autopilot. Opportunity grid — traffic × conversion: hidden gem, intent mismatch, defend, prune. Rank tracking (optional DataForSEO, under your spend cap). Redirects and 404s, slug monitor, static sitemap, robots.txt, alt-text filling, EU Omnibus history, hreflang, Local SEO. Selling more Recommendations — up-sell, cross-sell and same-need alternatives from your real sales patterns. Rails you order by drag-and-drop, block and classic themes, with custom slots. Pricing engine — role and wholesale prices, brand discounts, loyalty tiers, points, free gifts. Stacked, resolved ahead of time. Merchandising — swatches, labels, trust badges, payment logos, galleries, layout builder, custom tabs, one master button style. Lift measurement — the incremental orders and revenue the engine adds. Cart, checkout, recovery Side cart, sticky add-to-cart, wishlist, back-in-stock waitlist. Quote requests for catalogue shops — an ask-for-a-price card on products you do not sell online, a quote basket the shopper grows as they browse, and the browsing trail behind each request. Booked as valued leads per campaign, so a catalogue stops scoring EUR 0.00. Saved and abandoned carts — share and resume, cookieless restore that survives CDN caching. Checkout tuning — distraction-free checkout with A/B assignment, minimum order, and business-invoice fields. Full block and classic parity. Reaching customers Audiences — top, lapsed, lookalike, abandoned-cart, reactivation, competition entrants. Recomputed nightly. Automated campaigns — abandoned cart, win-back, birthday, back in stock, post-purchase. Email and web push, quiet hours honoured. Social posts from your catalogue, competitions on any Gravity Form, surveys scored into NPS and voice-of-customer. Knowing what worked Server-side measurement you own — Meta CAPI, GA4, Google Ads Enhanced Conversions, TikTok Events API. Deduplicated, sent after the order is saved, with a daily safety net. Consent / GDPR CMP — first-party banner, Consent Mode v2, proof-of-consent log, cookie scanner. ROI Wizard — orders, revenue, cost, net, ROAS and ROI by engine, offer, channel, campaign or creative. Ad spend typed, by CSV, or nightly from Google Ads / Meta / TikTok. Conversion goals for non-shops. Insights Chat — ask your shop questions in wp-admin. Customers pseudonymised, no data export. Running the shop Marketplace order import — Skroutz, Shopflix, eMAG, eFood, Wolt, Etsy, Amazon → native WooCommerce orders. The catalogue importer runs it in reverse. Streaming feeds — ready-made templates for Amazon Inventory Loader, BestPrice, eBay File Exchange, eFood, EMAG, Etsy, Facebook Product Catalog, Facebook Marketplace, Google Shopping, Google Local, Google AdWords Custom Remarketing, Shopflix, Skroutz, Tolstoy and Wolt, plus Generic CSV and a fully custom builder. Sixteen couriers — vouchers, labels, COD, tracking, bulk printing, daily closings. ACS, BOX NOW, Courier Center, ELTA, Geniki Taxydromiki, Speedex, DHL Express, FedEx, UPS, USPS, Royal Mail, DHL Paket, Colissimo, BRT, Correos Express, Sendcloud — plus a manual carrier for one with no API. Order documents — invoices, packing slips, proformas, credit notes. Singly or merged across a date range. Delivery economics — real break-even free shipping from your carrier costs, per-carrier × zone P&L. Operational intelligence — stock recovery, missing hot sellers, out-of-stock predictor, branch stock, barcode scanning, optional ERP. The withdrawal button — Directive (EU) 2023/2673 Every EU distance seller must now give consumers a prominent, permanently available button to declare withdrawal electronically. No transition period. A real button, for the whole statutory period. 14 calendar days from receipt — computed from delivery, not the order date. Guests included. An account is offered afterwards, never required. No reason, no prior contact, partial withdrawal by item and quantity. Acknowledgement on a durable medium with content, date and time. Cancellation stays distinct from withdrawal — one you may refuse, the other you may not. Return vouchers checked by an operator before the customer sees them. Ships disabled. Content, blocks and regional selling Events with RSVP and self-registration, FAQ accordions, Store Pages, Food & Beverages option groups, Google reviews, Media Cleanup that quarantines before it deletes. Dozens of server-rendered blocks — store, product, recommendation, swatch, brand, category, blog, competition and event, plus Custom Slot regions. Regional checkout — COD by country or courier, “from X,XX €” labels before a postcode is entered, and per-country payment and shipping rules. Speed and resilience Pre-computed into flat tables; the storefront reads single cached rows. A thin front-end runtime plugin (Pro) serves the storefront even when the admin plugin is trimmed from the request. Self-healing jobs re-arm after updates, stay dormant until used, and collapse runaway third-party tasks. Tables are never dropped on update, activation or deactivation — only on explicit uninstall. Free and Pro GPLv3. The free version is a complete, working product — not a demo with the useful parts removed. GPLv3 throughout. There are three separate things here, and it is worth being precise about which is which, because two of them are called “Pro”. 1. This plugin, free. A complete, working product, not a demo with the useful parts removed: AI chat and semantic search, the whole SEO engine, pricing and merchandising, storefront features, measurement and consent, product feeds and marketplace feed export, courier fulfilment across all sixteen carriers, the block library, Ctrl+K — and the complete withdrawal button. That last is a legal obligation for every EU distance seller; charging for it would be a poor thing to do. 2. A Pro subscription (or the 14-day trial), activated by connecting the site to your Rooster One account. No per-feature keys. It unlocks the Pro screens whose code is already inside this download: Marketplace order import — Skroutz, Shopflix, eMAG, eFood, Wolt, Etsy, Amazon. Attribution and ROI — dashboard, ROI Wizard, ad-spend connectors, shipping cost against margin. Audiences and campaigns — audience builder, email and web-push flows, social posts, AI-suggested offers. Customer intelligence — customer lookup, surveys, cancellations and returns analysis, chat analytics. Insights Chat, events and competitions, Action Scheduler cleanup. 3. Two companion plugins, included with a Pro subscription and installed separately. A subscription on its own does not put their code on your server, so these screens ask you to install the plugin rather than pretending to work: Rooster One Runtime — serves the storefront, SEO head, sitemap and redirects without loading the admin half. The biggest single speed difference between free and Pro. Rooster One Pro — carries six engines this download does not contain: supplier invoice scanning, the accounting and ERP connectors (Entersoft, Galaxy, Soft1, Zoho Books, and Oxygen supplier sync), the catalogue importer for building a product source from a supplier feed, the product exchanger for sharing content between WP sites, the duplicate-product merge engine that auto detects simple products and converts them to variations, and semantic internal linking. Everything Pro-locked stays visible with an explanation of what it does, and where a screen also needs the Pro plugin it says so before you buy, not after. Optional integrations Rooster One runs entirely on your own server. Nothing below is required for the plugin to work — each is an opt-in add-on you enable only if you want that capability, using your own account. Rooster AI credits (rooster.systems) — powers the AI chat, AI SEO copy and Insights Chat via Anthropic Claude and Voyage AI embeddings, with no per-provider API keys to manage. Recommendations service (eshop-optimizer.com) — graph-database up-sell/cross-sell analysis of your order history. DataForSEO — optional keyword rank tracking under a spend cap you set. Ad and measurement platforms — Google Ads, GA4, Meta and TikTok, each independently selectable. Couriers and marketplaces — your own carrier and marketplace accounts, for vouchers and order import. Google Places / Search Console for location data and search performance.

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.