Do you need a bilingual website in Quebec?

A Montréal restaurant owner asked us last spring whether adding a little EN/FR switch in the corner of his site was enough. It is not, and the gap between "we have a French toggle" and "we have a French website" is where most small Quebec businesses get caught. This post is the practical version, written for an owner, not a lawyer.

To be clear up front: this is not legal advice. Quebec's language rules are real and they change, so for anything specific to your situation you want a professional who works in that area. What follows is how the requirement actually shapes a website build, which is the part we can speak to.

What the rule is asking for

Quebec's Charter of the French Language, strengthened in recent years, treats a commercial website as commercial communication. If you do business in Quebec, your public-facing content is expected to be available in French. In a lot of contexts French also has to be at least as prominent as the other language, not buried behind a flag icon.

The practical translation for a small business: French is not the afterthought version of your site. It is a first-class version. Both languages carry the same pages, the same menu, the same service descriptions, the same contact form. A site that has a polished English homepage and three half-translated French pages is the thing that gets a business in trouble, and it also reads as careless to a Montréal customer who lands on the French side and finds it thinner than the English one.

Why the auto-translate toggle fails

Three reasons, and they stack.

First, quality. Machine translation of a restaurant menu or a legal service description produces French that a native speaker clocks as wrong in the first sentence. In Montréal that is not a small thing. It signals that the French market is an afterthought, which is exactly the impression the rules exist to prevent and exactly the impression that loses you the table booking.

Second, indexing. A toggle that swaps text on the page with JavaScript after it loads often leaves Google with one URL and one language to index. You want the French version to live at its own real address, something like votresite.ca/fr/menu, so it can rank on its own for French searches. Montréal customers search in French. If your French content does not exist as its own page, it does not show up.

Third, maintenance. A bolted-on translation layer breaks quietly. You update the English menu, the French falls out of sync, and nobody notices until a customer does. A proper bilingual build treats the two languages as two parallel sets of pages that you maintain on purpose.

What a compliant build actually looks like

The shape we use for a Quebec business is boring on purpose, because boring is what holds up.

Two language paths, each with its own URLs. A clear language choice that a visitor makes once and the site remembers. Real human-written French, not generated, with a francophone reviewing it before launch. The hreflang tags that tell Google these are the same pages in two languages, so the right one shows for the right searcher. And a content workflow where the French and English versions get updated together, not one and then eventually the other.

That last part is the one owners underestimate. Bilingual is not a launch task you finish. It is a habit the site has to support, which is why the structure matters more than the initial translation.

What it changes about the project

A few things, and it is worth knowing before you start.

It roughly doubles the copy. Every page exists twice, which means every page has to be written twice, well, in both languages. Budget for the French writing the same way you budget for the English.

It changes the navigation and the small UI text, the buttons, the form labels, the error messages, the email confirmations. Those have to be bilingual too, and they are the bits a rushed project forgets.

It does not double the design or the build. The layout, the components, and the structure are shared. Done right, the second language is mostly a content and routing problem, not a second website. A studio that quotes you for "two sites" either does not build this often or is padding.

The Montréal work we do

We build bilingual the way Quebec actually needs it: French as a first-class version with its own URLs, written by a person, indexed on its own. The Montréal page covers what we do for businesses across the city and the rest of Québec. For the vertical we get asked about most there, see web design for restaurants in Montréal.

If you have a site today and you are not sure whether the French side holds up, send it over for a free audit. We will tell you plainly whether what you have is a real bilingual site or an English site wearing a toggle, and what it would take to fix it. The comparison page covers how a built-for-purpose bilingual site stacks up against the template-builder version, which is where most of these compliance gaps start.