BOTMETRIA
Botmetria translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Botmetria does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- AI bot detection via User-Agent substring scanning per request, using a cached bot detect list (no DB writes or HTTP calls on the hot path).
- Impostor detection by verifying a visitor’s IP against Botmetria-published bot vendor IP ranges before trusting the claimed bot User-Agent.
- AI firewall modes that can temporarily return 503 with Retry-After for AI bots (e.g., Showcase/Allowlist/Server relief or per-bot custom matrix), while exempting classic search engine crawlers from blocking at code level.
- AI referral attribution for human visitors arriving from AI assistants (e.g., chatgpt.com/perplexity.ai), tracking first-touch source and (with WooCommerce) attributing to orders/revenue.
- WooCommerce-integrated conversion analytics: when an order is placed, the plugin sends purchase analytics including order ID, totals/currency, line items, payment method slug, and whether the customer is new/returning; refunds/cancellations send negative correcting amounts.
- Machine-readability outputs intended for AI agents: generates valid JSON-LD Product markup, an llms.txt summary, and a robots.txt helper; JSON-LD and order/revenue attribution require WooCommerce.
Distinctive features
AI bot detection via User-Agent substring scanning per request, using a cached bot detect list (no DB writes or HTTP calls on the hot path). Impostor detection by verifying a visitor’s IP against Botmetria-published bot vendor IP ranges before trusting the claimed bot User-Agent. AI firewall modes that can temporarily return 503 with Retry-After for AI bots (e.g., Showcase/Allowlist/Server relief or per-bot custom matrix), while exempting classic search engine crawlers from blocking at code level. AI referral attribution for human visitors arriving from AI assistants (e.g., chatgpt.com/perplexity.ai), tracking first-touch source and (with WooCommerce) attributing to orders/revenue. WooCommerce-integrated conversion analytics: when an order is placed, the plugin sends purchase analytics including order ID, totals/currency, line items, payment method slug, and whether the customer is new/returning; refunds/cancellations send negative correcting amounts. Machine-readability outputs intended for AI agents: generates valid JSON-LD Product markup, an llms.txt summary, and a robots.txt helper; JSON-LD and order/revenue attribution require WooCommerce. Cloud-connected event pipeline with HMAC-signed events: sends AI-bot visit events, AI-referral events, and approved one-click fix action results; receives an up-to-date AI bot detect list, vendor IP ranges, configuration (including firewall settings if managed from the dashboard), and approved FAQPage Q/A pairs.
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
Keep plugin capabilities separate from translation scope.
Current evidence documents what Botmetria does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Botmetria and REEID Translate FAQ.
Does the current evidence establish translation scope for Botmetria?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.