WordPress runs a considerable share of the web, yet it still cannot publish a site in several languages on its own. The official roadmap files multilingual support under “phase 4”, after the collaboration work now underway, with no date attached.
Until then, plugins do the job. And they do it in very different ways: some create a real post for each language, others translate the page at the moment it is displayed, and others keep your translations on their own servers.
That architectural choice matters more than any feature list. It decides how Google indexes your language versions, what you pay every year, and what is left on your site the day you change your mind.
Here are the ten solutions worth your attention in 2026, with what they actually do, where they fall short, and the kind of site each one suits.
How we ranked them
We used six criteria, in this order of importance. The first is architecture: where translations live, in your database or in a vendor’s cloud, and in what form.
The second is search quality: a distinct URL for each language, correct and reciprocal hreflang tags, translated slugs and metadata. The third is workflow: human translation, machine translation, review, translator roles.
Then come compatibility with WooCommerce and page builders, the maintenance and security record in 2026, and total cost. That last one includes renewals, word quotas and the add-ons you need before you get what the homepage promises.
Install counts and prices were read in October 2026 on the official WordPress.org directory and on vendor pricing pages. They change often, so check them before you buy. If you are starting from scratch, our list of essential WordPress plugins will help you build the rest of the stack.
Two architectures, two consequences for SEO
Before comparing products, you need to understand the two main families. Almost every difference in price, performance and search visibility follows from them.
One WordPress content item per language
In this family, each translation is a full post or page, linked to its equivalents. WPML and Polylang do this inside a single site. MultilingualPress and Multisite Language Switcher do it with WordPress Multisite, one site per language within the same network.
The advantage is robustness: your translations are ordinary WordPress content, editable, backed up with everything else, independent of any subscription. The downside is volume: ten languages means ten times more content to manage, and every change to the source text must be carried over by hand or through a workflow.
A translation layer on top of the page
In the second family, there is only one piece of content, in the original language. The plugin splits the rendered page into text strings, translates them and serves the requested version. TranslatePress keeps those strings in your database. Weglot, Linguise, ConveyThis and the paid version of GTranslate keep them in their cloud.
Setup is fast, but it creates a dependency: with hosted services, stopping payment makes your translations disappear from your site. And you usually pay per word, counted across all languages.
What Google expects, whatever the family
Google Search Central documentation is clear on three points. Each language needs its own URL, rather than content that changes with a cookie or browser settings. Versions must be linked with reciprocal hreflang tags, each page listing the others and itself.
Finally, Google advises against automatically redirecting visitors to another language and against adapting content based on IP address. Its crawler sends requests without a language header and mostly from US addresses: a site that redirects by default may only ever show it one version.
One detail many guides miss: Google determines a page’s language from its visible content. The lang attribute and hreflang tags are not used to detect language; hreflang links equivalent pages together.
1. WPML: the most complete option for team-run sites
What it does
WPML is the long-standing commercial multilingual plugin for WordPress. It is not distributed through the official directory but sold directly by its developer, OnTheGoSystems. Each translation is a separate content item, attached to a translation group in dedicated tables.
You choose the URL structure: subdirectories, subdomains, separate domains or a language parameter. WPML inserts the hreflang tags itself and keeps them up to date as you edit.
Strengths
Its strength is coverage: translation of theme and plugin strings, translator and translation job management, a dedicated WooCommerce module with multi-currency, and compatibility with the main page builders. Few setups defeat it.
Version 5.0, released on September 16, 2026, merged the admin into a single menu and made automatic translation truly autonomous, with no browser tab left open. With WPML’s own engine, each page is billed once per language. DeepL, Google and Microsoft are now presented as legacy engines, in favor of WPML’s own engine.
Limits
There is no free version, and the entry plan includes neither string translation nor WooCommerce. WPML adds around twenty tables to your database, which makes migrations heavier. Its own support pages say that browser-language redirection comes with no guarantee for indexing.
On the security side, a remote code execution flaw, exploitable from a contributor account through the language switcher shortcode, was fixed in August 2024 in version 4.6.13. It is a reminder that a plugin this central must be updated without delay.
Price and audience
At the time of writing, in October 2026, WPML costs €39 for the first year for a blog, €99 for the CMS plan (three production sites, string translation, WooCommerce, machine translation credits) and €199 for the agency plan with unlimited sites. It is built for agencies, WooCommerce stores and teams working with translators.
2. Polylang: translations that stay WordPress posts
What it does
Polylang, developed by WP SYNTEX, links posts, pages, media, categories and tags written in different languages. It relies on WordPress’s native taxonomies rather than its own tables. The official directory credits it with more than 800,000 active installations.
The language appears in the URL as a language code (a subdirectory by default), or through a subdomain, or a separate domain. Hreflang tags are generated automatically, the x-default tag only on the homepage.
Strengths
The free version handles unlimited languages and translates custom post types as well as taxonomies. For developers, the API is simple and documented. Your translations remain ordinary WordPress content, which makes backups, exports and a future exit easier.
The Pro version adds machine translation with DeepL, translated slugs, the option to share the same slug across languages, and XLIFF import and export for professional translators. In the interest of transparency: the blog you are reading runs on Polylang.
Limits
WooCommerce requires a paid add-on. The free version offers no machine translation. Browser language detection redirects first-time visitors on the homepage, which you can turn off if you follow Google’s recommendation.
Stable version 3.8.10, released on September 28, 2026, fixes two vulnerabilities reported through Patchstack. As with any plugin that touches every request, prompt updating is not optional.
Price and audience
Polylang Pro costs €99 per year excluding VAT for one site, with renewals currently discounted by 50%. The WooCommerce add-on also starts at €99. Polylang suits blogs, corporate and editorial sites, and developers who want translations as native content.
3. TranslatePress: translating the page as it is displayed
What it does
TranslatePress, from Cozmoslabs, belongs to the translation-layer family, with one important difference: everything stays on your side. Translated strings are stored in tables in your own database. You translate directly on the site, in a visual editor that shows the real page.
Languages are served in subdirectories, and an add-on allows a separate domain per language. The plugin generates hreflang tags and offers an option for the x-default tag. It has more than 400,000 active installations.
Strengths
Visual editing makes translation accessible to people who do not know the WordPress admin. Theme and plugin strings are translated in the same place as content, which works well with page builders and WooCommerce.
The free version already includes limited machine translation (TranslatePress AI up to 2,000 words, or Google Translate with your own key), a manual-only translation mode and translation memory. Paid plans add DeepL (from the Business plan), a much larger word quota, extra languages and the SEO Pack.
Limits
The free version handles only one translation language. Translations are tied to the original string: editing a sentence in the source language hides its translation until it is redone, except for minor edits when the automatic translation memory option is on. They also depend on the language configuration, which must stay identical during a migration.
Above all, a critical privilege escalation flaw, exploitable without authentication and affecting versions up to 3.3.1, was published on September 2, 2026 (CVE-2026-19632, CVSS 9.8) and flagged as actively exploited. If you use this plugin, make sure you are on 3.3.2 or later, and consider a WordPress security plugin that can block this kind of attack between disclosure and your update.
Price and audience
The Personal plan costs €99 per year for one site, Business €199 for three sites with every add-on. TranslatePress suits small and mid-size sites that want visual translation while keeping their data at home.
4. Weglot: the hosted service, quick to launch, rented by the word
What it does
Weglot is a hosted translation service. The WordPress plugin connects to your account; the service detects texts, translates them automatically and serves the translated versions. On WordPress, each language gets its own subdirectory, such as /es/ or /fr/.
The service adds hreflang tags, but not the x-default tag by default: you need a filter to get it.
Strengths
A translated site can go live in hours. The glossary, the visual editor, translation of metadata and image alt text, access to professional translators from the Business plan: everything is designed for a marketing team that does not want to touch WordPress.
Because translations are served from Weglot’s cloud, your database does not grow.
Limits
That is the other side of the same coin. Translations live at Weglot: if you cancel, they disappear from your site, and the company itself states that translated pages are progressively removed from search engines. After cancellation, the project is deleted after three months of inactivity.
Quotas count every word in every language, and translated URL slugs only come with the Pro plan.
Price and audience
A free plan covers 2,000 words and one language. Starter costs €15 per month or €150 per year for 10,000 words, Business €29 per month for 50,000 words and three languages. Weglot suits marketing sites with modest text volume and organizations running several CMSs.
5. MultilingualPress: one site per language, for large organizations
What it does
MultilingualPress, developed by the German agency Syde, is built on WordPress Multisite: each language is a site in the network, with its own settings, plugins and users. The plugin links equivalent content across sites and generates hreflang tags.
Watch out for one trap: the listing on the official directory is an old, abandoned 2.x version. The current product, version 5, is sold on the developer’s website.
Strengths
This model fits organizations where each language has its own team, its own rules and sometimes its own products. Since version 5.0 in June 2025, a machine translation feature uses DeepL, OpenAI or Amazon Translate, with those services billed separately by their providers.
Because each translation is native content on a site in the network, it survives deactivation of the plugin. If you are weighing this model, our WordPress Multisite guide covers its constraints in detail.
Limits
Multisite requires network administration, per-site configuration and hosting that handles it well. Pricing depends on the number of languages, which makes it expensive for a simple bilingual site.
Price and audience
The Starter plan costs €149 per year including VAT for two languages, Professional €499 for six languages. MultilingualPress is aimed at media groups, universities and international organizations.
The swissinfo.ch case: ten languages, eleven sites, one WordPress network
The best way to understand what a multilingual architecture changes is to look at one in production. SWI swissinfo.ch is the international service of the Swiss Broadcasting Corporation. It publishes news about Switzerland in ten languages, from English to Chinese, including Arabic and Japanese.
The starting point
Until 2024, the newsroom worked on an aging proprietary CMS. In a talk given at WordCamp Netherlands in 2025, the agency Syde described a fragmented architecture that had been designed neither for ten languages nor for change. Its opening image says it all: the same headline translated ten times, then ten pages to check before publishing.
The migration
With Syde as technical partner, swissinfo.ch moved to WordPress VIP, Automattic’s enterprise hosting offer. The project took about eighteen months and was completed in February 2024. According to the case study published by WordPress VIP, some 300,000 articles and one million images had to be transferred.
Why Multisite
The team chose WordPress Multisite with MultilingualPress. Each of the ten language desks has its own site within a shared network, eleven sites in total. The reasoning was editorial before it was technical: autonomous desks under central governance.
An article is born in one language, then adapted into others. DeepL provides a first draft on news topics, which journalists then rework. Some stories go out in every language, others stay in one or two. Even reader comments go through language detection and machine translation, after moderation.
What the site shows today
Looking at the site in October 2026, you find Google’s principles applied to the letter. Each language has its subdirectory (/eng/, /fre/, /ger/, /jpn/…). Hreflang tags use regional codes, such as fr-CH or de-CH, and an x-default tag points to the English version.
Even more instructive: an English article picked at random declares only seven versions, with no German, French or Italian. It simply does not exist in those languages. The hreflang tags list only the translations that are real, which a “one item per language” architecture allows naturally.
What to take away
The published results are qualitative. swissinfo.ch’s head of audience told WordPress VIP how easy it had become for journalists to create article translations. Syde reports that the release cycle for new features went from several months to one or two weeks, a figure only the agency provides.
A caveat is needed: every source for this story has a commercial interest, since Syde sells MultilingualPress and WordPress VIP hosts the site. The lesson still holds. The architecture followed the newsroom’s organization, machine translation serves as a draft inside an editorial workflow, and the choice carries an infrastructure cost that only makes sense at that scale. A project like this also requires WordPress hosting that can keep up.
6. GTranslate: from free widget to indexable proxy
What it does
GTranslate, with more than 900,000 active installations, is really two products. The free version is a widget: the visitor’s browser sends the page text to Google and displays the translation. The developer itself acknowledges that this version brings no SEO benefit.
Paid versions work as a translation proxy: GTranslate mirrors your site in other languages, on subdomains, or on subdirectories and your own domains with the top plan, with hreflang tags and translated URLs depending on the plan.
What changed in 2026
Version 5.0.1 replaced the legacy Google Website Translator widget, whose end of support is announced for October 1, 2026 according to GTranslate. It also tightened the terms: the free version is now reserved for personal, educational, nonprofit or government use. A commercial site needs a paid plan.
Limits and price
The free version is not indexable and no longer suits a business. Paid translations are machine-generated and hosted by the vendor. Plans start at $12 per month. GTranslate suits non-commercial sites that want a reading aid, and businesses looking for indexable machine translation with no word limit.
7. Linguise: unlimited languages at a flat price
What it does
Linguise is a cloud machine translation service. Translations are stored on its servers, with an optional local cache. The service translates the URL and the full page content, declares alternate versions including the x-default tag, and produces translated sitemaps and canonical URLs.
Strengths and limits
Its appeal is pricing: a flat price per site, with more than 80 languages available at no extra cost. The entry plan costs $15 per month for 200,000 translated words, the top plan $45 with unlimited volume under a fair use policy. The first month is free.
On the other side: a still small user base (just over 1,000 active installations on WordPress.org), no lasting free plan, and translations that stay with the vendor. Linguise suits sites that want many languages through machine translation on a predictable budget.
8. ConveyThis: the cloud alternative with small price steps
What it does
ConveyThis works on the same principle as Weglot: translations stored on its servers and served from its delivery network, hreflang tags added automatically, subdirectories or subdomains, translated URLs and slugs.
Strengths and limits
The pricing grid is very granular, with about a dozen tiers. A free plan covers 10,000 words and one language, and Starter costs $12 per month for 60,000 words. That makes it easy to match spending to actual volume.
The downside is familiar: a small installed base, complete dependency on the provider for your translations, and a bill that follows the word count. ConveyThis suits small sites that want a hosted service with a cheap entry point.
9. Multisite Language Switcher: Multisite for free
What it does
Multisite Language Switcher is the free counterpart to MultilingualPress. Each language is a site in the network, and the plugin links posts, pages, custom post types, categories and custom taxonomies across sites. It has a few thousand active installations and is still maintained.
Strengths and limits
The plugin generates hreflang tags and never redirects visitors automatically, which matches Google’s recommendations. By default, the tags use only the language code (en, de, fr). To target Switzerland and France separately, you need the msls_head_hreflang filter.
It offers no machine translation, no workflow and no translator management: linking content is manual. It is an excellent choice for a developer comfortable with Multisite and a zero budget.
10. Loco Translate: for theme and plugin strings, not content
What it does
Loco Translate, with more than one million active installations, does not translate your posts. It lets you edit theme and plugin translation files in the browser: buttons, WooCommerce labels, error messages. It stores your custom translations in a protected folder so that an update does not overwrite them.
Why it is on this list
Every multilingual site ends up showing a button left in English or a sentence badly translated by a plugin. WPML and TranslatePress handle this internally. With Polylang or a Multisite setup, Loco Translate is the natural companion.
It can call DeepL, Google, Microsoft or OpenAI with your own API keys, and supports the faster translation file format introduced in WordPress 6.5. It is free, with translation services billing their own usage.
Machine translation and SEO: what Google says in 2026
Machine translation has become excellent, and almost every solution above offers it. The question is no longer whether it is allowed, but under what conditions it stays useful.
The robots.txt advice is gone
On June 11, 2025, Google removed from its multilingual documentation the passage that recommended blocking automatically translated pages. Google told Search Engine Roundtable that its policies do not automatically treat AI-translated content as spam. It described the change as a documentation update, with no change in behavior.
Scaled spam still covers translation
Google’s spam policies still list translation among the automated transformations used to mass-produce pages with no added value. A translated version is judged on its real usefulness to readers of that language, not on the mere fact that it exists.
Reddit, a dated example
Reddit machine-translated its discussions into more than twenty languages starting in 2024, with translated pages flagged by a URL parameter and linked through hreflang. Consultant Glenn Gabe documented strong visibility for these pages in 2025, then sharp drops in Italy, Spain, Germany and France after the May 2026 core update and the June 2026 spam update.
Keep his conclusion in mind: scaling through machine translation remains risky unless you are certain of the quality of the result. Have your priority languages reviewed before making them indexable. For the rest of your search setup, our comparison of WordPress SEO plugins explains what each tool handles in a multilingual context.
How to choose
Start with your organization, not with the plugin. One person translating a two-language brochure site does not have the needs of an international newsroom.
By situation
- Bilingual brochure site or blog, tight budget: free Polylang, plus Loco Translate for strings.
- Multilingual WooCommerce store: WPML (CMS plan), Polylang with its WooCommerce add-on, or an up-to-date TranslatePress.
- Marketing team with no WordPress skills, little text: Weglot, accepting the dependency on the service.
- Many languages through machine translation: Linguise or paid GTranslate.
- Autonomous country teams: MultilingualPress, or Multisite Language Switcher if you know how to run a network.
The question to ask before you sign
Ask yourself what will remain on your site the day you switch solutions. With WPML, Polylang or a Multisite setup, your translations stay WordPress content. With TranslatePress, they stay in your database, but in a plugin-specific format. With a cloud service, they leave with the subscription. If you sell online, cross-check this choice with the WooCommerce plugins you plan to use, since not all of them work with every solution.
Summary table
| Plugin | Architecture | Where translations live | Entry price (Oct. 2026) |
|---|---|---|---|
| WPML | One item per language | Your database | €39 first year |
| Polylang | One item per language | Your database | Free, Pro €99 per year excl. VAT |
| TranslatePress | Translation layer | Your database | Free (1 language), €99 per year |
| Weglot | Translation layer | Vendor cloud | Free (2,000 words), €15 per month |
| MultilingualPress | One site per language | Your network | €149 per year incl. VAT |
| GTranslate | Widget or proxy | Google or vendor cloud | $12 per month (commercial use) |
| Linguise | Translation layer | Vendor cloud | $15 per month |
| ConveyThis | Translation layer | Vendor cloud | Free (10,000 words), $12 per month |
| Multisite Language Switcher | One site per language | Your network | Free |
| Loco Translate | Translation files | Your server | Free |
Frequently asked questions
Does WordPress handle multiple languages natively?
No. The official documentation states that WordPress does not support a bilingual or multilingual site without an extension. Multilingual support sits in phase 4 of the roadmap, which has no date so far.
Subdirectory, subdomain or separate domain?
Google accepts all three. A subdirectory is the easiest to set up and maintain, on a single host. A country-code domain sends a strong geographic signal but multiplies costs. Only the URL parameter, such as ?lang=fr, is discouraged by Google.
Does machine translation hurt SEO?
Not in itself. Google does not classify it as spam by default, but it judges the value of each page. A reviewed, useful and consistent translation can rank. Thousands of translated pages published without review run into the policies against scaled content.
What happens to my translations if I switch plugins or cancel?
With WPML, Polylang, MultilingualPress or Multisite Language Switcher, they remain WordPress content. With TranslatePress, they remain in its tables, unusable by another plugin without conversion. With Weglot, Linguise, ConveyThis or paid GTranslate, they disappear from your site with the subscription.
Do I need an x-default tag?
It is recommended, not required. It indicates the page to show when no language matches the visitor, often the English version or a language picker. Leaving it out carries no penalty.
Conclusion
The right multilingual plugin is first of all the right architecture. One content item per language gives you robustness and control of your data. A translation layer gives you speed, at the cost of a dependency that is more or less strong depending on where your translations live.
Either way, follow Google’s three rules: one URL per language, reciprocal hreflang tags, no forced redirection. And treat machine translation as a draft to review, the way swissinfo.ch does, rather than as a publish button.
Sources
- Google Search Central (December 2025). Managing multi-regional and multilingual sites
- Google Search Central (September 2026). Tell Google about localized versions of your page
- Google Search Central (December 2025). How Google crawls locale-adaptive pages
- Google Search Central (August 2026). Spam policies for Google web search
- Google Search Central (June 11, 2025). Latest Google Search documentation updates
- Search Engine Roundtable, Barry Schwartz (June 12, 2025). Google Softens Its Stance On Automated Translation After Reddit Implementation
- WordPress.org (2026). Roadmap
- WordPress Developer Resources (2025). Multilingual WordPress
- WPML (September 16, 2026). WPML 5.0: One Admin, Background Translation, and Pay Only for New Content
- WordPress.org (October 2026). Polylang
- TranslatePress (October 2026). Pricing
- Patchstack (September 2, 2026). Privilege Escalation in WordPress TranslatePress Plugin (CVE-2026-19632)
- Weglot Help Center (2025). How can I pause or cancel my subscription
- MultilingualPress (June 2025). MultilingualPress 5.0.0 is here, now with AutoTranslate
- WordPress.org (October 2026). Translate WordPress with GTranslate
- WordPress VIP. SWI swissinfo.ch case study
- Syde (July 8, 2025). Website relaunch in 10 languages: success factors from the SWI swissinfo.ch project
- Syde, Ronny Marx (WordCamp Netherlands 2025). Smart Multilingual WordPress: When and Why to Go Multisite
- GSQi, Glenn Gabe (July 9, 2026). Reddit’s AI translations finally drop heavily in Google and AI search
- WPML (October 2026). Purchase WPML
- Polylang (October 2026). Pricing
- Weglot (October 2026). Pricing
- MultilingualPress (October 2026). MultilingualPress
- GTranslate (September 6, 2026). Google Translate website widget discontinued
- Linguise (October 2026). Prices
- ConveyThis (October 2026). Pricing
- Syde. Case Study: SWI swissinfo.ch
- Syde (October 4, 2024). Unpacking the swissinfo relaunch
- GSQi, Glenn Gabe (March 27, 2025). Reddit AI translations have scaled across languages and Google rankings are booming
LaFactory designs, builds and maintains multilingual WordPress and WooCommerce sites, and develops its own plugins. Talk to us about your WordPress project.