How to prepare a multilingual website without contradictory information

A multilingual website needs more than translated headings. People must understand the offer, conditions, form and reply they receive. Start with languages you can provide support in and the content needed for a decision. Prepare an inventory and name someone responsible for each version. Machine translation may help with drafts, but commercial and operational elements need appropriate review before publication.

By Lyntev. Updated on .
About 6 minutes to read.

The answer starts with the sourceApproved information, defined access and a verifiable answer.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Choose languages based on observed needs
  • Keep offers and conditions consistent
  • Test navigation, forms and replies in every version

Choose the first additional language using evidence

Record requests received, the language used and the tasks those people want to complete. Use necessary, aggregated information without creating excessive customer profiles. Distinguish a visitor’s language from their country: someone in Portugal may prefer English, and a customer in another country may read Portuguese. A flag does not unambiguously represent a language.

Choose a complete initial journey, such as learning about a service and requesting a proposal. Publishing a consistent version of that journey is preferable to translating the homepage while leaving every condition in another language without notice. Confirm who can reply and through which channels. Do not advertise service in a language merely because the editor can generate text in it.

Create an inventory including less visible states

List pages, menus, buttons, captions, fields, errors, confirmations and follow-up messages. Add documents customers need to consult before contracting. Translating only the main content may leave visitors stuck when correcting a field or interpreting confirmation. Also identify files and images containing text, because they need their own preparation.

Link each item to a source and status: awaiting preparation, translated, reviewed or published. If the original changes, its translation must return for review. Do not use the build date as evidence that someone checked the text. Record the actual review and responsible person. A small editorial table may suffice if the team can identify differences without relying on memory.

Create an inventory including less visible states
ItemReview neededAcceptance criterion
Offer and scopeMeaning, exclusions and sector terminologyVersions describe the same service
Prices and conditionsCurrency, unit, renewal and ending the serviceNo translation changes the commitment
FormLabels, examples, errors and confirmationThe full task works in the chosen language
Follow-up contactEmail and available customer serviceThe team can continue the conversation
Associated documentsCorrect version and identified languageThe customer knows what will open

Translate meaning and context, rather than words alone

Explain local abbreviations and adapt format examples without changing facts. A telephone number must remain usable from outside the country. Ambiguous dates can use the month written out; units and currency should be clear. Do not automatically convert amounts or conditions without an approved commercial process. A website in a new language does not itself create an offer valid for every market.

Prepare a short glossary for terms appearing on several pages: appointment, quote, order, payment and cancellation. Have someone competent in the language and service review it. Also test understanding with someone uninvolved in translation. If an expression sounds elegant but the person does not understand the commitment, prefer simple, explicit wording.

Fictional scenario: a private-tour company

A fictional company receives requests in Portuguese and English. It starts by translating the service, practical conditions and enquiry form. A review finds that the English wording appears to confirm a booking while the Portuguese only requests availability. The team corrects the meaning before publication and aligns the message sent after the form, avoiding two different commitments for the same service.

In the next test, someone changes language part-way through reading and remains on the same service. The form retains consistent labels and confirmation explains when and how a reply will arrive. The team tests a later timetable change to ensure both versions return for review. This fictional scenario is neither a recommendation on legal requirements nor a guarantee of international demand.

Decide what to do when a version becomes outdated

Name a responsible person and an internal review deadline suited to the business. When an essential condition changes, do not leave an old translation public as though valid. You may need to suspend the offer temporarily in that version or display a clear updating notice while keeping a working contact channel. The option must match what the team can explain and fulfil.

Avoid publishing dozens of languages nobody reviews or supports. Volume increases the risk of differences in contacts, prices and conditions. A sample of well-translated pages does not prove every error message or document is good. Use a task list for each version and retest it when the system or journey changes. Pages must remain readable on mobile, where longer translations may change the layout.

  • The selector works with a keyboard and has an understandable label.
  • The chosen version covers the offer, conditions and confirmation.
  • The team knows what information changed and who should review it.
  • A link to a document in another language tells visitors that.

Create a worksheet for each language version

Complete the worksheet for one journey before expanding the site. Mark shared elements and those needing adaptation. The inventory should link each original page to its equivalent so later reviews do not leave forgotten pieces. Use stable names and references internally without turning technical codes into text customers must interpret.

Finally, ask someone reading only the new language to explain the service, choose an option and send a test request. Compare their interpretation with the approved offer. Keep corrections and selected terms in the glossary. This procedure creates a quality baseline repeatable for the next language, rather than restarting with isolated, inconsistent translations.

Worksheet for your project

Website language version
Language and initial journey:
Observed need and available customer service:
Equivalent pages and documents:
Commercial terminology glossary:
Fields, errors, confirmations and emails:
Reviewer and actual review date:
Discrepancies found and corrections:
Language-switching test:
Rule when the original changes:
Person responsible for maintaining the version:

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.