Multilingual Website SEO

Multilingual SEO is the language half of the international matrix: the same offer serving several languages, with the goal that each language's searchers find a version that reads native and ranks locally. The machinery is settled (separate URLs, hreflang, per-language everything); the quality bar is where multilingual sites actually separate — because a translated page is not yet a translated search asset. Here's the complete practice.

The non-negotiable foundation: separate, crawlable URLs

Each language at its own stable URL (/de/seite/, per the structure decision) — which rules out the classic anti-patterns: cookie/session-based language swapping on one URL (crawlers see one language; the others don't exist), JS-only translation layers with no URLs, and auto-redirecting by browser locale or IP (the switcher guide's cardinal sin — Googlebot crawls mostly from the US and gets trapped in your English version; users get overridden; everyone loses). Serve every visitor the URL they asked for, suggest alternatives politely, wire the versions with hreflang — the whole pattern.

Translation as search work, not just language work

1. Keywords re-originate per language — the market research guide's founding fact: translating your keyword list produces the phrases a translator would use, not the phrases searchers use (the German buyer's actual query is discovered in German, per market, with local SERP reads). Titles, headings and the map itself rebuild from local demand.
2. The quality bar is the local SERP's: per the translation-tier guide — money pages and competing content get native-quality treatment; the bar isn't "understandable", it's "the best answer in this language", because that's what it competes against.
3. Everything translates: titles, metas, slugs (localised URLs read native and rank better — /de/preise/ not /de/pricing/), image alts, schema text fields, and the template furniture (breadcrumbs, CTAs) — the half-translated page whose chrome stays English is the give-away of process gaps, and localisation beyond language (formats, currency, examples) finishes the job.

The per-language operations

Each language is a small publication, not a mirror: prioritised coverage (money pages and top performers first — full-archive translation is rarely the right first spend; thin-but-complete beats broad-but-abandoned per the standing doctrine), internal links within the language (German pages linking German siblings — cross-language links are for the switcher, not the prose), per-language Search Console segmentation (folder-level properties or filters — each language's chain read separately, because a healthy English burying a stalled French is what blended dashboards do), and maintenance parity: the refresh discipline per language, since translations rot at the same speed as originals plus the drift from their source.

Frequently asked questions

Which languages should we add first?

By the same portfolio math as market sequencing: demand (your analytics' existing foreign-language visitors are the pre-validated vote), commercial fit, and SERP winnability per the local difficulty read — many non-English SERPs are dramatically less competed, which is the multilingual opportunity in one sentence. One language done whole per cycle.

Do we translate the blog too, or just the money pages?

Phase it: money pages and the highest-performing evergreen first (proven assets travel), then the audit's winners per language performance — full-blog mirroring is the completeness instinct misapplied, and each language's own demand research should increasingly steer its calendar (some content deserves to originate in German).

Same language, multiple regions — multilingual or multi-country?

Multi-country wearing familiar clothes: en-US/en-GB versions differ by localisation not translation, need hreflang most (the near-duplicate problem), and justify separate versions only where the differences are real (spelling, currency, offers) — otherwise one version geotargeted broadly serves better than cloned folders. The matrix names it; the usual engines rank it — localised content and per-market authority (sprechen Sie mit uns).