Before signing off a multilingual site, pick one service page and one enquiry in every language. Ask the supplier to run the same checks on a phone and a desktop. Record the address, the language, the observed result and the person responsible for any fix.
Six checks before you accept the site
Open a deep link with another browser language
The requested address opens in its own language, including the title, navigation and error messages.
Evidence to keep: Address, browser language and screenshot.
Switch languages from a service page
The switch opens the same service in the chosen language. If the translation is missing, the site explains that clearly.
Evidence to keep: Starting address, chosen language and resulting address.
Submit an invalid, then a valid enquiry
Errors appear in the page language. The valid request receives a localised confirmation and reaches the right inbox once.
Evidence to keep: One test reference from the inbox; remove any personal information.
Update a service condition
An editor can change a booking or delivery condition and identify every translation that still needs an update.
Evidence to keep: Before and after values and the person who approved them.
Check search settings
Each page points to its own canonical address. Indexable translations are linked to each other; private or unfinished pages stay out of the sitemap.
Evidence to keep: Canonical address, language links and sitemap result.
Rehearse a return to the previous release
A test environment can restore the previous version without losing a newer enquiry or content edit.
Evidence to keep: Release references, recovery steps and the result of the rehearsal.
Record the handover decision
Leave a test open if it fails in just one language or on one device. Agree which failures block release, who owns each fix and which checks to repeat after the change. Keep the completed checklist with the handover record.