One design, every language, on Polylang or WPML
Install Polylang or WPML on the site and the theme recognizes it by itself. Pages, fields and site settings get a version per language, and the admin helps translate them, so your client does not need a developer to add a language.
Polylang is free · WPML is paid · no extra theme setup
Yes. The same theme works on a one-language site and on a site with Polylang or WPML: no separate build and no extra markup. Each language keeps its own page content, field values and site settings (phone, address, footer text), and the theme’s own admin speaks eight languages.
Languages handled by the theme, not by your markup
Content per language
- Every page field in every language
- Lists and groups translated row by row
- Site settings per language: logo, phone, footer
- Menus per language
Translate helper
- Translate a field with one click
- Translate a whole page, title and text included
- Translate many pages from the page list
- All site strings side by side in one table
Translation engine
- Works out of the box
- Or plug in your own DeepL key
- Machine translation is a draft: you edit it before publishing
Shop in several languages
- With Polylang, product translations share price and stock
- The cart follows the visitor’s language
- Order emails in the language of the order
Add a language in an afternoon
- Step 1
Install Polylang or WPML
Activate the plugin and add your languages. The theme detects which one is running; nothing to switch in the theme.
- Step 2
Create the translations
Use the plugin’s usual “+” next to a page, or translate many pages at once from the page list. Field values come along for you to translate.
- Step 3
Translate and check
Translate fields one by one or the whole page, review the result, then fill the site settings for each language.
Good to know
Translation is a draft
Machine translation saves typing, not reading. Plan for someone who knows the language to review each page.
Polylang or WPML, not both
Run one of them. Moving a site from one to the other keeps the links between translations; field values do not need converting.
Shared shop stock needs Polylang
One stock and price for all translations of a product is built for Polylang. On WPML the shop works per language.
Start from where your design lives
Add a shop and forms to the same site
- Sign up
- Preview your admin
- Subscribe
- Download and update
Cancel any time · 14-day refund · your site keeps working after you cancel
Multilingual WordPress, answered
Do I need to mark up anything for languages?
No. You mark fields once. Polylang or WPML decide which language a page is in; the theme shows the fields of that language.
Which plugin should I choose?
Polylang is free and covers most sites, including a shop with shared stock. WPML is paid; choose it if your client already uses it.
Is the translation automatic?
Only when you ask for it. The helper translates a field, a page or many pages on request, and you review the result before publishing.
What happens to translations when I change the design?
They stay. Each language’s content lives in WordPress, not in the theme. Rebuild the theme and every language keeps its texts.
Can the admin itself be in my client’s language?
Yes. The theme’s admin screens come in English, Russian, Ukrainian, German, Spanish, French, Czech and Latvian, next to WordPress’s own translations.