WP MULTILANG
WP Multilang – Translation and Multilingual Plugin translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WP Multilang – Translation and Multilingual Plugin 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
- Translates post types, taxonomies, meta fields, options, menus, titles, widgets, and multimedia text fields.
- Runs translation at PHP and is compatible with REST API.
- Supports multisite and WordPress installations in a sub-folder.
- Keeps separate menu items, posts, terms, widgets, and comments per language without duplicate posts or additional database tables.
- Supports configuration via `wpm-config.json` and filters for multidimensional arrays in options, meta fields, and post content.
- Provides WooCommerce support including product translation, customer-language emails, REST API support, import/export, and cart synchronization across languages.
- Supports export and import of content in XLIFF or XML format for translation outside WordPress.
- Includes a language switcher shortcode/function and supports translation syntax, URL translation, and string/value translation helpers.
Distinctive features
Notable differentiators include language-specific handling of menus, posts, terms, widgets, and comments without duplicate posts or extra database tables, WooCommerce support with product translation and cart synchronization across languages, and support for translation workflows outside WordPress through XLIFF or XML export/import.
Dynamic content
Evidence supports translation-related handling for widgets, comments, menus, and WooCommerce cart synchronization across languages. It also mentions REST API compatibility and helpers for string/value translation. Broader runtime content behavior is not established by the supplied evidence.
SEO and metadata
The supplied evidence mentions translation of titles and meta fields, but it does not establish broader SEO metadata handling beyond that. No additional metadata behavior is confirmed.
URLs and navigation
Evidence mentions URL translation and a language switcher shortcode/function. It also states compatibility with multisite and sub-folder WordPress installations. Other navigation behavior is not established.
Forms and commerce
WooCommerce support is explicitly mentioned, including product translation, customer-language emails, REST API support, import/export, and cart synchronization across languages. No broader forms behavior is established.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WP Multilang – Translation and Multilingual Plugin 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
- Evidence does not establish support for every possible WordPress surface or every plugin feature. The available information shows translation-related behavior for specific content types and site elements, but it does not confirm broader compatibility beyond those items. Some behavior is described for REST API, multisite, sub-folder installs, and WooCommerce, but user-facing limits outside those areas are not established.
COMMON QUESTIONS
WP Multilang – Translation and Multilingual Plugin and REEID Translate FAQ.
Does the current evidence establish translation scope for WP Multilang – Translation and Multilingual Plugin?
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.