ByWordPress multilingual plugins let you translate posts, pages, menus, and themes into additional languages without rebuilding your site from scratch, and in 2026 the three serious contenders are WPML, Polylang, and TranslatePress. Each one handles translation differently, and the right pick depends on your budget, how much automation you want, and whether you already run WooCommerce. This guide compares all three so you can choose the one that fits your site instead of guessing.
What Are WordPress Multilingual Plugins and Do You Need One in 2026?
WordPress multilingual plugins add a translation layer on top of your existing content so visitors can switch between languages using a language switcher, usually placed in the menu or footer. Instead of running separate WordPress installs for each language, one plugin manages every translated version from a single dashboard, keeping your media library, theme, and plugins shared across languages.
You need one if any meaningful share of your traffic comes from a non-English-speaking country, if you sell internationally through WooCommerce, or if a government or industry rule requires content in a specific language. A single-language blog aimed at one country rarely benefits enough to justify the setup time and the ongoing cost of a premium plugin.
WordPress multilingual plugins also change your site’s URL structure, typically adding either a subdirectory (/fr/), a subdomain (fr.example.com), or a query parameter for each language. Search engines treat each language version as a separate indexable page, which is why hreflang tags and a clean internal linking structure matter more once you add a second language.
How Does WPML Work and What Does It Cost in 2026?
WPML is the oldest and most feature-complete of the three WordPress multilingual plugins, built for sites that need full control over translation workflow rather than quick automatic translation. It lets you assign human translators, send content to a translation service, or use its Advanced Translation Editor with machine-translation suggestions you edit by hand.
WPML has no free version, and pricing is tiered by feature set rather than site count. According to WPML’s official pricing page in 2026, the Multilingual Blog plan costs €39 per year and covers posts and pages only. The Multilingual CMS plan costs €99 per year and adds the Advanced Translation Editor, string translation for theme and plugin text, and WooCommerce Multilingual support. The top Multilingual Agency plan costs €199 per year and is meant for agencies managing several client sites.
Because WPML translates everything, including theme strings and plugin output, it’s the plugin most likely to work correctly with a complex page builder or a WooCommerce store out of the box. The tradeoff is a steeper learning curve and a yearly renewal fee even for a small brochure site.
How Does Polylang Compare to WPML for Multilingual Sites?
Polylang takes a lighter approach: the core plugin is free on WordPress.org and lets you assign a language to every post, page, category, and tag, then link translated versions together as a set. It doesn’t automatically translate anything by default, so you or a translator write each language version directly in the WordPress editor.
For stores and sites that need more, Polylang Pro costs €99 per year for a single site according to Polylang’s official pricing page in 2026, and it adds translation of custom post types, taxonomies, and menus, plus a translation management interface. Polylang for WooCommerce is a separate €99-per-year add-on, and the Polylang Business Pack bundles both for €139 per year.
Polylang suits sites where a human is writing or reviewing every translation anyway, since its free tier already covers the structural work of linking languages together. It’s a weaker fit if you want one-click machine translation across an entire site, because that workflow is built into WPML and TranslatePress rather than Polylang’s core.
What Makes TranslatePress Different From WPML and Polylang?
TranslatePress translates your site visually: instead of opening a separate translation screen, you click “Translate Page” and edit text directly on a live preview of the front end, including text generated by your theme or plugins. That front-end editor is the plugin’s main selling point over WPML and Polylang, both of which translate from inside the WordPress admin.
TranslatePress also connects to Google Translate and DeepL for automatic machine translation, which you can then review and correct in the same visual editor. A free version is available on WordPress.org with a single additional language; paid add-ons unlock extra languages, automatic translation, and SEO features like translated slugs and hreflang tags.
Because it edits what’s rendered on the page rather than the raw database content, TranslatePress tends to handle oddly built themes and page builders more gracefully than plugins that only translate structured post data. The visual workflow is also easier to hand off to a non-technical translator who shouldn’t be given access to wp-admin.
WordPress Multilingual Plugin or Multisite: Which Should You Use?
WordPress Multisite lets you run several separate WordPress installs — one per language — from a single dashboard, sharing users and plugin activation but keeping each site’s content completely independent. A WordPress multilingual plugin instead keeps one site and one set of content, with translations layered on top and linked together automatically.
Multisite makes sense when each country or language needs genuinely different content, pricing, or a local team publishing independently, because nothing forces the sites to stay in sync. A multilingual plugin makes more sense when you want every language to mirror the same pages, since it tracks translation status and flags pages that fall out of date in the source language.
Most small and mid-sized sites choose a WordPress multilingual plugin over Multisite simply because it’s less to maintain: one database, one set of plugin updates, and one login, instead of managing several installs that can drift apart over time.
What Mistakes Should You Avoid When Translating a WordPress Site?
The most expensive mistake is picking a plugin before checking that it works with your specific theme and page builder. WPML, Polylang, and TranslatePress all publish compatibility lists for popular builders like Elementor and Divi; skipping that check can mean rebuilding translated pages from scratch after a broken installation.
Another common mistake is translating navigation menus and widgets last. Visitors judge whether a site genuinely supports their language within seconds, and an untranslated menu sitting above perfectly translated body content undermines that impression immediately. Translate the structural elements — menus, footer, search placeholder text — before polishing individual blog posts.
Teams also tend to under-budget the review step. Machine translation from any WordPress multilingual plugin produces usable first drafts, but publishing them unreviewed risks awkward phrasing at best and factually wrong pricing or legal text at worst. Budget a native speaker’s review time into the project from the start, not as an afterthought if something looks off later.
WPML vs Polylang vs TranslatePress: Which One Should You Choose?
The table below lines up the three WordPress multilingual plugins on the factors that usually decide the choice: starting price, translation method, and WooCommerce support.
| Plugin | Starting Price | Translation Method | WooCommerce Support | Best For |
|---|---|---|---|---|
| WPML | €39/year (Blog); €99/year (CMS, with WooCommerce) | Manual, agency, or Advanced Translation Editor | Built in on CMS plan | Agencies and WooCommerce stores needing full control |
| Polylang | Free core; €99/year (Pro) | Manual, inside wp-admin | Separate €99/year add-on | Sites where humans write every translation |
| TranslatePress | Free (1 extra language); paid tiers for more | Visual front-end editor with Google Translate/DeepL | Included on paid tiers | Visual editing and quick machine translation |
If you’re running WooCommerce and want one vendor to handle everything, WPML’s CMS plan is the safest default among WordPress multilingual plugins. If budget matters more than automation and you’re comfortable writing translations by hand, start with Polylang’s free core and add Pro only when you need WooCommerce or menu translation. If you want to see translations in context and lean on machine translation as a starting draft, TranslatePress is the fastest of the three WordPress multilingual plugins to set up.
How Much Does Running a WordPress Multilingual Plugin Actually Cost?
The plugin license is the smallest line item. WPML’s €99-per-year CMS plan, Polylang’s €99-per-year Pro license, and TranslatePress’s paid tier all cost roughly the same for a single site, so license price alone shouldn’t decide which WordPress multilingual plugin you pick.
The real cost is translation itself. A professional human translator typically charges per word, and a mid-sized site with a few hundred published pages can easily run into four figures to translate properly, regardless of which plugin moves the text around. Machine translation through any of the three WordPress multilingual plugins cuts that cost close to zero but shifts the expense to review time instead.
Budget for ongoing cost too: every new post, product, or page you publish in the source language needs a matching translation, and that review cycle repeats for as long as the site is active, not just during the initial setup.
Do WordPress Multilingual Plugins Work With Page Builders and Custom Fields?
Mostly yes, but support varies by builder. WPML publishes official integrations for Elementor, Divi, and Advanced Custom Fields, translating custom field values and builder-generated content alongside standard post content. Polylang Pro also supports ACF and most major builders, though some third-party addons need their own translation-compatible version.
TranslatePress takes a different approach that sidesteps most compatibility issues: because it translates whatever text renders on the page, it generally works with any builder or custom field setup without needing a dedicated integration, since it never needs to understand how that text was generated in the first place.
Before committing to a WordPress multilingual plugin, check its documentation for your specific theme and any custom post types your site relies on, and test the free or trial version on a staging copy rather than the live site.
How Do You Set Up a Multilingual WordPress Site Step by Step?
Setting up WordPress multilingual plugins follows the same broad sequence regardless of which one you pick, since every plugin needs the same decisions about languages and URL structure before it touches content.
- Back up your site before installing anything — WordPress multilingual plugins touch your database schema and permalink structure, so a bad install is hard to undo without a backup.
- Install your chosen plugin and run its setup wizard, choosing your default language and every additional language you plan to support.
- Pick a URL structure — subdirectory, subdomain, or parameter — and stick with it; changing this later breaks every indexed URL.
- Add a language switcher to your menu or footer using the plugin’s widget or block so visitors can find the other languages.
- Translate your highest-traffic pages first — homepage, top blog posts, and checkout flow if you sell online — rather than trying to translate everything at once.
- Check that hreflang tags are generating correctly by viewing your page source, since a missing or malformed hreflang tag is the most common multilingual SEO mistake.
- Submit each language’s sitemap to Google Search Console separately so every version gets crawled and indexed.
Translating everything on day one is the most common mistake. Start with the pages that drive revenue or search traffic, confirm the translated versions rank and convert, and expand language-by-language from there.
How Do WordPress Multilingual Plugins Affect SEO and Performance?
Installing WordPress multilingual plugins multiplies your page count, since every translated page is a separate URL that needs its own title, meta description, and internal links. Without a deliberate internal linking structure connecting language versions of the same page, search engines can end up treating translations as unrelated duplicate content instead of alternate versions of one page.
WordPress multilingual plugins also add real page-weight: extra database joins to fetch the right language version, additional JavaScript for the language switcher, and often a larger options table. On a site already fighting slow load times, pairing a multilingual plugin with one of the best WordPress caching plugins available in 2026 keeps the extra overhead from showing up as a Core Web Vitals regression.
Because these plugins run on every single front-end request to decide which language to serve, they’re also a common target in automated scans. Run a WordPress plugin security audit after installing one, and keep it updated the same way you would any plugin that touches every page on your site.
Translated content also gets crawled by AI assistants and chatbots, not just traditional search engines, so it’s worth checking that your llms.txt file points AI crawlers toward your most important translated pages alongside the English originals.
Frequently Asked Questions About WordPress Multilingual Plugins
Can I switch WordPress multilingual plugins later without losing content?
Switching is possible but rarely clean. Each plugin stores language relationships differently in the database, so migrating usually means exporting translated content and re-importing it into the new plugin, then rebuilding your language switcher and checking every permalink. Pick carefully up front rather than planning to switch.
Do WordPress multilingual plugins slow down my site?
Yes, to some degree, because they add database queries to determine the visitor’s language on every page load. The slowdown is usually small with a caching plugin in place, but it’s worth testing your site’s load time before and after installation rather than assuming it’s negligible.
Is machine translation good enough for a business website?
Machine translation from Google Translate or DeepL is a reasonable starting draft for informational content, but it should be reviewed by a fluent speaker before publishing anything customer-facing, especially pricing, legal text, or checkout flows where a mistranslation has real consequences.
Does WooCommerce work with all three plugins?
Yes, but support differs: WPML includes WooCommerce Multilingual on its CMS plan, Polylang requires the separate Polylang for WooCommerce add-on, and TranslatePress supports WooCommerce on its paid tiers. Confirm which plan you need before buying, since WooCommerce support is rarely included in the cheapest tier.
Should I use a subdirectory or subdomain for each language?
A subdirectory like /fr/ is simpler to set up and keeps all your domain authority in one place, which is why most small and mid-sized sites use it. A subdomain or separate country-code domain makes more sense only if you’re running genuinely separate regional teams or need a local server location for legal reasons.
Can free WordPress multilingual plugins still rank well internationally?
Yes. Polylang’s free core and TranslatePress’s free tier are both free WordPress multilingual plugins that generate correct hreflang tags and separate indexable URLs, which are the technical requirements search engines actually check. Ranking well then depends on translation quality and content relevance, not on which plugin tier you paid for.
How many languages should a small business site start with?
One additional language is enough to start. Adding a second language before confirming the first one actually drives traffic or sales just multiplies the review and maintenance workload for every future content update, no matter which of the WordPress multilingual plugins you picked, without proving the investment pays off.
Picking between WPML, Polylang, and TranslatePress comes down to three honest questions: how much you’re willing to pay upfront, whether a human or a machine should write the first draft of each translation, and how tightly your theme or page builder needs to integrate with the plugin. Answer those three before reading another comparison post, install the plugin that matches your answers on a staging site first, and translate your highest-value pages before anything else. That sequence works regardless of which language you’re adding or which of these three plugins you ultimately choose.
Subscribe for Newsletter
