Quebec Bill 96 + Bilingual SEO (2026)

The compliance position in one paragraph

Quebec's Bill 96 (in force since June 2022, with full enforcement progressively rolling out through 2025–2026) strengthens the Charter of the French Language. For SEO and websites, the practical impact: French content must be 'as available' as content in any other language. For commercial websites serving Quebec consumers, that effectively means French versions of all marketing pages, product descriptions, and customer-facing communications. The SEO architecture that works: full content equivalence in French, hreflang annotations, distinct French URLs (or path-prefix structure), and translated metadata. Half-measures (auto-translated pages, partial coverage) create both legal and SEO risk. This guide is informational; consult Quebec counsel for your specific situation.

What Bill 96 changed

Bill 96 amended the Charter of the French Language (commonly known as Bill 101, in force since 1977). The amendments strengthen French as the language of commerce in Quebec, expand the Office québécois de la langue française's (OQLF) authority, and tighten requirements for commercial communications.

For website operators, the most significant changes are around the 'as available' principle: French content must be available on terms at least as favourable as any other language. This affects not just translation completeness, but how French content is surfaced, navigated to, and presented.

Who it applies to (and who it doesn't)

• Applies: businesses with a Quebec presence

  If you have an office, employees, or registered business presence in Quebec, the Charter applies broadly to your commercial activities.
• Applies: businesses targeting Quebec consumers

  If your website actively markets to Quebec consumers (Quebec-specific landing pages, Quebec-routed advertising, Quebec shipping addresses), Charter requirements apply to those communications.
• Does not apply: business outside Quebec without active Quebec marketing

  A US-based business with a website that occasionally receives Quebec orders is not generally subject to the Charter's commercial-communications requirements (though other Canadian regulations may still apply).
• Does not apply: purely informational content

  Non-commercial blogs, personal sites, and editorial content from non-Quebec publishers generally aren't covered.
• Caveat: this is informational, not legal advice

  Application to specific businesses depends on facts and circumstances. Consult Quebec counsel if your situation is ambiguous.

Website-specific requirements

• French version of commercial website pages

  Marketing pages, product/service descriptions, contact pages, and key conversion paths need to be available in French.
• French content 'as available' as English

  If your English homepage has 5 prominent CTAs and a video, your French homepage should too. Stripped-down French pages are not 'as available'.
• French-by-default for Quebec visitors

  Best practice (not strictly mandated): geo-detect Quebec IPs and serve French by default, with an English language switcher. Technically you can show English by default with a language picker, but the OQLF has indicated French-by-default better aligns with the spirit of the Charter for Quebec audiences.
• Equivalent metadata

  Page titles, meta descriptions, OG tags, social previews — all in French for French pages.
• Customer service availability in French

  If you offer customer service through the site (chat, contact form, phone numbers), French-language service must be available.

Bilingual SEO architecture that works

• URL structure: subfolder by language

  /en/ and /fr/ subfolders work well in Canada and are Google's preferred pattern. Separate domains (.ca for English, .qc.ca or .fr for French) are also valid but harder to manage. Avoid query-string language parameters (?lang=fr) — they index inconsistently.
• hreflang annotations on every bilingual page

  <link rel='alternate' hreflang='en-CA' href='...' /> and <link rel='alternate' hreflang='fr-CA' href='...' />. Plus self-referencing entries. Plus an x-default fallback. Implement as link tags in <head>, not via HTTP headers (more reliable).
• 1:1 content equivalence

  Every English URL has a French equivalent at the corresponding subfolder. If /en/services/seo/ exists, /fr/services/referencement/ exists too. Mismatched coverage signals confused intent to both Google and the OQLF.
• Translated, not transliterated, slugs

  /fr/services/seo/ is wrong; /fr/services/referencement/ is right. The French URL should use French keywords.
• Sitemap segmentation

  Submit a sitemap-en.xml and sitemap-fr.xml, plus an index sitemap referencing both. Helps Google understand the bilingual structure.
• GBP listings in both languages where possible

  For physical Quebec locations, run primary GBP listings in French. English-language secondary descriptions are allowed but French should lead.

Translation quality and the auto-translate trap

Auto-translated French content is a frequent compliance and SEO risk. Modern machine translation (DeepL, Google Translate) is good — sometimes excellent — for general content, but it consistently fails on idiom, tone, and Quebec-specific French (which differs in vocabulary and phrasing from European French).

The OQLF has explicitly noted that auto-translated content can fail the Charter's quality requirements. From an SEO perspective, low-quality French content underperforms in French Quebec search.

• Use professional Quebec French translators

  Native Quebec French translators, ideally with Canadian commercial-content experience. Costs C$0.20–C$0.45/word for high-quality work.
• Translate and adapt, don't just translate

  Cultural references, examples, brand voice — all need adaptation, not just word-for-word translation.
• Use AI as a draft layer, not a publishing layer

  DeepL or GPT-class translation can produce a serviceable first draft for a Quebec French translator to refine. Faster and cheaper than full from-scratch translation; safer than auto-translation alone.
• Quality-check with French-speaking team or consultant

  Have a Quebec French speaker review final content before publication. The mistakes auto-translation makes are often invisible to non-French-speakers but obvious (and damaging) to Quebec readers.

A pre-launch bilingual checklist

• Every English commercial page has a French equivalent

  1:1 content coverage.
• URL structure uses /en/ and /fr/ subfolders

  Or equivalent clear-language path.
• hreflang annotations on every page

  Including self-references and x-default.
• Page titles, meta descriptions, and schema metadata are translated

  Not just body content.
• Translation done by Quebec French native speakers

  Not auto-translated.
• French is default for Quebec-IP visitors

  With an English-language switcher.
• Forms, error messages, and email auto-responders are bilingual

  Conversion paths must work end-to-end in French.
• Customer service available in French

  Hours, channels, response times documented.
• Quebec-specific GBP listings are French-primary

  Where applicable.
• Sitemap segmented by language

  Submitted to GSC and Bing Webmaster Tools.

Frequently Asked Questions

Common compliance questions from Canadian operators (informational, not legal advice).