Making a WordPress site multilingual used to mean a heavy plugin and a lot of manual work. In 2026 you have real choices — and the right one depends on how much you want to automate, whether you want to own your translations, and how your site is hosted. This guide lays out the approaches and the trade-offs so you can pick with confidence.
First, decide what "multilingual" means for you
Two questions settle most decisions:
- Faithful mirror or distinct markets? Do you want the same site in more languages, or genuinely different content per country (different products, pricing, legal text)?
- Manual or automatic? Will humans translate every page, or do you want AI to translate automatically and edit where needed?
The main approaches
1. Manual, per-post translation
Plugins like Polylang have you create a linked, translated copy of each post and page. You get full editorial control and the content lives in your own database — but you translate everything by hand, which doesn't scale past a small site unless you add machine translation.
2. Multisite, one site per language
MultilingualPress makes each language a separate site in a WordPress Multisite network. It's excellent when markets should be genuinely independent, but it requires running and maintaining a multisite network — more infrastructure and more sites to update.
3. Automatic AI translation
The newer approach: a plugin intercepts your rendered pages, translates them with AI, and serves language-prefixed versions automatically. It's the fastest path to a faithful multilingual mirror of an existing single site, with no per-post duplication. This is how Gloty works.
4. Cloud SaaS
Services like Weglot translate automatically too, but store your translations in their cloud and bill per word, per month. Setup is fast; the trade-offs are data ownership and recurring cost that scales with your content.
Get the URL structure right
Use language-prefixed subdirectories — /de/, /fr/ — for most sites. It's the structure Google and users expect, it keeps link equity on one domain, and it's simple to host. Set the correct lang attribute on <html> for each version, and give each page a clean, transliterated slug (our slug generator helps).
Don't skip multilingual SEO
Whatever approach you pick, you need hreflang tags (reciprocal, with x-default), per-language canonical URLs, translated titles and meta descriptions, and language-aware sitemaps. See our guide on adding hreflang in WordPress, and verify with the hreflang checker. A good plugin generates all of this automatically.
Don't forget WooCommerce
If you run a store, confirm your approach translates product titles, descriptions, attributes, the cart, checkout, and order emails — including blocks that render in JavaScript. This is a common gap; check it before you commit.
What it costs
Costs vary wildly by approach. Manual is free but labor-intensive. Cloud SaaS is a recurring subscription that grows with your word count and languages. Bring-your-own-key AI is often just a few dollars of provider usage, paid once, because translations are cached. Estimate your case with the translation cost calculator.
A sensible default
For most people translating an existing single site, automatic AI translation with your own provider key — stored in your own database — gives the best balance of speed, cost, and control. Keep the ability to edit translations by hand for the pages that matter, and make sure human edits are protected from being overwritten.