Key takeaways
- Localisation adapts the whole site for a language and a place: the words, and also the layout, formats, images, examples and speed.
- Choose a few locales from evidence and your mission. Two well-maintained languages beat six stale ones.
- Give every language version its own URL, link the versions with hreflang, and suggest a language rather than redirecting people.
- Set up the translation workflow in the CMS before anyone translates: one source language, a glossary and a fallback rule.
- Design for the longest language and every script, including right-to-left, and test each version on a slow phone and with a native speaker.
What is website localisation, and how is it different from translation?
Website localisation is adapting a whole site for a language and a place: the words, but also the layout, formats, images, examples, legal pages and performance. Translation changes the text. Localisation makes sure the translated page still reads naturally, displays correctly and works for the person in front of it.
A translated page with dates in the wrong order, a currency nobody uses there, a font that can’t show the script or an example that means nothing locally is not localised yet. The steps below take a site from one language to several, in the order the decisions need to be made.
The sections below take each step in turn, with what to decide and what to check.
Publishing in several languages?
Research institutes and digital public goods often need several languages and several audiences on one site. Tell us who you publish for.
Step 1: choose your locales from evidence
Start with the few languages and countries that matter most, not with a long list. A locale is a language plus, where it matters, a country: Spanish for Spain and Spanish for Mexico are two locales; Hindi for India is one.
- Look at your data. Your analytics show where visitors already come from and which browser languages they use.
- Look at your mission. A research institute publishing for policymakers in several states, or a global open-source project with country partners, may need languages that the traffic data doesn’t show yet.
- Decide language or country. If the content is the same everywhere and only the language changes, target languages. If prices, laws, offices or offers change by country, target countries.
- Budget for upkeep. Every locale has to be kept up to date. Two well-maintained languages beat six stale ones.
Step 2: pick a URL structure, and add hreflang
Give every language version its own URL, then tell search engines how the versions relate. Never serve different languages at the same URL based on cookies or location, because search engines and shared links will only ever see one.
Then add hreflang annotations, in the page head, in HTTP headers or in the XML sitemap:
- Each version lists every language version, including itself.
- The links are reciprocal: if the English page points to the Hindi page, the Hindi page points back.
- Use language codes such as
hioren, with a region code where you target a country, such asen-GBores-MX. - Add an
x-defaultversion for visitors whose language you don’t serve.
Don’t redirect visitors automatically by IP address or browser language. Suggest the likely version with a banner, and add a language switcher in the header that keeps the visitor on the same page in the new language rather than sending them to the home page. Name each language in its own script: “हिन्दी”, not “Hindi”.
Step 3: set up the translation workflow in the CMS
The CMS decides how painful localisation will be for years, so set it up before anyone translates a word.
- Translate per field, not per page copy. Most CMSs store translations per locale, and headless systems such as Contentful can localise per field, so a layout change happens once.
- One source language. Edits start in the source and flow to translations, which are flagged as out of date when the source changes.
- A glossary. Fix how key terms, programme names and product names are translated, and which stay in English.
- A translation management tool for volume. Tools such as Crowdin, Lokalise or Phrase handle translation memory, reviewer workflow and machine-translation drafts.
- Human review where meaning matters. Machine translation gives a first draft; findings, claims and anything a reader acts on need a fluent reviewer.
- A fallback rule. Decide what a visitor sees when a page isn’t translated yet: the source language with a clear note is better than a blank page.
Step 4: design layouts that survive translation
Design with the longest language in mind, not the one the mock-ups were written in. Translated text is often longer than English, and some scripts need more line height.
- Let components grow. Buttons, menus and cards should wrap or expand, never truncate.
- No text inside images. Text in images can’t be translated, searched or read by screen readers.
- Fonts for every script. Check that your typeface covers each script you publish in. The Noto family covers most scripts if your brand font doesn’t. Indic scripts such as Devanagari and Tamil need correct shaping for conjuncts, so test with real text, not placeholder Latin.
- Images and examples that travel. People, settings and examples should make sense to each audience, or be swapped per locale.
- Colour and icons with care. Meanings vary between cultures, so don’t let colour or a gesture icon carry the meaning on its own.
Step 5: support right-to-left scripts
If you publish in Arabic, Urdu, Hebrew or Persian, the whole layout mirrors, not just the text.
- Set
dir="rtl"and the rightlangon the page. - Use CSS logical properties (
margin-inline-start,padding-inline-end,text-align: start) so one stylesheet works in both directions. - Mirror directional icons such as arrows and back buttons, but not logos, media controls or charts with a time axis.
- Test mixed content: English product names, numbers and URLs inside right-to-left sentences.
Step 6: format dates, numbers, currencies and names per locale
Formats are where a page quietly feels foreign. 03/04 is March in one country and April in another; a large number is written as 1,00,000 in India and 100,000 elsewhere.
- Use the browser’s
IntlAPIs (Intl.DateTimeFormat,Intl.NumberFormat) or your framework’s locale tools, which draw on the Unicode CLDR data, instead of hand-writing formats. - Write dates unambiguously where possible: “4 March 2026”.
- Show prices in the currency people pay in, and say so.
- Let name, address and phone fields accept local formats: not everyone has a “first name” and a “last name”.
- Handle plurals properly with a message format that supports them, rather than adding an “s”.
Step 7: keep pages light for slow networks
A global audience includes people on slow mobile connections and older phones. Performance is part of localisation.
- Subset web fonts to the characters each language needs, and load only the scripts a page uses.
- Serve images in modern formats at the right size, and lazy-load what’s below the fold.
- Use a CDN with edge locations near your readers.
- Offer large reports as an HTML summary plus a downloadable file, with the file size shown.
- Test on a throttled mobile connection, not only on office broadband.
Step 8: make every language version accessible
Accessibility has to be checked in every language, not only the source. Accessible design under WCAG 2.2, the W3C’s current accessibility guidelines, applies to each version.
- Set the
langattribute on every page, and on any passage in a different language, so screen readers pronounce it correctly. - Translate alt text, captions, transcripts, form labels and error messages, not only body copy.
- Check contrast and focus states with each language’s fonts, which can render thinner.
Our post on accessible website design goes into the details.
Publishing in several languages: research institutes and digital public goods
Research institutes, policy bodies and digital public goods often have the hardest localisation job: dense content, several audiences and limited translation budgets. Five patterns help.
Our page on websites for digital public goods covers how to give each audience its own route in, and research website design covers publications and data. For an Indian government site, the GIGW 3.0 checklist adds its own language rules, such as a bilingual site with every language updated together.
Tailwebs built the MOSIP website. MOSIP is an open-source digital identity project with an international audience. We have also shipped sites and chatbots in Indian languages other than English.
Before a launch, our research website checklist is a useful pass over publications, data, accessibility and search.
Privacy and consent across countries
Privacy and consent rules differ by country, so a global site needs to know where its readers are and what data it collects. Keep forms and analytics to the data you need, show consent choices in the reader’s language, and get legal advice for each market you target. For an introduction to the main data protection laws, see GDPR, CCPA and DPDP compliance.
A launch checklist for a multilingual site
Ten checks before a multilingual site goes live. Tick the ones you have done:
Web design for global audiences is never finished: new pages, new languages and new readers keep arriving. Build the structure once, keep the workflow simple, and each new language becomes a content task rather than a rebuild.
