What should a bilingual website offer beyond a translated homepage?
Follow one customer from their first search through a quote request, a reply and an update in their chosen language.
Imagine a Markham picture-framing studio where two staff members handle enquiries in English and French. A customer reads the French service page, opens the framing request and finds the measurements, error messages and confirmation in English. The translation ended a few clicks before their task did.
Start with the service your team can actually deliver in both languages. A Toronto studio might support a different pair, or offer its second language only by appointment. Choose the languages and contact options from how your staff serve customers.
Map the smallest complete customer journey
For the framing studio, the first release could cover custom framing, examples of materials, how to visit and the enquiry form. Include the thank-you email and the message acknowledging a request. If one staff member handles French replies on weekdays, state the response window in both versions.
Give a fluent staff member the job of reading the journey as a customer. Ask them to explain a phrase such as “float mount” in the words they use at the counter. Let them check sizes, currency and timing too. A natural-sounding translation can still describe the wrong service.
Give each language its own address
The studio could publish its English service at /en/custom-framing/ and its French equivalent at /fr/encadrement-sur-mesure/. Both URLs can be shared directly. Put a plainly labelled “English” and “Français” switcher on the service pages and connect each choice to that service in the other language.
A bilingual customer might search in English and prefer to read in French. Keep the language choice available regardless of device language or location. When a page is available in only one language, label that clearly at the link and offer a way to ask for help.
Show search engines which pages belong together
Ask your developer to add hreflang annotations to each matching pair. These identify the equivalent page for another language. For the illustrative Canadian pair, each page can reference both the en-CA and fr-CA URLs, including itself. Both URLs should load directly and be accessible through ordinary links.
Read the main heading, title and description in each language. The French service page should describe the same framing offer in language a French-speaking customer would use. Keep the customer’s selected location when they switch languages. Opening a French page for a Toronto visitor should never silently switch their chosen store to Markham.
Test the switch and assign an editor
- Start on one translated service page, switch languages twice and confirm you return to the same service and location.
- Submit a French test enquiry. Check the required-field message, confirmation, email subject and the staff member who receives it.
- Before publishing a new turnaround time, change both service pages and both automated replies. Keep a short list of paired URLs and assign the update to one owner.
Get the Done48 website launch checklist