Updated 8 October 2026.
A reliable translation workflow covers the whole website, not just its paragraphs. Navigation, buttons, forms, image text, metadata, checkout messages and support pages all contribute to whether someone can complete a task in another language.
Choose a workflow by content risk
Use human specialists where precise meaning is essential, particularly for contracts, regulated claims and important sales pages. Machine translation can help create an initial draft, but a draft should not be treated as an approved publication. A hybrid process gives a reviewer responsibility for checking terminology, intent and suitability.
Decide who approves each content type before selecting tools. Give the reviewer the intended audience, screenshots, source references and the reason the page exists. The most fluent sentence is not necessarily the best translation of a technical instruction or purchasing condition.
Inventory and prepare the source
- List every page, template and interactive message that needs translation.
- Identify the owner and review frequency for each item.
- Remove contradictory or obsolete source copy before translating it.
- Record product names, preferred terminology and words that must stay unchanged.
- Provide context for short strings such as labels and error messages.
Build a small glossary and style guide before the first batch. Include examples of the desired tone and how to handle names, measurements, dates and addresses. Keep corrections in a shared record so they improve subsequent work instead of disappearing into email.
Make review a publication requirement
Review the translation for meaning first, then for readability. Check numbers, links, product identifiers and any claim that depends on a current specification. Flag uncertainty for the source owner rather than silently guessing.
Next, review the page in the actual website. Long translated headings can overflow a card. A form label may lose its relationship to an input. A translated link may lead back to the wrong language. These are functional defects, even when every individual sentence is correct.
Give languages stable public URLs
Google recommends separate URLs for language versions and supports language annotations such as hreflang. A visible language switcher also helps people choose the version they need. See Google’s multilingual website guidance.
Match each translated page to its genuine counterpart. Translate titles and descriptions as part of the page, use consistent canonical rules, and test that alternate-language links are reciprocal where appropriate. Do not advertise a completed translation when the page still contains only the original-language article.
Test layout and accessibility
For right-to-left languages, check reading order, alignment, directional icons and mixed-direction data such as telephone numbers. Use fonts with the necessary character coverage. Test tables, menus, consent controls and error states on mobile as well as desktop.
Give buttons enough room for the translated label instead of forcing every language into the original text width. Keep meaningful alternative text and accessible names aligned with the page language. Include keyboard checks in the same acceptance process as the visual review.
Keep languages in sync
When source content changes, mark affected translations as needing review. Record the source revision behind each approved translation. Set an explicit policy for whether an outdated translation remains available, displays an update notice, or is temporarily withdrawn.
Maintain a release checklist containing copy approval, metadata, links, layout, forms and public HTTP status. Small batches are easier to review and recover than a single uncontrolled import of the whole website.
Frequently asked questions
Is machine translation enough for a business website?
Evaluate the purpose and consequences of each page. Public copy still needs an accountable approval process; important commercial and specialist content benefits from qualified human review.
Does translating text finish multilingual SEO?
No. Language URLs, metadata, navigation, internal links and technical annotations need testing too.
Who should approve a translation?
A reviewer competent in the target language and subject should approve the meaning. The website owner should approve business claims, and the implementation team should verify the live page.
See our website development services or plan a multilingual release.
Want this handled for you?
We build and optimise sites like this every week. Book a free 30-minute call and we will tell you exactly what we would change on yours.
Get a free site review
