Bilingual Website SEO: Separate URLs, Subdomains or hreflang for English + Chinese Content?

In Metro Vancouver, running your website in both English and Chinese isn’t a nice-to-have — for businesses in Richmond, Burnaby or along Cambie, it can be the difference between reaching half your market or all of it. But most bilingual sites we audit are built in one of two broken ways: a JavaScript toggle that swaps text on a single URL (Google only ever sees one language), or a machine-translated mirror bolted on and forgotten (thin content in two languages instead of one). Both waste the advantage.

Here’s how to structure a bilingual site so each language can actually rank — and what hreflang does and doesn’t do.

Why does each language need its own URL?

Google indexes URLs, not toggles. If /services shows English by default and Chinese after a click, the Chinese version effectively doesn’t exist to search engines — there’s no address to index, rank or link to. The non-negotiable rule of multilingual SEO: one language per URL. Every page you want found in Chinese needs its own crawlable URL with the Chinese content in the HTML, not injected client-side after a button press. Cookie- or IP-based language switching on a single URL fails the same way, with a bonus problem: Googlebot mostly crawls from US IPs and will only ever see one version.

Subdirectory, subdomain or separate domain — which structure wins?

Three viable patterns, one usual winner:

• Subdirectories — moncepts.com/en/ and moncepts.com/zh/. Both languages accumulate authority on one domain: every backlink helps both. One site to host, secure and maintain. For a local business serving one region in two languages, this is the right answer almost every time.
• Subdomains — zh.moncepts.com. Works, but search engines treat subdomains as semi-separate sites, so your Chinese section starts closer to zero and builds authority alone. Choose it only when a technical constraint forces separation.
• Separate ccTLDs — a distinct domain per country. The heavyweight option for companies targeting different countries with different offerings. For “one business, one city, two languages,” it doubles your cost and splits your authority for no gain.

What does hreflang actually do?

hreflang is an annotation, not a ranking boost. It tells Google which pages are language versions of each other, so the right one appears for the right searcher — and so your two versions aren’t mistaken for competing or duplicate pages. The parts people get wrong:

• Use correct codes. For Chinese, script matters: zh-Hant for Traditional, zh-Hans for Simplified — not a bare “zh” and definitely not “cn” (a country, not a language). A Vancouver audience spans both scripts; pick based on who you serve, or provide both.
• Tags must be reciprocal. The English page points to the Chinese page and the Chinese page points back. One-way tags are ignored.
• Every page includes itself in its own hreflang set, plus an x-default pointing to the version (or language chooser) for everyone else.
• Pair it with self-referencing canonicals. Each language version canonicals to itself. Canonicalizing Chinese pages to English ones — a common CMS default — tells Google to ignore your Chinese content entirely.

Should you translate content or write it natively?

Structure gets you indexed; content gets you chosen. Two things matter more than perfect translation:

• Keyword behaviour differs by language. Chinese-speaking searchers don’t just translate English queries — they phrase things differently, use bilingual Richmond moving-company queries, and search different platforms along the way. Translating your English meta titles word-for-word usually means targeting phrases nobody types. Do a small keyword check in each language before writing.
• Parity beats symmetry. Your core pages — services, pricing, contact — deserve full native-quality versions in both languages. But it’s fine for the blog to differ: write for what each audience actually asks. A machine-translated blog nobody edits helps neither language; label the site honestly around what you maintain well.

And keep navigation, contact forms and confirmation emails in the visitor’s language end to end. A Chinese-language page that dumps users into an English-only enquiry form leaks exactly the customers the page was built to win.

FAQ

Can I just use a translation plugin like WPML or Weglot?

As infrastructure, yes — the good ones generate separate URLs, hreflang and translatable metadata, which solves the structural half of the problem. What no plugin solves is the content half: machine output still needs a native-speaking editor, and your key pages still need language-specific keyword thinking. Plugin for plumbing, humans for words.

Will duplicate content between my English and Chinese pages hurt my rankings?

No — content in different languages is not duplicate content, even as a direct translation. Google evaluates each language version on its own merits, and correct hreflang plus self-referencing canonicals removes any ambiguity about which version serves whom. The real duplicate-content risk is two URLs in the same language (e.g., with and without trailing slash) — that’s a canonical problem, not a bilingual one.

We have an English site and want to add Chinese. Where do we start?

In this order: choose the subdirectory structure, set up hreflang and canonicals correctly, then launch native-quality Chinese versions of your five to ten highest-value pages — services, pricing, about, contact, your best-converting articles — rather than machine-translating everything at once. Expand based on what earns Chinese-language impressions in Search Console. This is a project Moncepts handles end to end for Metro Vancouver businesses: architecture, hreflang implementation, and natively written Chinese and English content from a team that works in both. Email team@moncepts.com and we’ll map out what your bilingual build should look like.