Six illuminated editorial pages converge on a reference version in a dark studio

GUIDE / LANGUAGES

Publish a coherent multilingual site

Fluent translation is insufficient when dates, links or the journey tell a different story. Every language should support the same informed decision.

Five layers to alignFour publication passesCommon differences

01 / GUIDE / LANGUAGES

Define useful equivalence

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.

Guides

02 / GUIDE / LANGUAGES

Five layers to align

Check the full page, then a real journey through to the form or linked document.

01

Facts and promises

Compare names, roles, figures, dates, scope and caveats. Local examples may vary without creating a conflicting offer.

Record to retain · Fact matrix by language
02

Addresses and variants

Each language needs a stable URL, coherent canonical and reciprocal hreflang links to versions that exist.

Record to retain · URL, canonical and hreflang matrix
03

Language and direction

Declare the document language and check reading direction. Fragments in another language must remain identifiable.

Record to retain · lang, dir and actual reading
04

Images and components

Localize useful alt text, inspect images containing words and test menus, buttons, filters, empty states and errors.

Record to retain · Captures by device and language
05

Journey and upkeep

Test 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 checks

03 / GUIDE / LANGUAGES

Four publication passes

Aim for an equivalent, verifiable experience rather than identical sentences.

  1. 01

    Set invariants

    List facts, terms, links and actions that must match across languages.

  2. 02

    Adapt meaning

    Write for the local audience, then review headings, calls to action, caveats and proper names in context.

  3. 03

    Validate delivery

    Open each URL and check canonical, hreflang, language, direction, structured data and sitemap.

  4. 04

    Test and maintain

    Complete a real task in each language and record date, owner and versions to revisit.

04 / GUIDE / LANGUAGES

Common differences

A failure may arise in content, markup or journey continuity.

01

A version states a different fact

Record the divergence, reference version and date; fix the pages and reused excerpts.

Read the dossier
02

Search shows the wrong language

Check internal link targets, canonical URLs and reciprocal alternates.

Read the dossier
03

A form changes meaning

Compare labels, consent, validation and result messages through to mobile.

Read the dossier

05 / GUIDE / LANGUAGES

Method references

01

Google Search Central · Localized versions

02

W3C · Declaring language in HTML

06 / FAQ

Publishing questions

Must every page be translated?

No. Publish only useful versions that can be kept current; do not list a missing page in hreflang.

Can every language share one canonical?

Each indexable version should normally have its own canonical and use hreflang to connect equivalents.

When should checks be repeated?

After changes to facts, offer, navigation, forms or templates, and on a defined editorial cycle.

07 / Discuss a context

Keep every version accurate

A fact matrix, coherent URLs and tested journeys make multilingual upkeep manageable.

Discuss a contextGuides