REEID TRANSLATE

— Documentation Hub —

Welcome to the REEID Translate documentation hub.

This guide explains how the plugin works, what makes it different, and how to use its multilingual features safely in production environments.

Tip:

REEID Translate is designed to automate multilingual workflows while preserving editor structure, SEO signals, and WordPress architecture.

The documentation below will help you understand how to use the system effectively.

  Getting Started

How do I translate a post or page?

Open the REEID Translate panel inside the editor, choose your target language, and click Translate.
If a translation already exists, REEID updates it safely instead of creating duplicates.

The plugin automatically detects the correct translation engine for:

• Gutenberg
• Elementor
• Classic Editor
• WooCommerce products

This keeps the workflow simple while the underlying translation logic remains highly specialized.

What gets translated?

• Post titles
• Slugs
• Body content
• Editor blocks
• SEO fields
• WooCommerce product content

The goal is not only linguistic translation, but also structural preservation so the translated version remains visually aligned with the original.

Which editors are supported?

• Gutenberg
• Elementor
• Classic Editor
• WooCommerce

Each editor uses dedicated extraction and reinjection logic, allowing REEID to preserve layout, block structure, metadata, and editor-specific content models safely.

Where are translations stored?

REEID works with native WordPress structures and metadata relationships instead of large shadow systems or fragile duplication layers.
This keeps the architecture cleaner and easier to maintain long-term.

Can I re-translate safely?

Yes. Re-running translation updates the existing translated version while preserving relationships and structure.

How do custom instructions work?

Custom Instructions allow you to guide the translation engine using your own rules.

Examples include:

• Protecting brand names
• Forcing preferred terminology
• Preserving product codes
• Maintaining tone of voice

Instructions can be applied globally or per item.

Why can the first translation take longer?

The first translation performs additional work including:

• Structural analysis
• Content extraction
• Translation generation
• Translation memory updates

Later translations become faster because REEID can reuse existing knowledge.

Why does the translated page keep the same layout?

REEID preserves the original editor structure and translates only the text layer.

This protects design integrity and reduces layout breakage across languages.

How does REEID translate WooCommerce products?

REEID avoids unnecessary product duplication.

Instead, it translates language-specific content while preserving:

• pricing
• inventory
• product configuration
• relationships

Titles, descriptions, attributes, SEO fields, and slugs can be localized independently.

---

Strings Localization

What is Strings Localization?

Strings Localization is REEID’s control center for interface-level translation.

While posts and products translate full content entities, this area handles smaller UI text such as:

• menu labels
• buttons
• widget headings
• navigation text
• interface phrases

This layer is critical for achieving a fully polished multilingual frontend.

Why is Strings Localization important?

A site rarely feels fully multilingual if menus, buttons, and interface elements remain untranslated.

Strings Localization closes this gap and ensures a consistent interface experience.

How is it different from translating posts?

Posts and products represent complete content objects.

Strings Localization focuses on short reusable UI phrases that appear across many parts of the site.

Examples:

• About Us
• Read More
• Add to Cart
• Login

Menu Labels Sub-Tab

This section focuses specifically on navigation labels.

It allows you to:

• review menu labels
• see automatic translations
• apply manual overrides

UI Dictionary Sub-Tab

The UI Dictionary acts as a persistent translation memory for interface strings.

When REEID encounters a new phrase it can:

• normalize the string
• check existing translations
• reuse stored translations instantly

Semantic Review Sub-Tab

Semantic Review provides a quality-control layer above the dictionary.

It helps you:

• review translation consistency
• identify recurring UI phrases
• improve terminology alignment

What does “Load” do?

Load refreshes the current view for the selected language and context.

What does “Auto-fill Missing” do?

This action translates only dictionary entries that do not yet exist for the selected language.

It is ideal for quickly warming up a new language.

What does “Rebuild Semantic Index” do?

This regenerates semantic analysis data for UI strings, helping maintain translation consistency across languages.

Why do some interface labels remain untranslated initially?

Because REEID builds a self-learning UI dictionary.

Once a string is translated and stored, it can be reused automatically.

When should I use overrides?

Use overrides when:

• automatic translation is correct but stylistically weak
• navigation needs shorter wording
• brand terminology must be enforced

Does this reduce API usage?

Yes. Stored translations can be reused without sending repeated requests.

---

SEO & Indexing

Will search engines index translated pages correctly?

Yes. REEID supports multilingual SEO including:

• language-aware URLs
• hreflang relationships
• canonical logic

Is REEID compatible with Yoast and Rank Math?

Yes. The plugin is designed to coexist with major SEO plugins while avoiding duplicate SEO emitters.

Are native slugs preserved?

Yes. REEID supports native-language slugs including Chinese, Thai, Arabic, and Greek.

How are duplicate SEO issues avoided?

REEID isolates multilingual branches and keeps canonical relationships predictable.

---

Common Error Messages

AJAX failed

Usually indicates a nonce mismatch, timeout, or translation engine interruption.

Translation engine not available

The translation engine failed to load or execution was blocked.

Missing parameters

A required field such as language, post ID, or nonce was missing.

---

Performance

Does REEID slow the frontend?

No. Heavy translation work occurs in admin workflows while the frontend uses stored data.

How does bulk translation manage memory?

Bulk translation runs in controlled batches rather than processing everything simultaneously.

Recommended PHP settings

• PHP 8.1+
• 256MB memory minimum
• 512MB recommended for large sites

---

Why REEID Translate?

How is REEID different?

REEID focuses on AI-driven automation, structural integrity, and SEO precision rather than manual multilingual management layers.

The result is a cleaner, scalable translation workflow with fewer operational complexities.

Does REEID replace WPML or Polylang?

REEID represents a different philosophy: automation-first multilingual architecture.

Who is REEID best suited for?

REEID is ideal for site owners, agencies, and teams that want multilingual scale without inheriting heavy editorial overhead.