A multilingual website content workflow records each page’s language counterpart, source version and reviewers. When the source changes, return affected translations for review. Separate language quality, factual approval and live-page checks so a revised offer does not remain outdated in another language.
Record equivalent pages and market differences
Include a page identifier, URLs for each language, the latest source version and publication status in the inventory. Match pages by their purpose rather than heading similarity. Do not create an empty counterpart for a service that is not offered in a particular market merely to increase the language count.
Test the language switch on individual pages. Does it open the equivalent content, a different service or the homepage? Make unavailable translations clear. Google recommends separate URLs for language versions; relying only on browser-language content switching can make discovery more difficult.
Separate fixed meaning from adaptable expression
Prepare shared terminology for services, product codes, brand names and technical concepts. Literal wording may sound unnatural in another market; preserve the meaning through local usage. Tone, examples and discovery questions may also need adaptation.
Consider the Turkish phrase for requesting an offer. Depending on the task, an English button might need to say “request a quote” or “discuss your project”. A product-price request and a service requiring discovery are different actions. This hypothetical example shows why the destination should guide wording instead of applying one translation everywhere.
Separate language review from business approval
A fluent editor may not know whether every technical detail is accurate. Assign language review, service-scope approval and the final website check separately. When copy is shortened, verify that an important boundary has not disappeared. Differences involving delivery or usage conditions should be reviewed by the relevant business owner.
| Stage | Decision owner | Check |
|---|---|---|
| Source copy | Content and service owner | Is the information current and approved? |
| Adaptation | Language and market editor | Are expression and terminology natural? |
| Business review | Subject expert | Are scope and conditions preserved? |
| Page layout | Editor and design team | Do headings, links and buttons work? |
| Later changes | Content owner | Are affected language counterparts flagged? |
Make affected languages visible whenever content changes
Open a change record showing the previous sentence, new sentence and affected page identifiers. Changes to specifications, deliverables or service regions require another review of the relevant languages. Even for a minor copy correction, record which version was checked.
Review headings, main copy, form labels, downloads and language links together on the live page. Check dates, numbers, currencies and product codes for unintended changes. When page pairs change, the technical team should verify canonical and hreflang relationships too; those annotations cannot repair an inaccurate translation.