Bill 96 and SEO: What Quebec's Law Requires

Since June 1, 2025, any commercial website reachable by Quebec residents has been operating under a legal requirement most SEO teams outside the province have never had to think about: French content must be presented with prominence at least equal to English. That requirement comes from Bill 96, an amendment to Quebec's Charter of the French Language, and it turns what used to be a nice-to-have (a French version of the site, eventually, maybe) into a compliance obligation with real financial exposure attached.

For SEO specifically, the law doesn't just ask for a French page to exist somewhere. It reshapes hreflang architecture, metadata, URL structure, schema markup and Google Business Profile management for any brand with Quebec-facing business, whether or not that brand has any interest in ranking well in French. This piece walks through what the law actually requires, what the enforcement reality looks like so far, and what a technically correct response looks like for a website's SEO foundation.

What Bill 96 Actually Requires

The core rule is prominence, not just presence. A commercial website reaching Quebec residents needs French content that is at least as visually and structurally prominent as any English equivalent, enforced by the Office québécois de la langue française (OQLF). In practice, legal guidance interprets "markedly predominant" to mean the French version must occupy at least twice the visual space of any other language on the page, a specific, measurable standard rather than a vague aspiration. This is a meaningfully higher bar than simply having a French link buried in a footer, or a machine-translated version accessible through a small language toggle. Legal analysis from multiple Canadian firms describes penalties running CAD 3,000 to 30,000 per day of offence for non-compliance, a range confirmed independently by Éducaloi, Norton Rose Fulbright, Borden Ladner Gervais and Osler in their public guidance on the law, with penalties doubling for a second violation and tripling for subsequent ones.

The OQLF isn't a paper tiger here, and the enforcement data tells a consistent story across two different measurement windows. Nimdzi-reported figures put OQLF complaints at 9,125 in the 2023-2024 period, a 33% year-over-year increase. A separate measurement window, April 2024 to March 2025, recorded more than 10,000 complaints and 9,813 inspections carried out. These are two different reporting periods from different sources, not a single figure to be merged, but both point the same direction: complaint volume in the low five figures annually, with inspection activity roughly matching complaint volume, which is a meaningfully active enforcement posture for a language law rather than a rule that sits quietly unused, an assumption a lot of non-Quebec-based businesses seem to be operating under.

One enforcement detail worth knowing specifically: the OQLF has publicly cautioned that AI-generated translation carries particular risk, precisely because it tends to produce the kind of perfunctory, non-localised French that fails the "markedly predominant" and genuine-equivalence standard the law is built around. A machine-translated page might technically have French text on it and still trigger a complaint, both because of quality issues in the translation itself and because automated tools frequently miss functional elements, forms, checkout flows, error messages, that also need to be French-equivalent, not just the visible marketing copy.

The SEO Architecture This Forces

Once French prominence is a legal requirement rather than a marketing choice, the technical SEO implications follow directly.

Dual hreflang architecture becomes mandatory, not optional. A site targeting Quebec needs correctly implemented hreflang="en-CA" and hreflang="fr-CA" tags connecting genuinely equivalent pages, not a single English page with a translation plugin bolted on. Search engines use hreflang to decide which language version to serve which searcher, and getting this wrong creates duplicate-content confusion on top of the legal exposure.

French metadata, URL slugs and schema, not just body content. Bill 96's prominence standard reasonably extends to everything a searcher or search engine sees before reaching the page itself: title tags, meta descriptions, URL structure and schema markup. An English URL slug with a French body underneath is a half-measure that satisfies neither the law's spirit nor a genuinely bilingual SEO strategy.

Quebec French, not generic French translation. This is where the legal requirement and the SEO opportunity point the same direction. Search performance data confirms that genuinely localised Quebec French content outperforms generic French translation in Quebec's own search results, because Quebec French carries distinct vocabulary, idiom and cultural reference points that a France-oriented translation misses. Treating this as a single "French" content pass rather than a Quebec-specific one leaves ranking performance on the table even after the legal box is technically checked.

French Google Business Profile listings. For any business with local Quebec presence, that means a French-language Google Business Profile alongside the English one, not a single bilingual listing that satisfies neither language cleanly.

SEO Element	Half-Measure (Risk)	Bill 96-Aligned Approach
Language toggle	Small link, English page loads by default	Equal visual weight, French detected/served appropriately
URL structure	English slug retained for French page	Genuine French URL slugs, hreflang-linked
Content source	Machine translation of English original	Native Quebec French writing/review
Local listings	One bilingual Google Business Profile	Separate French-language listing
Schema markup	English-only structured data	Parallel schema for French pages

Quebec French Keyword Research Isn't French Keyword Research

Compliance aside, there's a purely commercial reason genuinely Quebec-focused keyword research matters: France-derived French keyword databases are unreliable for Quebec, because Quebec French vocabulary genuinely diverges from European French in ways that change what people actually type into search boxes. A "dépanneur" is a convenience store in Quebec, not a repairman. "Cellulaire" is the everyday Quebec French word for a mobile phone, where European French defaults to "portable." "Fin de semaine" is standard Quebec usage for "weekend," while European French commonly uses "week-end" itself, borrowed directly from English. None of these are edge cases, they're common, everyday commercial search terms, and a keyword strategy built on a European French dataset will systematically miss them.

Seasonal and cultural search patterns compound this. Terms like "cabane à sucre" (sugar shack, tied to Quebec's spring maple season) and "déneigement" (snow removal) spike on a schedule tied to Quebec's own cultural and climate calendar, not a generic North American pattern a translated content calendar would assume. A workable Quebec French keyword research process combines Google Keyword Planner segmented specifically to Canada with French language settings, Quebec-specific competitor analysis through tools like Ahrefs or Semrush, Google Trends Canada to compare French versus English query volume regionally, and, where possible, primary research through Quebec-specific forums and social communities to surface authentic vocabulary that automated keyword tools may not fully capture on their own.

There's a bilingual-switching pattern worth planning content around too: many Quebec users move between French and English queries depending on topic, particularly in technology and professional-services categories, which means a Quebec content strategy sometimes needs to account for genuinely bilingual search behaviour within the same user, not just two separate, cleanly divided audiences.

The Opportunity Hiding Inside the Compliance Requirement

Quebec's SEO agency market shows roughly 3.4 times lower competition density than English Canada, according to research cross-validated across multiple sources for this piece, which makes genuine Quebec French capability a real first-mover advantage rather than pure cost. Combined with 52% of Quebec internet users having tried generative AI by October 2025 (NETendances 2025, Université Laval), a properly built bilingual site isn't just avoiding OQLF penalties, it's positioned in a market with real, under-served demand.

One caution worth naming plainly: bilingual scope adds genuine production and QA overhead. Estimates for that uplift vary, and a single-source figure circulating in some market research (a 30-50% uplift over English-only scope) hasn't been independently corroborated in this research, so it's presented here as a planning consideration rather than a fixed rule. What is consistent across sources is that bilingual Quebec work needs to be scoped as its own workstream from the proposal stage, not estimated as "add French later" once an English site is already built.

Where to Start

For a business that hasn't yet addressed Bill 96 on its website, the practical starting point is an honest audit: does French content exist at genuine visual and structural parity with English, or is it a smaller, secondary version. From there, the technical fixes (hreflang, French URL slugs, French schema, separate Google Business Profile listings) are well understood and implementable in a defined project, while the content itself, the part that actually determines whether the French site performs, needs native Quebec French involvement rather than a translation pass treated as the finish line.

---

Frequently Asked Questions

Does Bill 96 apply to us if we're not based in Quebec or even in Canada?

Yes. The law applies based on whether the website reaches Quebec residents, not where the business or its website operator is located. A foreign-based company selling to Quebec customers is subject to the same French-prominence requirement as a Quebec-headquartered business.

Is a machine-translated French page enough to comply?

It reduces legal risk somewhat by having French content present, but it's a weaker position than genuinely localised Quebec French, both for compliance (prominence and quality can be scrutinised) and for SEO performance, since translation-derived content consistently underperforms native Quebec French in this market's own search results.

What counts as "at least as prominent" under the law?

The general standard is visual and structural parity: comparable placement, size and accessibility for French content relative to English, not a smaller link or a secondary page reached only through extra clicks. Specific edge cases are best reviewed with Quebec-qualified legal counsel, since this piece is not legal advice.

Do we need a separate French Google Business Profile?

For any business with genuine local presence in Quebec, yes, a dedicated French-language listing performs better and aligns with the broader French-prominence principle better than a single bilingual profile trying to serve both languages at once.

Does the OQLF specifically warn against using AI or machine translation for the French version?

Yes. The OQLF has publicly cautioned that AI-generated translation carries particular compliance risk, both because it tends to produce non-localised, perfunctory French that can fail the law's genuine-equivalence standard, and because automated tools frequently miss functional site elements, forms, checkout flows, error messages, that also need proper French versions, not just visible marketing copy.

How much more does bilingual SEO scope typically cost?

This varies by project and hasn't been independently corroborated to a single fixed percentage in this research. What's consistent is that bilingual Quebec work should be scoped as a distinct workstream, with native-speaker content review built in, from the proposal stage rather than added as an afterthought to an English-only budget.

---