Give each language its own address

An explicit language URL should take precedence over browser preferences. Automatic selection belongs at an unspecified entry point, with language links that also work without scripts. An article switch should lead to its translation where possible and explain any fallback to a listing.

Look beyond body copy

Navigation, labels, alternative text, text inside images, sharing cards and error pages all need localisation. Longer English text should not be forced into fixed-width buttons. Check keyboard journeys, mobile menus and 200% zoom separately for each language.

Document how translations are maintained

Connect translations through stable content IDs and record dates and publication states explicitly. Each language may have its own pins and ordering, but listings must not mix in untranslated body text. When facts change, review every translation. Language coverage should not depend on runtime machine translation.

Original insights from Diande Technology.
← Back to insights