French comes first, and that changes the Montreal SEO brief
Quebec regulates the language of commercial communication, and a commercial website aimed at consumers here is expected to exist in French, with any other language no more prominent than the French version. That is a legal obligation for many businesses rather than a marketing preference, and it lands squarely in the middle of an SEO programme.
Once you accept it, several decisions follow at once. Which language lives at the root of the site. How the two versions are linked so that search engines serve the right one. Whether the French pages are originals or translations. Who signs off on terminology. An agency that treats the French side as a bolt-on to an English site has misread both the law and the audience, and you will pay for the correction later.
Put the requirement in the brief on the first page. It changes cost, timeline and staffing more than any other variable in this market.
Local French is not the French in a translation tool
The vocabulary people type here diverges from the vocabulary used in other francophone markets, and SEO does not forgive the difference. Everyday commercial terms, job titles, product categories and even the verbs used for buying and booking have local forms that a generic translation will miss. Anglicisms that are normal in one francophone market are avoided here, and words that sound formal elsewhere are ordinary here.
This is the single most useful thing to test during selection. Ask each shortlisted SEO agency to produce a short keyword set for one of your services in French, and to justify three choices. A team that works in this market will explain why a particular form is used locally. A team that does not will hand you a translated English list, and the giveaway is usually a phrase that reads correctly and is never searched.
Ask who writes. Native francophone writers who live here are not interchangeable with francophone writers elsewhere, and the difference shows in conversion long before it shows in rankings.
Two language versions, one crawl budget
Bilingual sites fail technically in predictable ways, and each failure is an SEO failure before it is anything else. Language annotations that point at the wrong pages. A language switcher that sends every page to the home page of the other version. Duplicate content when both versions exist at nearly identical addresses. Pages that exist in one language and silently fall back to the other. Each of these can neutralise months of content work.
Ask for the architecture in writing before anyone starts producing pages: where each version lives, how the pair is declared, what happens when a page has no counterpart, and how the two versions stay in step when one is updated. Drift is the slow killer. An English page revised repeatedly across a year while its French counterpart sits untouched leaves you publicly out of date in the language your customers actually read.
Choosing between a bilingual agency and two specialists
There are two viable structures. A single bilingual agency gives you one accountable supplier and one strategy, with the risk that one language receives noticeably more care than the other. A specialist per language gives you depth on both sides, with the risk of two plans that quietly contradict each other and two invoices for the same technical fix.
If you go with one supplier, ask how many francophone specialists are on staff rather than on call, and ask to see published work in both languages produced by the people who would be assigned to you. If you go with two, name one of them as technical owner of the site so that structural decisions have a single home.
Measurement when half the demand is in another language
SEO reporting has to be segmented by language or it tells you nothing useful. A single organic traffic line hides the case you most need to see, which is whether one version is carrying the other. Ask for non-branded organic sessions, enquiries and revenue split by language version and by landing page, from the first month.
That segmentation also protects your budget. It is common for one language to be cheaper to win in and the other to convert better, and you cannot allocate sensibly between them until the report shows both separately.
Contracts, language obligations and asset ownership
Agree in the contract who is responsible if published content fails to meet language obligations, and build in a review step with someone qualified to make that call. Most agencies will happily accept the review requirement. Very few will volunteer it.
On ownership, the rule is the same as anywhere but the stakes are higher because you are paying for two versions of everything. Your company holds the domain and DNS, the content management system administration, the analytics property and the search console properties, with agency users invited rather than owning. Content in both languages is assigned to you on payment with source files. Ask specifically for the terminology glossary and any translation memory built during the engagement, because that accumulated vocabulary is the asset that saves you the most time when the supplier changes.
Briefing a Montreal shortlist so the replies compare
Write the brief once and send it unchanged. State your language obligations, your platform, whether your French content will be original or adapted, your catchment, what counts as a result, your budget band and your start date. Ask for answers in the same structure, including named bilingual staff, a first quarter plan, the reporting split, term and notice.
Decide as well whether search should be bought on its own. Teams in this city often pair it with web development, animation and video or mobile app work, which matters when the site structure and the content plan are being decided together. To check whether the quotes you receive are in a normal range, comparable proposals from SEO agencies in Toronto or Ottawa are a quick benchmark, and the broader SEO agency directory covers every other market we list.
With the brief ready, ask for offers in a single step and let the shortlisted teams reply in a format you can lay side by side.