TRANSLATEWP
TranslateWP compatibility with REEID Translate
TranslateWP compatibility with REEID Translate is being evaluated from available plugin evidence. On-demand (real-time) translation per page/language request, with results cached for subsequent visitors in that language. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for TranslateWP.
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
TranslateWP is documented in the Other category with 6 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 TranslateWP 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
- On-demand (real-time) translation per page/language request, with results cached for subsequent visitors in that language.
- No pre-translation/background sync workflow; translations are generated when a visitor requests a page in a target language.
- Integration with an external TranslateWP translation service/API (api.translatewp.ai) to generate and serve translations.
- Language switcher support via multiple UI mechanisms: floating switcher, native menu item, classic widget, and a [twp-languages] shortcode.
- Cache behavior and page-cache compatibility requirements for the `lang` query parameter (e.g., do not strip/normalize `lang`, and do not serve a cached default-language page for `?lang=` requests).
- Privacy behavior: visitor personal data is stated as not leaving the site; page content samples/host/home URL may be sent to the TranslateWP service when using translation/scanning features or completing setup registration.
Distinctive features
On-demand (real-time) translation per page/language request, with results cached for subsequent visitors in that language. No pre-translation/background sync workflow; translations are generated when a visitor requests a page in a target language. Integration with an external TranslateWP translation service/API (api.translatewp.ai) to generate and serve translations. Lexicon feature to define fixed term translations per language so the AI follows user-specified vocabulary rules. Language switcher support via multiple UI mechanisms: floating switcher, native menu item, classic widget, and a [twp-languages] shortcode. Cache behavior and page-cache compatibility requirements for the `lang` query parameter (e.g., do not strip/normalize `lang`, and do not serve a cached default-language page for `?lang=` requests). Privacy behavior: visitor personal data is stated as not leaving the site; page content samples/host/home URL may be sent to the TranslateWP service when using translation/scanning features or completing setup registration.
CONTENT BOUNDARY
TranslateWP 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
TranslateWP and REEID Translate FAQ.
What does TranslateWP do according to the available plugin evidence?
TranslateWP has 6 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 TranslateWP?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for TranslateWP?
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 TranslateWP in a multilingual WordPress workflow.
REEID documents TranslateWP 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.