When a company redesigns its website, a lot of attention usually goes into the visible details: layout, navigation, page speed, typography, imagery, calls to action and mobile performance.
Translation often comes later.
Sometimes much later.
The English version is designed, written, approved and built first. Then, once everything looks good, someone asks: “Can we translate this into German, French, Arabic or Japanese?”
That is where the problems start.
Website translation is not only about replacing one set of words with another. It affects how people move through a website, how they understand your offer, how much they trust your brand and whether they feel the page was genuinely made for them.
In other words, translation is part of user experience.
And when it is treated as an afterthought, users usually notice.
Translation changes the way a website works
A translated website is not just the same website in another language. It is often a slightly different experience.
Words expand. Sentences shrink. Formality changes. Humour may fall flat. A button that looks neat in English might become awkwardly long in German. A short product message may need more context in Japanese. A phrase that sounds warm and friendly in English may feel too casual in another market.
Even basic interface text can become complicated.
Take a simple call to action such as:
Get started
In English, it is short, direct and widely understood. But the best translation may not be equally short. Depending on the language and audience, the phrase may need to become more formal, more specific or less sales-driven.
The same happens with buttons like:
Request a quote
Book a demo
Create account
Continue to checkout
Upload documents
These are not decorative words. They are part of the journey. If users hesitate, misunderstand or feel uncertain, the design has failed, even if the translation is technically correct.
A common example is English-to-German website translation. German text often needs more room, which can affect buttons, navigation labels and mobile layouts. A neat English CTA such as “Get started” may become longer once translated. If the design has no flexibility, the button either wraps awkwardly or forces the translator into a weaker, less natural phrase.
That is why website translation should be considered early in the design and UX process, not squeezed in at the end.
Good translation protects the user journey
A multilingual website has many small points where trust can be built or broken.
A homepage headline matters, of course. But so do form labels, menu items, error messages, confirmation emails, cookie banners, checkout instructions, privacy notices and help text.
These smaller pieces of content are easy to overlook because they do not feel as visible as the main marketing copy. Yet they often appear at the exact moment when the user is trying to take action.
A customer is filling in an address form, but the fields do not match the way addresses are written in their country.
A user is ready to upload a document, but the instructions are still partly in English.
Someone reaches the checkout, but the translated delivery information sounds unclear or machine-generated.
A visitor sees a legal or privacy notice that uses the wrong level of formality for their market.
None of these issues may look dramatic on their own. But together they make a website feel unfinished. Worse, they make the user feel like an afterthought.
Address forms are a good example. A UK-style form may ask for postcode, county and house number in a familiar order. That structure does not work neatly everywhere. Some countries use apartment numbers differently. Some rely more heavily on region, province or district. Some do not use postcodes in the same way. If a translated website keeps the original form logic, the language may be local, but the experience still feels foreign.
The same applies to ecommerce. A product page may be translated well, but if the returns information, delivery options, payment methods or size guides do not match local expectations, users may still hesitate before buying.
For a translated website, consistency matters. Users should not feel as though they are moving between a polished local experience and a half-translated version of the original site.
Design can break when language changes
Designers naturally work with the words they have in front of them. If those words are in English, the layout is usually shaped around English.
That can create problems later.
English is often compact compared with other languages. A navigation item, headline or button may take up much more space once translated. German, Finnish and Russian, for example, can produce longer phrases than English. Chinese or Japanese may take up less horizontal space, but create different expectations around clarity, hierarchy and tone.
Then there are right-to-left languages such as Arabic and Hebrew, where translation can affect not just text length but the whole visual direction of the page.
This is not only a design issue. It is a usability issue.
If translated text is forced into a layout that was never designed to hold it, the result can feel cramped, broken or unprofessional. Buttons wrap onto two lines. Menus become messy. Headings lose impact. Mobile screens become harder to scan.
For Arabic or Hebrew, localisation can affect the whole interface. It is not enough to translate the words. Navigation, alignment, icons, progress indicators and page flow may need to work from right to left. A checkout or onboarding journey designed only for English can feel visually confusing if it is simply translated and mirrored at the last minute.
A good multilingual website needs flexible design. That means allowing for text expansion, testing translated layouts, avoiding hard-coded text in images and making sure the website can handle different scripts and reading directions where needed.
Translation does not sit outside design. It changes design.
Tone of voice does not translate automatically
Many websites now put serious effort into brand voice. They want to sound friendly, expert, bold, playful, reassuring or premium.
That voice needs to survive translation.
But tone is one of the hardest things to carry across languages. A phrase that sounds confident in English may sound arrogant elsewhere. A joke may not work. A casual expression may feel too informal for a professional audience. A warm message may become strangely flat if translated too literally.
Many global brands already treat localisation as part of the product experience, not just as a language layer.
Airbnb is a useful example. The company does not only translate listing pages. The experience has to work around local currencies, date formats, host and guest expectations, address conventions, trust signals and customer support. A translated button is only one small part of that journey.
The same is true for streaming platforms such as Netflix. Subtitles, dubbing, programme descriptions, artwork and even the way content is presented can vary between markets. The user does not experience this as “translation”. They experience it as whether the service feels natural to use.
For ecommerce brands, the issue becomes even more practical. A checkout page may be translated accurately, but if the delivery information, returns policy, address fields or payment options do not match local expectations, users may still abandon the purchase.
This is why tone of voice matters. So does context.
A playful error message may work for a consumer app, but it may feel wrong in a banking, legal or healthcare setting. A direct sales CTA may feel normal in one market and too pushy in another. A luxury brand may need language that feels restrained and precise, while a lifestyle brand may need something warmer and more conversational.
The translator’s job is not simply to preserve every word. It is to preserve the effect.
That may mean changing sentence structure, replacing idioms, adapting examples or rewriting a line so that it creates the same feeling for the new audience.
This is where translation begins to overlap with localisation and transcreation. The question is no longer only “What does this sentence mean?” It becomes “How should this message work for this audience?”
Machine translation can help, but it cannot own the experience
Machine translation has improved enormously. For internal understanding, rough drafts or large volumes of low-risk content, it can be useful.
But a public-facing website is different.
Your website carries your brand, your credibility and your commercial intent. It is where users decide whether to trust you, contact you, buy from you or move on.
Machine translation may produce a sentence that is understandable, but that is not always enough. Website copy needs to guide, persuade, reassure and convert. It also needs to fit the layout, match the brand voice and make sense within the user journey.
There is also the issue of context.
A word like “copy” is a good example. On a marketing page, it may mean written content. In a software interface, it may mean duplicate. In a legal context, it may refer to an official copy of a document. Without context, even a fluent-sounding machine translation can choose the wrong meaning.
The same is true of words such as “clean”, “free”, “case”, “file”, “claim” or “charge”. Each can mean something different depending on the page, the product and the action the user is expected to take.
For example, “free” on a pricing page might mean no cost. In a product description, it might mean free from allergens or certain ingredients. In a software environment, it might mean available or unrestricted. The wrong choice can make the text confusing, misleading or legally risky.
A human translator or localisation specialist looks at the wider situation. What is the page trying to achieve? Who is the user? What happens before and after this screen? What tone should this brand use? What would sound natural in this market?
That judgement is difficult to automate fully.
The strongest approach is often not “human or machine”. It is knowing where technology can support the process and where expert human review is essential.
Localisation starts before the first page is translated
Many businesses think about translation when they are ready to launch in another market. By that point, the website may already be designed, built and approved.
That can make localisation slower and more expensive than it needs to be.
A better approach is to plan for multilingual use from the beginning.
This might include:
- designing buttons and menus with text expansion in mind
- avoiding text embedded in images where possible
- making sure the CMS supports multilingual content properly
- separating translatable text from code
- planning URL structures for different language versions
- checking whether forms, dates, currencies and measurements need localisation
- creating a glossary for key terms
- preparing tone of voice guidance for translators
- deciding which pages need translation, localisation or transcreation
These decisions do not have to make the initial project more complicated. In many cases, they make the whole process smoother.
It is much easier to build a website that can become multilingual than to repair one that was designed as if English would always be the only language.
A simple example is a website hero banner with text embedded directly into the image. In English, it may look polished. But when the same campaign has to run in French, Arabic or Chinese, every image needs to be redesigned. If the text had been handled separately from the image, localisation would be cleaner, faster and easier to control.
The same applies to websites where menu labels, buttons or system messages are hard-coded. They may work well enough for one language, but they create friction as soon as another language is added.
Real localisation goes beyond the words on the page
A translated website can still feel foreign if the wider experience has not been adapted.
Users may expect different types of proof, different payment methods, different address formats, different levels of formality or different information before they feel comfortable taking action.
For example, a B2B buyer in one market may respond well to a direct “Book a demo” CTA. In another market, the better first step may be a softer “Speak to an adviser” or “Request more information”.
A retail customer may expect prices in their local currency, delivery details that match their region and customer service information in their language.
A legal, financial or medical user may need very clear terminology and a more formal tone because mistakes feel higher risk.
Even images and examples can matter. A campaign that uses humour, cultural references or very local idioms may need more than translation. It may need creative adaptation.
Think about a UK company using a phrase such as “from the high street to the boardroom”. It may make sense to a British audience, but it may not carry the same meaning elsewhere. A literal translation might be understandable, but the local audience may not feel the same connection. In that case, the line needs to be adapted, not simply translated.
This is why website localisation is not just a linguistic task. It sits at the intersection of language, design, culture, marketing and user behaviour.
Translators need context, not just strings
One of the most common mistakes in website translation is sending translators isolated text strings with little or no context.
A spreadsheet of words may be efficient, but it can also create problems.
The translator may not know whether a phrase is a button, a heading, a form label, a navigation item or an error message. They may not see the character limit. They may not know whether the audience is technical, casual, professional or academic. They may not know whether a term appears elsewhere on the site and needs to remain consistent.
Context improves quality.
Useful supporting materials might include:
- screenshots or staging links
- brand and tone of voice guidelines
- target audience notes
- glossaries of approved terms
- character limits for buttons and menus
- explanations of product features or service categories
- notes on whether a page is sales-focused, informational or legal/compliance-related
When translators understand how the content functions, they can make better decisions.
This is especially important for UX microcopy: the small pieces of text that guide users through forms, account areas, checkout flows, software interfaces and support journeys.
Microcopy is easy to underestimate. But when it is unclear, users get stuck.
A phrase such as “Try again later” may seem simple, but in a banking app, a healthcare portal or a legal document upload system, the user may need more reassurance. Has the payment failed? Has the document been saved? Is the action complete? Should they contact support?
The translation has to support the user’s next step, not just repeat the original words in another language.
Website translation should connect teams
A strong multilingual website usually needs more than a translator working alone.
It may involve marketers, UX designers, developers, SEO specialists, project managers and native-language reviewers. Each person sees a different part of the problem.
The designer knows where space is limited.
The developer knows how the CMS handles language versions.
The SEO specialist knows which terms people actually search for in the target market.
The translator understands meaning, tone and cultural expectations.
The local reviewer can spot when something sounds unnatural, even if it is technically correct.
The best results come when these people are not working in separate silos.
For example, an SEO keyword may not translate directly. The literal translation of an English keyword may not be the phrase real users search in another language. A translator and SEO specialist may need to work together to find wording that is both natural and visible in search.
This happens often with service pages. A company may want to translate an English page targeting “certified translation services”, but the best search term in another language may depend on local legal processes, document types and how people actually describe the service. A literal translation may be linguistically correct and still miss the search behaviour of the audience.
A designer may need to adjust a layout after seeing the translated version.
A developer may need to fix a field that cannot handle accents, non-Latin characters or longer text.
These are not failures in the process. They are part of creating a website that works properly across languages.
When translation becomes transcreation
Some website content can be translated quite directly. Product specifications, service descriptions, support pages and technical information often need clarity, accuracy and consistency.
Other content needs more creative handling.
Homepage headlines, campaign messages, brand slogans, advertising copy and emotionally driven landing pages may not survive a literal translation.
For example, a phrase built around an English pun may need to be rewritten completely. A confident headline may need to become more restrained. A playful tone may need to be adapted so it does not feel childish or unprofessional in another language.
This is where transcreation can be more appropriate than standard translation.
Transcreation keeps the purpose of the message but gives the linguist more freedom to adapt it creatively for the target audience. It is especially useful when the words are doing more than explaining. They are selling, positioning or creating a feeling.
A campaign line for a travel brand, for instance, may rely on emotion, rhythm and cultural familiarity. The same is true of beauty, fashion, food, entertainment and consumer technology. In those cases, a literal translation may be accurate but forgettable. A transcreated version can keep the intent while giving the message a more natural local shape.
A simple rule is this:
If the content needs to be understood, translation may be enough.
If it needs to persuade, impress, reassure or emotionally connect, it may need localisation or transcreation.
What a good multilingual website feels like
Users should not feel that they are using a translated version of your website.
They should feel that they are using your website.
That distinction matters.
A good multilingual website feels natural. The menus make sense. The tone feels appropriate. The forms work. The messages are clear. The layout does not break. The calls to action feel right for the audience. The user is not suddenly pushed back into English halfway through the journey.
Everything feels intentional.
That does not happen by accident. It happens when translation is treated as part of UX, not as a final production task.
Think about the websites and apps people use every day: booking platforms, streaming services, online shops, banking apps, travel sites, software dashboards. The best ones rarely make users think about translation at all. The experience simply works in their language.
That should be the goal.
Website translation is design, strategy and language working together
Website translation has moved far beyond the old idea of simply converting pages from one language into another.
For modern organisations, it is part of international growth, brand consistency, digital experience and customer trust.
The words matter. But so does where they appear, how they behave, how they sound and what users are expected to do next.
That is why translation should be included early in website planning, especially when a business knows it will need to serve more than one language or market.
At Kwintessential, we support businesses with website translation, localisation, transcreation and multilingual content projects that are built around real users, not just word counts. Whether you are adapting an existing website or planning a multilingual launch from the start, the goal is the same: to make every version of your site feel clear, credible and natural to the people using it.