Plan a multilingual Drupal site beyond the language switcher

A language switcher is only the visible edge of a multilingual website. Behind it are decisions about who translates content, which information should be shared, and what visitors see when a translation is missing. Planning those details early helps keep the experience consistent as the site grows.

List the audiences and the content they need

Decide which languages you will support and whether all audiences need the same pages. Identify the most important journeys in each language. A complete translation of an outdated page is not necessarily more useful than a carefully maintained set of essential content with clear ownership.

Separate different translation tasks

Drupal distinguishes interface, configuration, and content translation. Your menus, editorial field labels, and published articles may require different handling. Make an inventory rather than assuming that translating a body field also translates the rest of the experience. Include automated messages and form feedback in the review.

Decide which fields should be shared

Some information may stay the same across translations; other information needs a language-specific value. Discuss images, alternative text, contact information, and links as well as paragraphs. Record those decisions in the content model so editors understand whether an update affects one translation or several.

Create an editorial review process

Agree who requests translations, who reviews them, and what happens when the source content changes. Make untranslated and outdated material visible to the responsible team. Plan the publishing sequence so a visitor is not guided through a journey that suddenly changes language halfway through.

Test real translated content

Longer labels and different writing conventions can change the layout. Test navigation, cards, forms, dates, and mobile pages using representative translations. Review the correct language URLs and links, then include translation checks in future release routines instead of treating multilingual support as a one-time feature.

Further reading: official guidance.

Make the next step practical

Have a question about your own platform? Plan a multilingual website and tell us what you would like to improve.