Adding another language to a website can look straightforward: duplicate the page, translate the copy and add a language switcher.
In practice, that is only part of the job.
Language affects how people understand navigation, what they expect from a button, how search engines find the right version, and whether assistive technology can interpret the content correctly.
Language is part of the user experience
A translation can be grammatically correct and still feel wrong.
A short Norwegian heading may need a different rhythm in English. A call to action that sounds natural in one language can feel too strong or too vague in another.
The goal should therefore be to translate the intention, not simply the words. That matters especially for headings, buttons, forms, error messages, product names and help text.
The useful question is not only whether the translation is correct, but whether the user understands what is happening and what to do next.
Each language version needs a clear technical identity
Google recommends using separate URLs for different language or regional versions and using hreflang to indicate which version is intended for which language or market.
That gives search engines a clearer structure and also gives users stable URLs they can share or bookmark.
Google also advises against relying only on automatic IP-based adaptation. People should be able to choose their language, and each version should be reachable through normal links.
The exact URL structure matters less than keeping it consistent and maintainable.
The language should also be declared in HTML
W3C recommends declaring the default language of a page with the lang attribute on the html element.
This is a small implementation detail with practical consequences. Language information can help screen readers and speech synthesis use the appropriate pronunciation and language processing.
Layout across languages
Different languages need different amounts of space. The interface should be tested with real content in each version.
A button that fits in one language may be longer in another. Navigation, cards, forms and mobile layouts should have enough flexibility for those differences.
The language switcher should be easy to understand
People should not have to search for the language option. Where possible, changing language should keep the user on the equivalent page instead of returning them to the home page.
The harder problem often starts after launch
Launching several languages at the same time is relatively easy. Keeping them current is harder. If one version gets a new price, project or policy, the team needs a clear way to see which other versions also require an update.
A practical content setup should therefore include one clear source for the core content, a status for each language version, responsibility for quality control and a routine for updates.
Translation is only one layer
A multilingual website combines content, language, design, code, SEO and maintenance. When these are planned together, the site feels like one product available in several languages.
For organisations working across markets, multilingual support is best planned as part of the website structure from the beginning.
See also how I work with websites and web design →.