WPGLOBUS
WPGlobus translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WPGlobus 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
- URL-based multilingual site support with manual translation entry for posts, pages, custom post types, categories, tags, menus, widgets, site title, and tagline.
- Multilingual SEO titles and meta descriptions, with compatibility for Yoast SEO (free version).
- Per-language URLs and language switching on the front end, including a drop-down menu extension and a customizable widget.
- Admin interface language switching from the top bar.
- Uses a browser cookie to remember the selected language preference.
- Requires pretty permalinks; plain query-string URLs are not supported.
- Stores translations in a shared special format and provides a cleanup step before uninstalling to remove extra languages.
Distinctive features
URL-based multilingual site support with manual translation entry across common content and site elements, plus front-end and admin language switching. The plugin also notes multilingual SEO titles and meta descriptions and compatibility with Yoast SEO (free version).
Dynamic content
The evidence shows language-specific content can be entered for posts, pages, custom post types, categories, tags, menus, widgets, site title, and tagline. No additional runtime content behavior is established beyond the documented language switching and remembered language preference.
SEO and metadata
The evidence supports multilingual SEO titles and meta descriptions. No official evidence was found for schema output, indexing controls, canonical handling, or sitemap integration.
URLs and navigation
The plugin uses per-language URLs and front-end language switching. A drop-down menu extension and a customizable widget are documented for switching languages. Pretty permalinks are required, and plain query-string URLs are not supported.
Forms and commerce
No official evidence was found for forms or commerce-specific behavior.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WPGlobus 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
- WPGlobus requires pretty permalinks; plain query-string URLs are not supported. The available evidence does not establish support for schema output, indexing controls, canonical handling, or sitemap integration. The evidence also does not establish broader SEO behavior beyond the documented multilingual title and meta description support.
COMMON QUESTIONS
WPGlobus and REEID Translate FAQ.
Does the current evidence establish translation scope for WPGlobus?
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.