Website planning
How to find gaps in a multilingual website enquiry journey
A translated service page can look finished while its enquiry form still leaves visitors guessing. Error messages may appear in another language, a language switch may lose their place, or the team may receive a request without knowing the visitor's preference. Review the complete journey from reading the offer to receiving a reply. That turns translation into a usable customer experience.
Choose a language scope the team can support
Use actual customer questions and the team's response capability to decide where to begin. Identify a complete service journey that deserves another language: the page, form, confirmation and reply. Assign someone to approve the text and keep it current when the offer changes.
Create an inventory of the small messages as well as the main paragraphs. Include button labels, instructions, validation errors, success messages and email templates. Mark what is translated, what has been reviewed and what still needs work. This makes an unfinished stage visible before launch.
Test switching language during a real task
Link equivalent service pages so a visitor can continue comparing the same offer after changing language. Agree what should happen to partially completed forms. If the interface cannot keep entered information, explain that clearly before the visitor loses it.
For an illustrative test, start an enquiry in English, choose a service and enter a date, then switch to another supported language. Check what remains selected, whether the date is understandable and what language the validation messages use. Record the expected behaviour so the developer and reviewer are testing the same thing.
Review the interface as well as the translation
W3C distinguishes language declaration from text direction. Configure both appropriately, then inspect the actual interface on a phone. When Arabic is supported, check mixed-script names, phone numbers and email addresses alongside the right-to-left content.
Ask a fluent reviewer to complete the form without coaching. Leave a required field empty and enter an incorrectly formatted value to reveal the real error messages. Check that labels remain visible while typing and that help text explains the next step. Document the specific field and message causing confusion.
Include the human reply in the acceptance check
Save the chosen language with the enquiry and agree which person or queue receives it. Define working hours and an alternative route when the usual responder is unavailable. The website should describe the response arrangement the team can actually provide.
Send one test enquiry in each supported language. Compare the visitor's confirmation with the record received by the team: reference, service choice and contact details should agree. Continue through a test reply. Then assign owners to the remaining gaps and repeat the affected journey after they are corrected.
Your next step
A practical checklist
- Each supported journey has a content reviewer.
- Language switches lead to equivalent service pages.
- The behaviour of partially completed forms is defined.
- Labels, help text and error messages have been tested.
- Text direction and mixed-script fields work on mobile.
- Language preference reaches the responder.
- A test enquiry and reply have been reviewed together.