How does SEO work on a multilingual site?
If your site is published in more than one language, search engines need to find each language as a separate page and show visitors the version in their own language. This article covers the key decisions that shape the search visibility of a multilingual site.
- 01
The short answer
Give every language version a permanent address of its own, connect the versions with hreflang tags, let visitors choose their language instead of forcing a redirect, and publish content that is genuinely prepared for each language. Google's guidance on multilingual and multi-regional sites rests on the same four points.
- 02
URL structure: folder, subdomain, country domain
There are three common options: language folders on the same domain (example.com/de/), subdomains (de.example.com) and country-code domains (example.de). A country-code domain signals the target country most strongly, but every domain needs separate management and builds trust separately. Folders are the easiest to set up and maintain, and the trust the domain has built is shared by every language. Changing the content at the same URL based on a cookie or the browser language is not recommended: the search engine only ever sees one language at that address.
- 03
hreflang and x-default
The hreflang tag tells search engines which pages carry the same content in other languages, so that someone searching in English is shown the English page. The rules are simple but often broken: every version must list all versions including itself, the links must be reciprocal, and language codes must be correct (for the United Kingdom it is “en-GB”, not “en-UK”). For visitors who match no language, the x-default value names a fallback page; this is often a language selector or a home address that opens in the visitor's language. The tags can go in the page head, in the HTTP response headers or in the sitemap.
- 04
Automatic redirects and language choice
Forcing visitors into another language based on their IP address causes two problems: a Turkish speaker abroad or a foreigner in Turkey lands in a language they did not want, and search engine crawlers, which mostly come from a single country, may never see the other versions. The safer approach is to suggest the visitor's language but keep a visible language switcher on every page and remember the choice. Using each language's own name (Deutsch, Français) rather than country flags in the switcher is also clearer.
- 05
Localisation, not just translation
Translating only the menus and leaving the main content in one language makes for a poor experience for readers and a weak page for search engines. The main text, titles, descriptions and any text in images should be translated too. The words people search for change from language to language: a German speaker searches for “Webdesign Agentur”, a French speaker for “agence web”, so each language needs its own keyword research. Machine translation saves time, but text published without a human review loses readers and can fall foul of Google's rules on scaled content.
- 06
Regional targeting and local signals
Language and country are not the same thing: a Spanish page can speak to both Spain and Mexico. If prices, currency, phone numbers, address or delivery terms differ by country, consider separate regional versions (such as es-ES and es-MX); if they don't, one language version is enough. Links earned naturally from sites in your target countries and local business profiles also support visibility there.
- 07
Checklist, and multilingual sites at Doki
Before launch, check: does every language version have its own URL, are the hreflang tags reciprocal and self-referencing, does each version's canonical point to itself, are all languages in the sitemap, and is the language switcher visible on every page? After launch, follow impressions by country and language in Search Console. This site is published in eight languages, each with its own URL and hreflang. If you are planning a multilingual site or adding a new language to your current one, we can plan these steps together at the start of the project.
Related pages
Articles that complete this topic, plus the matching service page.
Let's talk about your project.
Tell us what you need; we will define the scope together.