4.2Multilingual site
The essentials in 30 seconds
- Polylang (free, lightweight) or WPML (paid, comprehensive) organise the versions by language; they do not translate for you.
- Each content item, menu and product has its language versions, with a switcher to move between them.
- The hreflang tag tells Google the language of each version; URL architecture (subdirectory /en/) is the most common choice.
Running mini-case — opening the workshop to Arabic-speaking visitors
Hassan receives requests from Arabic-speaking clients and English-speaking tourists. Samir suggests an Arabic version and an English version of the main pages. He installs Polylang, genuinely translates the content with Hassan's help, translates the menus and checks the URLs and hreflang. He rejects unreviewed machine translation, which would damage the workshop's image.
Sequel to case 4.1 — the shop exists, and the site opens up to new audiences.
1. Organising the languages
WordPress does not handle multilingual sites natively: you rely on a plugin. Polylang is free in its basic version and lightweight; WPML is paid, comprehensive and widely used by agencies. The principle is the same: each content item has one version per language, linked to the others.
You define a default language, then add the others. Each page, post, menu and product has its own versions. Samir starts with the essential pages — home, collections, contact — rather than translating everything at once. The language switcher goes in the header or the menu.
2. Translating and looking after SEO
The plugin organises the versions; it does not translate. Real translation is human work (or a reviewed service): texts, images containing text, documents. Unreviewed machine translation undermines credibility, especially for a craftsperson selling expertise.
On the SEO side, each version has its own URL: the subdirectory (/en/) is the most common choice, ahead of the subdomain. The plugin adds the hreflang tags that tell Google the language of each page and prevent duplicate content. Samir also checks that menus, forms and error messages are translated.
🔎 Concrete example — Opening the workshop in Arabic and English (Samir's case)
Plugin: Polylang.
Languages: French (default), Arabic, English.
Translated pages: home, collections, contact.
Menus: one menu per language + switcher.
URL: /ar/ and /en/.
hreflang: generated by the plugin, checked.
→ Review by Hassan for Arabic.Result: a genuinely bilingual, credible site.
Lesson: three well-translated pages are better than the whole site done automatically.
Section vocabulary
- Polylang / WPML
- The reference multilingual plugins: they link the versions by language.
Simple example: Polylang for a lightweight bilingual site.
What it is not: installing both at the same time.
Reflex: only one multilingual plugin.
- Language switcher
- A menu or flags that let the visitor change language.
Simple example: a switcher in the header.
What it is not: creating versions with no way to switch between them.
Reflex: always accessible.
- Content translation
- The real work of translating pages, menus and products, with review.
Simple example: Hassan reviews the Arabic version.
What it is not: publishing unreviewed machine translation.
Reflex: the plugin does not write the texts.
- hreflang
- A tag telling Google the language and region of each version.
Simple example: the Arabic version flagged as such.
What it is not: leaving several languages with no indication.
Reflex: hreflang = multilingual SEO.
- URL architecture
- The form of the addresses per language: subdirectory, subdomain or dedicated domain.
Simple example: /en/ for English.
What it is not: mixing languages in the same URL.
Reflex: subdirectory = common choice.
In practice — Adding a second language
- Install Polylang and define the languages and the default language.
- Create the version of a page in the second language and genuinely translate the content.
- Translate the menu and add the language switcher to the header.
- Check the URLs per language and the hreflang in the source code.
Ready-to-use script — framing multilingual (25s)
"We can offer your workshop in Arabic and English, but I advise starting with the essential pages, properly translated and reviewed. Unverified machine translation would give the wrong impression. We can expand later."
Set the translation budget from the start: that is the real cost.
Copy-paste template — multilingual plan
PLUGIN: Polylang / WPML
DEFAULT LANGUAGE: _______________
OTHER LANGUAGES: _______________
PAGES TRANSLATED FIRST: _______________
MENUS PER LANGUAGE: yes / no
URL ARCHITECTURE: /xx/ / subdomain / domain
REVIEWED BY A NATIVE SPEAKER: yes / noLocal bilingual
French + Arabic, essential pages, local review.
Tourism
Add English and Spanish, with practical information.
Shop
Also translate products, cart and order emails.
Limited budget
Translate the home page, collections and contact first.
✓ Best practices
- Translate for real, with review.
- Start with the essential pages.
- Check hreflang and URLs per language.
✗ Common pitfalls
- Publishing unreviewed machine translation.
- Forgetting to translate menus and forms.
- Installing two competing multilingual plugins.
Key takeaways
- Polylang or WPML organise the versions by language.
- The plugin does not translate: translation is human and reviewed.
- The switcher and hreflang are essential.
- The subdirectory is the most common URL architecture.
48h Challenge — apply tomorrow
Install Polylang on a test site, add a second language, translate a page and a menu, then check the URLs and the switcher. 30 minutes.
- I choose and configure a multilingual plugin.
- I genuinely translate a page and a menu.
- I check the URLs and the hreflang.
Frequently asked questions
Polylang or WPML?
Polylang is free in its basic version, lightweight and sufficient for a simple site. WPML is paid, more comprehensive and common in agencies, particularly for shops and complex sites. The choice depends on the budget and the needs.
Can I translate only a few pages?
Yes, and it is even recommended at the start: home, collections, contact. The other pages can stay in the main language or be added gradually, provided you do not display broken links.
Is machine translation acceptable?
As a draft, yes; as a publication, no. Unreviewed machine translation contains awkward phrasing and sometimes misunderstandings that damage credibility, especially for a craftsperson or a shop.
Samir wants to offer the site in French and Arabic. Which approach is the soundest?