Bilingual Web Design: Reaching Sydney’s Chinese and Local Customers
A bilingual website for a Sydney business means two complete sets of pages — one English, one Chinese — each at its own address, linked so Google knows they are the same page in two languages. What it does not mean is a translate button. The button is cheap and it does not rank; the second set of pages is the thing that brings in enquiries.
We have written before about why running one language costs a Sydney business half its market. This is the practical follow-up: how the thing is actually built, what it costs to keep running, and where people get it wrong.
Auto-translate widgets versus real pages
The plugin that adds a flag icon to the corner of your site translates on the fly in the visitor’s browser. Nothing new gets saved, so there is no Chinese page for Google to index and nothing for an AI assistant to quote. Search for your service in Chinese and your site does not exist.
Real bilingual means each page exists twice, with its own URL, its own title and description, and its own text saved on your server. That is what gets indexed, and that is what someone searching in Chinese can actually land on.
There is a second reason to avoid the widget. Machine translation of a service page is usually recognisable as machine translation, and for a Chinese-speaking customer choosing between two businesses, that reads as carelessness.
How to structure the two languages
Three structures work. Pick one and keep it.
| Structure | Looks like | Best for |
|---|---|---|
| Subfolder | yoursite.com.au/zh/ | Almost every small business — simplest to run, keeps all the SEO value on one domain |
| Subdomain | zh.yoursite.com.au | When the Chinese site is run by a separate team with different content |
| Separate domain | a .cn or second .com.au | Only when you are genuinely targeting mainland China, with the hosting and filing that implies |
For a Sydney business selling to Sydney, the subfolder is almost always right. Then three technical things have to be in place: hreflang tags so Google knows the two pages are a pair rather than duplicates; a language switch on every page that lands you on the matching page rather than dumping everyone on the home page; and each page declaring its own language in the code, so browsers and screen readers handle it correctly.
Who writes the Chinese, and what goes in it
This is where budgets get decided. Three options, in order of cost:
- Straight translation. Cheapest. Fine for pages where the facts are the point — hours, address, what a service includes.
- Adapted writing. Same information, rewritten for how Chinese-speaking customers actually search and what they ask first. This is what we recommend for your main service pages.
- Separate content. Articles and pages that only exist in Chinese, because the question only comes up in that community. Worth it once the first two are working.
The adaptation matters more than people expect. A Chinese-speaking customer searching for a trades service often wants to know whether someone on site speaks Chinese, whether payment can go through WeChat Pay or Alipay, and what the process looks like start to finish — questions your English page may never have needed to answer. Translating an English page word for word leaves all of that out.
One practical note on search behaviour: plenty of Chinese-speaking customers in Sydney use Google, but many also start on WeChat or RED and only visit your site after seeing it mentioned. So the Chinese pages need to make sense to someone arriving cold from a shared link, not just to someone who worked through your navigation.
What it costs to run, and where it goes wrong
The build is the smaller half. The ongoing cost is that every change now happens twice: new price, new service, changed hours, new article. A bilingual site that is only updated in English slowly turns into two sites of different ages, and the Chinese one starts telling customers things that are no longer true.
The failures we see most often are the same few:
- Only the home page is translated; every service page is English-only.
- The language switch always returns to the home page, so visitors give up.
- Chinese pages carry no hreflang, so Google treats them as thin duplicates.
- The enquiry form is in Chinese but the auto-reply is in English.
- Nobody in the business can read the Chinese enquiries that come in.
That last one is not a website problem, but it sinks more bilingual sites than any technical fault. Decide who answers before you launch.
What we do
Melmel builds bilingual sites for Sydney businesses as a single project: both language sets, hreflang and switching handled, Chinese written rather than machine-translated. Pricing sits in the same $1,588–$3,588 range as our single-language builds, depending on page count — the breakdown is in our 2026 cost guide, and the usual timeline applies. Our website design Sydney page explains how we work.
Frequently asked questions
Is a bilingual website better than using Google Translate on my site?
Yes, for anything you want found in search. A translate widget changes the text in the visitor’s browser but creates no Chinese page for Google to index, so you do not appear in Chinese search results at all. A bilingual site stores each page in both languages at separate addresses, which is what gets indexed and what customers can land on.
Should the Chinese pages use Simplified or Traditional characters?
For most Sydney businesses, Simplified, because it matches the largest group of Chinese-speaking residents. If your customers are mainly from Hong Kong or Taiwan, Traditional is the better fit. Running both is possible but doubles the upkeep, so pick one unless you have a clear reason not to.
How much extra work is a bilingual site to maintain?
Roughly double for anything customer-facing: price changes, new services, hours, articles. The practical approach is to decide which pages must always match — services, contact details, pricing — and keep those in sync strictly, while allowing blog content to differ between the two languages.
