Migrating from Another Plugin

Switching to Omnalingo is straightforward, with one thing to know up front: Omnalingo generates fresh translations rather than importing your old plugin’s database.

Why a fresh start is recommended

Other plugins store translations in incompatible formats, and those translations were made from a snapshot of your content at the time. Importing them risks carrying over stale text — wording that has since changed — or translations made with different context. A fresh scan reflects what your site actually says today, and with AI translation you get a complete first pass quickly, ready to refine in the Visual Editor.

There’s no automated import, but you can migrate by hand if you prefer — paste your existing translation into each text block in the Visual Editor. For most sites AI is faster, unless you put significant effort into your previous translations and want to carry them over exactly.

Step by step

1. Install and activate Omnalingo. It’s fine to leave your old plugin active during the switch — it keeps serving its translations while you set up.

2. Add your languages. Under Settings → General → Language Settings, add the same languages you had before, and pick your content types under Sitemap Content Settings.

3. Connect your key under Settings → License.

4. Translate. Turn on Auto Translate (per page, or Enable Auto translate for all) to generate translations across the site, or work page by page in the Visual Editor.

5. Review the important pages — homepage, key landing pages, product descriptions — in the Visual Editor.

6. Deactivate your old plugin (don’t delete it yet) and check your translated pages in a browser.

7. Clear your cache so visitors get the new translations.

Tip

Running both plugins at once causes no conflict — once Omnalingo is serving the frontend, the old plugin’s output simply isn’t shown, but its data stays available for reference until you remove it.

Per-plugin notes

WPML and Polylang

Both create real duplicate WordPress posts for each translated language. Omnalingo uses virtual prefixed URLs instead, so it never duplicates posts. After deactivating WPML or Polylang, delete the duplicate translated posts they created to avoid duplicate-content issues in search engines (WPML also has its own cleanup tool). Their URL structure (/de/about/) is similar to Omnalingo’s, so existing links keep resolving.

TranslatePress

Uses URL-prefix switching much like Omnalingo (/de/about/). After switching, confirm your language URLs resolve and update any hardcoded internal links. Omnalingo outputs hreflang automatically once your languages are set.

Weglot

Serves translations through a proxy/CDN, so its translated URLs stop working once you remove its DNS/configuration. Before switching, update internal links that point to Weglot-style URLs and consider redirects from any external backlinks to the new Omnalingo URLs. Clear your CDN cache afterward.