
LOBBIT MULTILINGUAL
Lobbit Multilingual compatibility with REEID Translate
Lobbit Multilingual compatibility with REEID Translate is being reviewed using official plugin documentation. Translates site content dynamically at the output level without creating duplicate pages or posts, ensuring compatibility with any theme and page builder (including Elementor and block editor). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Lobbit Multilingual 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
Lobbit Multilingual 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 Lobbit Multilingual 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
- Translates site content dynamically at the output level without creating duplicate pages or posts, ensuring compatibility with any theme and page builder (including Elementor and block editor).
- Supports manual translation editing and one-time AI generation via Claude, OpenAI, Gemini, Grok, or DeepL using user-provided API keys, with translations stored in the local database.
- Integrates with WordPress 7.0+ Connectors to reuse existing AI service credentials, eliminating the need for separate key entry within the plugin settings.
- Generates language-specific URLs under unique prefixes (e.g., /en/, /de/) with hreflang tags, translated canonical URLs, og:locale, and per-language sitemaps compatible with Yoast SEO and Rank Math.
- Provides multiple language switcher options including menu integration, floating buttons, Gutenberg blocks, and shortcodes, with customizable flags, styles, and keyboard accessibility.
- Respects `translate="no"` attributes and `.notranslate` classes to exclude specific scripts, styles, code, and elements from the translation process.
TRANSLATION BOUNDARY
Lobbit Multilingual 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. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
Lobbit Multilingual and REEID Translate FAQ.
What does Lobbit Multilingual do?
Lobbit Multilingual has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Lobbit Multilingual 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 Lobbit Multilingual?
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 Lobbit Multilingual in a multilingual WordPress workflow.
REEID documents Lobbit Multilingual 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.