Multilingual website SEO: a practical guide to ranking in every language.

1. Pick a URL structure

This is the first decision, and the hardest to undo later. There are three common options.

• Subdirectories (example.com/fr/): one domain, one property to manage, and every language benefits from the site's overall authority. For most projects, this is the sensible default.
• Subdomains (fr.example.com): handy when each version is hosted or run separately. The trade-off is slightly heavier set-up and monitoring.
• Country domains (example.de, example.fr): a very clear geographic signal for users and search engines. But you have to buy, renew and maintain several domains, and each one starts from scratch.

Avoid URL parameters such as ?lang=fr. They work, but they are harder to read and easier to break. Whatever you choose, apply it consistently across the whole site.

2. One URL per language

This is the golden rule. Every language version of a page needs its own address. Googlebot usually crawls without cookies, from US IP addresses, and without asking for a particular language.

If your site serves English or French on the same URL depending on a cookie or the browser's language, Google will probably see only one version. The others may never be indexed.

3. Connect versions with hreflang

The hreflang annotation tells Google that a page exists in other languages, and which ones. It helps the search engine show the right version in its results. Three rules matter:

1. Make it reciprocal. If the English page points to the French one, the French page must point back. Each page should also list its own URL. Without the return link, the annotation may be ignored.
2. Use valid codes. The language follows ISO 639-1 (en, fr, de), optionally followed by an ISO 3166-1 region (en-GB, fr-CA). Writing en-UK is a classic mistake: the correct region code is GB.
3. Set a fallback. The x-default value marks the page to show when no language matches, often a language picker or your main version.

You can declare these links in each page's <head> with <link rel="alternate" hreflang="…"> tags, or in your XML sitemap. Both methods are equally valid: choose one and keep it up to date. On large sites, the sitemap is usually easier to maintain.

4. Don't redirect automatically

Redirecting visitors based on their browser language or IP address sounds helpful. It is not recommended. A traveller, an expat or a search engine crawler ends up stuck on a version they did not choose.

Offer a visible language switcher instead, on every page, linking to the equivalent page rather than the home page. A discreet banner suggesting a better-suited version is fine too, as long as it does not force the switch.

5. Translate everything, not just the body copy

A half-translated page sends mixed signals. Remember to localise:

• the title tag and meta description;
• the URL slug (/fr/tarifs rather than /fr/pricing);
• image alt text;
• structured data (name, description, FAQ and so on);
• menus, buttons, forms and error messages.

6. Machine translation: a starting point, not the finish line

Machine translation has become remarkably good. It saves real time on a first draft. But publishing unreviewed output is still risky: clumsy phrasing, mistranslations, the wrong tone.

More importantly, translation is not localisation. People search with different words in different countries. British users look for a quote or a flat; American users for an estimate or an apartment. Run fresh keyword research for each market, then have every page reviewed by someone fluent in the language.

7. Regional variants and duplicate content

Near-identical pages in en-GB and en-US are not penalised. However, Google may pick only one of them as the main version. Hreflang helps it serve the right variant to each audience.

To make these pages genuinely distinct, add what actually differs: currency, prices, contact details, legal information, local examples. If nothing changes, a single English version is often enough.

8. A self-referencing canonical for each language

Each version should carry a canonical tag pointing to itself. Never set the English page as the canonical of the French one: you would be telling Google to ignore the translation. Canonical tags and hreflang must tell the same story.

9. Track performance by language

In Google Search Console, the Performance report lets you filter by country and by page. With subdirectories, you can also add a URL-prefix property for each folder (/fr/) to monitor it separately. Keep an eye on indexed pages, any errors, and the queries that bring traffic in each language.

Putting it into practice with a CMS

These rules are simple on paper but tedious to apply by hand across dozens of pages. This is where a multilingual CMS earns its keep. In Plumixia, for instance, the language variants of a page are linked together, and hreflang tags (including x-default) are generated automatically in the sitemap. Assisted translation, available through the built-in MCP server among other routes, produces drafts that a person reviews before anything goes live.

To find out more, explore our multisite and multilingual features and the built-in SEO tools. Planning a site in several languages? Let's talk about your project.

Frequently asked questions