Start your language decision with how customers communicate with you. Chinese, English or a bilingual website can each be appropriate. What matters is whether readers understand the service and whether your team can keep the information accurate.
Look at real enquiries before choosing a main language
Review recent enquiries, the channels you use to reach people and your existing service information. Note the languages customers use for reading and asking questions, and consider new audiences you intend to serve. A visitor’s location in Hong Kong or their name does not tell you which language they prefer.
- If your main customers use Traditional Chinese and you can handle enquiries clearly in Chinese, a complete Traditional Chinese version can be a sensible start.
- If customers mainly compare services in English, or your core material and support are in English, you can begin with English.
- If both audiences have a real need and someone owns updates in each language, plan bilingual content, starting with the most-used pages.
Test the decision with a hypothetical situation
Imagine a small consultancy receiving mainly English-language business enquiries, while partners share a Chinese introduction. It could finish its English service, team and enquiry pages first, then plan translations around Chinese readers’ actual questions. This is a planning example, not a customer case study or a rule that consultancies should always start in English.
A bilingual site needs an update process
When a service scope, price, event time or contact detail changes, know which language pages need attention. A short checklist can record the source-content owner, translation reviewer and last confirmation date. Keep important pages accurate before expanding into more material that nobody has time to maintain.
If you support enquiries in only one language, explain that near the contact route. The existence of an English introduction should not imply that you offer English customer support when you do not.
Help readers reach the corresponding version
Google’s multilingual-site guidance recommends separate URLs and links between language versions, with language annotations helping search systems understand their relationship. Ask your website maintainer to handle the setup. A language link should ideally take readers to the translation of the current content, such as the matching service page, rather than return them to the homepage every time.
Webetter sample language and your finished website
Webetter groups Chinese and English samples of the same design on one card. You can switch the sample language, preview it and choose that version. This is a content starting point; selecting one sample does not mean that a complete bilingual website or translations of all its pages have been created.
For a bilingual site, list the pages that need both versions, then confirm the translation, URLs, switching links and update process. Bring that list to iGears if you want help defining the work. A designer can also review wording against the audience you actually serve.
Answer these five questions before starting
- Which language do our main customers use to understand our services?
- How many versions do the important service, contact and enquiry pages need?
- Who checks the accuracy of each version?
- Which languages can we support after an enquiry arrives?
- Who updates every affected version when information changes?
The number of language versions is not a measure of success. First help a real reader understand the service and complete an enquiry, then expand according to actual need.