LINGOJS
LingoJS – Website Translation Integration compatibility with REEID Translate
LingoJS – Website Translation Integration compatibility with REEID Translate is being reviewed using official plugin documentation. Integrates LingoJS into WordPress by inserting a LingoJS script and connecting to the LingoJS translation engine via a remote script. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What LingoJS – Website Translation Integration does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
LingoJS – Website Translation Integration is documented in the Other category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How LingoJS – Website Translation Integration compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Integrates LingoJS into WordPress by inserting a LingoJS script and connecting to the LingoJS translation engine via a remote script.
- Provides an admin-panel configuration flow under “Settings > LingoJS” to set a LingoJS project key and language preferences (base and target languages).
- Supports persistent language selection and a language switcher UI that can be shown/hidden via plugin settings.
- Renders the language switcher either as a floating widget or embedded in page via a shortcode (`[lingojs_widget]`).
- Supports dynamic content translation by detecting/handling dynamic content, including guidance to use “ for dynamic variables and `translate="no"` to exclude content.
- Includes a workflow where texts are selected in the LingoJS dashboard (e.g., “published” vs “blocked”) and then automatically translated into target languages on the website after refresh.
TRANSLATION BOUNDARY
LingoJS – Website Translation Integration capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
LingoJS – Website Translation Integration and REEID Translate FAQ.
What does LingoJS – Website Translation Integration do?
LingoJS – Website Translation Integration has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does LingoJS – Website Translation Integration have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from LingoJS – Website Translation Integration?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate LingoJS – Website Translation Integration in a multilingual WordPress workflow.
REEID documents LingoJS – Website Translation Integration functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.