Multilingual WordPress set-up

Where WordPress stands

The WordPress project's roadmap lists four phases, the fourth of which is multilingual: a core implementation for multilingual sites ¹. The roadmap names that phase without a date, so for now a WordPress site in several languages relies on one of two routes.

• A multilingual plugin on a single installation. The plugin stores which posts and pages are translations of each other, adds a switcher, and can output hreflang. Several established plugins take this route with different approaches to storage and pricing.
• A multisite network, with one site per language and a plugin or custom code linking equivalent pages across sites. This suits organisations whose language versions are run by separate teams.

How we choose between them

We do not resell any plugin and have no affiliate arrangements with plugin makers. The choice comes from your situation, which we work through with you:

The outcome is a short written recommendation with the reasons, so the decision can be revisited later by someone who was not in the room.

What we configure

1. The chosen plugin or network, with languages, default language and address structure set up.
2. Translated slugs, if your plugin supports them and you want them.
3. A language switcher in the header, built to the principles in our switcher guide.
4. Hreflang output checked against Google's requirements, including return links on every template ².
5. XML sitemaps that include every language.
6. Language tags on each page, matching its content, as WCAG 2.2 criterion 3.1.1 requires ³.
7. Theme strings, menus and widgets translated or prepared for translation.
8. A tested route for exporting content to translators and importing their work.

Moving an existing site

If your site already runs in one language, adding a multilingual plugin is a change to its structure. We take a backup, set everything up on a staging copy, and test there before anything reaches the live site. Existing addresses in the original language stay the same unless you decide otherwise.

If the site already runs a multilingual plugin that is not working well, the first step is a review of what it does today. Switching plugins means migrating the record of which pages belong together, and that migration needs care to avoid losing translations or creating one-sided hreflang pairs.

Editing workflow

A multilingual set-up only works if editors can use it. We write a short guide for your team covering how to create a translation of a page, how to see which pages are missing in which language, how to send content to translators, and what to check before publishing. For larger teams, the translation workflow service goes further.

What is not included

Plugin licence fees are paid by you directly to the plugin maker. Translation is done by translators you appoint. Custom theme development beyond what the multilingual set-up needs is quoted separately.

Price

From CHF 4,500 to set up a multilingual plugin on an existing WordPress site in up to three languages, plus VAT where applicable. Multisite networks, shops and sites with complex page builders are quoted after a first look. See pricing for the other starting points.