A multilingual website needs more than accurate translations. Each language version must work as a complete experience, from the first menu click to form submission and confirmation. Before launch, review pages in their intended language, test important user journeys, and check how visitors move between versions. A structured review helps uncover missing content, awkward layouts, broken links, and confusing language controls while there is still time to fix them.
Review Every Translated Page
Compare each translated page with its source, but do not expect every sentence to follow the same length or structure. Check that headings, body copy, calls to action, image captions, error messages, and footer text are all translated. Look for text that remains in the original language, placeholder copy, and inconsistent terms. Confirm that links lead to the equivalent page in the selected language rather than sending visitors back to the source version.
Read the pages in context, preferably with a fluent reviewer who understands your audience and subject matter. Check that the meaning, tone, and instructions remain clear, including in product details, service descriptions, and legal or policy content. Review dates, addresses, measurements, and other region-specific details for accuracy. If a page has no suitable translation, decide whether to provide a clear alternative or keep it out of that language’s navigation.
Test Navigation and Layout
Click through the main navigation, dropdowns, breadcrumbs, footer links, and calls to action in every language. Confirm that menus open and close correctly on desktop and mobile, and that each item points to the right localized destination. Longer translated labels may wrap, overlap, or push nearby controls out of place, so inspect real pages at common screen sizes rather than relying only on a preview.
Check page titles, browser tabs, and search-related page details for the correct language. Verify that images and icons still make sense alongside translated text, and that text direction and alignment match the language where relevant. Also review the site on keyboard and touch devices. A menu that works with a mouse but cannot be navigated by keyboard can prevent visitors from reaching essential pages.
Submit Forms in Each Language
Complete every important form from start to finish in each language. Check field labels, instructions, required-field markers, dropdown choices, consent text, and validation messages. Enter both valid and invalid information to confirm that errors explain how to fix the problem. Make sure the form accepts the characters people use in the target language and does not reject a valid name or address because of assumptions built into the fields.
After submission, confirm that the success message and any follow-up email use the visitor’s selected language. Check that submissions reach the intended team and that translated form labels remain understandable in notifications or records. For phone numbers, addresses, and other localized fields, provide clear formatting guidance without making unnecessary formats mandatory. Test the form on a phone, where small controls and long instructions can create extra friction.
Verify Language Switching
Use the language switcher from several types of pages, including a service page, a blog post, and a form. It should take visitors to the corresponding page when that version exists. If it does not, send them to a sensible destination in the chosen language and make the change clear. Avoid switching languages automatically based only on location or browser settings; visitors should be able to choose and change their preference.
Check that the switcher is easy to find, works with a keyboard, and clearly identifies each language. Test whether a visitor’s choice persists as they browse, while still allowing them to change it. Review how language preferences interact with links shared from the site and with direct visits to localized URLs. Before launch, ask someone unfamiliar with the site to find the switcher and complete a key task without assistance.
A careful multilingual prelaunch review checks both the words and the paths visitors take through the site. Record issues by language and page, assign each a clear owner, and retest fixes before publishing. If you need help reviewing localized pages and user journeys, Alamo Localize can discuss your website’s launch needs.