Do Ottawa businesses need a bilingual website?

Ottawa owners ask this more than owners anywhere else in the country, and they usually ask it as a compliance question. It is not one. A private business in Ontario is under no general obligation to publish a French website, and anyone telling you otherwise is confusing Ontario with Québec, where the situation is genuinely different and we covered it in do you need a bilingual website in Québec.

So the real question is commercial. Does French earn its cost for your specific business? For some Ottawa businesses it is the highest-return work available. For others it is a project that produces nothing. The useful part is that you can tell which one you are without guessing.

Work it out from your own data

Four checks, none of which take long.

Your Search Console. Look at the queries bringing people to your site and check whether any of them are French. If French queries are already reaching an English-only site, there is demand you are capturing badly. That is the strongest signal on this list.

Your call log. Ask whoever answers the phone how often somebody opens in French, and how often that call goes well. If it happens weekly and the caller ends up switching to English out of politeness, you have French customers who are working around you.

Your catchment. Gatineau is a short drive and a large market, and a Gatineau resident searching for a service in the region is searching in French. If your service area crosses the river in practice, French is not optional in the commercial sense. Within Ottawa itself, the francophone population is concentrated enough in certain communities that a business in Orleans or Vanier has a different answer from one in Kanata.

Your customer type. Federal contracting, healthcare, legal services, and anything involving families and schools skew toward this mattering more. A B2B software company selling nationally usually finds it matters less.

If three of those four point the same way, you have your answer.

What "properly" means, and why the widget fails

The most common version of a bilingual Ottawa website is a translate button in the corner. It does essentially nothing for search.

A translation widget renders in the visitor's browser after the page loads. Search engines index the page they were served, which is the English one. So you get a translated experience for a visitor who already found you, and zero additional visibility for the French searches you were trying to reach. If the goal was to be found, the widget is the wrong tool.

Real French pages means each page exists at its own address, written in French, with hreflang tags telling search engines which version to serve to whom. That is the version that ranks.

It also has to be written rather than translated. French translated word for word from English marketing copy reads as translated, and francophone readers notice immediately. It also frequently misses the actual search terms, because the French phrase people type is not always the direct translation of the English one. Keyword research done in French turns up a different list.

Half a site is usually worse than none

The failure mode we see most often is a site with a French homepage and English everything else.

That is worse than staying English, because it makes a promise the rest of the site breaks. A visitor who arrives in French, gets a French homepage, clicks through to services and lands in English has learned something about how seriously the business takes them.

If you are going to do it, do the pages that matter: the homepage, the services people actually search for, the contact page, and anything involving a form. A form that only accepts English answers undercuts everything upstream of it.

The part people forget

If the site is in French, someone has to answer in French.

This sounds obvious and it is the most common reason a bilingual site disappoints. The page produces a call, the caller opens in French, and nobody available can continue. The customer is now more annoyed than if they had never found you, because the site implied a capability that does not exist.

So the honest sequence is: capability first, website second. If you have French-speaking staff, build the pages. If you do not, and hiring for it is not on the table, put the money into something else. We will tell you this at the audit rather than sell you a translation project.

What it is worth when it works

The reason this comes up so often in Ottawa is that the upside is real and the competition is thin.

Most local businesses publish in English only. French search in this region therefore has a fraction of the competition of the English equivalent, and the person searching is frequently choosing between very few options. Ranking for a French service query in Ottawa is often meaningfully easier than ranking for the same query in English, and the customer arrives already reassured.

That combination, low competition and high intent, is rare. It is why we list it near the top for Ottawa businesses that genuinely have the capability.

Where to look next

The Ottawa city page covers how the rest of the local market behaves, including the suburb-level search habit that costs businesses here more traffic than the language question does. SEO services in Ottawa sets out how the bilingual structure fits into the wider on-page work, and for firms in particular, law firm websites in Ottawa covers what changes when the client is choosing a professional service in either language.

If you want the answer for your business specifically, the free audit looks at your existing French queries, your service area, and your site structure, and tells you plainly whether it is worth building.