Adding a language selector is easier than keeping several language versions accurate. A multilingual website needs a content workflow that tracks what changed, who reviewed it, and which version is ready to publish.
Related service: Website and ecommerce development- 01Update the source
- 02Flag affected translations
- 03Review localized meaning
- 04Test the journey
- 05Publish approved versions
SECTION 01
Agree the content and responsibility model
List the pages and interface text included in the first language release. Navigation, form labels, errors, download descriptions, and confirmation messages are easy to overlook. Identify who approves meaning, terminology, and any market-specific information. A developer can build the workflow, but should not be treated as the final reviewer of a language they cannot evaluate.
Give related translations a shared content identifier while retaining separate draft, reviewed, and published states. A source update should flag translations for review rather than automatically declaring them current. W3C explains language declarations in HTML; Google's localized-page guidance explains relationships between language versions. These technical signals do not substitute for an approved translation.
SECTION 02
Illustrative example: a changed service prerequisite
Imagine a business has English and Spanish service pages. The team changes the prerequisite for an onboarding workshop. The English editor publishes the approved change, while the Spanish page still contains the old instruction. A useful workflow identifies that mismatch and assigns it to the translation owner before the outdated instruction reaches another customer.
The business can choose to hold both versions until review or publish one with a clearly defined temporary fallback. It should not silently combine an updated heading with stale body text. Test the related inquiry form too: a translated page that sends an English-only confirmation may create an incomplete experience even when the main paragraphs look correct.
SECTION 03
Scope a first release that can be maintained
Start with a limited page set and a named reviewer for each language. Ask the agency to demonstrate a changed source paragraph, an unavailable translation, and a language switch from a deep page. The switch should retain the equivalent topic where it exists, not unexpectedly return everyone to the home page. Avoid treating a flag as a complete language label.
Acceptance includes long translated headings, date and number formats, image text, downloadable resources, keyboard access, and the form journey. Agree which URLs are public and which incomplete drafts remain unpublished. Document how editors retire or restore a translation and how outdated versions are reported. The tradeoff is straightforward: fewer complete language journeys are more useful than many selectors leading to unfinished or contradictory content.
SECTION 04
Frequently asked questions
Can we launch only the important pages in another language?
Yes. Define the available journey and make missing equivalents clear rather than implying the whole site is translated.
Is machine translation enough?
It may help prepare a draft, but assign a competent reviewer for meaning, business details, and customer-facing instructions.
Does a language version require a new office claim?
No. Serving readers in a language does not establish a local office, legal presence, or country-specific service capability.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Localized versions of pagesGoogle Search Central
- Declaring language in HTMLW3C Internationalization
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy