REEID Translation (Universal)

Quick User Manual

1. Plugin Setup

  • Activate the plugin in your WordPress dashboard.
  • Go to Settings → REEID Translate to configure:
    • OpenAI API Key (required)
    • Default Source Language (your site’s main language)
    • Tone / Style (set the default writing style, optional)
    • Bulk Translation Languages (choose available languages for bulk translation)
    • OpenAI Model (select your preferred AI model; GPT-4o is recommended)
    • License Key (if using PRO)

2. Translating a Single Post or Page

  • Edit any post or page in the WP admin.
  • Find the REEID Translation meta box (sidebar or below content).
  • Select target language with the picker.
  • Optionally set:
    • Tone override
    • Prompt override (custom translation instructions)
    • Publish mode (publish or save as draft)
  • Click Translate.

The plugin will:

  • Generate a translated copy (SEO title, slug, all content)
  • Assign the correct language
  • Link the translation to the original post (no duplicate mapping by slug)

3. Bulk Translation

  • Set your bulk languages in plugin settings.
  • Open any post/page, use the meta box, click Bulk Translation.
  • Translations for all selected languages are generated and linked.

4. SEO, Canonical, and Slugs

  • The plugin auto-creates unique SEO slugs per language:
    • Default language: /your-page-slug/
    • Other languages: /fr/votre-slug-de-page/, /de/ihr-seiten-slug/, etc.
  • Menus and switcher always use proper /lang/slug/ URLs for translated pages.
  • Canonical URLs and <html lang=""> tags are output correctly for all languages, for perfect SEO and indexing.

5. Menus & Language Switcher

  • Use
      shortcode anywhere for a dropdown/flags switcher.
    • Menus automatically show only items for the current language, and all menu links use the correct /xx/slug/ format for translated pages.

    6. Changing Default Language

    • Change the Default Source Language in plugin settings.
    • The root URL / always serves the default language; all other languages have their own /xx/slug/ structure.

    7. Elementor & Gutenberg Compatibility

    • Elementor and Gutenberg blocks are fully supported.
      • All user-visible text is translated, but design/layout, images, widths, and technical settings are preserved.
      • Use the REEID meta box in the standard WP editor (not Elementor’s front-end editor) to translate.
    • The plugin:
      • Extracts only user-visible content for translation
      • Automatically re-injects translations into the correct places
      • Never alters layouts, images, paddings, columns, or technical/design controls
    • If you want to further tweak layout/design, do so after translation on the translated page.

    8. Best Practices

    • Always translate via the REEID meta box (never copy/duplicate manually).
    • Never edit translated slugs/titles by hand unless you want to override AI output.
    • For Elementor, if any text isn’t translated, it may be from a custom widget or hardcoded—edit manually as needed.
    • To customize translation behavior, use the Prompt override field.

    9. Troubleshooting

    • Nothing happens? Check your OpenAI API key and license.
    • Missing translation options? Ensure the post is published.
    • Duplicate pages? Each translation is mapped by ID to avoid duplication.
    • Menus/switcher missing links? Flush permalinks and save your menus.
    • Elementor layout issues? All technical/design fields are skipped—set image sizes using Elementor’s controls, not in the text.

    10. Support

    Summary for Elementor/Gutenberg

    SEO, menus, URLs, canonical, and hreflang: all correct.

    Translate in the WP backend (REEID meta box).

    All user-visible strings: translated.

    All design/layout: preserved.

    Scroll to Top