Contents＋
Traditional Chinese promises one thing. English promises another. Three languages, no shared promise.
01 / Direct answer
Three languages are not one page translated three times
Multilingual failure is usually an operating-model failure. Translation is treated as one-off output without defining a source of truth, how changes trigger other languages, what may be localised, and which legal or product facts must remain identical. A plugin faithfully scales that ambiguity.
02 / Market difference
Changing language changes market, promise and evidence
Illustrative scenario, not a client case: A Hong Kong fintech updates fees and eligibility in English while Traditional Chinese retains old information and the Simplified form routes to general support. Search can land users on any version. When a buyer forwards the page to a Mainland colleague and the numbers disagree, the issue is no longer translation quality but which company version is trustworthy.
Three languages mean three complete enquiry journeys
One page promises a reply in two working days, another says 24 hours and the third shows an old price. Every translation can be grammatical while the company makes contradictory commitments. Treat scope, pricing rules, address, hours and response windows as shared facts, then adapt the expression for each language.
03 / Hong Kong reality
Small details make Hong Kong multilingual sites look untrustworthy
Google recommends separate URLs for each language and links them with hreflang; it mainly determines language from visible content and advises against mixing side-by-side translations.
WPML can generate hreflang and translate SEO fields, but the business still owns content and workflow correctness.
A three-language site needs three information classes: immutable facts such as legal name, licence and specification; localisable expression such as contact route, case order and terminology; and intentionally asynchronous material such as local events. Without classification, every update relies on memory and eventually drifts.
04 / Management error
Translation complete does not mean project complete
The common completion metric is page count: thirty pages times three means ninety, therefore 100% translated. Yet a Simplified page may only change characters, Cantonese phrasing may be mechanically converted, English form fields may differ, and language switching may return to the homepage. Existence is not service parity.
The words can be correct while the arrangement is wrong. That’s the awkward bit after ‘translation complete’.
05 / Six layers
Check consistency from content to categories
- Maintain a language matrix with the three URLs, status, owner and last verification date for every page.
- Label immutable facts, localisable content and region-specific material and apply different approval rules.
- Test that language switching reaches the equivalent content rather than a language homepage.
- Validate titles, descriptions, canonicals, hreflang, schema, forms and thank-you pages.
- Quarterly audit five high-risk pages for drift in pricing, terms, contact details and proof.
| Content class | Treatment | Examples |
|---|---|---|
| Immutable fact | Synchronise and double-check | Licences, prices, specifications |
| Localisable expression | Rewrite for the market | Tone, contact path, case order |
| Region-specific | State applicability | Events, regulation, support hours |
| Shared function | Test in every language | Forms, search, language switcher |
A WordPress category displaying “SEO” is not necessarily the same term across languages. Multilingual systems can create distinct terms linked as translations. After import, inspect post language, term language and translation relationships—not merely the category field in JSON. Open each language's archive and hub to verify that the intended posts appear.
06 / Release process
The right order from language architecture to release
Every language version needs its own audience, URL, page relationships, metadata, contact journey and maintenance owner. Translated copy is only one layer.
- Define the market, offer and conversion path for each language version.
- Create one-to-one URL mapping and missing-page rules before implementing hreflang.
- Translate from a controlled source, then localise cases, terminology, regulations and contact details page by page.
- Test navigation, search, forms, analytics and future updates separately in each language.
07 / Measurement
Measure the complete journey for each language market
| Layer | What to record | What it means for management |
|---|---|---|
| Completeness | Mapped pages, hreflang, canonical and index status | Confirms systems understand language relationships |
| Credibility | Errors in local cases, contact details and terminology | Finds details that make readers hesitate |
| Commercial | Qualified enquiries and sales paths by language | Stops sitewide averages hiding a failed version |
Language switching should preserve the current service rather than repeatedly return to the homepage. Disclose missing translations. Character conversion does not automatically localise terminology, pricing or service geography; English also needs a service-aware reviewer, not only spellcheck.
08 / FAQ
Three common multilingual questions
Is automatic Traditional–Simplified conversion enough?
It changes characters, not market tone, terminology, regulation, cases or search behaviour.
What if a corresponding page does not exist?
Do not force every missing page to the homepage. Keep the nearest useful language, explain the gap or omit a false language relationship.
Must English live at the root domain?
No. Directories, subdomains and separate domains have different operational costs; consistency and maintainability matter most.
09 / Limits and conclusion
Consistency means equally credible, not word-for-word identical
Not every page needs full parity. A Hong Kong-only event or jurisdiction-specific notice may remain local when clearly labelled. The difference is an intentional decision rather than an omission. A smaller complete set is often better than a large library of partial translations.
A professional multilingual site does not make every sentence identical. It gives every language the same facts, an appropriate expression and a service path that genuinely works.
I’d treat the language switch as walking a different route, not changing the font.
10 / Sources