REEID Translate FAQ & Operational Guide

Open the REEID Translate panel inside the editor, choose the target language, and click Translate. If a translation already exists, REEID updates the existing translation safely instead of creating unnecessary duplicates. The plugin automatically detects the correct workflow for Gutenberg, Elementor, Classic Editor, and WooCommerce products.

REEID can translate titles, slugs, body content, supported Gutenberg blocks, Elementor layouts, Classic Editor content, SEO fields, navigation menu labels, reusable UI strings, and WooCommerce product content. The goal is not only language translation, but also preserving structure, layout, metadata, and multilingual relationships.

REEID supports Gutenberg, Elementor, Classic Editor, and WooCommerce product workflows. Each editor uses dedicated extraction and reinjection logic so translated content stays aligned with the original structure. This is safer than treating every page as plain text.

No. REEID is designed to detect existing translations and update them when possible. Translation relationship metadata keeps the source item and its translated versions connected, which helps the language switcher, admin tools, SEO output, and repair tools work correctly.

Yes. AI translation can save a large amount of time, but final review is still recommended for brand tone, legal wording, product details, and SEO-sensitive pages. REEID helps automate the translation workflow, but editorial approval remains important for production websites.

Local BYOK means Bring Your Own Key. Your OpenAI API key is stored and used on your own WordPress site. Translation requests are sent directly from your site to OpenAI. This mode gives the site owner direct control over API usage and billing.

Cloud Assist uses REEID server-side assistance for selected translation workflows, caching, and protected logic. Depending on the selected configuration and consent settings, Cloud Assist may use api.reeid.com to process or cache translation-related data. It is designed to improve advanced workflows while keeping the WordPress interface simple.

In Local BYOK mode, the user OpenAI API key is intended to stay on the WordPress site. Cloud Assist behavior depends on the enabled mode and consent settings. Use Local BYOK when you want the strictest separation between your API key and REEID cloud services.

Some Pro features may use api.reeid.com for protected logic, Cloud Assist transport, sealed builder rules, cache support, or advanced WooCommerce and Elementor workflows. These calls are separate from normal WordPress page rendering and are used only where the related feature requires them.

The Glossary helps REEID keep important words, brand names, product names, technical terms, and preferred phrases consistent across translations. It gives the translation engine terminology guidance so repeated terms are handled more predictably.

Use the Glossary when certain words should stay unchanged, follow a preferred translation, or avoid being translated literally. Common examples include brand names, service names, product names, legal phrases, industry terminology, acronyms, and words that should remain in English.

Yes. If a brand name, product name, company name, or trademark should not be translated, add it to the Glossary with clear instructions. This helps prevent unwanted translation or rewriting of important names.

The Glossary is used as translation guidance where supported by the selected workflow. Its effect depends on the content type, translation mode, and how the translation request is built. Treat it as strong guidance, not as a guaranteed replacement for final editorial review.

Keep entries short, specific, and unambiguous. For example: “Do not translate REEID”, “Keep WooCommerce unchanged”, or “Translate checkout as pago in Spanish”. Avoid long paragraphs inside a single glossary rule.

No. The Glossary improves consistency, but translated content should still be reviewed, especially for legal pages, checkout text, product claims, medical or financial wording, and SEO-sensitive landing pages.

In Local BYOK mode, translation usage is billed directly by the AI provider connected to your own API key. REEID does not control the provider’s pricing, billing rules, token accounting, or account limits.

Cost depends on the amount of source content, page structure, number of target languages, glossary or prompt context, editor type, and how much structure-preservation data must be sent with the translation request. A simple text page usually costs less than a large Elementor, Gutenberg, or WooCommerce page with many fields.

Prompt tokens include source content, translation instructions, glossary rules, structural context, formatting rules, and safety instructions. Completion tokens are only the translated output. For structured WordPress content, prompt tokens can be higher than completion tokens because REEID must preserve layout and metadata context.

Yes. Bulk translation can multiply usage quickly because each selected language may require its own translation work. Translating one page into ten languages can consume much more than translating the same page into one language.

Cache reuse can reduce repeated work in supported workflows, especially when the same strings or translation payloads are reused. However, cache behavior depends on content type, translation mode, exact source text, language, chunking, and whether the cached data still matches the current request.

A small visible edit may change the underlying payload, block structure, chunk, context, or cache key. When that happens, the translation engine may need to reprocess part of the content to preserve layout and consistency.

Translate only the languages you need, review bulk language selections before running them, avoid repeated unnecessary retranslations, use the Glossary for predictable terminology, test large pages on one language first, and monitor usage in your AI provider dashboard. Use Cloud Assist mode where available so REEID can reuse previously translated segments.

No exact pre-translation cost can be guaranteed because final token usage depends on the translation provider, content structure, request context, and generated output. REEID can help make usage more understandable, but the AI provider remains the source of truth for billing.

REEID uses an inline WooCommerce translation strategy. Instead of creating separate product posts for every language, translated product fields can be stored as per-language WooCommerce translation packets. This helps preserve product IDs, prices, stock, variations, product type, and WooCommerce relationships.

REEID can translate product titles, slugs, short descriptions, long descriptions, supported SEO fields, and supported product attributes. Core commercial data such as price, stock, SKU, product type, tax settings, and checkout behavior should remain controlled by WooCommerce.

Translation Map Repair is mainly for standard post and page translation relationship metadata. WooCommerce inline translations use separate WooCommerce metadata, such as per-language product translation packets and localized slugs. WooCommerce repair and cleanup should be handled through WooCommerce-specific logic rather than the standard post/page map repair tool.

Products have prices, stock, checkout behavior, variations, attributes, and order relationships. Creating separate product posts for every language can cause unnecessary complexity. REEID therefore uses a controlled WooCommerce-specific strategy to keep commercial product data stable while displaying translated frontend content.

Strings Localization is the area used to manage smaller reusable interface texts, especially menu labels and UI-level phrases. It is separate from full page, post, Elementor, Gutenberg, Classic Editor, or WooCommerce product translation.

The Menu Labels sub-tab focuses on navigation text. It lets you review menu item labels, see automatic translations, and apply manual overrides when a menu label needs shorter, clearer, or more brand-aware wording than a generic translation.

The UI Dictionary is a persistent translation memory for reusable interface strings. When REEID encounters a known UI phrase, it can reuse the stored translation instantly instead of translating the same short label again. This improves consistency and can reduce repeated translation work.

The UI Dictionary is intended for menu labels and registered UI phrases handled by REEID. It is not the main page or post translation engine, and it does not globally scan every WordPress, theme, or plugin gettext string by default. Its scope is intentionally narrower and safer.

The UI Translation Scanner scans navigation menu labels and prepares their translations in advance. This helps visitors see translated menu labels without waiting for runtime translation. It does not scan every frontend button, widget, theme string, or plugin string.

Semantic Review is a quality-control layer above the UI Dictionary. It helps review reusable interface translations, recurring phrases, and consistency across languages. It is useful for improving short labels and repeated UI wording, but it does not rewrite full page or product content.

Rebuild the Semantic Index after adding many new UI Dictionary entries, changing menu labels, refining terminology, or updating multiple language overrides. Rebuilding refreshes the review layer from the current dictionary data.

Manual overrides let you replace an automatically generated UI translation with your preferred wording. This is especially useful for navigation labels, short calls to action, brand terms, or wording that should be shorter than a literal translation.

Yes. REEID supports multilingual URLs and translated slugs. Depending on the content type and workflow, translated slugs may be stored in standard post data or in WooCommerce-specific translation metadata.

REEID can generate hreflang output for translated content so search engines can understand language relationships between source and translated URLs. Correct translation relationships are important for accurate hreflang output.

REEID Pages Sitemap is a dedicated sitemap feature for translated page URLs. It helps expose translated page URLs to search engines when the site owner chooses to enable it. It is designed to work alongside common SEO plugin workflows without taking over all SEO plugin behavior.

It is disabled by default intentionally. This avoids exposing translated URLs before the site owner has reviewed them. Enable it when translated pages are ready for indexing.

This option adds REEID sitemap references to robots.txt so search engines can discover them more easily. It is disabled by default because not every site wants extra sitemap URLs exposed automatically.

Enable sitemap exposure only after checking that translated URLs are correct, published, and ready for search engines. For staging sites, test sites, or unfinished translations, it is safer to leave sitemap exposure disabled.

No. REEID is not intended to replace a full SEO plugin. Its SEO features focus on multilingual translation support, translated URLs, hreflang, and REEID-specific sitemap discovery. You can still use a dedicated SEO plugin for titles, schema, indexing controls, and broader SEO management.

Translation Map Repair rebuilds REEID relationship metadata for translated posts and pages. It repairs the connection between a source item and its translated versions so the language switcher, admin translation links, hreflang output, and related tools can correctly identify translation groups.

The repair tool focuses on standard REEID translation relationship metadata such as _reeid_translation_map and _reeid_translation_source. These values are used to connect source posts and pages with their translated versions.

No. It does not translate, rewrite, or regenerate content. It only repairs relationship metadata so existing translations can be connected correctly.

No. The standard map repair tool works from local WordPress post metadata and does not need to call the translation API. It is a local repair tool for translation relationships.

Purge All REEID Caches clears REEID-generated temporary cache data such as local translation/runtime caches and sitemap cache data. If Cloud Assist is active, it may also trigger Cloud Assist cache purge logic.

No. It should not delete translated posts, translated products, plugin settings, translation maps, UI Dictionary entries, or manual overrides. It is intended to clear temporary cache data only.

The main risk is performance and cost, not data loss. After cache purge, future translations, previews, sitemap generation, or Cloud Assist workflows may need to rebuild cached data. This can make the next operation slower and may increase API usage until caches are rebuilt.

Use cache purge after major translation changes, URL or slug corrections, sitemap troubleshooting, stale frontend output, or when testing Cloud Assist cache behavior. Avoid purging repeatedly on a live site unless you are actively troubleshooting.

This usually means the translation request did not include required data such as post ID, target language, nonce, mode, or editor context. Refresh the editor, confirm the REEID panel loaded correctly, and try again. If the issue continues, check for JavaScript errors or conflicting admin scripts.

AJAX failed means the browser request to WordPress did not complete successfully. Possible causes include nonce mismatch, server timeout, PHP fatal error, security plugin blocking, memory exhaustion, or a network interruption. Check the browser console, WordPress debug log, and server error log.

This means the expected translation function or runtime was not available when the request ran. It may happen if required plugin files were not loaded, the selected mode is misconfigured, or another error stopped the translation engine from initializing.

First check whether the active theme menu location is assigned correctly. Some themes fall back to a page list when no menu is assigned. If the menu is assigned correctly, scan or rebuild the Menu UI Dictionary and check the Menu Labels overrides.

The switcher depends on translation relationships and available translated content. If a language is missing, confirm that the translated item exists, is published if needed, and is connected to the source item through the translation map.

A 404 can happen when permalink rules are stale, a translated slug is missing, translation metadata is incomplete, or a product/page URL was changed after translation. Save permalinks, verify the translated slug, and use Translation Map Repair when relationship metadata looks broken.

Large Gutenberg pages, Elementor layouts, long product descriptions, and multi-language bulk operations can require many extracted strings and multiple API calls. REEID prioritizes structure preservation, which can take longer than plain-text translation.

Prompt tokens include source content, instructions, formatting rules, context, glossary or terminology guidance, and structure-preservation data. Completion tokens are only the generated translation output. For structured content, prompt tokens are often higher than completion tokens.

Yes. REEID uses cache layers for selected translation/runtime operations, UI strings, WooCommerce runtime data, sitemap output, and Cloud Assist workflows where enabled. Cache reuse can improve speed and reduce repeated work.

Small edits can change the surrounding extraction payload, chunk structure, or cache key. Some workflows may still need to reprocess a chunk to preserve layout and consistency. Cache behavior depends on the mode, content type, and exact data being sent for translation.

Translate in smaller batches, avoid running many large pages at the same time, use reliable hosting resources, and review server memory/time limits. For very large sites, staged translation and careful testing are safer than translating everything at once.

REEID is designed to preserve the original source content and create or update translated versions separately, depending on the workflow. WooCommerce inline translation stores translated product display data separately from core commercial product settings.

Yes. Always keep a recent database and file backup before large translation batches, major slug changes, WooCommerce translation work, or cache cleanup on production sites.

Any content sent to an AI translation provider or Cloud Assist transport should be treated as shared with that service for processing. Do not translate confidential drafts, private customer data, personal data, or sensitive business material unless your workflow and provider terms allow it.

Use a dedicated API key for your website when possible. Monitor usage from the provider dashboard, keep the key private, and replace it if you suspect exposure. Do not paste API keys into public support tickets or screenshots.

Not necessarily. Short helper text is best for settings that affect behavior immediately, such as translation mode, source language, sitemap exposure, cache purge, and repair tools. Longer explanations belong in the FAQ so the settings screen stays clean.

The most important settings to explain are Local BYOK versus Cloud Assist, source language, enabled target languages, sitemap exposure, cache purge, Translation Map Repair, UI Dictionary, and Semantic Review. These are the settings most likely to be misunderstood.

Choose the language used by your original content. REEID uses the source language to understand translation direction, URL behavior, switcher relationships, and language-specific processing.

Only enable languages you intend to use and review. Enabling many languages can increase translation time, API usage, UI dictionary size, sitemap output, and maintenance work.

REEID is built for WordPress structure, not just plain text. It detects editors, preserves layouts, manages multilingual URLs, stores translation relationships, supports WooCommerce-specific workflows, and provides tools for UI strings, SEO, cache, and repair operations.

REEID is best suited for WordPress site owners, WooCommerce stores, agencies, freelancers, SEO teams, and multilingual website managers who want AI-assisted translation without rebuilding their site in a separate translation interface.

REEID automates much of the translation workflow, but it is not a replacement for human review. The strongest workflow is AI-assisted translation followed by quick editorial review for tone, terminology, legal wording, and SEO-sensitive pages.