SAM Optirank vs VigIA – AI Visibility, Analytics & Control

SAM Optirank is a WordPress plugin that improves your natural and local search engine optimization using artificial intelligence (Claude Haiku by Anthropic). Description en français SAM Optirank est un plugin WordPress qui améliore votre référencement naturel et local grâce à l’intelligence artificielle (Claude Haiku d’Anthropic). IA incluse dans l’abonnement — avec une licence active, l’IA fonctionne immédiatement, sans clé API à configurer. Chaque licence inclut un quota mensuel (≈ 140 pages satellite générées). Une jauge dans les réglages affiche votre usage restant sous la forme « ≈ N pages restantes ». Aucune clé Anthropic à fournir : tout passe par l’IA incluse dans votre abonnement. Gratuit — score SEO local de 0 à 100, champs titre/méta-description avec compteur dans l’éditeur, aperçu SERP en direct, zone géographique pour le SEO local, compatible Gutenberg, Oxygen, Elementor, Beaver Builder. Premium (licence) — analyse SEO complète par IA, assistant « Analyser → Valider → Optimiser », génération de contenu HTML, recherche de mots-clés (longue traîne, local, questions PAA, LSI), suivi des positions Google (Serper.dev / Search Console), corrections en un clic, rapports, et cocon sémantique (pages satellites optimisées et maillées, créées en brouillon puis publiées manuellement). Compatible avec tous les page builders : les balises SEO sont injectées via les hooks natifs de WordPress, sans modifier le builder. Free features Local SEO score from 0 to 100 (title, meta description, H1, word count, links, images) SEO title and meta description fields with character counter in the editor Live SERP preview Geographic zone for local SEO Compatible with classic WordPress, Gutenberg, Oxygen Builder, Elementor, Beaver Builder Premium features (license required) AI included in your subscription. With an active license, AI features work out of the box — no API key to configure. Each license includes a monthly allowance (about 140 satellite pages worth of generation). A simple gauge in the settings shows your remaining usage as “≈ N pages left”. No Anthropic key is required: all AI requests go through the AI included in your subscription. Full AI analysis — score, strengths, detected issues and prioritized suggestions via Claude Haiku (Anthropic) “Analyze → Validate → Optimize” Wizard — Claude analyzes your page semantics, generates ~20 keywords to validate in one click, then automatically optimizes SEO title, meta description, Schema.org, Open Graph and canonical URL AI-generated HTML content — H1, H2s, paragraphs and conclusion ready to paste into the editor AI keyword research — primary, long-tail, local, PAA questions, LSI semantic clusters, CSV export Google position tracking — via Serper.dev (Google Search API) One-click auto-fix recommendations — apply all SEO fixes instantly Progress reports — dashboard, charts, AI-generated executive summaries Semantic Cluster (Cocon Sémantique) — automatically generate SEO-optimized satellite pages, interlinked and ready to index Royalty-free images — optionally illustrate each satellite page with a relevant Unsplash photo (imported into your media library) Manual publishing — generated satellite pages are always created as drafts; you review and publish each one yourself, so nothing goes live without your action Compatibility Fully compatible with Oxygen Builder, Elementor, Beaver Builder, WPBakery and the classic WordPress/Gutenberg editor. All meta tags and SEO data are injected via native WordPress hooks — the builder is never modified. External Services This plugin connects to the following external services. These services are only called when you have configured the corresponding API keys in the plugin settings. No data is sent without your explicit action. Anthropic Claude API (premium features) Used for AI-based SEO analysis, keyword research, content generation and optimization recommendations. Data sent: page content (title, meta, headings, body text), target keyword, geographic area When: only when you trigger an AI analysis or content generation from the plugin interface Routing: requests are relayed through the Groupe Coste license server (see below), which forwards them to Anthropic using its own key and meters your monthly token allowance. No personal Anthropic key is used. Service provider: Anthropic, PBC — https://www.anthropic.com Terms of use: https://www.anthropic.com/legal/aup Privacy policy: https://www.anthropic.com/privacy Serper.dev (optional — position tracking) Used to retrieve Google search results and detect the position of your pages for tracked keywords. Data sent: tracked keywords, target country/language When: only during scheduled or manual position tracking updates Service provider: Serper.dev — https://serper.dev Terms of use: https://serper.dev/terms Privacy policy: https://serper.dev/privacy Unsplash (optional — satellite page images) Used to fetch a relevant royalty-free photo to illustrate each generated satellite page. The image is then downloaded into your WordPress media library. Data sent: the target keyword (search query) of the satellite page When: only when you generate a satellite page AND have entered an Unsplash API key with the image option enabled Service provider: Unsplash Inc. — https://unsplash.com Terms of use: https://unsplash.com/terms Privacy policy: https://unsplash.com/privacy Google Search Console (optional — position tracking) Optional OAuth 2.0 connection to import click and impression data from your GSC account. Data sent: OAuth token (stored locally), site URL When: only when you connect GSC and trigger a data import Service provider: Google LLC — https://search.google.com/search-console Terms: https://developers.google.com/terms Privacy policy: https://policies.google.com/privacy Google Analytics 4 (optional — visitor tracking) If you enter a GA4 Measurement ID in the settings, the plugin loads Google’s official gtag.js tracking script on your public pages. Leave the field empty to load nothing. Data sent: standard Google Analytics traffic data (page views, visitor/device info collected by gtag.js) When: on every public page load, only when a GA4 Measurement ID is configured Service provider: Google LLC — https://www.google.com/analytics Terms: https://marketingplatform.google.com/about/analytics/terms/us/ Privacy policy: https://policies.google.com/privacy Groupe Coste License Server (premium features) Used to validate your premium license key when activating or using premium features, and to relay AI requests through the AI included in your subscription. Data sent: license key, WordPress site URL; and — only when using the included AI — the same page content/keyword data described in the Anthropic section above, forwarded to Anthropic on your behalf When: on plugin activation, periodically to verify license validity, and each time you trigger an AI action while using the included AI allowance Service provider: Groupe Coste — https://groupe-coste.fr Terms: https://groupe-coste.fr/mentions-legales Privacy policy: https://groupe-coste.fr/mentions-legales

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.