Why HandNorth · 06
French and English are one product, not a translate widget
Public pages, legal, Help and the cabinet switch with one language control. Write hello@handnorth.com if you need a person in either language.
Reviewed 13 September 2026
Clear price.
Is HandNorth actually French, or a translate widget?
HandNorth is built as one product in French and English. The EN / FR control in the header is not a third-party translate widget laid over English. Public pages, Help, legal, How it works, Why HandNorth, Pricing, service spokes, city landings and the Work cabinet switch together. hreflang marks en-CA and fr-CA on those URLs. We opened visit booking in Greater Montreal because both languages are the market: Montreal, Laval, Longueuil, Brossard and Terrebonne. A person at hello@handnorth.com answers in either language. We will not claim a 70-city bilingual visit map. Other listed Canadian and U.S. cities can search Find a pro in both languages; a booked visit is not live there yet. City pages keep their own copy. We will not paste a Montreal walk-up story onto Toronto or Miami.
Jobs this rule applies to
These six Greater Montreal job pages use the same all-in quote, catalog label, and visit cities. Each spoke has its own copy.
What switches with EN / FR
- Public marketing pages and this Why cluster
- Help, Terms, Privacy, Cancellation, Disputes
- Find, Post a job, Become a pro, Pricing
- The Work cabinet, including Plan & add-ons
Why Greater Montreal first
A bilingual product has to work in the cities where people actually book. Laval, Longueuil and Brossard are not a translate afterthought. They are live cities on the same five-city map as Montreal and Terrebonne.
A person, not a bot
If a page is unclear in either language, write hello@handnorth.com. Disputes and reports go to a person: one business day to acknowledge, seven days to write a decision. There is no chatbot queue.
Same URL, a language control, not a second site
EN / FR in the header switches the page you are on. The path stays the same. French uses ?lang=fr. hreflang marks en-CA and fr-CA so search engines see both. This Why cluster, Help, legal, Pricing, Find, Post a job and the Work cabinet — including Plan & add-ons — follow that control. It is not a widget laid over English-only HTML.
Laval, Longueuil and Brossard are live cities, not a translation afterthought. Montreal and Terrebonne sit on the same five-city map. Quotes and messages stay with the pro who received them — you can write in the language you share. A person at hello@handnorth.com answers in either language. See service areas and how it works.
What we will not claim about language
All-in quotes, 0% on the job, and the Quebec file are the same product in both languages. About HandNorth is the company page.
- A 70-city bilingual map
- A chatbot that “speaks French”
- Machine-only legal pages
- A separate .fr product with different prices
Questions on this rule
Is French a plugin?
No. It is the same product. EN / FR is a language control, not a widget over English-only pages.
Can I get support in French?
Yes. hello@handnorth.com. A person answers. No chatbot.
Does the cabinet switch too?
Yes. Plan & add-ons, jobs and messages follow the same control.
Can a thread mix French and English?
Yes, if you and the pro share both. The product does not auto-translate your messages.
Is there a separate French price list?
No. Public plans and all-in quotes are the same product. The language control does not change the number.