Setup & site building · Guide
How to Make a Multilingual WordPress Site

Short answer
To make a multilingual WordPress site, pick a translation plugin, choose subdirectories such as /es/ for each language, and translate every page, menu and SEO field. Polylang is free with no language limit, TranslatePress adds visual on-page translation, and WPML suits large sites with WooCommerce.
Key takeaways
- Each language needs its own translation, its own URL, and a language switcher for visitors.
- Subdirectories such as /es/ suit most sites; subdomains and separate domains cost more to run.
- WPML costs €39, €99 or €199 a year, with 22,500 AI words on the €99 CMS plan.
- TranslatePress costs €99, €199 or €349 a year, with 50,000 AI words on the €99 Personal plan.
- Polylang is free with no limit on languages, but the free version has no machine translation.
- Translate the title and meta description of every page, and add hreflang tags.
What does a multilingual WordPress site need?
A multilingual site needs one translation for each page, a way for visitors to switch languages, and a separate URL for each language version.
WordPress ships in one language at a time, so a plugin adds the rest. The plugin links each translation to its original page, adds a language switcher to the menu or page, and gives each version its own address, such as /es/ for Spanish or /fr/ for French.
Plan the languages before you install anything. Two languages are easy to run; six languages mean six versions of every new page, and every update must be made in each one.
Start with the one extra language your visitors ask for most, and add more only when the first one is fully translated.
Should you use subdirectories, subdomains or separate domains?
Use subdirectories such as /es/ for most sites, since they keep all languages on one WordPress install and one domain.
Subdirectories are the default in most translation plugins. The Spanish version of a page lives at example.com/es/page-name/, the French version at example.com/fr/page-name/, and the whole site stays in one dashboard. That keeps backups, updates and links simple.
Subdomains put each language on its own address, such as es.example.com. They suit large sites where each language has its own team, but they need extra DNS setup and each subdomain is treated as a separate site by search engines.
Separate domains, such as example.es, suit a business with a legal base in each country, but they cost the most to run and to keep in sync.
Polylang states on its WordPress.org page that the language can be set by the language code in the URL, or you can use a different subdomain or domain per language.
See the Polylang listing at wordpress.org/plugins/polylang/ for the feature list. Pick subdirectories unless you have a clear reason to split the site, and do not change the structure later, since every translated URL would move.
Which translation plugin should you pick?
Pick Polylang for a free start, TranslatePress for visual on-page translation, or WPML for a large site with WooCommerce and a translation team.
The three plugins store translations in your own WordPress database, so the translated text stays yours even if you stop paying. They differ in price, in how you edit translations, and in how much they automate.
Compare them on the figures from their own pricing pages (checked November 2026):
| Plugin | Free version | Paid plans | AI words included |
|---|---|---|---|
| Polylang | Yes, no limit on languages | Pro from €99 a year | None in the free version |
| TranslatePress | Yes, one extra language | €99, €199 or €349 a year | 50,000, 200,000 or 500,000 a year |
| WPML | No free version | €39, €99 or €199 a year | None, 22,500 or 45,000 a year |
Polylang is the only one of the three with a free version that has no limit on languages. WPML has no free version at all, and its cheapest plan covers blogs only.
TranslatePress sits between them, with a visual editor that lets you click text on the live page and type the translation. If you run a store, check WooCommerce support before you buy, since each plugin handles products and checkout text differently.
If the site runs on WordPress.com, paid plans allow plugin installs from a library of 50,000 or more, according to the WordPress.com pricing page. That means any of the three plugins can run there once the plan allows installs.
How do you set up WPML?
Install WPML from its site, run its setup wizard, add your languages, and translate each page in its side-by-side editor.
WPML is not on WordPress.org, so you buy a plan, download the plugin files, and upload them under Plugins, then Add New, then Upload Plugin.
The Multilingual Blog plan costs €39 a year for 1 production site and 3 development sites, the Multilingual CMS plan costs €99 a year for 3 production and 9 development sites, and the Multilingual Agency plan costs €199 a year for unlimited sites, according to the WPML pricing page (checked November 2026).
The CMS plan is the one most business sites need. It adds the Advanced Translation Editor, String Translation for theme and plugin text, Translation Management, page builder support, menu translation and WooCommerce support, as listed on the same pricing page.
It also includes 22,500 AI translation words a year, while the Agency plan includes 45,000. All plans include one year of support and updates and a 30-day money-back guarantee.
WPML works with WordPress 6.0 or higher, as stated on its pricing page. Its support team is available 24 hours a day, 7 days a week, in 14 languages. If you stop renewing, WPML keeps working and the translations keep showing, but you lose updates, as the pricing page FAQ explains.
How do you set up Polylang?
Install Polylang free from WordPress.org, run its setup wizard, add your languages, and create a translation for each post and page.
Polylang needs WordPress 6.8 or later and PHP 7.4 or later, as stated on its WordPress.org page. Install it from Plugins, then Add New, search for Polylang, and activate it. The setup wizard opens at once and walks through the main settings in a few clicks.
Add each language under Languages, then Add New Language, and pick the name, code and flag.
Polylang then adds a language column to the post and page lists, with a plus sign next to each item that has no translation yet. Click the plus sign to create the translation, and Polylang links the two versions together.
Polylang translates posts, pages, media, categories, post tags, custom post types and taxonomies, and it supports RTL scripts, according to its WordPress.org page. It also downloads WordPress language packs by itself when they are ready, and it adds a language switcher block, widget or menu item.
The free version has no machine translation, so you or your translator write each version by hand. Polylang Pro, from €99 a year, adds DeepL machine translation, translated URL slugs and more, as listed on the vendor pricing page (checked November 2026).
How do you set up TranslatePress?
Install TranslatePress free from WordPress.org, add one language, then open any page on the front end and click the text to translate it.
TranslatePress is known for its visual editor. You open the live page, click a sentence, and type the translation beside it, instead of working in a separate admin screen. The free version covers one extra language, and the paid plans add more languages and the SEO Pack.
The paid plans are Personal at €99 a year for 1 site with 50,000 AI translated words, Business at €199 a year for 3 sites with 200,000 words, and Developer at €349 a year for unlimited sites with 500,000 words, according to the TranslatePress pricing page (checked November 2026).
All plans are billed yearly, include one year of updates and premium support, and carry a 15-day money-back guarantee.
Translations are stored in your own server database, and they stay there if you do not renew, as the pricing page FAQ states.
The free version also includes Google Translate integration with your own API key, while the paid plans add TranslatePress AI. For a site that leans on machine translation, read how to translate WordPress with AI before you pick a plan.
How do you handle SEO for translated pages?
Give each language its own URL, add hreflang tags that link the versions together, and translate the title and meta description of every page.
Hreflang tags tell search engines which language version to show for each visitor. Most translation plugins add them for you, but check that they appear on a translated page before you publish it. The guide to adding hreflang tags shows where they go and what a correct set looks like.
Translate the SEO fields, not just the page text. A Spanish page with an English title and description will rank poorly in Spanish search, even if the body is translated.
WPML covers this with String Translation on its CMS plan, and TranslatePress covers it with its SEO Pack add-on on paid plans. Polylang handles translated slugs and SEO fields through its own settings and add-ons.
Keep the URL structure the same in every language. If the English page is /services/, the Spanish page should be /es/servicios/ or /es/services/, not a different shape. A steady structure helps search engines match the versions, and it keeps the hreflang tags simple to check.
How do you keep translations up to date?
Translate new pages before they go live, review machine translations by hand, and re-check the switcher after every theme or plugin update.
Machine translation is a draft, not a finished page. WPML includes 22,500 AI words a year on its CMS plan, and TranslatePress includes 50,000 on its Personal plan, but both expect a person to read the result before it goes live.
A wrong translation on a price page or a legal notice costs more than the time saved.
Set a routine for updates. When an English page changes, its translations go out of date at once, so update them in the same session. Keep a short list of pages that change often, such as pricing, contact and legal pages, and check them first after each change.
Test the site in each language after updates. Open the switcher, move between languages, and confirm the menu, footer and forms all switch too.
The guide to setting up a staging site shows how to run these checks on a copy before they reach the live site. A site with one broken language looks worse than a site with one language done well.
Frequently asked questions
Should I use subdirectories for each language?
For most sites, yes. Subdirectories keep all languages on one WordPress install and one domain, which keeps backups, updates and links simple. Subdomains and separate domains suit large sites with a team per language, but they cost more to run and to keep in sync.
Is there a free multilingual plugin for WordPress?
Polylang is free on WordPress.org with no limit on languages, but it has no machine translation in the free version. TranslatePress free covers one extra language, and its Personal plan is €99 a year. WPML has no free version; its Blog plan is €39 a year.
How much does WPML cost?
WPML Multilingual CMS costs €99 a year for 3 production sites and includes 22,500 AI translation words, String Translation, Translation Management and WooCommerce support. The Blog plan costs €39 a year, and the Agency plan costs €199 a year for unlimited sites.
Can I use automatic translation for my site?
Yes, but treat the result as a draft. WPML includes AI words on its CMS and Agency plans, and TranslatePress includes AI words on all paid plans. Read every machine translation before it goes live, since errors on price or legal pages cost more than the time saved.
What are hreflang tags and do I need them?
Hreflang tags link each language version of a page together so search engines show the right one. Most translation plugins add them for you. Also translate the title and meta description of every page, and keep the URL structure the same in each language.
Sources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


