Best WordPress Multilingual Plugins
Your Dutch pages are live, but the menu is still in English, the contact form replies in English, and Google keeps showing the English page to people in Amsterdam.
For most small sites, the best WordPress multilingual plugin is free Polylang, if you write the translations yourself. TranslatePress fits when you want to translate on the live page with AI words. WPML suits a store or a page-builder site, and Weglot fits when you’d rather pay a subscription and have the whole site translated for you.
Here’s how I’d pick a second language you can manage and still afford after the first year, with a done-for-you path if you’d rather hand it over.
Quick answer: the best WordPress multilingual plugins
| Plugin | Best for | Free version | Paid from (first year) | Renews at | Machine translation | Catch |
|---|---|---|---|---|---|---|
| Polylang | a site you translate yourself | yes: pages, posts, menus, language URLs, hreflang | €99/yr, 1 site (Pro); store add-on €99/yr | currently 50% of the new licence price | DeepL in Pro, your own DeepL account | a store needs the add-on |
| TranslatePress | translating on the page with AI words | yes: 1 extra language, 2,000 AI words, no translated slugs or meta | €99/yr, 1 site, 50,000 AI words | no discount listed; auto-renews yearly | included words, counted per language | words run out faster than you expect |
| WPML | a store or page-builder site | no | €39/yr Blog (pages and posts only); €99/yr CMS, 3 sites, 22,500 AI words | shown in your account | 22,500 words with CMS, more pay-as-you-go | no free version to test |
| Weglot | the whole site translated for you | 2,000 words, 1 language | €150/yr (10,000 words, 1 language); €290/yr (50,000 words, 3 languages) | the plan’s current price | the whole site, automatically | translated slugs need Pro (€790/yr); translations live on Weglot’s servers |
Prices at the time of writing; all four vendors bill in euros. “Shown in your account” means the renewal price isn’t published.
Three of the four keep the translations in your own WordPress database; Weglot keeps them on its servers and bills for the total translated words every year. Polylang free already gives each translation its own slug; TranslatePress needs its paid SEO Pack and Weglot its Pro plan for that.
Do you need a translation plugin at all?
For one or two translated pages, say a Dutch pricing page, create normal pages and link from the English ones. No plugin needed.
GTranslate’s free widget translates text in the visitor’s browser. The address doesn’t change, so the translated version isn’t indexed. WordPress multisite gives each language a separate site to update.
Google’s guidance is the useful test: each language gets its own address, and visitors aren’t redirected by location or browser language. Choose a plugin that does that on five points:
- Who translates Choose your own writing, a translator or machine drafts you review; this decides whether word allowances matter.
- Where translations live Your WordPress database keeps them for good; a hosted service serves them only while your plan covers them.
- What the free version leaves out Check translated slugs, titles and descriptions, extra languages, and theme and plugin strings.
- Compatibility with your site Test your builder, forms and, on a store, products, checkout and order emails on staging before buying.
- Price at renewal and per word AI words and hosted services count every language separately.
Polylang: best free option if you translate the pages yourself
With Polylang, you write translations of pages, posts, categories and menus inside WordPress, each with its own address.
What stands out
- Each language gets its own address as a subdirectory, a subdomain or a separate domain, with hreflang tags added for you.
- The free version translates posts, pages, media, categories, tags and custom post types.
- Pro adds DeepL machine translation through your own DeepL account, translated URL bases for categories and custom post types, and copying content between translations.
I run this site on Polylang, so the free version is the one I know best.
The minus
- No machine translation in the free version; you write or paste every translation.
- A store needs Polylang for WooCommerce (€99 a year), and Pro’s DeepL skips Elementor, Divi and Site Editor content and works one item at a time.
Price: free on wordpress.org. Pro from €99 a year (ex VAT) for 1 site, Polylang for WooCommerce from €99, both as the Business Pack at €139. Renewal is currently 50% of the new licence price; an unrenewed licence keeps working without updates or support. Refund within 30 days of purchase if the plugin doesn’t work and support can’t fix it; not for upgrades or renewals.
On wordpress.org: 900,000+ active installs, updated October 21, rated 4.7 out of 5.
Not for: a site you want translated automatically.
TranslatePress: best for translating on the page with AI words
With TranslatePress, click text on the live page and type a translation or use AI. Translations stay in your WordPress database.
What stands out
- You translate what you see, including theme text, menus and most plugins.
- Paid plans include AI words (50,000 on Personal) and the SEO Pack for translated slugs, titles and descriptions; Business adds DeepL, translator accounts and a separate domain per language.
- The free version can use your own Google Translate key instead, billed by Google.
The minus
- Words are counted per language: a 15,000-word site into two languages uses 30,000 words, and the free 2,000 cover a few pages.
- Free means one extra language and no translated slugs or meta descriptions.
One owner on Reddit found formatted paragraphs split into pieces to translate one by one.
Price: free on wordpress.org. Personal €99 a year for 1 site with 50,000 AI words; Business €199 for 3 sites and 200,000 words; Developer €349 for unlimited sites and 500,000 words. Plans auto-renew yearly with no renewal discount listed, so check the price in your account; each renewal brings the words again. An expired licence keeps the plugin and your translations working as configured, but updates, support and AI words stop. Refund within 15 calendar days of the original purchase, after a support ticket; used AI word packs aren’t refunded.
On wordpress.org: 400,000+ active installs, updated October 13, rated 4.7 out of 5.
Not for: hundreds of pages in several languages, where the word allowance becomes the budget.
WPML: best for a store or page-builder site
WPML keeps translated pages, products and strings inside WordPress, with translation management for teams and translation services.
What stands out
- Multilingual CMS covers strings, menus, page builders, WooCommerce and the Site Editor, with 22,500 AI words that are topped up at each renewal and never expire.
- One €99 licence covers 3 production sites and 9 development sites.
The minus
- No free version and not on wordpress.org, so you judge it by the docs and the 30-day money-back window.
- Since January a licence registered by your developer can’t be transferred to you, so buy it in your own account.
Price: Multilingual Blog €39 a year for 1 site covers pages and posts only, no strings, menus, builders or store. Multilingual CMS €99 a year for 3 sites with 22,500 AI words; Agency €199 for unlimited sites and 45,000 words. Renewal price shown in your account; more words are bought pay-as-you-go (the first 500 a month are free) or prepaid, priced in the account. An unrenewed WPML keeps working but can’t be updated. 30-day money-back on the licence.
Not on wordpress.org: sold at wpml.org.
Not for: a blog with a handful of pages you translate yourself; Polylang free does that.
Weglot: best when the whole site should translate itself
Weglot’s WordPress plugin translates the whole site automatically. You review translations in its dashboard; Weglot serves them from its servers.
What stands out
- Pages, menus, forms and meta text are translated automatically in one pass, with language subdirectories and hreflang tags set up for you.
- Review and editing happen in one dashboard outside WordPress; your database stays untouched.
The minus
- You pay for the total translated words, counted per language, every year. Over the limit, Weglot moves you up a plan if auto-upgrade is on; if it’s off, new text stops being translated (the pricing FAQ says translations are discontinued), and on the free plan translations stop showing.
- Translated slugs need Pro (€790 a year) and bulk export needs Advanced (€2,990 a year). Stop paying and the translated site stops being served.
Price: free up to 2,000 words in one language. Starter €150 a year (10,000 words, 1 language), Business €290 (50,000 words, 3 languages), Pro €790 (200,000 words, 5 languages, 3 sites); monthly €15, €29 and €79; free trial. Charged in euros, the dollar prices are estimates. Refund within 15 days of the original purchase, not for renewals or upgrades.
On wordpress.org: 50,000+ active installs, updated October 15, rated 4.8 out of 5.
Not for: anyone who wants translations in their own database or wants to avoid a subscription.
Which multilingual plugin fits your site
- If you write or commission the translations and have no store, use Polylang free.
- If you want to translate on the live page with AI drafts and keep translated slugs and descriptions, use TranslatePress Personal.
- For a store or page-builder site needing one licence for strings, products and builder content, use WPML Multilingual CMS.
- If you want several languages live without translating anything and accept a yearly word bill, use Weglot.
Take a 30-page business site, about 15,000 words, into two more languages: roughly 30,000 translated words, plus menus and meta text. First year, one site: Polylang free costs €0 plus your translation time (Pro at €99 adds DeepL, billed by DeepL separately). TranslatePress Personal at €99 covers it with 50,000 words. WPML Multilingual CMS at €99 includes 22,500 words; the remaining 7,500 or so are bought in your account at the price shown there. Weglot Business at €290 covers 50,000 words, charged every year; translated slugs would need Pro at €790. Taxes and a translator’s fee are extra.
For a typical small site I’d start with Polylang free, then switch to TranslatePress Personal the day I want AI drafts on the page instead of writing every translation by hand.
Setting up a multilingual site: what to get right
- Choose the URL format before launch Subdirectories such as /nl/ work with all four plugins; changing the format later means a redirect for every translated page. Give each translation its own slug, title and description too: Polylang does it per translated post with your SEO plugin, TranslatePress with its SEO Pack, WPML with Multilingual CMS, Weglot from Pro.
- Translate the strings, forms and emails Menus, footer text, form messages and store emails live outside your pages. Open them in the second language before launch.
- Keep page caching on Two extra languages triple the number of pages your cache and visiting bots have to handle. If your host reports memory limits, ask for the error log entries before you blame the translation plugin.
- Don’t redirect visitors by location Google advises against automatic redirects by IP or browser language. A language switcher visible on every page is the better move.
Then check the result as a visitor: open a translated page and confirm its own address, a translated menu and footer, and a switcher back to the original. Look in the page source or the sitemap for hreflang tags pointing to each language version. Send a test form message and, on a store, place one test order in the second language and read the emails.
Rather have the languages set up for you?
If the theme, forms and store emails all need translating and you’d rather not learn a plugin, a multilingual specialist can set it up; a small setup often takes a few days. On Fiverr Pro, one extra language on a small site starts at about $150 plus Fiverr’s service fee; a store or builder site costs more, and the translations themselves are a separate quote.
Before ordering, read how to hire a WPML or Polylang expert for scope, safe access and a pilot of one language and a few page types. My tool and contractor picks are on the Recommended page.
Summary
The best WordPress multilingual plugin fits how you’ll translate and what you’ll keep paying for. Count words per language, and decide whether you accept translations living on someone else’s servers. Start with one language and a few page types, check the addresses and the tags, then roll out the rest.
FAQ
Is machine translation good enough to publish?
As a first draft, yes; as a final page, only after someone who speaks the language reads it, starting with prices, legal text and buttons. All four tools let you edit the draft before it goes live.
Will a second language hurt my rankings?
It shouldn't, when each language has its own address, hreflang tags sit in the pages or the sitemap, and visitors aren't redirected by location. That setup helps Google show each visitor the right version, and your English pages keep their own addresses.
What happens when the licence or subscription ends?
Polylang Pro, TranslatePress and WPML keep working with the translations in your database; you lose updates and support, and TranslatePress's AI words stop. Weglot stops serving the translated site, and only Advanced plans and up can export the translations in bulk.
Can I switch from WPML to Polylang later?
Yes, but treat it as a project. A free WPML to Polylang plugin moves the translations, but the two plugins store them differently: run it on a staging copy, keep a backup, and check that every translated address still works before switching the live site.