TERMINOLOGY CONTROL

Protect the words your brand cannot afford to get wrong.

Use the REEID Translate Pro Glossary to control how brand names, product names, technical terminology, legal wording and preferred translations are handled across supported WordPress content.

See how rules work
View pricing

CONSISTENT TERMINOLOGY

Give the translation workflow explicit instructions for important terms.

Apply terminology rules across Gutenberg, Elementor, WooCommerce and supported Cloud Assist workflows.

  • Protect names
  • Guide preferred wording
  • Target individual languages

Keep as-is

Protect names and terms that must stay unchanged.

Translate as

Force a preferred translation for an important source term.

Per language

Apply terminology globally or only to selected target languages.

WHAT THE GLOSSARY CAN DO

Two rule types cover the most important terminology decisions.

Use Keep as-is when a term must remain unchanged. Use Translate as when a source term must consistently become your preferred target wording.

RULE TYPE 01

Keep as-is

Use this when a word or phrase must remain unchanged in every translation.

Good examples

REEID Translate Pro
WooCommerce
Elementor
Gutenberg
Cloud Assist
BYOK
Classic Editor

Example result

Source:
Translate WordPress pages with Elementor and Gutenberg.

Arabic:
ترجم صفحات WordPress باستخدام Elementor وGutenberg.

The protected terms remain exactly as written.

RULE TYPE 02

Translate as

Use this when a source term must always become a specific target term.

Example rule

Source term:
AI-powered translation plugin

Translate as:
translation plugin for real websites

This tells the translation workflow to use your preferred wording instead of choosing an alternative automatically.

LANGUAGE TARGETING

Apply one rule everywhere—or tailor it by language.

Glossary rules may apply to all languages or to one specific language such as Arabic, Danish or Chinese.

ALL LANGUAGES

Use for universal terminology

Best for brand names, product names and terminology that should behave the same way in every target language.

SPECIFIC LANGUAGE

Use for localized preferences

Best when preferred terminology or wording changes between individual target languages.

RECOMMENDED USE CASES

Use the Glossary where terminology carries business meaning.

The strongest use cases are names, short technical terms, product phrases, legal wording and industry-specific terminology.

Protect names

  • Brand names
  • Product names
  • Plugin names
  • Feature names

Control terminology

  • Technical terms
  • Legal terms
  • Compliance wording
  • Industry-specific language

Guide wording

  • Preferred translations
  • Short marketing phrases
  • Words that must remain untranslated
  • Required target wording

BEST PRACTICES

Short, exact rules usually produce better results.

Shorter glossary entries are easier to match and generally interfere less with natural sentence construction.

BETTER

Elementor
Gutenberg
Cloud Assist
BYOK
WooCommerce

AVOID WHEN POSSIBLE

Very long sentence fragments
Phrases crossing formatting tags
Whole paragraphs as glossary terms

Protecting a long phrase may leave that entire phrase untranslated.

This is correct Keep as-is behavior, but it may not read naturally inside otherwise translated content.

Keep as-is:
Translate WordPress pages, posts, WooCommerce products,
Elementor layouts, Gutenberg content

IMPORTANT LIMITATION

Glossary matching is text-based.

For the strongest match, the source phrase should not cross HTML or formatting boundaries.

STORED CONTENT

<strong>REEID Translate Pro</strong>
is an AI-powered WordPress translation plugin

VISUALLY DISPLAYED

REEID Translate Pro is an AI-powered
WordPress translation plugin

The visible sentence looks continuous, but internally the formatting splits it. A rule for the complete sentence may therefore fail to match.

BETTER RULE

Translate as:
is an AI-powered WordPress translation plugin
→ translation plugin for real websites

OR PROTECT THE NAME ONLY

Keep as-is:
REEID Translate Pro

PRACTICAL WORKFLOW

Add terminology rules before translating.

  • Add glossary rows before starting translation.
  • Use Keep as-is for names and technical terms.
  • Use Translate as for preferred wording.
  • Keep rules short and specific.
  • Translate the page, post, Elementor layout or WooCommerce product.
  • Review the translated output in context.
  • Clear Cloud Assist cache and retranslate if old wording remains.

WHEN TO CLEAR CACHE

Changed a glossary rule but still see the old wording?

Cloud Assist may reuse a previous translation. Clear the relevant page or product cache, then translate again so the updated terminology rule can be applied.

CURRENT GLOSSARY BEHAVIOR

Terminology enforcement across supported workflows.

The Glossary is designed as a practical terminology control layer. It is not a complete CAT-tool termbase or translation-memory system with style-preserving segment locks.

Currently supported

  • Gutenberg pages and posts
  • Elementor pages
  • WooCommerce inline product translations
  • Cloud Assist translations
  • Cached Cloud Assist translations

TERMINOLOGY CONSISTENCY

Make important terminology predictable across your multilingual site.

Protect names, define preferred wording, target rules by language and review the final translated output without losing control of essential terminology.

View pricing
Explore features
Shopping Cart
Scroll to Top