ZELVO
Zelvo – AI Website Translation compatibility with REEID Translate
Zelvo – AI Website Translation compatibility with REEID Translate is being reviewed using official plugin documentation. AI-provider-based translation using a user-supplied access key (plugin sends page text to the chosen provider after configuration). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Zelvo – AI Website Translation 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
Zelvo – AI Website Translation is documented in the Other category with 8 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 Zelvo – AI Website Translation 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
- AI-provider-based translation using a user-supplied access key (plugin sends page text to the chosen provider after configuration).
- Automatic translation workflow that scans pages and translates content, including automatic translation of new content as it is published.
- Per-language dedicated addresses (e.g., language-prefixed paths such as `/en/`) to serve translated versions without duplicating posts in the admin.
- Translation persistence in the WordPress database: translations remain available even if the plugin is deactivated.
- SEO/metadata handling for translated pages, including hreflang tags and a sitemap per language, plus translated titles/descriptions/social tags and canonical tag correction on translated pages.
- Frontend language switching support via a built-in language switcher that can be placed where desired.
- Compatibility claims with common WordPress builders/editors (Elementor, Divi, Bricks, and the block editor).
- Manual correction of translations from the WordPress admin for each language.
TRANSLATION BOUNDARY
Zelvo – AI Website Translation 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
Zelvo – AI Website Translation and REEID Translate FAQ.
What does Zelvo – AI Website Translation do?
Zelvo – AI Website Translation has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does Zelvo – AI Website Translation 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 Zelvo – AI Website Translation?
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 Zelvo – AI Website Translation in a multilingual WordPress workflow.
REEID documents Zelvo – AI Website Translation 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.