Internationalization for Canadian sites in 2026 is mostly about three languages: English, French, and one of Mandarin, Cantonese, or Punjabi depending on your geography. Done right, multilingual sites pick up substantial slices of audiences that English-only competitors leave on the table — for the cost of a translator, a CMS template, and some hreflang discipline. Done wrong, you get duplicate- content penalties, broken canonical signals, and visitors landing on the wrong language. This guide covers what to ship, the tooling that matters, and the BC-specific patterns most sites get wrong.
Who needs multilingual in Canada
Honest take: not every Canadian site needs French, and very few need anything beyond English + French. The real audiences:
- National brands and federally-regulated entities. French is mandatory under federal language requirements for many sectors (banks, telcos, federal agencies).
- Quebec-targeting businesses. Quebec's Bill 96 and Charter of the French Language require French as the primary language for businesses operating in the province.
- Canada-wide e-commerce serving Quebec customers meaningfully — French translation pays back via better Quebec conversion.
- BC service businesses in Lower Mainland communities. Mandarin/Cantonese for Richmond and Burnaby, Punjabi for Surrey, Tagalog and Vietnamese for some neighborhoods. ROI varies by category but is real for service businesses serving immigrant communities.
Two architectural approaches
Path-based (/en/, /fr/, /zh/)
The Canadian default. URLs likeclickwebstudio.com/en/services andclickwebstudio.com/fr/services. Cleanest separation, easiest hreflang setup, simplest CMS structure.
Trade-off: root domain serves a redirect or language-switcher rather than English directly. Most modern frameworks (Next.js, Astro) handle this with a default locale that doesn't carry the prefix.
Subdomain-based (en.example.com, fr.example.com)
Less common in 2026. Used by some large enterprises with separate regional teams managing each language site. Adds DNS and SSL complexity. Not recommended for most Canadian SMBs.
ccTLD-based (example.ca, example.qc.ca)
Rare and expensive. Different domains for different languages or regions. Justified only for major brands with serious budget and strong reasons to keep regional brands separate.
hreflang: the part that breaks
Every page in every language needs hreflang annotations telling Google which language version to serve to which audience. Two ways:
- HTML link tags in the head — easiest for most sites:
<link rel="alternate" hreflang="en-CA" href="https://example.com/en/page" /> <link rel="alternate" hreflang="fr-CA" href="https://example.com/fr/page" /> <link rel="alternate" hreflang="zh-CA" href="https://example.com/zh/page" /> <link rel="alternate" hreflang="x-default" href="https://example.com/en/page" />
Sitemap-based hreflang is also valid and scales better for large sites. Each URL in the sitemap lists its alternates.
Three rules that must hold:
- Every alternate must point back. Bidirectional, always.
- x-default fallback set, usually to the primary language.
- The page rendered must match the language indicated.
Quebec compliance: Bill 96 and Charter of the French Language
Operating in Quebec or selling to Quebec customers means complying with the Charter of the French Language as amended by Bill 96 (in force since 2022, fully phased in by 2025). Practical requirements for websites:
- French must be the primary language. Cannot be visibly secondary or smaller than other languages.
- Required notices, terms, and consumer-facing content must be available in French.
- Marketing materials targeting Quebec must be in French (with English permitted as a secondary language, equally or less prominent).
- Office québécois de la langue française (OQLF) actively enforces. Penalties exist.
Practical implication for most Canadian SMBs: French version genuinely good (not Google-translated), French rendered as primary or equal-prominence on Quebec-targeting pages.
Translation tooling
| Tool / approach | Best for | Typical cost |
|---|---|---|
| Professional human translator | Public marketing copy, legal, brand | CA$0.18–$0.35/word |
| Smartling, Phrase, Lokalise | Translation management at scale | From USD $200/mo + translation fees |
| DeepL Pro | Internal docs, supplementary content | From USD $9/mo |
| Google Translate API | Last-resort, emergency | USD $20/1M characters |
| Hybrid: machine + human review | Most cost-effective for volume content | CA$0.06–$0.12/word |
For public-facing marketing copy, especially French for Quebec compliance, use professional human translators or hybrid machine-plus-human workflows. Pure machine translation reads as AI-translated to native speakers and converts worse than English-only.
CMS support for multilingual
- Sanity — strong field-level localization, code-defined schema. Good for technical teams.
- Contentful — mature locale-per-field, marketing-team friendly UI.
- Storyblok — folder-based locale system. Visual editors love it.
- WordPress + WPML or Polylang — heavy but battle- tested. Many Canadian SMB sites still use this.
- MDX in repo with locale files — for static sites, works but requires discipline.
For broader CMS picks, see our 2026 headless CMS comparison.
BC-specific multilingual: Mandarin, Cantonese, Punjabi
Lower Mainland service businesses often see real ROI from a third language. Honest specifics:
- Mandarin and Cantonese for Richmond and Burnaby practices. Family medicine, dental, real estate, legal services serving these communities measurably out-convert with Mandarin or Cantonese pages. Both languages share written characters; many sites ship one set of Chinese pages with a toggle for traditional vs simplified.
- Punjabi for Surrey practices. Family law, immigration, personal injury, home services serving the Surrey-area Punjabi community. Gurmukhi script support required.
- Tagalog and Vietnamese for specific neighborhoods, less commonly translated. Higher conversion per page but smaller absolute audience.
Multilingual SEO patterns
- One canonical per language version. Each language version self-canonicalizes; alternates link to the others.
- Structured data in the page's primary language. Article schema on the French page should have French headline and description.
- Sitemap entries for every language version. With hreflang annotations.
- Don't auto-redirect by IP or browser language. Show a language switcher; let visitors choose. Auto-redirects confuse search crawlers and frustrate visitors who want English in a French region or vice versa.
Cost ranges for multilingual Canadian sites in 2026
| Scope | Cost (CAD) | Timeline |
|---|---|---|
| Adding French to existing 20-page site | $5,500 – $15,000 | 3–5 weeks |
| EN/FR built from start, marketing site | $22,000 – $55,000 | 8–14 weeks |
| EN/FR + one Asian language | $35,000 – $85,000 | 10–16 weeks |
| Enterprise multilingual (4+ languages) | $70,000 – $200,000+ | 14–24 weeks |
Common multilingual mistakes
- Google Translate widget as the entire i18n strategy. Damages SEO (translated content isn't indexed), reads as machine-translated to native speakers, doesn't comply with Bill 96.
- Auto-redirect by IP. Confuses search engines, frustrates traveling visitors, breaks shareable links.
- Hreflang pointing to redirects or 404s. Common cause of multilingual SEO problems. Test alternates regularly.
- French translation that's clearly machine-done. Conversion-killer in Quebec; legal risk under Bill 96.
- Forgetting structured data localization. Article schema on the French page should have French content.
Adding multilingual support to your Canadian site?
Tell us your audience, the languages you need, and your CMS. We'll send a one-page recommendation with platform, translation approach, and a fixed quote — within three working days.
Book a consultation →Frequently asked questions
Do all Canadian websites need to be in French?
No. French is mandatory only for federally-regulated entities (banks, telcos, federal agencies) and businesses operating in or targeting Quebec under Bill 96. National e-commerce sites benefit from French translation but aren't legally required to. BC-only service businesses serving English-speaking customers don't need French. The honest test: do you sell to Quebec customers meaningfully? If yes, ship French; if no, the cost rarely pays back.
What does Bill 96 require of my website?
Quebec's Bill 96 (in force since 2022, fully phased in 2025) requires French as the primary language for businesses operating in or marketing to Quebec. French content must be visibly equal or more prominent than other languages on Quebec-targeting pages. Required consumer-facing content (terms, notices, marketing) must be available in French. The OQLF actively enforces. Pure machine translation typically isn't considered compliant.
Should I use Google Translate or pay for human translation?
Pay for human translation on public marketing copy, especially French for Quebec compliance. Cost: CA$0.18–$0.35/word for professional human, CA$0.06–$0.12/word for hybrid machine-plus-human review. Pure machine translation reads as AI-translated to native speakers, converts worse than English-only on conversion-sensitive pages, and may not comply with Bill 96.
How do hreflang tags work?
hreflang tells Google which language version of a page to serve to which audience. Each language version of every page needs hreflang link tags pointing to all alternates, including itself. Add an x-default fallback. Three rules must hold: every alternate is bidirectional, x-default is set, the page rendered matches the language declared. Sitemap-based hreflang is also valid and scales better for large multilingual sites.
Should my Canadian site auto-detect language by IP?
No. Auto-redirecting by IP confuses search crawlers (which can't index a French version they keep getting redirected away from), frustrates traveling visitors, and breaks shareable URLs. Show a language switcher and let visitors choose. Optionally store the preference in a cookie for return visits, but the first visit should land at the URL the visitor or referrer specified.
Is Mandarin or Cantonese worth translating to for BC service businesses?
For Lower Mainland service businesses (Richmond, Burnaby, parts of Vancouver), often yes. Family medicine, dental, real estate, legal, and home services serving these communities see measurable conversion lift from Mandarin or Cantonese pages. Both languages share written characters, so one Chinese version with simplified/traditional toggle covers both audiences. ROI varies; a small translated landing page (CA$2,500–$5,000) often pays back within 6 months for high-volume practices.
