Website & Development
Weglot vs WPML (and TranslatePress, Polylang): comparison and switching on WordPress without losing rankings
Copy for AI
Weglot vs WPML is a choice between renting translations and owning them.
Weglot is a translation platform that runs outside WordPress and keeps your translations with it. WPML is a plugin that stores them in your own WordPress database.
The verdict: Weglot wins on speed of setup. WPML, TranslatePress and Polylang win on ownership, URL control and a licence instead of a price per word.
TranslatePress and Polylang sit in the plugin camp too, but each works in its own way.
Below, we compare the four fairly. Then we show step by step how to move from Weglot to a plugin without losing rankings.
Also weighing other platforms or SaaS tools? Read our broader comparison of Weglot alternatives.
The general plan for any tool and any CMS is in our guide on how to leave a translation tool without losing SEO.
How do Weglot, WPML, TranslatePress and Polylang differ?
They differ most in where your translations live, and in what happens when you stop paying.
Here are the four side by side:
| Weglot | WPML | TranslatePress | Polylang | |
|---|---|---|---|---|
| Type | Translation platform (proxy and JavaScript) with a WordPress plugin | WordPress plugin | WordPress plugin | WordPress plugin |
| Where do translations live? | At Weglot, not in your CMS | In your WordPress database, as separate pages per language | In your WordPress database, as translated strings | In your WordPress database, as separate pages per language |
| URL per language | Subdirectory or subdomain | Directory, (sub)domain or parameter | One directory per language | Directory, subdomain or domain |
| Translated slugs | From Pro | Yes | Yes (paid version) | In Polylang Pro |
| Automatic translation | Included, within your word limit | AI words included from Multilingual CMS | AI words included per plan | Through a translation service or separate integration |
| Export of translations | From Advanced (CSV or XLIFF) | XLIFF | Translations are already in your database | XLIFF in Polylang Pro |
| Price model | Subscription by words and languages | Annual licence by number of sites | Annual licence by number of sites | Free base, Pro as annual licence |
| When you stop paying | Translated pages are progressively removed from Google | Keeps working, no updates | Translations keep working | Keeps working, no updates or support |
Sources: Weglot pricing, Weglot features, Weglot on cancelling, WPML plans, TranslatePress pricing and Polylang pricing, rechecked 5 November 2026.
Also used, checked 7 October 2026: WPML URL formats, TranslatePress settings and Polylang URLs.
The amounts per plan are in our article on Weglot pricing.
Weglot: fast and fully automatic, but rented
You install Weglot in an afternoon. That’s its appeal.
Weglot’s own FAQ says your translations are “stored by Weglot, accessible through your Weglot Dashboard, and not in your CMS”.
That’s the strength and the weakness at once. You build nothing in WordPress. But you own nothing either.
What Weglot does well for SEO, and where its translation quality falls short, is in our Weglot review.
WPML: the most complete, with the steepest learning curve
WPML creates a separate version of every page, post and product per language.
It adds string translation for themes, menus and forms. It works with most page builders, and with WooCommerce from the Multilingual CMS plan up.
URL options: per site, you choose directories, a domain or subdomain per language, or a parameter. You can even put your main language in a directory.
That makes WPML the most flexible choice for rebuilding an existing Weglot URL structure exactly.
Price: Multilingual CMS costs 99 euros a year for 3 sites, with 22,500 words of AI translation (WPML, checked 5 November 2026).
TranslatePress: closest to the way Weglot works
TranslatePress translates the page as it’s displayed, with a visual editor on the page itself.
If you’re used to Weglot’s visual editor, you’ll feel at home quickly.
The difference: translations live in your WordPress database. The pricing page says they keep working when your licence expires.
Languages sit in one directory per language, and you set the language slug in the URL yourself.
Price: Personal costs 99 euros a year for 1 site, with 50,000 AI-translated words (TranslatePress, checked 5 November 2026).
Polylang: light and free to start
Polylang, like WPML, creates separate translated posts per language.
The free plugin on wordpress.org is enough for many sites. Polylang Pro adds translated slugs and XLIFF import and export.
Main language: Polylang’s documentation says you can hide your main language code. Your existing Dutch URLs then stay unchanged.
Price: Polylang Pro costs 99 euros a year excluding VAT, with a 50% renewal discount (Polylang, checked 5 November 2026).
All three plugins run on the same platform:
WordPress.org, October 2026. In the Weglot vs WPML choice, the plugin side keeps translations in this CMS’s own database.
Which one should you pick when leaving Weglot?
Pick by the kind of site you run, then check it against your URL structure.
Here’s the rule of thumb from our projects in one picture:
Why each one fits
- Online shop, many languages or a complex page builder: WPML covers WooCommerce, strings and page builders most broadly.
- You want to work the way you did in Weglot: TranslatePress’s visual editor and string model are closest.
- Simple site, small budget, technical team: Polylang’s free version covers a lot and stays light.
Every plugin adds weight, so keep the rest of your stack lean. Our piece on too many WordPress plugins shows where that tips.
Let the URL structure decide the tie
Pick the plugin based on your URL structure in Weglot.
For example, say Weglot ran on subdomains (fr.example.com) and you want to keep them. Then a plugin without subdomain support is out.
The other route is a deliberate move to directories, with 301s. Our guide to subdomain vs subdirectory SEO weighs both.
Rule of thumb: every URL you keep is a URL you don’t have to redirect.
Switching from Weglot to a WordPress plugin in eight steps
Map every old URL, keep it or redirect it, and keep hreflang correct.
That principle comes from Google’s guide to a site move with URL changes. It’s the order we follow ourselves.
1. Inventory every translated URL
Crawl your site per language, and export the indexed URLs per language from Google Search Console.
Note the structure for each language:
- subdirectory (
/fr/) or subdomain - translated slugs or not
- which pages bring in traffic and leads
This list is your checklist for the whole switch.
2. Export your translations from Weglot
Weglot exports translations as CSV or XLIFF per language pair, according to the Weglot Academy.
Export comes with the plans from Advanced, according to the pricing page.
You get translation pairs, the original sentence and its translation. You don’t get WordPress pages.
Keep the export. You’ll need it even if you rewrite your most important pages.
3. Install the plugin on a staging environment
Build the new language versions on a copy of your site. Never on the live site.
Why: as long as Weglot runs live, it serves your translated directories. A second translation plugin on the same site clashes with it.
4. Rebuild the languages with the same URL structure
Set exactly the same language codes in the plugin as in Weglot, such as /fr/ and /en/.
Use the same place for your main language too, usually without a directory.
If you had translated slugs in Weglot, create the same slugs in the plugin. Our guide to the URL slug explains why they matter per language.
5. Put the translations into the plugin
Create the translated version of each page, with the Weglot export as the source.
With WPML and Polylang, these are separate translated pages. With TranslatePress, they’re translated strings.
Don’t forget the parts outside the pages, such as:
- menus, forms, buttons and footer
- SEO titles and meta descriptions per language
- image alt text
This is also the moment to have your lead pages checked by a native speaker.
Our experience: translation tools often pick the wrong keyword. For Suivo, Weglot wrote “tijdsregistratie” while Belgian searchers type “tijdregistratie”, as in our Suivo go-to-market case.
6. Put a 301 on every URL that changes
Compare the URL list from step 1 with the new site.
Every old URL that no longer exists gets a permanent server-side redirect to the new version in the same language.
Google recommends permanent server-side redirects, and JavaScript redirects only when nothing else is possible.
Subdomains: if you moved from subdomains to directories, redirect every subdomain URL. Also update the DNS records that pointed to Weglot.
Our 301 redirect plan shows how to build the mapping. The free redirect checker tests each URL afterwards.
7. Check hreflang, canonicals and the sitemap
Every language version must list itself and all other versions in hreflang.
If two pages don’t point to each other, Google ignores the tags. The documentation on localized versions explains this.
Give every page a canonical to itself in its own language, not to the Dutch version.
After going live, test with our hreflang checker. It also shows whether Weglot traces are still active.
How the tags work is in our explainer on hreflang. The usual mistakes are in fixing hreflang errors.
8. Switch over, remove Weglot and measure
Put the new site live, then clean up:
- deactivate and remove the Weglot plugin
- remove Weglot scripts and language switchers from your theme
- submit your new sitemap in Search Console
Follow indexing and positions per language for several weeks. Google says to expect temporary ranking fluctuations while it recrawls.
Only then do you cancel your Weglot subscription, with your export safely stored.
How cancelling works exactly is in our guide on exporting your Weglot translations.
The wider checklist for any move is in our WordPress migration guide.
When are you better off staying on Weglot?
When your site is small, has one extra language and won’t grow.
Then the smallest Weglot plan is cheaper. A migration costs more work than it saves.
Stay if:
- you don’t need translated URLs
- you have no plans for more languages
- nobody can manage a WordPress plugin for you
Without technical help, Weglot can be the calmest choice.
The maths tips when your site grows, opens a third language or you want to own your translations. We work that out in what Weglot really costs.
Frequently asked questions about Weglot vs WPML
Is WPML better than Weglot for SEO?
Both can deliver an SEO-correct multilingual site with its own URL per language and hreflang. The difference is control: with WPML you manage titles, slugs, canonicals and the URL structure yourself in WordPress, and your translations stay in place if you stop paying. With Weglot, translated slugs only come with Pro and the translated pages disappear when you cancel.
Can I import a Weglot export straight into WPML?
Not as ready-made pages. WPML works with XLIFF files it creates itself for its translation jobs. The Weglot export contains translation pairs per language, which you use as the source to build the translated pages and strings, by hand, with a script or with an AI agent that writes into your CMS.
Is TranslatePress a good alternative to Weglot?
Yes, for anyone who likes the way Weglot works. TranslatePress has a comparable visual editor, but stores the translations in your own WordPress database and, according to the vendor, keeps working when your licence expires.
How long does a switch from Weglot to WPML take?
That depends on the number of pages and languages, your page builder, the URL structure (directories or subdomains) and whether you have an export. Plan for a project with a staging phase, a switchover moment and several weeks of follow-up in Search Console.
Have the switch done for you
Want to move from Weglot to WPML, TranslatePress or Polylang without putting rankings at risk?
Our translation tool migration rebuilds every language version in WordPress, with the same URLs or a complete redirect plan.
We check hreflang and canonicals before and after the switch.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.