Give each language its own home
Dutch and English pages each belong on a fixed, indexable URL. They use self-referencing canonicals and reciprocal hreflang links to their equivalent version.
That is clearer than replacing text after load based on browser language. Search engines and visitors can then share the exact version they mean.
- Dutch on the root route
- English under /en
- Self-referencing canonicals
- Reciprocal hreflang and an x-default
Suggest, but never lock people in
Country and browser language can help suggest a suitable version on the first visit. The language switch must remain visible and a manual choice should take priority.
Avoid unconditional IP-based redirects. They can send travellers, VPN users and crawlers to the wrong language.
Translate meaning, not just words
A good English version translates navigation, forms, metadata, error messages, structured data and legal explanations too. The message can become natural English as long as facts and project context remain consistent.
Google treats HTML tags, HTTP headers and sitemap hreflang as equivalent methods. Using several methods provides no additional search benefit and only makes sense when they are maintained automatically from the same source.
Test both languages as separate user journeys. A perfect homepage with a half-translated form is not a multilingual website.
Primary sources
The factual and technical claims in this article were checked against these sources.
