REEID Translate Pro documentation
REEID Translate Documentation Hub
Learn how REEID Translate Pro works, how to start safely, and how to use its translation, localization, glossary, SEO, builder, WooCommerce, and Cloud Assist features in production WordPress environments.
Start small
Translate one page, product, or post first. Review the output, confirm layout, then continue with more languages or bulk workflows.
Choose a mode
Use Local BYOK when you want your OpenAI key to stay on your WordPress site, or Cloud Assist when you want REEID’s cloud-assisted workflow and cache reuse.
Protect structure
REEID translates text while preserving WordPress structure, editor data, SEO relationships, slugs, and builder-specific content models where supported.
Getting Started
How do I translate a post or page?
Open the REEID Translate panel inside the editor, choose the target language, then run translation. If a translation already exists, REEID updates the existing translated version instead of creating unnecessary duplicates.
Which editors and content types are supported?
- Gutenberg pages and posts
- Classic Editor content
- Elementor pages and text nodes
- WooCommerce products and product strings
- Titles and slugs
- Body content and editor blocks
- SEO fields where supported
- Translation relationships and language metadata
Where are translations stored?
REEID uses native WordPress structures and metadata relationships where possible. This avoids fragile shadow systems and helps keep translated content easier to manage, inspect, repair, and maintain long-term.
Can I re-translate safely?
Yes. Re-running translation is designed to update the existing translation while preserving relationships and structure. For best results, keep the original editor consistent and avoid mixing builder data from different editors.
Local BYOK Mode
Local BYOK means “Bring Your Own Key.” In this mode, your OpenAI API key stays on your WordPress site and is used by the plugin-side translation engine.
- Good for users who want local control of their API key.
- Translation requests are initiated from the WordPress admin workflow.
- Your OpenAI usage depends on your own OpenAI account and model configuration.
- Best when you prefer direct local control over cloud-assisted processing.
Cloud Assist Mode
Cloud Assist routes selected translation workflow through REEID’s cloud service. It can support cache reuse, usage controls, cloud-side processing, and more consistent translation reuse across repeated runs.
- Useful for repeated translations and ongoing site maintenance.
- Can reduce unnecessary repeated token usage through cache reuse.
- May include usage limits depending on license status and plan.
- Best when you want cloud-assisted workflow features.
Cloud Assist Cache Reuse
Cloud Assist cache reuse helps avoid translating unchanged content again and again. When the same string appears in a repeated translation run, Cloud Assist can reuse the previous translation instead of sending every unchanged string back to the AI translation engine.
- Useful when translating the same page again.
- Helpful after small edits to existing content.
- Can reuse unchanged Gutenberg, Elementor, Classic, or WooCommerce strings where supported.
- Can reduce repeated token usage.
- Does not guarantee zero tokens.
- Changed text still needs fresh translation.
- Formatting changes can affect reuse.
- Prompt or glossary changes may reduce cache hits.
Practical expectation: first translation uses normal tokens; unchanged retranslations should use much less; small edits should mainly translate changed strings; large rewrites will still use more tokens.
Glossary
The glossary helps guide translation decisions for brand names, product names, preferred terminology, terms that should not be translated, and client-specific language rules.
- Add preferred terms before translating important content.
- Protect brand names, product names, codes, and technical terminology.
- Use glossary rules to improve consistency across pages and languages.
- Keep glossary guidance stable when using Cloud Assist cache reuse.
Prompt and Custom Instructions
Prompt guidance lets you add extra translation instructions without replacing the plugin’s core safety and structure-preservation rules.
- Preserve names or product codes.
- Use a formal, natural, technical, or marketing tone.
- Follow brand terminology.
- Adapt style without changing layout structure.
Strings Localization
Strings Localization handles smaller interface-level text that may not belong to a single page or product. This helps make the frontend feel fully multilingual.
Menu Labels
Review navigation labels, auto-fill missing translations, and apply manual overrides for short menu wording.
UI Dictionary
Store reusable translations for interface phrases such as buttons, labels, headings, and repeated UI text.
Semantic Review
Review recurring phrases and improve consistency across languages, menus, widgets, and interface strings.
Stored UI translations can reduce repeated API usage because known interface strings can be reused instead of translated again.
WooCommerce Translation
REEID Translate Pro supports WooCommerce product translation while preserving product configuration. The goal is to translate language-specific product content without damaging pricing, inventory, relationships, or core product setup.
- Product titles and slugs
- Short and long descriptions
- Product attributes where supported
- SEO fields where supported
- Preserves pricing and stock logic
- Preserves product configuration
- Supports product string reuse in Cloud Assist
- Designed to avoid unnecessary product duplication
SEO and Indexing
REEID is designed to support multilingual SEO while keeping language relationships predictable. It helps translated pages use language-aware URLs, SEO metadata, hreflang relationships, and canonical logic where supported.
- Supports translated slugs, including native-language slugs.
- Can work alongside major SEO plugins such as Yoast and Rank Math.
- Helps avoid duplicate SEO emitters where possible.
- Supports hreflang and canonical relationships for translated content.
- Preserves the original English/root URL structure where configured.
Layout Protection and Contamination Blocking
REEID protects layouts by detecting editor and builder structure before translation. If a page appears to contain mixed editor data, translation may be blocked to avoid damaging the layout.
Why translation may be blocked
- Gutenberg content with stale Elementor metadata
- Elementor content with mixed block markup
- Builder data that does not match the active editor
- Potentially unsafe structure conversion
What to do
- Open the page in the editor originally used to create it.
- Save once, then try translation again.
- For intentionally rebuilt pages, stale builder data may need cleanup.
- Do not force translation if the layout source is unclear.
Typical message: Translation was blocked to protect this layout. No changes were made.
Common Error Messages
- AJAX failed: may indicate timeout, nonce issue, server interruption, or network failure.
- Invalid nonce: refresh the admin page and try again.
- Missing parameters: required language, post ID, or request value was not sent.
- Translation engine not available: translation runtime failed to load or was blocked.
- No enabled languages found: configure target languages in settings.
- Mixed builder blocked: page has conflicting editor data.
- License invalid: check license key and domain activation.
- Limit reached: wait for the usage window to reset or adjust plan/settings.
Performance and Recommended Setup
- Translation work runs in admin workflows; frontend visitors normally see stored translated content.
- Use PHP 8.1 or newer where possible.
- 256MB memory is a minimum practical starting point; 512MB or more is recommended for larger sites.
- Large pages, heavy Elementor layouts, WooCommerce products, and bulk translation may require more memory and execution time.
- Cloud Assist cache reuse can help reduce repeated token usage on unchanged content.
- Keep prompt and glossary guidance stable when testing cache behavior.
Why REEID Translate Pro?
REEID Translate Pro is built for AI-first WordPress translation with structural protection, SEO awareness, builder-specific handling, glossary guidance, Cloud Assist cache reuse, and practical workflows for real websites.