Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Plan a multilingual website that keeps its meaning

    Every published language version should be understandable and usable from the first page through the confirmation message.

    Go to the method

    Illustration of website project planning: Plan a multilingual website that keeps its meaning

    Choose audiences and reviewers

    Identify the people you actually serve and the pages needed for their journey: home, services, terms and contact. A language in the selector creates an expectation of usable coverage.

    Assign someone to check terminology, examples, prices, units and contact details. Machine translation may help draft copy, but review for the intended audience remains essential.

    Give each version its own address

    Use a stable URL per language. Connect genuinely equivalent pages with reciprocal hreflang links, including self links, and keep a separate canonical URL for each version.

    The selector should open the equivalent page when available. Otherwise, state clearly that the section has no translation. Google’s localized versions guide describes these conventions.

    Check localized pages as a network of relationships, not just a list of flags. Declare each equivalent URL using an absolute address and the required return links. If a French page references its English counterpart without a matching return reference, Google ignores that hreflang relationship. A missing language does not prevent processing the other valid reciprocal relationships.

    Separate language, region and fallback. en-GB can target English content for the United Kingdom; UK is not the region code to use for that targeting in hreflang. x-default identifies the fallback for preferences not covered without creating an additional translation. Record the URLs actually reached through the language selector: correct tags do not guarantee that the language button opens equivalent content.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Language versions: four relationships to check
    CheckRequired resultDefect to fix
    Reference to the current versionThe page includes itself in its alternate set.The current URL is missing from the list.
    Link between two translationsEach page references the other using its absolute URL.The relationship works in only one direction.
    Translation unavailableOnly existing equivalent pages are presented as translations.A generic homepage silently replaces the expected page.
    x-default fallbackThe fallback destination is deliberately chosen and accessible.The fallback is presented as a translation that does not exist.

    Test and maintain every journey

    Check menus, filters, forms, errors and confirmations in every language, on phone and desktop. Test accented characters, longer text and right-to-left scripts when published.

    After a price or service change, identify all affected translations. Article counts can differ, but pages presented as equivalents should serve the same purpose.

    Manage delayed translations

    Connect versions serving the same intent. A missing language version should offer an explicit choice, such as an English guide labelled as English. Changing navigation alone does not translate a French page.

    Assign an owner and validation status to each version. Identify affected translations when changing a price or condition. Test names, numbers, dates, contacts, errors and confirmations. The declared HTML language must match the content.

    Check that browser preferences do not override the language selected on the site.

    Synthetic case: a browser prefers English but someone intentionally opens a French page. Keep that URL and content. Then test an unavailable language and a preference list without inferring country or identity. Keep the language selector available for switching to an equivalent page.

    • Explicit choice is respected; unsupported preferences cause neither loops nor an incomprehensible page.
    • MDN Accept-Language

      Request header indicating language preferences as a hint rather than an explicit visitor choice.

    Measure a language task

    You understand a dialogue but struggle to answer spontaneously. Progress depends on the target skill, not just viewing time.

    Choose a short task, record a trial if desired and compare your productions. Completing an activity does not certify a language level.

    • Choose comprehension or production
    • Keep a comparable task
    • Note what needs practice

    Reuse a cultural image

    You want to illustrate a presentation with a collection reproduction. The age of the work does not establish the image file's rights.

    Find the object record and reuse terms for the selected image. Keep its identifier, credit and permission for that particular version.

    • Note the work's identifier
    • Read reproduction rights
    • Keep the requested credit

    Test a shared deep link

    Open an internal page directly in each language. The language selector should reach equivalent content when available and clearly explain a missing translation. Check the form subject and received email too: translated controls are insufficient when the subsequent process becomes unclear.

    Reference documents

    Content updated on

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    W3C · HTML language
    <html lang="fr">The default language is declared on html; local language changes are marked.
    Google Search · Canonical
    rel="canonical"A preference signal for Google; neither a redirect nor a selection guarantee.
    W3C Internationalization · HTML direction
    lang="ar" dir="rtl"Language and reading direction are separate information. Declaring ar alone does not establish the base direction; dir="rtl" does. Logical CSS properties adapt spacing without hard-coding left and right throughout the layout.
    Google Search Central · Multilingual sites
    URL · hreflang · linksProvide separate URLs per language and links for choosing an edition. Redirecting on an assumed language can prevent access to a version. Translating only navigation and footer does not translate the main content.
    MDN · Vary
    Vary: Accept-LanguageWhen one URL produces different responses according to Accept-Language, Vary identifies that cache selection criterion. Keep the value consistent on 200 and 304 responses. Separate language URLs do not require this header merely because the website is multilingual.

    Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.

    Acceptance matrix to adapt to your project

    These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    An entry has no English translation.The switcher does not claim a missing equivalent and labels the language of any fallback.Original URL, offered destination, stated language and absence of a misleading translation link.
    Language switchSame subject or explicit absenceURL pair
    Changed priceAffected translations identifiedValidation register
    Translated formErrors and confirmation understoodComplete test case

    Frequently asked questions

    Can only part of a site be translated?

    Yes, if the journey is explicit. Connect actual translated equivalents and label resources available in another language. Menus, forms and errors in the offered journey must be understandable. Avoid a switcher that always returns to the home page while suggesting the current page has been translated.

    Must all languages launch together?

    Publish validated versions and explain availability. Clear partial coverage is preferable to a journey mixing instructions its audience cannot understand.

    Is translated navigation enough?

    Copy, forms, errors, confirmations and practical information also need adaptation. Validate a complete task.