VIGIA
VigIA – AI Visibility, Analytics & Control | REEID Translate Compatibility
REEID processes supported labels, notices and consent-related text while VigIA remains responsible for tracking IDs, events, measurement and analytics data.
AWAITING VERIFICATION
Translate visible text. Preserve measurement logic.
Multilingual visitor-facing wording stays separate from tracking configuration, event definitions and collected analytics data.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
CONTENT BOUNDARY
Translatable content remains separate from plugin-specific functional configuration.
DATA-SAFE
Tracking IDs, events, measurement rules and collected analytics data remain functional configuration.
PRACTICAL WORKFLOW
Translation workflow
01 · Configure analytics normally
Maintain tracking, events and measurement settings through VigIA.
02 · Identify visible analytics text
Locate supported consent labels, notices, embedded labels or other visitor-facing wording.
03 · Translate supported wording
Process multilingual text without altering IDs, event names or measurement configuration.
04 · Validate tracking and frontend text
Review translated wording while confirming analytics collection still behaves as intended.
SUPPORTED CONTENT
Translation scope
Visitor-facing text
Replace this draft item with the exact content coverage.
Interface content
Document supported labels, titles or interface strings where applicable.
Product-specific content
Add confirmed product-specific support before publication.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- AI crawler monitoring and analytics dashboard: tracks AI crawler visits (total visits, unique crawlers, pages crawled) with timeline breakdown, top crawlers/pages tables, recent activity log, and advanced filters (crawler, content type, HTTP status, date range) plus server-side pagination and CSV export with metadata banner.
- Crawler access control: supports blocking AI crawlers via PHP to return a 403 Forbidden response, including quick-block controls in the analytics dashboard and block management from an Extras page.
- Robots.txt management and compliance monitoring: can add Disallow rules for AI crawlers, provide a visual preview of robots.txt, monitor which crawlers ignore rules, and offer one-click blocking for non-compliant crawlers (including support for physical and virtual robots.txt).
- AI visibility scoring analyzer: provides a 100-point analyzer with letter grades (A+ to F) across 20 checks in categories covering access/discovery signals (robots.txt, llms.txt, sitemap/RSS, etc.), structured data/semantic context (JSON-LD, Open Graph, Twitter Cards, canonical/meta), content structure/readability, AI interaction/distribution (markdown delivery/AI share buttons), and access performance (TTFB measurement).
- LLMs.txt generation: generates llms.txt and llms-full.txt with content selection by post type and taxonomy filters, manual include/exclude and URL-pattern exclusions, SEO noindex auto-exclusion integration, scheduled auto-regeneration, and robots.txt integration to reference llms.txt files.
- Markdown for Agents endpoints: serves optimized markdown for posts/pages and public post types via dedicated .md endpoints and/or Accept: text/markdown negotiation; supports taxonomy archive markdown (opt-in per taxonomy) and WooCommerce product/category markdown with YAML frontmatter and schema-like fields; includes analytics tracking for markdown requests and respects blocking rules (403) and llms.txt exclusion filters.
- JSON-LD structured data generation for AI discovery: generates Site Identity JSON-LD (WebSite + Organization/Person with social profiles/sameAs) and AI Discovery JSON-LD containing ReadAction pointers to llms.txt/llms-full.txt and Markdown for Agents endpoints; includes live preview and SEO plugin conflict detection.
- Abilities API exposure (WordPress 6.9+): registers abilities for analytics (crawler stats, top crawlers, top pages), blocking (list blocked items, block/unblock by User-Agent pattern), and robots.txt management (get rules, add Disallow, remove rule).
Distinctive features
AI crawler monitoring and analytics dashboard: tracks AI crawler visits (total visits, unique crawlers, pages crawled) with timeline breakdown, top crawlers/pages tables, recent activity log, and advanced filters (crawler, content type, HTTP status, date range) plus server-side pagination and CSV export with metadata banner. Crawler access control: supports blocking AI crawlers via PHP to return a 403 Forbidden response, including quick-block controls in the analytics dashboard and block management from an Extras page. Robots.txt management and compliance monitoring: can add Disallow rules for AI crawlers, provide a visual preview of robots.txt, monitor which crawlers ignore rules, and offer one-click blocking for non-compliant crawlers (including support for physical and virtual robots.txt). AI visibility scoring analyzer: provides a 100-point analyzer with letter grades (A+ to F) across 20 checks in categories covering access/discovery signals (robots.txt, llms.txt, sitemap/RSS, etc.), structured data/semantic context (JSON-LD, Open Graph, Twitter Cards, canonical/meta), content structure/readability, AI interaction/distribution (markdown delivery/AI share buttons), and access performance (TTFB measurement). LLMs.txt generation: generates llms.txt and llms-full.txt with content selection by post type and taxonomy filters, manual include/exclude and URL-pattern exclusions, SEO noindex auto-exclusion integration, scheduled auto-regeneration, and robots.txt integration to reference llms.txt files. Markdown for Agents endpoints: serves optimized markdown for posts/pages and public post types via dedicated .md endpoints and/or Accept: text/markdown negotiation; supports taxonomy archive markdown (opt-in per taxonomy) and WooCommerce product/category markdown with YAML frontmatter and schema-like fields; includes analytics tracking for markdown requests and respects blocking rules (403) and llms.txt exclusion filters. JSON-LD structured data generation for AI discovery: generates Site Identity JSON-LD (WebSite + Organization/Person with social profiles/sameAs) and AI Discovery JSON-LD containing ReadAction pointers to llms.txt/llms-full.txt and Markdown for Agents endpoints; includes live preview and SEO plugin conflict detection. Abilities API exposure (WordPress 6.9+): registers abilities for analytics (crawler stats, top crawlers, top pages), blocking (list blocked items, block/unblock by User-Agent pattern), and robots.txt management (get rules, add Disallow, remove rule).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Separate multilingual wording from analytics data and tracking logic.
REEID handles supported visitor-facing text while VigIA controls tracking configuration, measurement logic and analytics data.
Tracking IDs, event configuration and collected data are not translation content.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
VigIA – AI Visibility, Analytics & Control and REEID Translate FAQ.
Does REEID Translate work with VigIA?
REEID Translate Pro processes the supported visitor-facing fields documented for this integration while VigIA retains control of its own functionality.
Does REEID translate or alter tracking IDs and events?
No. Tracking identifiers, event definitions and measurement rules remain controlled by VigIA.
Can consent or visitor-facing analytics labels be translated?
Yes when those strings are available through supported visitor-facing content paths.
RELATED GUIDES
Continue through the compatibility library.
ANALYTICS INTEGRATION
Translate visitor-facing VigIA text without disturbing analytics.
Keep multilingual wording separate from tracking IDs, events and measurement logic.
Supported content and limitations are defined by the integration record.