Multilingual site: from translation to page verification

A translated page is ready for publication when the visitor can understand it and complete the intended path. Translating the main text while leaving buttons, forms, or links in the original language can break that path. To manage a multilingual site you therefore need to check the entire page, not just the sentences.

The work can be organized with a tab for each content: source page, target language, version, manager and status. This guide proposes an editorial process that can be applied even to small teams, without assuming that machine translation will resolve all linguistic or contextual differences.

Establish what must remain identical

Before translating, separate invariable information from adaptable information. Product name, feature code, and documented features must remain consistent. Title, order of examples and wording of the button may instead require adaptation to be natural to the recipient.

Prepare a short glossary with approved terms and terms to avoid. A hypothetical example: "order" may require a different choice according to the process described. If it is translated differently on each page, the reader can interpret it as distinct concepts that coincide in the product. The glossary makes this decision explicit.

Check the path, not just the content

Open the page in the target language and follow the path of a new person. Does the menu lead to the correct page? Does the product link preserve the language? Does the form explain which fields to fill in? After sending, is the confirmation still understandable? These steps are a substantial part of the editorial work.

Also checks alternative image texts, captions, error messages and information in boxes. An accurate description can lose its usefulness if an image contains untranslated instructions. When material is not yet available, declare the language of the linked document instead of making a partial version appear complete.

Give each version a verifiable address

Search engines must be able to distinguish language versions. The Google documentation on localized pages explains the use of hreflang references to report linguistic or regional variations, also through a sitemap. References must link actual, consistent versions, not languages ​​for which content is missing.

From an editorial point of view, it maintains a list of public addresses associated with the same page. This allows you to quickly check for a bad link and distinguish a published translation from a draft. The number of languages configured in the CMS does not demonstrate that each article is available in all those languages.

Manage source update

The most delicate step comes after the first publication. If a product feature changes, you need to know which translations still report the previous version. Then record the topic of the change and the pages involved: adding a paragraph, correcting a value, new link or removal of a function.

Not all changes require the same work. A spelling correction in the source may not affect other languages. However, a change to the terms of use requires a revision of the relevant content. Evaluating the impact avoids both unnecessary updates and important misalignments.

A checklist before publishing

• The title describes the content without introducing new promises.
• Product terms are consistent with the glossary.
• Buttons, forms and messages are understandable in the chosen language.
• The links open existing pages and indicate any documents in another language.
• The page remains readable on a narrow screen even with longer texts.
• The editorial sheet indicates which version of the source has been adapted.

It is useful to assign the final verification to a person competent in the language and product. AI assistance can prepare a proposal and help spot inconsistencies; the quality must however be verified in the real context of the page. If that review has not occurred, do not present the translation as already validated by an expert.

ElaiFlow offers multilingual content management and assisted preparation tools. The organizational process remains a team choice: those who translate, those who verify and those who publish must have clear responsibilities. To design the complete flow, continue with the guide from draft to published page.

Content prepared with AI assistance; sources consulted on September 19, 2026. The proposed flow does not describe a linguistic certification nor guarantee placement results.

Illustrative AI-generated cover; it does not depict actual EL-AI people, premises or installations.