Choosing a WordPress translation plugin is not really a choice between brand names. It is a choice between three fundamentally different architectures, and once you understand which one fits your site, the shortlist writes itself. Pick wrong and you inherit problems that no amount of configuration will fix: translations Google refuses to index, page weight that wrecks your Core Web Vitals, or a recurring bill that balloons as your content grows. This guide is organized around that decision, with the real plugins worth installing in 2026.

The three architectures, and why they decide everything

Every serious multilingual plugin works one of three ways. Everything else — the editor UI, the price, the SEO behavior — flows from this.

1. Separate-post (self-hosted)

Each translation is a genuine post in your own database. Your French homepage is a real WordPress page with its own ID, its own SEO metadata, its own revision history. You own every word, the content lives on your server, and you have total control over per-language URLs and metadata. The cost is database overhead and a heavier editorial workflow — you maintain N copies of everything. Polylang and WPML live here.

2. Output translation (table-based)

Instead of duplicating posts, these plugins translate the rendered front-end. The original page renders, the plugin intercepts the output, and swaps in stored translations from its own tables. You translate through a single live visual editor — click any string on the page, type its translation. This is the friendliest model for page-builder sites (Elementor, Bricks, Divi) where content is scattered across widgets. TranslatePress is the standard-bearer.

3. SaaS proxy (cloud-hosted)

Your content is sent to an external service, machine-translated, stored on the vendor's servers, and served back through a JavaScript layer or a reverse proxy on language subdirectories. Setup is near-instant — point it at your site, pick languages, done. The trade-off is recurring cost (usually metered per translated word and per language) and vendor lock-in: cancel the subscription and the translations vanish. Weglot, Linguise, and paid GTranslate belong here.

The plugins worth your time

Polylang — the default for most self-hosted sites

Polylang is where I start most projects. The free tier is genuinely generous: unlimited languages, separate posts per language, custom-post-type and taxonomy support, and a clean language switcher. It does not translate content for you — you (or a translator) write each version — which is exactly what you want for editorial quality. Polylang Pro adds slug translation, REST API support, and a string-translation interface for theme strings. If you run WooCommerce, you will need the separate Polylang for WooCommerce add-on, which is the plugin's one notable extra cost.

WPML — the compatibility incumbent

WPML is paid-only and has been the heavyweight for over a decade. You are not paying for translation quality — you are paying for compatibility. WPML has the broadest tested support across commercial themes, page builders, and especially WooCommerce, where it handles translated products, variations, attributes, and checkout strings more thoroughly than anything else. For a complex multilingual shop, the Multilingual CMS tier is the usual pick. The downsides are real: it adds meaningful database queries, the admin UI is dense, and a poorly configured WPML install is a classic source of slow WordPress backends. Buy it when compatibility is the constraint, not by default.

TranslatePress — best for page-builder and visual sites

TranslatePress shines when your content does not live in tidy post bodies. Its visual editor lets you walk the front-end and translate every string in context, which is a relief on Elementor or Bricks sites where WPML and Polylang sometimes struggle to find strings buried in widget settings. The free version covers one extra language; Pro unlocks unlimited languages, DeepL integration for automatic first-pass translation, SEO title/meta translation, and translator user accounts. Because it stores translations in its own tables rather than duplicating posts, your post count stays sane.

Weglot — fastest setup, watch the meter

If you need a site multilingual this afternoon and budget is secondary, Weglot is the path of least resistance. It auto-detects and translates everything, serves translations on proper subdirectories, and handles hreflang for you. The catch is the pricing model: you pay per translated word and per language, billed annually, and that meter only goes up as your site grows. A large or fast-growing site can find Weglot becomes the most expensive line item in its stack. It is excellent for getting live quickly and for sites with bounded content; it scales painfully for sprawling ones.

Linguise — the newer neural-MT challenger

Linguise is a younger SaaS competitor in the Weglot mold — neural machine translation, subdirectory URLs, a front-end live editor for fixing the AI's mistakes. It tends to undercut Weglot on price and is worth quoting against it if you have decided the proxy model is right for you. As with any SaaS option, remember the translations are not yours: they live on Linguise's infrastructure.

GTranslate — read the free-tier fine print

GTranslate's free version is a client-side widget that machine-translates on the fly in the visitor's browser. It looks magical and is an SEO dead end: those translations are never server-rendered at distinct URLs, so Google does not index them. You get the appearance of a multilingual site with none of the search benefit. The paid tiers fix this by serving indexable translations on subdirectories or subdomains — but at that point you are comparing it head-to-head with Weglot and Linguise, not using it for free.

Two traps that catch almost everyone

Loco Translate is not a multilingual-site plugin. It is superb at what it actually does — editing the .po and .mo string files that translate a theme's or plugin's interface ("Add to cart", "Read more"). If your theme ships a half-finished French translation, Loco fixes it. It will not let visitors read your blog posts in three languages. Reaching for Loco to build a multilingual site is the single most common wrong turn in this space.

Abandoned plugins. qTranslate-X and its forks were once popular but are effectively unmaintained and store translations as inline markup inside a single post — a data model that is painful to migrate away from. Avoid building anything new on them.

The SEO non-negotiable: indexable URLs and hreflang

Whatever you choose, the search-engine backbone is the same. Each language must live at a distinct, crawlable URL — almost always a subdirectory like /fr/ or /es/ — and every page must emit correct hreflang annotations telling Google which URL serves which language and region. Polylang, WPML, TranslatePress, Weglot, and Linguise all handle this when configured for separate URLs. Client-side widgets (free GTranslate) do not, which is why they fail as an SEO strategy. Verify your translated pages return real translated HTML on a unique URL by viewing source, not just by toggling the on-page switcher.

WooCommerce and Core Web Vitals

For a multilingual shop, translation is not just product descriptions — it is variations, attributes, categories, emails, and checkout strings. WPML and Polylang (with its WooCommerce add-on) are the most battle-tested here; TranslatePress handles stores well via output translation but verify your specific gateway and shipping plugins. The SaaS options translate the storefront cleanly but give you less granular control over per-product SEO.

On performance, the self-hosted plugins add database queries but no external requests, so with good caching they keep your LCP under the 2.5-second Core Web Vitals threshold easily. SaaS proxies add a third-party dependency in the render path; the better ones cache aggressively, but it is one more network hop to account for. Test your actual translated pages in PageSpeed Insights before committing.

The short version

Most self-hosted sites: start with Polylang (free, you own the content).
Complex sites or serious WooCommerce shops needing maximum compatibility: WPML.
Elementor/Bricks/Divi sites: TranslatePress for in-context visual translation.
Need it live today, content is bounded: Weglot or the cheaper Linguise — just respect the recurring per-word meter.
Translating theme/plugin interface strings only: Loco Translate — and nothing else on this list.

Decide the architecture first. The plugin follows from it.

Best WordPress Translation Plugins