OMOTETAG
OmoteTag compatibility with REEID Translate
OmoteTag compatibility with REEID Translate is being evaluated from available plugin evidence. Loads a hosted OmoteTag multilingual widget on every page (no theme file editing required). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for OmoteTag.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
OmoteTag is documented in the Other category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How OmoteTag compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Loads a hosted OmoteTag multilingual widget on every page (no theme file editing required).
- Provides a single settings value (site key) and an enable/disable checkbox controlling whether the widget is output.
- Enqueues exactly one script for the widget (widget.js) and uses a constant widget script URL with no override path (no filter/setting/stored value changes it).
- On every page view, the visitor’s browser loads the widget and then requests widget configuration from OmoteTag servers using the site key as a query parameter.
- When a visitor selects a non-original language, the browser sends the visible page text plus the selected language code and site identifier (site_key) to OmoteTag servers; OmoteTag uses Microsoft Azure AI Translator to return translations.
- Persists the visitor’s chosen language in the visitor’s browser (local storage and a cookie named `st_lang` lasting one year) and reads it on subsequent page loads.
- On the free plan, the widget displays a “Powered by OmoteTag” label linking to trendmap.jp, and this label cannot be switched off on that plan (paid plans do not display it).
CONTENT BOUNDARY
OmoteTag capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
OmoteTag and REEID Translate FAQ.
What does OmoteTag do according to the available plugin evidence?
OmoteTag has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for OmoteTag?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for OmoteTag?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate OmoteTag in a multilingual WordPress workflow.
REEID documents OmoteTag functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.