One address changes language
Users and crawlers cannot reliably access, share, or index each version.
Multilingual websites
Adding a language is not the same as copying a website.
Markets use different buyer language, product information, units, policies, cases, and contact habits. URLs, content, search signals, caching, and publishing ownership need one plan.
Who this fits
Businesses entering a new language market, sites with conflicting language indexing, and distributed teams maintaining shared product and market content.
Common mistakes
A completed translation can still fail in the market
Language, region, and market are different decisions. Browser translation is not a delivery model.
Only navigation and titles are translated
Product facts, cases, units, policy, and calls to action remain wrong for the market.
No owner updates each language
Product changes reach one version only, leaving specifications and promises inconsistent.
Approach
Treat language pages as independent but related market assets
- Use stable URLs and self-canonicals for every language.
- Connect real counterparts only with reciprocal hreflang.
- Negotiate at the root without overriding explicit language paths.
- Localize buyer language while keeping product facts consistent.
- Adapt currency, units, regulation, shipping, cases, and calls to action.
- Prevent language contamination in caching, release, and rollback.
Delivery
Use one page inventory for language, content, and technology
Track source, language status, counterparts, reviewer, and publication date per page.
Market scope
Define languages, regions, products, units, policy, and conversion goals.
Page mapping
Record true counterparts and market-only pages.
Content localization
Keep facts consistent while adapting language, proof, and next steps.
Search signals
Implement canonicals, hreflang, sitemaps, schema, and internal links.
Entry and caching
Test negotiation, cookies, CDN cache keys, and invalidation.
Publishing ownership
Assign confirmation, updates, publication, and review for each language.
Validation
Multilingual QA goes beyond translation
Check language, facts, URLs, canonicals, hreflang, links, structured data, images, forms, and counterpart switching. Monitor crawling, indexing, search, and enquiries separately after launch.
Send the current languages and target markets. Prioritize the core pages.
Planning can begin before every source document is translated.