LocaleReady
Menu

Migration

Leave Weglot without losing the translated site.

Weglot translates on its servers. LocaleReady translates on yours and keeps the result. That is the whole switch.

What transfers

Your WordPress pages, products, and forms stay put. LocaleReady reads the same HTML Weglot was sending out and translates it again.

What does not

Weglot's translation memory, glossary, and dashboard edits stay with Weglot. There is no import file we can pull from their account.

Storage

After the first pass, every string lives in your database. Cancel LocaleReady later and those pages still render. Cancel Weglot and they do not.

The actual steps

  1. Step 1

    Install LocaleReady alongside Weglot

    Leave Weglot running. Install LocaleReady, activate the license, and connect your own DeepL or Google Cloud Translation key.

  2. Step 2

    Turn on the same languages

    Enable the languages you already offer. LocaleReady serves each one from a folder on your existing domain, such as /es/.

  3. Step 3

    Let LocaleReady translate and save

    Visit key pages in each language, or run a pretranslate from Tools. Translations are stored in your WordPress database, not on our servers.

  4. Step 4

    Check shops, forms, and search snippets

    Open cart, checkout, a form confirmation, and a translated page's view-source. Confirm prices stayed intact and hreflang looks right.

  5. Step 5

    Turn Weglot off

    Deactivate the Weglot plugin and remove its JavaScript snippet. LocaleReady already has its own copies, so the translated URLs keep working.

Side-by-side product differences live on theWeglot comparison.

Questions

Can I import my Weglot translations?+

Not automatically. Weglot keeps those strings on its servers. LocaleReady translates your live pages again with your DeepL or Google key and stores the result in WordPress. Hand edits you made in Weglot do not come across.

What happens the moment I disable Weglot?+

Weglot-translated pages disappear, because they were never saved on your site. Disable it only after LocaleReady has stored translations for the pages you care about.

Will my existing /es/ URLs keep working?+

If Weglot used subdirectory URLs, set the same prefixes in LocaleReady. Then the addresses stay familiar. If Weglot used a different pattern, plan redirects before you switch.

Ready to move the translations onto your site?

A yearly license by site count. You pay DeepL or Google directly for the first pass.