Bilingual Websites in Québec: One Page per Language, Not a Translate Button

When a client asks me for a bilingual site, I start with the same question every time: do you want two real versions of your site, or just a button that translates whatever is on screen so the question goes away? The answer changes how the site gets built, how Google reads it, and what Québec's language rules expect from you. Here is how I approach a bilingual site when I build one, and why an automatic translation widget is almost always the wrong call.

What is wrong with a translate button?

A translation widget swaps out the text on screen, but it does not create a new page. The web address stays the same, the underlying code stays in whichever language it was written in, and what the visitor sees depends on a script running after the page loads. For a visitor in a hurry, that can look convenient. For everything else, it causes problems.

Start with quality. Automatic translation often misreads the sense of a sentence, especially in a technical field or with Québec-specific phrasing. A reader who hits an awkward sentence on your services page starts wondering whether the rest of your work got the same careless treatment.

Then there is structure. A search engine indexes a web address, not a temporary state of a page after someone clicks a button. If your English content only exists in the browser's memory after a language toggle, it has no address of its own to rank, so there is nothing for an English search to surface.

What does Québec's language law expect from a website?

The Charte de la langue française governs the language of commerce and business in Québec, including the tools a company uses to sell to its customers or communicate with them. The general principle, for a site aimed at a Québec audience, is that the French version needs to be at least as present and as complete as any other language on offer, not tucked behind a dropdown that translates it approximately.

I am not a lawyer, and the details depend on your industry and your situation. If language compliance is a sensitive question for your business, a lawyer or the Office québécois de la langue française can confirm exactly what applies to you. What I can say from the side I work on, building sites for Québec clients, is that a complete French page and a complete English page, each with its own address, settles the question at the root: there is no secondary or approximate version, there are two pages written to be read.

How do you structure a bilingual site with one page per language?

The simplest structure, and the one I use for a website build, puts French at the domain root and English under an /en/ subfolder. Every French page has an English counterpart at its own address, for example /services/ in French and /en/services/ in English.

That separation has a few concrete effects.

Each page gets its own title, its own meta description, and its own content, written for the language of that page instead of translated word for word from a master version. A literal translation often reads strangely, while text written directly in the target language reads naturally to the person receiving it.

The navigation menu offers an explicit link to the counterpart in the other language, instead of a toggle that swaps the display without changing the address. The visitor clicks, the address changes, and they know they moved from one version to the other.

Google can index both pages separately, each with its own content, and surface each one for the right search in the right language.

How do you write a translation that does not sound translated?

The surest way to get text that sounds translated is to start from one language and push it word for word into the other. The result reads, technically, but it never sounds quite natural: the phrasing still belongs to the source language, and a native reader of the other language notices, even without knowing why.

I would rather write each page directly in its own language, working from the same underlying message, instead of translating a page that already exists. A sales pitch in French sometimes leads with a different argument than the same pitch in English for the same service. The points that persuade are not always ordered the same way, and some words simply do not carry over cleanly.

The same goes for keywords. A client searching for your services rarely types the exact translation of a French term. A beauty clinic targeting "soins esthétiques" in French is not automatically targeting "esthetic care" in English. The term people actually type in English can be different, and each page should be built around the words its own audience uses, not a translation of the other page's keyword.

How do you connect your French and English pages with hreflang?

Once you have two separate pages, the next step is telling Google they are language versions of the same content. That is the job of the hreflang tag, placed in the header of each page, pointing to its counterpart in the other language.

In practice, the French page carries a tag pointing to where its English version lives, and the English page carries a tag pointing back to the French version. That link has to run both ways: if only one of the two pages points to the other, Google disregards it.

This is the mechanism that lets a visitor searching in English land directly on your English page, and a visitor searching in French land on the French version, without a redirect or a language picker on load. Much of the SEO work on a bilingual site comes down to this: two properly built pages, correctly linked, beat a single page trying to serve both languages at once.

What mistakes should you avoid when launching a bilingual site?

The first mistake is mixing languages on the same page, for example a French menu with English product listings because the translation is not finished yet. A visitor who lands on a half-translated page starts doubting the rest of the site.

The second is duplicating a page into another language without really adapting it: translating the words without revisiting the examples, the units, or the references that only make sense to a Québec audience. An English page aimed at a reader in Toronto or elsewhere in the country does not need the same local references as a French page built for Laval or Longueuil.

The third is forgetting to update both versions at the same time. If you change a price, a schedule, or an offer on the French page and leave the English version untouched, the two pages contradict each other, and a visitor who compares them notices.

The fourth, more technical, mistake is letting a page skip referencing itself in its own hreflang tag alongside the link to the other language. A page that does not confirm its own language in its own tags can confuse a search engine trying to decide which of the two versions to show for a given search.

A properly built bilingual site takes a bit more work up front than a translation widget, but it avoids all four of those problems at once, and it gives every visitor a page built for them, not an improvised translation of someone else's page.

Drafted with AI assistance, checked and published by Marven Salgado.