You've tried the translate widget. It turned your service names into something a customer politely mentioned on the phone, and you turned it off. Here's the thing worth knowing before you spend anything: a multilingual website isn't a translated website. It's a second version of your site, with its own URLs, its own upkeep and its own search presence. For most Metro Vancouver businesses that's worth building, but only for the pages that actually convert.
What is a multilingual website, and how is it different from a translated one?
A multilingual website serves separate, permanent versions of your content in each language, each with its own URL that Google can index and a person can bookmark. A translated website usually means a widget that rewrites the page in the browser after it loads. The first is content. The second is a convenience layer.
Two other terms are worth pinning down. A bilingual website is the two-language case, which is what most businesses here actually build. Localisation goes further than translation: it adapts dates, currency, phone formats, examples and tone so the second version reads as though it were written for that reader rather than converted for them.
Machine translation widgets sit outside all of this. Search engines generally have nothing to index because the translated text never exists at a stable URL, so the second-language version earns you no visibility at all. Almost every business that asks us about this has tried a widget first and found it embarrassing.
Does your Metro Vancouver business actually need a second language?
Sometimes the answer is no, and a studio that won't say so isn't being useful. Work through four questions honestly.
- Do enquiries already arrive in another language? If staff are already fielding calls or emails in Cantonese, Mandarin or Punjabi, the demand is proven. If they aren't, you're guessing.
- Is the purchase high-consideration? Comprehension matters far more for a legal service, an insurance product or a medical procedure than for a takeaway menu.
- Is there someone who can maintain it? A second language you can't update goes stale, and a stale page is worse than no page.
- Do your customers search in that language, or only speak it? These are different behaviours. Plenty of people converse in Punjabi and search in English. That distinction alone decides whether you're building for search visibility or for comprehension once someone arrives.
The regional context is real, not decorative. Statistics Canada's 2021 Census language release reported that in Toronto and Vancouver, more than one in four individuals speak predominantly a non-official language at home. Nationally, Mandarin (531,000 speakers) and Punjabi (520,000) were the two largest, and Punjabi grew 49 per cent between 2016 and 2021. Chinese and Punjabi are the two languages behind most of the requests that reach us.
There's a commercial argument too. CSA Research's 2020 "Can't Read, Won't Buy" study, run with Kantar across 8,709 consumers in 29 countries, found 76 per cent of online shoppers prefer to buy products with information in their native language, and 40 per cent will never buy from websites in other languages.
“most would rather think, act, and buy in their own language”
Dr. Donald A. DePalma, Chief Research Officer, CSA Research
Which pages to translate, and which to leave alone
This is where budgets are saved. Translate the pages that carry a decision, leave the rest.
- Home. The orientation page. If someone lands here in the wrong language, everything after it is harder.
- Your two or three main service pages. Not all twelve. The ones that generate revenue.
- Pricing, or whatever stands in for it. Money is the thing people most want to read in their own language.
- Contact, including the form itself. A translated page with an English-only form is a dead end.
- Anything legally significant. Consent forms, terms, safety information, intake paperwork. Get these professionally done.
What usually doesn't earn translation: blog archives, case studies, news posts and team bios. They're numerous, they age, and they rarely carry a decision. Across our bilingual builds the median comes out around nine translated pages.
The maintenance arithmetic is the part owners underestimate. Every translated page is a page that must be updated twice, forever. Change your pricing and you've got two edits. Add a service and you've got two pages. Ten translated pages is a manageable habit. Sixty is a job nobody has time for, and within a year half of them contradict the English.
Design decisions that change when your site is multilingual
Multilingual website design isn't the English site with the words swapped. Six things change.
- Text expands and contracts. Translated copy can run considerably longer or shorter than the English. Buttons, navigation labels and card headings are where this breaks first, so design them to flex rather than to fit one string exactly.
- Line length and leading differ by script. Chinese characters carry more meaning per character and need more vertical breathing room than a Latin font at the same size. Punjabi in Gurmukhi has ascenders and a headline stroke that a tight leading value will crowd. Set these per language, not globally.
- Check the typeface actually supports the script. This is the most common failure we see, and it's silent: the browser quietly falls back to a system font and the second-language pages stop looking like your brand. Test the real font with real text before you commit.
- The language switcher belongs in the header, in the language it switches to. Write it as the endonym, so the Chinese option reads in Chinese. Skip the flags. A flag is a country, not a language, and it excludes more people than it helps.
- Forms need attention. Name fields that assume a first and last name in Latin characters will reject perfectly ordinary names. Address fields that assume a Canadian format are fine here, but validation written for ASCII is not.
- Imagery should look like the audience. Obvious, and routinely ignored.
Layout flexing matters most on phones, where a longer string has nowhere to go, so the principles in mobile-first design apply doubly here. Language sits next to accessibility without being the same thing, and our piece on common website accessibility mistakes covers that ground properly.
The technical setup: URLs, hreflang and not splitting your own rankings
Three ways to structure a second language, and for a small business one of them is almost always right.
| Structure | Example | Verdict for a local business |
|---|---|---|
| Subdirectory | yoursite.ca/zh/ | Usually right. One domain, one pool of authority, cheapest to run |
| Subdomain | zh.yoursite.ca | Workable, but you're maintaining a second property for no local benefit |
| Separate domain | yoursite.cn | Almost never right here. You'd be building a second site's authority from zero |
Then the annotations. hreflang tells Google which version to show which reader, and the rule people miss is that it has to be reciprocal: if the English page points at the Chinese page, the Chinese page must point back. Google's own guidance on managing multi-regional and multilingual sites is the reference to work from, and it's worth reading rather than trusting a plugin's defaults. Roughly one in three bilingual sites we inherit have no hreflang at all.
On the duplicate content worry, which everybody asks about: genuinely translated pages aren't duplicates. Google treats them as alternates when the annotations are right. What does cause trouble is near-identical machine output across many URLs with nothing distinguishing them. Include both versions in your sitemap, keep canonicals pointing within each language rather than across them, and if adding the second language changes your existing URLs, follow our guide to migrating a website without losing rankings rather than improvising the redirects. The wider pre-launch checks sit in SEO basics before launch, and how a second language interacts with local visibility is worth reading alongside local SEO for Vancouver small businesses.
Getting the translation right, and who should do it
Three realistic routes, each with an honest cost.
- Machine translation with human review. Cheapest, and fine for straightforward informational copy. The reviewer has to actually be fluent and actually be given time, or you've paid for a rubber stamp.
- A professional translator. The right call for anything legal, medical or persuasive. Brief them on your business, not just your text, and give them your existing copy in both directions so terminology stays consistent.
- A bilingual staff member. Often the best voice, because they already speak to your customers. The risk is that it's unpaid extra work bolted onto a full job, and it stops the moment they get busy.
Brand voice is what suffers most under cheap translation. Machine output is grammatical and characterless, so a brand that sounds warm and specific in English arrives flat in the second language. Industry terminology is the other failure point, and it's the visible one: a mistranslated service name reads as carelessness to exactly the customer you were trying to reach. Translated pages still have to persuade, so the principles in writing website copy that ranks and converts apply to the second version too.
What a multilingual website costs to build and to keep running
As a rough shape, adding a second language to an existing site has run us between about 30 and 40 per cent of the original build cost, depending on page count. Upkeep is the line nobody budgets: expect around two extra hours of work per content update once the second version exists.
Four things drive the number: how many languages, how many pages, whether your CMS handles localisation natively or needs a plugin bolted on, and who's doing the translating. Native CMS support is worth paying for, because it's the difference between a maintainable habit and a manual chore. That's one reason we build most of these in Webflow, which we've written about on our Webflow agency page.
If you're weighing this against everything else on the list, affordable web design in Vancouver covers how we sequence work when the budget is finite. This comes up most often in Richmond and Surrey, and increasingly in Burnaby, which is where most of our second-language work has come from.
Frequently Asked Questions
What is a multilingual website?
A multilingual website serves permanent, separately indexed versions of your content in more than one language, each at its own URL. That's different from a browser widget that rewrites text after the page loads, which search engines cannot index and visitors cannot bookmark.
Does a multilingual website hurt SEO?
No, provided it's structured properly. Genuinely translated pages are treated as alternates rather than duplicates when hreflang annotations are reciprocal and canonicals stay within each language. Done badly, with machine output across dozens of thin URLs and no annotations, it can dilute your visibility.
Should I use a subdomain or a subfolder for a second language?
A subfolder, for almost every local business. It keeps everything on one domain and one pool of authority, and it's cheaper to maintain. Subdomains and separate country domains make sense for organisations running genuinely separate operations per market, which is rarely a Metro Vancouver small business.
Is Google Translate good enough for a business website?
As a courtesy layer, sometimes. As your second-language website, no. Widget output isn't indexed, so it earns no search visibility, and it reliably mangles service names and brand voice. Machine translation with a fluent human reviewer is the cheapest option we'd actually recommend.
Do I need to translate my whole website?
No, and you shouldn't. Translate home, your main service pages, pricing, contact and anything legally significant. Leave blog archives, case studies and news in English. Every translated page has to be maintained twice forever, so a smaller set you keep current beats a large set you don't.
Two things decide this. First, whether enquiries already arrive in another language, which tells you the demand is real rather than assumed. Second, which handful of pages carry the decision, because those are the only ones worth maintaining in two versions forever. Get the structure right at the start, subfolders and reciprocal hreflang, and a second language stays an asset instead of turning into a second website nobody updates.
We build websites for Metro Vancouver businesses whose customers don't all read English, with the URL structure, hreflang and upkeep plan that keeps a second language from becoming a second problem.
