Localization
Planning a multilingual website before launch
Treat navigation, support content and publication checks as part of the translation project.
A multilingual website needs more than a translated homepage. A visitor should be able to move from information to an action without unexpectedly switching language. Start with a list of pages and messages used along the main customer journeys, then decide what must be ready for launch.
Build a content inventory
Include navigation, forms, validation messages, confirmation screens, support pages and downloadable files. Record the owner and source version of each item. Prioritise the paths that visitors actually use. Avoid announcing a complete language version while essential steps still point to untranslated content.
Give short strings context
For every button or label, show where it appears and what it does. Keep sentences together rather than translating disconnected fragments. Identify product names, variables and links that must stay intact. Give the reviewer access to a preview so that unclear wording can be judged in the interface.
Check each language journey
Test the language switcher, key links, forms and mobile layouts. Review text that wraps differently and images containing words. Make sure later source edits trigger updates to the corresponding translations. Assign responsibility for maintenance: publication is the start of an ongoing multilingual content process.