Multilingual Website Planning: What to Decide Before Translation

Multilingual Website Planning: What to Decide Before Translation

Identify whom each version serves, then test a complete enquiry in each language.

Start multilingual website planning by defining each version’s audience, service area, URL and content owner. Before translation, map how visitors will switch languages, submit an enquiry and receive confirmation in that language. A worksheet can track differences across pages, forms and operational workflows.

Define audiences and local content during multilingual website planning

For each version, record the intended readers, service area and main visitor tasks. Two audiences reading English may need different contact details or service coverage. Page by page, mark which content stays consistent and where addresses, currencies, opening hours or product names need to change. Ask someone who knows the market to review those differences.

Give each language version a shareable URL

Google recommends separate URLs for language versions. Use hreflang to indicate equivalent pages. For each original page, record the proposed language URLs, page titles and release status. Design the language switcher so visitors can move from a service page to its equivalent. If an equivalent page is still in progress, explain where the visitor can find relevant information in the meantime.

Test the whole enquiry journey

Suppose a company launches an English service page first. A visitor switches to English, opens the quote form from the service page and sees English field labels, error messages and confirmation. The colleague receiving the enquiry should also be able to identify the page language and respond through the right process. During the same test, check navigation, the footer, downloads and automated messages for untranslated text.

Make translation updates part of routine publishing

Create a glossary for service names, job titles and brand terminology. When the source copy changes, have its owner identify affected pages and notify translators and reviewers. Before release, confirm that each language URL loads and that equivalent published pages reference one another. If service terms change, schedule the updates across the versions and verify any related forms and documents.

Identify content that comes from shared components, such as footer addresses and enquiry forms. Record which pages inherit each component. After editing one language, switch to the others and verify that each still shows the correct information. Have the people who will maintain the site run this check so they know what to do when a translation is pending. This also clarifies who should fix a problem in a shared component.

Frequently asked questions

Do we need separate Traditional and Simplified Chinese versions?

Decide based on the terminology your readers use and the services they need. If you maintain both versions, allocate time to review and update each one.

Should we redirect visitors based on browser language?

You can suggest a language while keeping a visible selector and direct links to each version.

Do all pages need to launch together?

You can launch a core set of pages that supports a complete enquiry, then add more pages as the content is ready.

Sources