GUIDE / LANGUAGES
Fluent translation is insufficient when dates, links or the journey tell a different story. Every language should support the same informed decision.
01 / GUIDE / LANGUAGES
A version need not mirror every word, but it must preserve facts, offer, limits and next action. Assign a reference version and an owner for each language. When a fact changes, every affected version needs a review.
GuidesIN PRACTICE
A page belongs to a system: summary, title, tables, links, language versions and structured data. Correcting a sentence requires finding where it is reused and checking that each version still tells the same story.
Choose the situation you observed. Each path gives a first check, useful evidence and the limit of that check.
Further reading
| Situation | Avoid | Useful correction |
|---|---|---|
| Corrected number | Changing only the paragraph. | Review the associated table, caption, summary and structured value. |
| Moved page | Updating only the visible link. | Check destination, fragment and return path. |
| Translated version | Copying words while retaining an obsolete example. | Also review unit, date, source, links and interpretive scope. |
Which claims depend on the change?
Which pages and languages reuse them?
Do numbers, links and limits agree everywhere?
An update date marks a real edit. It does not redefine source or observation dates. Keep those roles separate in prose and references.
Consulted on .
02 / GUIDE / LANGUAGES
Check the full page, then a real journey through to the form or linked document.
Compare names, roles, figures, dates, scope and caveats. Local examples may vary without creating a conflicting offer.
Record to retain · Fact matrix by languageEach language needs a stable URL, coherent canonical and reciprocal hreflang links to versions that exist.
Record to retain · URL, canonical and hreflang matrixDeclare the document language and check reading direction. Fragments in another language must remain identifiable.
Record to retain · lang, dir and actual readingLocalize useful alt text, inspect images containing words and test menus, buttons, filters, empty states and errors.
Record to retain · Captures by device and languageTest internal links, search, consent, forms and post-submit states. A change in one language should prompt review of the others.
Record to retain · Update log and journey checks03 / GUIDE / LANGUAGES
Aim for an equivalent, verifiable experience rather than identical sentences. Before approval, open an internal link, a source and the contact form in every language. Check that units, scope and destinations still suit the reader. A finished translation is not enough if the journey silently returns to another language.
List facts, terms, links and actions that must match across languages.
Write for the local audience, then review headings, calls to action, caveats and proper names in context.
Open each URL and check canonical, hreflang, language, direction, structured data and sitemap.
Complete a real task in each language and record date, owner and versions to revisit.
04 / GUIDE / LANGUAGES
A failure may arise in content, markup or journey continuity.
Record the divergence, reference version and date; fix the pages and reused excerpts.
Read the dossierCheck internal link targets, canonical URLs and reciprocal alternates.
Read the dossierCompare labels, consent, validation and result messages through to mobile.
Read the dossier05 / GUIDE / LANGUAGES
06 / FAQ
No. Publish only useful versions that can be kept current; do not list a missing page in hreflang.
Each indexable version should normally have its own canonical and use hreflang to connect equivalents.
After changes to facts, offer, navigation, forms or templates, and on a defined editorial cycle.
Identify the language actually available and flag the affected passage. Check that essential task instructions remain understandable. A partially translated page should not imply that every attachment, error or confirmation exists in the selected language.
07 / Discuss a context
A fact matrix, coherent URLs and tested journeys make multilingual upkeep manageable.
A few interventions relevant to this topic. Each amount covers the stated reference scope; the quote confirms priorities and overlapping tasks.
One language, metadata and journeys; language review to be agreed.
Pages · one language : 3 · 6 h
From 480 € excl. VAT / 576 € incl. VAT
Indicative working scope, to confirm in the quotation.
Useful answers, structure, sources and contextual links.
Pages : 5 · 8 h
From 640 € excl. VAT / 768 € incl. VAT
Indicative working scope, to confirm in the quotation.
Dimensions, compression, formats and alternative text.
Images : 10 · 2 h
From 160 € excl. VAT / 192 € incl. VAT
Indicative working scope, to confirm in the quotation.
Use these notes to scope the request and review delivery. The quotation defines the agreed work, volumes and schedule.
Publish understandable content with identifiable sources, media and versions.
Record source language, script and translation in the editorial record. A variant such as de-CH-1901 describes language use, not the document or translation date.
See scope and pricingDEEPER READING / PRACTICE
A translation retains the phrases, but some links and examples do not match the target audience. Multilingual publication must monitor the equivalence of the path as well as the quality of the language.
Updated on .
Compare promises, sections, links, forms and error messages in each language. Also check the date conventions, characters and reading of the interfaces from right to left.
An incomplete language version may appear to be published while steps remain in another language. Equivalence does not always imply a literal translation of the examples.
The publication sheet links each version to its source content, its adaptations and its controls. A functioning test follows the path to the final action in the chosen language.
PRACTICAL CASE / WORKED EXAMPLE
The example is a web control educational situation. It connects the defect to a concrete path and describes a way to verify the correction, rather than consider the only publication of the change as a proof of resolution.
A translated version refers to a form and document only available in the source language. The reader understands the page, but cannot continue with the same information.
Test all the continuation links and actions. Identify the necessary adaptations, translate the critical elements or announce their language. Check the dynamic messages and the proposed documents.
The version is published with a comprehensible path and an explicit coverage. The differences assumed remain visible instead of being discovered only after an interaction.
Priorize those necessary for understanding or action. For others, announce the language and explain the role of the document so that the reader can choose its continuation in knowledge of cause.
DETAILED WORKSHOP / APPLICATION
Preparing source page, versions, links and features. Identify the information necessary to understand the subject and continue an action in each language.
Compare promises, sections, examples and destinations. Test the dynamic elements and messages. Document the adaptations and content voluntarily proposed in another language.
If an additional document remains in its original language, announce this situation. Check that the main path does not depend on information that the reader cannot understand.
The publication is consistent when each version allows the announced path. Differences in formulation or example are acceptable if they preserve the intention and useful information.
Transmit a correspondence file and functioning test by language. Changes in the source page trigger a reading of the adaptations that depend on it.
ANNOTATED WORKING DOCUMENT / REVIEW GRID
The file connects source version, adaptations, links and interactions. It verifies the information necessary for understanding and action rather than a word-to-word equivalence.
On a small screen, scroll the grid horizontally to read all three columns.
| Observation | Supported interpretation | Next step |
|---|---|---|
| Each version preserves the intention and continuation. | The announced course is available in the languages examined. | Document the adaptations and control the dynamic elements. |
| One necessary document remains in another language. | The translation of the page is not enough to guarantee the path. | Translate, adapt or announce a comprehensible continuation solution. |
| The versions describe incompatible information. | The multilingual corpus no longer presents the same state of the subject. | Close the sources and review the contents before publication. |
The inspector shall verify coverage and decisive information. Adaptive examples are acceptable when they preserve the need; the differences that change the meaning must be explained.
REPORTING / EXAMPLE WORDING
Language equivalence also depends on the information necessary for the action.
Check key links, messages, and content in each advertised language.
The controlled versions preserve the intention and important stages of the path. The adaptations and documents proposed in another language are explicitly indicated.
