A business with a website in Spanish, English and French can have hreflang perfectly configured and still lose visitors over a completely different problem: the language switcher is hidden in a corner, or the button text gets cut off because the same word takes twice as many characters in German. Hreflang solves a search engine problem; multilingual design solves a human problem, and they are different things that need to be worked on separately.
Where the switcher should sit, and where it almost never works well
The most recognisable position for the visitor is the top-right corner of the menu, visible without having to search, with the current language clearly marked so there is no doubt about which version they are on. Hiding it in the footer, even though technically it is "there", greatly reduces the odds anyone finds it in time, especially if they landed on the wrong version by a geolocation error.
The invisible problem of text expansion
A button that says "Contact" in English can turn into "Kontaktieren Sie uns" in German, almost three times as long. If the design was only built with English in mind, that button visually breaks the moment it gets translated. The fix is not to translate worse so it fits: it is to design components with extra room from the start, thinking of the longest language you plan to support, not the shortest.
Flags yes, flags no: a debate that has a practical answer
Using a flag to represent a language is visually convenient, but it mixes up two different concepts: language and country. English is not just spoken in one country, and using the UK or US flag raises doubts about exactly which version that is. The clearer alternative, though less visually striking, is the language name written in its own language ("English", "Français"), which leaves no room for doubt.
What happens if you auto-detect the browser's language
Automatically redirecting based on browser language can help, but it should always be done with a visible manual option to switch, and without forcing a redirect the user cannot undo. Nothing is more frustrating than getting stuck on the wrong language version with no way out.
Frequently asked questions
Should the language switcher always show every language, even with only two versions?
Yes, clearly showing the available options avoids the feeling that the site is incomplete or that switching languages is not even possible, even if only two versions are active.
Should I translate literally or adapt content to each market?
It depends on the type of content: prices, legal references or specific cultural examples usually need real adaptation, not just word-for-word translation, to make sense in each market.
What about images with text baked directly into them in several languages?
That is one of the most commonly forgotten points: if the text is "burned" into the image itself, you need a version per language, because it cannot be translated afterwards with CSS or any automated tool.