Multilingual Dental Websites in the GTA: Adding a Language
When a multilingual dental website makes sense in the GTA, which pages to translate first, and how to set up a second language, including right-to-left scripts.
Many GTA clinics have a dentist or front desk team that speaks more than one language. For a lot of patients, that is the reason they choose you. A second language on your website can tell them before they ever call.
Statistics Canada's 2021 Census found that in Toronto and Vancouver, more than one in four people speak predominantly a language other than English or French at home. Mandarin was the main one in Toronto. The census also found that 56.1% of people in Toronto could hold a conversation in two or more languages (Statistics Canada, The Daily, August 17, 2022).
Those are citywide numbers. Your own patients matter more. This guide covers when a second language is worth it, which pages to start with, and how to set it up so patients and Google can find it.
When a second language is worth adding
- Your team speaks it. Someone at the front desk can answer the phone in that language, and ideally a dentist can treat in it.
- Your patients use it. Ask your front desk which languages come up on calls and at the counter. That tells you more than any census table.
- You can keep it current. Every change to hours, fees or team needs to appear in both languages.
- You can reply in it. A form in Persian or Mandarin needs a reply in Persian or Mandarin.
If nobody on your team speaks the language, a translated site sets an expectation you can't meet. A clear “Languages we speak” line on your homepage and team page is the honest option. My dental website checklist for GTA clinics includes it for that reason.
Start with the pages patients need most
You don't need to translate every page on day one. Start with the pages that get a new patient through the door.
- Homepage, with your hours, address and phone number.
- New patients, including what to bring to the first visit.
- Emergency appointments.
- Insurance, payment and the Canadian Dental Care Plan. See how to show CDCP on your dental website.
- Contact and booking.
Translate each of those pages in full. Google warns that translating only the menus and buttons while keeping the main content in one language can give visitors a bad experience (Google Search Central). Add service pages later, starting with the treatments you do most.
Use a fluent translator and a dentist's review
Machine translation is a fine first draft. It can get dental terms and tone wrong, though. Have a fluent speaker edit every page, then have a dentist who speaks the language check the clinical wording.
Translated pages are still your advertising. The same rules that apply to your English pages apply to every other version, so read my plain-English guide to RCDSO advertising rules and check the RCDSO's current guidance before you publish.
Give each language its own web address
Google recommends using a different URL for each language version of a page, rather than cookies or browser settings that change the language on the same address (Google Search Central). A simple pattern is yourclinic.ca/fa/ for Persian or yourclinic.ca/zh/ for Chinese.
- Link the versions with hreflang tags. Google says each language version must list itself and all the other versions, and tags are ignored if two pages don't point to each other (Google Search Central).
- Add an x-default page. Google uses it when no other language matches the visitor's browser setting.
- Don't redirect by guesswork. Google advises against redirecting people based on what you think their language may be.
- Show a language switcher on every page. Google suggests linking to the other language versions so visitors can choose.
- Set the page language in the code. The W3C says to declare each page's language with the lang attribute (W3C).
If you are adding languages as part of a rebuild, plan the new URLs and redirects together. My guide to redesigning a dental website without losing your Google rankings explains how.
Right-to-left languages need more than translation
Persian (Farsi), Arabic and Urdu are written right to left. The whole page has to flip, from the menu and the logo position to arrows, form fields and the order of buttons.
The W3C's advice is to add dir="rtl" to the html tag whenever a page's overall direction is right to left, and not to set base direction with CSS. It also says to declare the language separately, because a language tag does not set direction (W3C).
- Test mixed text, such as an English clinic name or a phone number inside a Persian sentence.
- Use a font that supports the script well at small sizes on phones.
- Check every form, including error messages, in right-to-left mode.
- Mirror icons that point a direction, like arrows, and leave logos and photos as they are.
I've built bilingual English and Persian products with full right-to-left support. On Cheraq, the build checks 2,218 English and 2,218 Persian translation keys, so a missing translation is caught before anything goes live.
Say who speaks which language
A patient who prefers Tamil or Cantonese wants to know who they will talk to. List the languages each dentist, hygienist and front desk member speaks on your team page. Add the same detail to your new-patient page and the footer of your English site, so it is visible even before someone switches language.
Be specific and honest. A line like “Speaks Persian and English” under a dentist's photo is more useful than a row of flags, and it avoids promising a language on days when that person isn't in.
Test every language on a phone
Translated text is often longer or shorter than the English, so buttons, menus and headings can break. Open each translated page on a small phone and check that nothing is cut off. Tap the language switcher from several pages and make sure it lands on the matching page, not the homepage.
Keep both languages in sync
The most common problem with multilingual sites is drift. Someone updates the English holiday hours and forgets the other version. Set a simple rule that no change is finished until it appears in every language.
Your booking form also needs a translated version, with a reply promise your team can keep in that language. My guide to online booking on dental websites covers what that form should ask.
Plan for the ongoing work
The translation is a one-time job, and the upkeep is not. Every translated page is a second copy you need to update when your hours, fees, team or services change. Budget a little time each month for it, and pick one person at the clinic who owns it.
Ask whoever builds your site how the second language works in the editor. Your team should see both versions of a page side by side, and the site should make it obvious when one language is missing or out of date. If updating the second language needs a developer every time, it will fall behind.
What I'd do
Start with one extra language that your team already speaks, and translate five key pages in full. Then watch your calls and form requests for a few months before adding more. Coverage pages are a good example of where this pays off. For Markhamack Dental, I built separate pages for CDCP and the Interim Federal Health Program (IFHP), so patients with those plans find their answer on one page. You can see that in the Markhamack Dental case study, and more on my page about dental website design for GTA clinics.
See your price in two quick steps →