Topic Policy and research

Web design for global audiences: a localisation guide

The short answer

Web design for global audiences means planning a site so each country or language gets content it can read, trust and load quickly. That covers chosen locales, clear URLs with hreflang, a translation workflow in the CMS, layouts that survive longer text and right-to-left scripts, local formats, light pages for slow networks, and accessible design.

Written by

Siddharth Kajaria, Founder and CEO

Published

Updated

Reading time

12 min read

One red plug surrounded by four travel adaptors, each with a different pin shape for a different country's socket.
In this post12 min read
  1. What is website localisation, and how is it different from translation?
  2. Step 1: choose your locales from evidence
  3. Step 2: pick a URL structure, and add hreflang
  4. Step 3: set up the translation workflow in the CMS
  5. Step 4: design layouts that survive translation
  6. Step 5: support right-to-left scripts
  7. Step 6: format dates, numbers, currencies and names per locale
  8. Step 7: keep pages light for slow networks
  9. Step 8: make every language version accessible
  10. Publishing in several languages: research institutes and digital public goods
  11. Privacy and consent across countries
  12. A launch checklist for a multilingual site

Key takeaways

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.

  1. Choose your locales

  2. Pick a URL structure

  3. Set up the CMS workflow

  4. Design for translation

  5. Support right-to-left

  6. Format per locale

  7. Keep pages light

  8. Make every version accessible

The sections below take each step in turn, with what to decide and what to check.

Publishing in several languages?

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.

Subdirectories, subdomains and country domains compared for a multilingual site
Compared onSubdirectoriesexample.org/hi/Subdomainshi.example.orgCountry domainsexample.in, example.co.uk
Set-up effortEasy to set up, and low upkeep: one domain on one hostEasy to set up, and each version can run on a different serverThe most work: a domain to buy and secure per country, more infrastructure, and some country domains have their own registration rules
How hreflang worksThe same in all three: in the page head, in HTTP headers or in the XML sitemap. Every version lists itself and every other version.The same annotations. Alternate versions don’t need to share a domain, so subdomains link to each other like pages on one site.The same annotations, across domains.
Who runs itOne team and one system for every languageSeparate systems or teams per language are possibleEach country can be close to a separate site, with its own team and content
What readers seeThe language is in the path, but readers may not read it as a countryThe language is in the address, but readers may not read it as a countryThe clearest local signal in the address, though each country domain can target only one country
Fits whenMost organisations: one domain, one site, simple to runLanguage versions run on separate systems or by separate teamsEach country is close to a separate site, with its own team and content

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 hi or en, with a region code where you target a country, such as en-GB or es-MX.
  • Add an x-default version 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 right lang on 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 Intl APIs (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 lang attribute 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.

5 patterns

Generic guidance, not client projects

Research and public-interest publishing

  1. Translate summaries first

    Needs
    A summary and key findings written for each report, so there is something short to translate.
    Watch for
    A long report half-translated, which serves no reader well.
  2. Keep reports findable in every language

    Needs
    A report page per language, linked to the others with hreflang.
    Watch for
    One PDF link that only the source-language reader can find or use.
  3. One glossary across the organisation

    Needs
    A glossary in the CMS or translation tool, with an owner.
    Watch for
    The same programme named three ways in three reports.
  4. Community translation, with review

    Needs
    A translation tool partners can use, and a fluent reviewer per language.
    Watch for
    Unreviewed translations of findings or anything a reader acts on.
  5. Audiences, not only languages

    Needs
    A route from the home page for each audience, in each language you publish.
    Watch for
    Translating the site while every audience still lands on the same page.

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 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:

10 checks before launch

Structure

Show or hide the checks4 checks
  1. 01 Locales chosen, each with an owner

    Done when
    Why it matters
  2. 02 One URL per version, with hreflang

    Done when
    Why it matters
  3. 03 A switcher that keeps the visitor on the page

    Done when
    Why it matters
  4. 04 The CMS workflow is set up

    Done when
    Why it matters

Read next Research website design

Design and formats

Show or hide the checks3 checks
  1. 05 Layouts tested with every script

    Done when
    Why it matters
  2. 06 Formats per locale

    Done when
    Why it matters
  3. 07 Light pages on a slow connection

    Done when
    Why it matters

Read next Accessible website design

Content and launch

Show or hide the checks3 checks
  1. 08 lang set; alt text and captions translated

    Done when
    Why it matters
  2. 09 Each version read by a native speaker

    Done when
    Why it matters
  3. 10 Analytics segmented by language

    Done when
    Why it matters

Read next Research website checklist

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.

02 FAQ

Questions, answered

What are the steps to localize a website for global audiences?
Choose your locales from evidence, pick a URL structure and add hreflang, set up translation in the CMS with a glossary, design layouts that handle longer text and right-to-left scripts, format dates, numbers and currencies per locale, keep pages light for slow networks, make every language version accessible, then test each one with native speakers before launch.
Should a multilingual site use subdirectories, subdomains or country domains?
Subdirectories such as /fr/ or /hi/ are the simplest to run and keep everything on one domain, so they suit most organisations. Country domains send the strongest local signal but mean separate domains to buy, secure and build up. Subdomains sit in between. Choose by how separate each country's content and team really are.
Is machine translation good enough for a website?
Machine translation is a useful first draft, especially with a glossary, but it is not enough on its own for pages that carry meaning: policy findings, product claims, legal text or anything a reader acts on. Have a fluent reviewer check those pages, and label any content that is machine-translated.
Does a global website need hreflang?
If you publish the same content in more than one language or for more than one country, it is strongly recommended. Google can sometimes find alternate versions without it, but hreflang annotations tell search engines which version suits which reader, so a Hindi speaker finds the Hindi page. Each version should list every other version and itself, and an x-default can point to the fallback page.
Have business queries?
Chat with us