Planning a Multilingual Website: Content, Navigation and Maintenance

Planning a Multilingual Website: Content, Navigation and Maintenance

A multilingual website works when each language version is planned as a complete site for real readers, not as a translation job squeezed in at the end. Before anything is built, decide which languages you need and why, what each audience needs, how visitors will switch between versions, and who will keep every version up to date. The technical side – URL structure and hreflang – follows from these decisions, so we only touch on it briefly here.

Start with markets, not languages

"We need English and German" is a starting point, not a plan. For each language, write down:

  • Who the readers are – customers abroad, foreign residents in your country, partners, tourists, job applicants;
  • What they need to do – request a quote, order, book, check specifications, find a distributor;
  • Whether you can serve them – can someone answer an enquiry, a call or a complaint in that language? Do you deliver to their country?
  • What is different for them – prices, delivery terms, payment methods, legal information, product range.

The last two questions often change the plan: a language version that invites enquiries nobody can answer does more harm than good.

Decide what gets translated – and what gets localised

Not every page has to exist in every language. The common approaches:

ApproachWhen it fitsWhat to watch
Full parity – every page in every languageYou sell the same thing to all audiencesHighest translation and maintenance effort
Core pages only – home, services or products, about, contactSecondary markets, partners, foreign residentsSay clearly that some content exists in one language only
Separate content per marketDifferent offer, prices or regulations by countryEffectively several sites; plan budget and people accordingly

Whichever you choose, localise rather than just translate. In its research on international B2B websites, Nielsen Norman Group (NN/g) advises making sure content is actually localised, not translated verbatim: the right tone, the measurement systems and date formats the audience expects, and local contact details where you have them. The same research found that regional versions commonly left out key information such as price. A shorter version is fine; one missing the facts people need to decide is not. List in the plan:

  • prices, currency, VAT wording, delivery and return terms;
  • date, number and address formats, phone numbers with the country code;
  • examples and project descriptions that make sense to that audience;
  • legal pages checked by someone who knows the requirements;
  • images containing text, PDFs and videos.

Machine translation: a draft, not a finished page

Machine and AI translation make a first draft cheap, and that is a sensible start. Before publishing, though, someone who knows both the language and your business should review terminology, tone and anything that creates an obligation – prices, guarantees, terms. Google's spam policies describe "scaled content abuse" – generating many pages mainly to manipulate rankings – and list automated transformations such as translating among the ways it is done when little value is added for users. Translating your own useful pages for a real audience is fine; mass-producing thin language versions to catch search traffic is not. A short glossary – service and product names, terms that must never be translated – helps every translator, human or machine.

Navigation and the language switcher

W3C's internationalisation guidance recommends adding links to the other language versions on every page and not hiding them, because a visitor may be looking at a page full of text that means nothing to them. Specific points from W3C and NN/g:

  • Placement: in NN/g's studies, users looked to the upper right corner to change a country or language setting. On mobile, put the switcher above the fold or in the menu, not only in the footer.
  • Language names in their own language: "Deutsch", "Español", "Български" – not "German", "Spanish", "Bulgarian" written in the language of the current page.
  • Flags with care: W3C advises against using flags to identify languages – flags represent countries and suit country versions, not translations. NN/g does not recommend a flag alone either.
  • Language and country separately: if you sell in several countries, NN/g recommends letting users change language, country and currency independently.
  • Same page, other language: the switcher should lead to the equivalent page, not back to the home page. Decide in advance what happens when a page has no translation.

Menus need planning as well. A label that is short in one language can be long in another; NN/g suggests allowing 50% more room for languages other than English. Test the design with the longest real texts, not placeholder words.

Suggest, don't force

It is tempting to detect where a visitor is and send them to "their" version automatically. W3C advises being wary of using IP addresses or location to guess a reader's language – think of an expat or a business traveller. The browser's language setting is a better signal, and NN/g recommends defaulting to the version that matches it. Google, however, recommends avoiding automatic redirects between language versions, because people and search engines may then never reach every version; Googlebot usually crawls from the USA without sending a language preference. The practical compromise: use the browser language at most to suggest a version ("This page is also available in English") or to pick a default before the visitor has chosen, never to lock anyone out – and remember the visitor's choice.

We have seen how fragile automatic detection can be. On auto-data.net, a multilingual car specifications catalogue with an Android and iOS app, an Italian user's app stayed in English after the language codes sent by the device changed from "it" to "it,it-IT,it-CH". The fix was to normalise language codes in the API. Whatever you detect automatically, test it with real device settings and keep a manual way to switch.

The technical part, briefly

Google recommends a separate URL for each language version rather than switching language with cookies, connecting equivalent pages with hreflang, and one language per page – Google determines a page's language from its visible content, so side-by-side translations make that harder. Folders such as /de/, subdomains or separate domains: decide at the planning stage. When we split our own site, Bulgarian moved to seoandweb.bg and English to seoandweb.eu, connected with hreflang and around 45 permanent (301) redirects from the old addresses. The details deserve their own article; for planning, know that the structure is hard to change later – see redesigning a site without losing Google rankings.

The parts that usually get forgotten

  • form labels, error messages and confirmation pages;
  • automatic emails – order confirmations, password resets, enquiry receipts;
  • the cookie banner and consent texts;
  • on-site search, filters and "no results" messages;
  • page titles and meta descriptions for each language;
  • 404 pages, PDFs and downloadable price lists;
  • the admin panel: can editors see which pages are missing or outdated in each language?

Maintenance: who keeps the versions in sync

Many multilingual sites look fine at launch and drift apart within a year: a price changes in one language but not in the other, a new service appears in one version only. A few rules agreed before launch prevent most of this:

  1. A source language. Changes start in one version and flow to the others.
  2. An owner for each language – a person who approves texts and answers enquiries in that language.
  3. A trigger. Every change to a page in the source language creates a task for the other versions. A well-planned admin panel can flag pages that were edited after their translation.
  4. A review rhythm. Once a quarter, compare the key pages across languages: prices, contact details, services, legal texts.
  5. Separate measurement. Look at each language version separately in analytics and in Search Console. A version with no visits or enquiries after several months may need better content – or may not be needed at all.

Budget realistically: every language multiplies not only the translation cost but also the ongoing editing work. Our article on what a website's price depends on covers languages alongside the other cost factors.

If you are planning a site in two or more languages, put these decisions into your brief – our guide to writing a website brief that gets comparable quotes shows how. We build multilingual websites and can plan the admin panel around the way your team will keep the versions in sync, and our content marketing work can cover preparing and localising the texts. Contact us to talk through your languages and markets.

Sources

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.