Originally published: November 17, 2025 · Last reviewed and updated: October 2026
WordPress still has no built-in way to run a site in several languages, so a translation plugin is the usual choice. The right plugin depends on three things: who does the translating (people, machine translation, or both), where translations are stored, and how much you want to pay as your word count grows.
This guide compares the best WordPress translation plugins in 2026: WPML, Polylang, TranslatePress, Weglot, and MultilingualPress. It also covers the SEO setup every multilingual site needs.
The Short Answer
- Polylang: best for small sites and blogs translated by hand. The free version is enough to start.
- TranslatePress: best if you want to translate visually on the front end. It has a free version for one extra language.
- WPML: best for complex sites and WooCommerce stores that need professional translation workflows.
- Weglot: best if you want hosted machine translation with almost no setup and are happy to pay a subscription that grows with your word count.
- MultilingualPress: best for larger organizations that want each language on a separate site in a WordPress Multisite network.
Whichever you choose, give each language its own URL and make sure the plugin outputs correct hreflang tags.
How Translation Plugins Differ
| Plugin | How it works | Where translations live | Free version | Paid pricing model |
|---|---|---|---|---|
| WPML | Separate post for each language, plus a string translation tool | Your database | No | Yearly licence; automatic translation uses credits |
| Polylang | Separate post for each language | Your database | Yes (manual translation) | Yearly Pro licence; WooCommerce add-on sold separately |
| TranslatePress | Translate on the live page with a visual editor | Your database | Yes (one extra language) | Yearly licence by tier |
| Weglot | Hosted service that detects and translates content | Weglot’s servers | Small free plan | Monthly or yearly subscription by words and languages |
| MultilingualPress | One site for each language in a Multisite network | Each language site | Limited | Yearly licence |
Prices change often and differ by currency. In 2026, comparisons put the cheapest WPML, Polylang Pro, and TranslatePress licences at roughly €39 to €99 a year. Weglot’s plans are priced by word count, and they can cost several times more over a few years on a large site. One 2026 comparison estimates three-year costs for each option. Check each vendor’s pricing page before you buy.
Plugin Notes
WPML
WPML is the most complete option. It translates posts, pages, custom post types, menus, theme and plugin strings, and WooCommerce products. It supports a review workflow and connections to translation services. The trade-off is a heavier plugin and more database tables, so test it on staging first.
Polylang
Polylang links a separate post for each language. It is lightweight and works well for blogs where you or a translator write each version by hand. Polylang Pro adds features such as duplicating content between languages and better slug handling.
TranslatePress
TranslatePress lets you click any text on the front end and translate it in place. It is easy for non-technical editors to use. It also translates text that comes from themes and plugins without hunting for string files.
Weglot
Weglot detects your content and translates it automatically as a hosted service. Setup takes minutes, and editors can review translations in Weglot’s dashboard. Because it charges by words, costs rise as the site grows, and your translations live outside WordPress.
MultilingualPress
MultilingualPress connects separate sites in a WordPress Multisite network, one for each language or country. It suits organizations whose regional teams manage their own content. Our WordPress Multisite setup guide explains the network side.
Multilingual SEO Checklist
Google’s guide to managing multilingual sites and its localized versions documentation set out the rules. In practice:
- One URL for each language, such as
/es/subfolders, subdomains, or separate domains. Don’t switch language on the same URL with cookies or scripts. - Reciprocal hreflang tags. Each version must list itself and every other version, or Google ignores the tags.
- An
x-defaultpage for visitors whose language you don’t offer. - No automatic redirects based on IP or browser language. Googlebot mostly crawls from the US without a language header, so offer a language switcher instead.
- Translated titles, meta descriptions, and slugs, not just body text.
- A sitemap for each language, which most plugins generate together with your SEO plugin.
Our complete WordPress SEO guide covers the rest of the on-page setup.
Machine Translation vs Human Translation
Machine translation through DeepL, Google, or AI models is now good enough for a first draft in many language pairs. It still makes mistakes with product names, legal text, and tone. A practical approach is to machine-translate everything and have a native speaker review your most important pages. Those include the home page, product or service pages, and anything legal.
Publishing large amounts of unreviewed machine-translated text can also count against you. Google’s spam policies treat content made mainly to manipulate rankings as low-quality, whatever tool produced it.
Common Mistakes
- Translating only the content. Menus, buttons, forms, and emails also need translations.
- Mixing languages on one URL. Search engines cannot index each language properly.
- Forgetting performance. Each language adds pages to crawl and cache. Our page speed guide helps keep things fast.
- Ignoring WooCommerce details. Prices, currencies, taxes, and shipping text need attention; see our guide to e-commerce plugins for WordPress.
- Switching plugins later without a plan. Each plugin stores translations differently, so moving between them is real work.
FAQ
Can I translate a WordPress site for free?
Yes. Polylang and TranslatePress both have free versions that work well for manual translation into one or more languages. Paid versions add automatic translation, more languages, or WooCommerce support.
Which translation plugin is best for SEO?
All five plugins in this guide support separate URLs and hreflang. SEO results depend more on translation quality and correct setup than on the plugin you choose.
Will a translation plugin slow down my site?
Database-based plugins add some queries and pages, but caching handles most of that. Hosted services such as Weglot add an external dependency instead. Test speed before and after on staging.
Should I use subfolders or subdomains for languages?
Subfolders such as /fr/ are the simplest and keep all languages on one domain. Subdomains or separate domains make sense when each region needs its own hosting or team.
Does WordPress have built-in multilingual support?
Not yet. Multilingual support is part of the long-term plans for WordPress core, but in 2026 you still need a plugin.
The Bottom Line
Pick Polylang or TranslatePress for small sites and blogs, WPML for complex sites and stores, Weglot for fast hosted machine translation, and MultilingualPress for multisite networks. Then get the SEO basics right: one URL for each language, reciprocal hreflang, translated metadata, and no automatic redirects. Have a person review your most important translated pages.
Sources & Further Reading
- Google Search Central: Managing multi-regional and multilingual sites
- Google Search Central: Localized versions of your pages
- WordPress.org: Polylang
- WordPress.org: TranslatePress
- WPML
- Google Search Central: Spam policies
- Odd Jar: WPML vs TranslatePress vs Weglot vs Polylang (2026)
Articles are editorially reviewed by Jackober and factual claims are checked against cited sources.
