Bilingual WordPress site: keeping French on equal footing

Most Quebec WordPress sites are bilingual, or should be. The hard part is not translating the home page. It is keeping both versions complete over time: every new page, every plugin button, every automated email. Here is how to set up a bilingual site that keeps French at least on equal footing.

General information, not legal advice. Read the notice.

What “terms at least as favourable” means

The Charter allows a version in another language, provided the French version is available on terms at least as favourable (section 52). The Regulation adds that two separate versions are allowed if the French one is available on conditions of accessibility and quality at least equal (section 10).

The OQLF puts this in concrete terms: visitors should not have to make an extra effort to find the French, or change their computer or phone settings (OQLF website guide, in French). Any content published in the English version must also be in the French version.

Choosing a structure

Two approaches dominate on WordPress:

  • One page per language, linked together. Each page exists in French and in English, with its own URL, and a plugin links the two. This is the clearest approach for Bill 96: you can see right away when a translation is missing.
  • One page, two layers of text. Some plugins translate the displayed page string by string, from the front end. That is handy for a small site, but check that plugin text and emails are covered too.

Common tools include TranslatePress , Polylang and WPML. The choice matters less than the discipline: no new English page goes live without its French version.

Disclosure: the TranslatePress link may be a referral link. If you buy through it, we may earn a commission at no extra cost to you.

Avoid a partial French version on a forgotten subdomain, or an English site with a “Translate” button that relies on browser translation.

The language switcher

  • Put it somewhere visible, in the header, on every page.
  • Make it go to the equivalent page, not to the other language’s home page.
  • Use the language name (“Français”, “FR”) rather than a flag: a flag stands for a country, not a language.
  • If you detect the browser language, always let people switch with one click, and remember their choice.

The most common gaps

Main pages are usually well translated. The gaps are elsewhere:

  • theme and plugin strings: “Add to cart” and “Read more” buttons, form messages, the 404 page, search results;
  • menus and the footer, which are often separate menus per language;
  • third-party widgets: booking, chat, Google reviews, maps;
  • PDFs and downloadable documents;
  • image alt text and text inside images;
  • emails sent by the site: form, order and account confirmations;
  • the cookie banner and its preferences panel, which should follow the page language (see our cookie banner guide);
  • SEO titles and descriptions, which appear in Google and should be written for each language.

Machine translation: yes, but reviewed

A machine translation tool can produce a first draft. The equivalent-quality expectation the OQLF describes, though, calls for someone fluent in Quebec French to review the text, especially anything binding: terms, consent notices, the privacy policy. One poorly chosen word in a collection notice can change its meaning.

And if your site is written in English first, the French version should not lag behind: it must be as complete and as current as the English.

SEO: hreflang and URLs

For Google, two equivalent pages in two languages are declared with hreflang tags (for example fr-CA and en-CA) and an x-default value. Serious multilingual plugins add them for you; check them in the page source. Give each version a readable URL in its own language, for example /conditions-de-vente/ and /en/terms-of-sale/.

Checklist

  1. Every English page has a French page that is just as complete and current.
  2. The language switcher is visible and goes to the equivalent page.
  3. No content requires changing browser settings to be read in French.
  4. Theme, plugin and widget strings are translated.
  5. Automated emails go out in French.
  6. The cookie banner, privacy policy and form notices follow the page language.
  7. PDFs exist in French.
  8. hreflang tags are present and reciprocal.