Multilingual business websites: what to translate and what to keep consistent

A useful translated website gives a customer a complete route from understanding a service to contacting the business. Translating the home page is a start; the navigation, service details, and inquiry experience matter too.

Plan the languages around the customers you serve and the information you can keep accurate.

Separate website language from service language

A business can publish information in a language even when only part of its team can use that language in a call or appointment. State what follow-up is available so the customer knows what to expect.

This distinction belongs wherever it affects the next step. A contact form can ask for a preferred language, while the page explains the languages your team can use for that service.

Translate a complete customer path

Start with the important service pages, contact information, and navigation. Include the form’s labels, choices, instructions, error messages, and confirmation.

Give policy or preparation information the same attention when the customer needs it to proceed. A translated service description loses much of its usefulness if the linked instructions are available only in another language.

Longer resources and blog posts can follow according to demand. Choose them for their usefulness to the audience rather than trying to duplicate every page immediately.

Keep shared facts consistent

Business names, contact details, addresses, service areas, and pricing conditions should agree across language versions. Organize the content so someone is responsible for checking those facts when they change.

A translation can use natural local phrasing without changing the meaning of an offer. Review dates, units, currencies, technical terms, and conditions carefully. An automatic translation can be a draft; a person familiar with the business should check the result.

Connect the language versions

Give each version a stable address and an obvious way to switch languages. Where a corresponding page exists, the switch should make it easy to reach that version.

Language metadata and alternate-language links help describe these relationships to search systems. Keep the visible navigation and the technical relationships aligned as pages are added or removed.

Plan for the next update

When you change a service, list the affected pages, forms, and languages. Review each version before treating the update as complete. Keep a small change record if several people share the work.

Independent translations can become inconsistent gradually. A monthly review of frequently used pages can catch old hours or service conditions, while larger changes deserve an immediate check.

Review the submitted inquiry

Test the form in each language. Confirm that the submitted choices reach the business with the intended meaning and that the confirmation is understandable. Check how the language preference is communicated to the person replying.

Wirechunk connects translated pages and keeps localized form text attached to shared field definitions. Its AI can help prepare changes, and you can review and edit them before publishing.

Explore multilingual websites · Set up translations in Wirechunk