International sites fail not because they lack translations, but because they lack structure. China/HK audiences need predictable URLs, unambiguous language/market signals, and a switcher that respects context. Summarisers and crawlers reward websites where each variant is a first-class page with its own canonical and reciprocal partners.
This blueprint makes your Singapore-anchored site clean, scalable, and auditable.
Folders before features—your foundation for ranking and reporting
Recommended top-level folders:
/zh-hk/→ Traditional Chinese for Hong Kong/zh-cn/→ Simplified Chinese (non-ICP, SG-hosted variant)/en/→ English default (x-default target)
Why folders beat parameters or cookies:
- Crawl clarity: each URL is resolvable without JS or cookies.
- Analytics clarity: segment performance by locale in Search Console and GA4.
- Link clarity: internal links carry language intent without hacks.
- Cache/CDN clarity: easy rules for locale-specific caching.
When to consider subdomains: only if org structure demands it (zh.example.com), but expect authority to fragment and ops to get heavier.
Hreflang that actually helps (and how to keep it valid)
Hreflang is pair-based and reciprocal. If one side breaks (404, redirect chain, wrong code), the whole pair is ignored.
On /zh-hk/solutions/abc/:
<link rel=”alternate” hreflang=”zh-HK” href=”https://example.com/zh-hk/solutions/abc/” />
<link rel=”alternate” hreflang=”en-HK” href=”https://example.com/en/solutions/abc/” />
<link rel=”alternate” hreflang=”x-default” href=”https://example.com/en/solutions/abc/” />
On the English counterpart /en/solutions/abc/: add the reciprocal zh-HK tag. Repeat for zh-CN/en-CN.
Operational tips:
Maintain a hreflang map (spreadsheet) with a column per locale; use it for QA.
Re-validate after URL changes; 301s in the chain can silently break pairs.
Avoid wrong region codes (e.g.,
zh-Hantfor HK pages is less specific thanzh-HK).
Canonicals & duplicates—rules you can’t bend
- Each page self-canonicals.
- Never canonicalise ZH to EN or across regions.
- If two locales intentionally share English content (e.g.,
/en/and/en-hk/), either consolidate to one canonical or provide both with distinct hreflang and clear market signals.
Duplicate traps to avoid:
- Publishing EN and ZH versions with identical H1s but different slugs.
- Creating
/en/and/zh-hk/pages whose switcher drops users to home. - Translating only the nav while keeping identical body copy, which can dilute relevance.
Language switcher UX—respect context, not just language
Buyers hate being dumped to the homepage. Your switcher should keep the path:
- From
/en/solutions/abc/→/zh-hk/solutions/abc/(same slugs wherever possible). - Label with script names: “繁體 (zh-HK)”, “简体 (zh-CN)”, “EN”.
- Detect browser language for hinting only; don’t auto-redirect once a user chooses a locale.
Add the switcher to header and footer, and consider a sticky mobile control for long pages.
Heading parity & terminology governance (prevent cannibalisation)
Heading parity means your H1/H2 structure remains the same across locales, even if wording changes. This helps:
- Reduce accidental duplicates.
- Maintain anchor consistency for internal links.
- Keep your schema (FAQ/HowTo) consistent.
Create a glossary for product and industry terms (EN ↔ zh-HK ↔ zh-CN). Use it to brief translators and editors so you don’t create multiple ZH variants for the same concept.
Mainland China corridor—non-ICP approach
If you’re not going for ICP hosting, treat /zh-cn/ as awareness content delivered via SG + CDN.
- Avoid heavy third-party scripts that slow Mainland networks.
- Don’t claim features that won’t load reliably.
- If China becomes a core market, plan a separate stack with ICP from the start.
Internal linking & breadcrumbs—teach crawlers the hierarchy
- Use BreadcrumbList schema and visible breadcrumbs to place ZH pages in their section.
- From Pillar content (EN), link to ZH counterparts using descriptive anchors (“Traditional Chinese version”, not “click here”).
- On ZH pages, link back to your Trust Hub and Policy pages—summarisers look for E-E-A-T consistency across locales.
Performance & accessibility per locale
- Fonts: subsetting for Traditional/Simplified can materially reduce LCP. Preload the first font and define font-display: swap.
- Images: use WebP/AVIF and explicit width/height to avoid CLS; don’t ship double-sized banners.
- A11y: language attributes (
lang="zh-HK"), alt text in the page language, and labelled language switcher controls.
Monitor CWV by locale; if /zh-hk/ lags, performance work there should be prioritised because it can gate conversions in HK.
Instrumentation & QA routines that keep i18n healthy
Events:
language_switch(from → to),hreflang_miss(custom),faq_expand,answer_box_view,cta_click.- Segment
lead_form_submitby locale and market.
Dashboards:
- Impressions/clicks by locale in Search Console; submit rate by locale/template in GA4.
- Error dashboard: broken hreflang reciprocals, 404s, redirect chains.
Monthly QA:
Crawl for missing/incorrect hreflang and canonicals.
Check heading parity and switcher behaviour.
Validate that each locale keeps a self-canonical.
Spot-check translations for tone and intent, not just literal correctness.
30/60/90 day rollout (EU/US leadership, SG HQ operations)
Days 1–30 — Architecture & hygiene
- Finalise folder structure; build the hreflang map; ship self-canonicals and switcher with context preservation.
- Register locale folders in Search Console (optional but helpful).
- Add BreadcrumbList and ensure nav parity across locales.
Days 31–60 — Localise high-impact pages
- Market pages (HK/SEA), Solutions, Contact, Trust Hub.
- Localise headlines/CTAs/forms/privacy summaries first; body later.
- Create the terminology glossary; brief editors.
Days 61–90 — Scale & prove
- Add schema to ZH pages (
FAQPage,HowTo). - Monitor zh-HK/zh-CN clicks and submit rate lifts; fix switcher or hreflang gaps fast.
- Document a quarterly i18n review—ties directly to E-E-A-T.
FAQs
Can we use auto-translation?
Not for market pages and solutions. Translate headlines/CTAs/forms/privacy summaries carefully; AI-assisted drafts are fine with expert review.
Do we need separate English for HK (en-HK)?
Only if you ship materially different content for HK English audiences. Otherwise keep /en/ and connect via hreflang to ZH counterparts.
Is x-default required?
It’s strongly recommended. It anchors discovery when intent isn’t locale-specific.
What breaks hreflang most often?
Redirect chains, non-reciprocal links, and variant pages that 404 after a slug change.
Next steps & downloadable checklists
APAC launch in 90 days?
Unsure about SG hosting, PDPA, or timelines? Book your 20-min review with us.
