A French website is not a translated website

If your business is heading into Québec, or your Québec business is heading into English Canada, someone on your team has probably said the phrase “we’ll get the site translated”. That sentence is where the trouble starts, because it frames a product problem as a paperwork problem.

The enforcement floor

Start with the legal layer, because it has teeth now. The Office québécois de la langue française logged a record 10,371 complaints in 2024-25, up 14% in a year, and non-compliant websites have historically been among the top complaint categories (OQLF, annual reporting; Le Devoir, 2025). The office reports that the overwhelming majority of flagged businesses take corrective measures once contacted, which tells you two things: enforcement is real, and retrofitting under a deadline is how most companies end up doing this, at the worst possible moment.

Alongside sits Law 25, Québec’s privacy law, which carries its own obligations for any site collecting personal information from Québec residents: consent, transparency, a named person responsible. Neither law is exotic. Both are table stakes that Ontario businesses routinely discover late.

The product failure underneath

Compliance, though, is the shallow end of the problem. The industry that sells “translation” knows this privately. Toronto’s own trade press has covered how the standard model, where English creative is finished first and then handed to a Québec partner, keeps producing work that misses; as one agency put it in Strategy this year, “often, the creative doesn’t work.”

The reason is structural, and it is the same reason translated software fails. A product designed in English and translated afterwards is a French costume on an English body. The seams show everywhere the product does real work: the form that validates postal codes but not accents, the transactional emails still arriving in English, the search that cannot find “Geneviève”, the support flow that dead-ends the moment a customer replies in French. Each seam is small. Together they tell a French-speaking customer, precisely and repeatedly, that they are the second audience.

When we built the platform for Guy Hoquet Québec, the founders’ instruction amounted to one sentence: it must not feel like an import. That constraint shaped the architecture, not the copy. The broker-matching flow at the centre of the site was designed and built in both languages simultaneously, because a matching conversation that was conceived in English and then translated would ask French questions with English assumptions. The French was load-bearing, so it had to be present from the first commit.

What “built bilingual” means concretely

If you are evaluating a build, or auditing the one you have, bilingual-as-architecture looks like this:

• URLs and structure. Each language lives at its own stable addresses, with correct hreflang pairing, so search engines index two first-class sites rather than one site with a shadow.
• A content model where both languages are equals. Every piece of content has a home in both languages by design, and the team can edit either without a developer.
• Features, not just pages. Forms, validation messages, emails, receipts, error states, search: the product’s behaviour is bilingual, not just its brochure layer.
• A team that can operate it. If publishing a French page requires the vendor, the site is bilingual only until the first content change.

None of this costs meaningfully more when it is designed in from the start. All of it is expensive to retrofit, which is why the OQLF’s complaint statistics look the way they do.

The bilingual market is not a compliance burden wearing a maple leaf. Roughly one Canadian in five speaks French, Québec is an economy of nearly nine million people next door to Ontario, and most of your competitors are serving it in translation. Building for it properly is one of the cheaper competitive advantages available to a mid-sized Canadian business right now. It just has to be bought as software, not as translation.

If the product on your roadmap has to work in both languages, the cheapest moment to decide that is before the first commit. Book a Discovery and say “bilingual” in the first sentence; the spec will treat French as architecture from day one.