Chat on WhatsApp
Trilingual Websites for Singapore: English, Chinese and Bahasa with hreflang

Trilingual Websites for Singapore: English, Chinese and Bahasa with hreflang

One page per language or a switcher, how hreflang tells Google which version to show, what translation costs and who checks it, keeping three versions in sync, and which markets justify a third language. Checked October 2026.

By KYN AI Advisory Team — AI implementation specialists, Singapore

A Singapore business that sells to Chinese-speaking owners, to Indonesian partners, or to both, reaches them with pages in their language. Done well, each language version ranks on its own in its own market. Done badly, Google sees duplicate pages and ranks none of them. This is how we build trilingual sites on our own work and what the choices cost.

One page per language or one page with a switcher?

There are two ways to show a page in three languages, and only one of them ranks.

  • A switcher that swaps the text on the same URL. The visitor sees their language; Google sees one URL with one language, usually English. The Chinese and Bahasa text does not exist as far as search is concerned.
  • One URL per language: the English page at its path, the Chinese version under a language prefix, the Bahasa version under another. Each is a real page with its own title, content, schema and ranking.

From our own builds: a trilingual site carries every page at three URLs, English at the root and the other two under a two-letter prefix. Each version is indexed and each ranks for queries in its language. The language switcher links the visitor to the matching page, not to the home page of the other language.

How does hreflang tell Google which version to show?

hreflang is a tag on each page listing every language version of that page, including itself, and a default. It tells Google that these three URLs are the same content in different languages, so it shows the right one to each searcher and does not treat them as duplicates.

  • Every page lists all its versions, reciprocally. If the English page points to the Chinese one, the Chinese page must point back.
  • Use the correct codes: a language code, optionally with a region, for example en-SG, zh-Hans-SG, id-ID.
  • Include an x-default pointing to the version for everyone else, usually English.
  • Keep the canonical tag self-referencing on each version. A Chinese page whose canonical points to the English page tells Google to ignore it.

Build this into the page template so it cannot be forgotten on a new page. A guard in the deploy can check that every page's hreflang set is complete and reciprocal.

What does translation cost and who checks it?

Translation is where trilingual projects stall, because it is budgeted as an afterthought.

  • Machine translation produces a usable first draft of every page in minutes at almost no cost. It also produces tone and terminology errors a native reader notices immediately.
  • A native review of the machine draft is the practical middle path: a reader fluent in the language and familiar with the business corrects terms, names and tone. Budget this per page and schedule it before launch.
  • Professional translation from scratch costs the most and is justified for legal pages, pricing and anything that creates a contract.

From our own builds: the Chinese and Bahasa versions of a site were machine-translated from the English, then held for a native read before either language was promoted in navigation. The site shipped with all three live and the review marked as pending in the content files, so nobody mistook a draft for final copy.

How do you keep three versions in sync?

The failure mode is drift: English is updated, the other two are not, and a year later the Chinese page describes a service that no longer exists.

  • Keep the copy for each page in one file with three language blocks, so an edit to one is visible next to the other two.
  • Treat a change to the English copy as a task that is not done until the other two are updated or marked as needing review.
  • Generate shared elements, navigation, footer, forms and schema, from one source with a translation table, so they never drift.
  • Publish articles in English first and translate the ones that earn traffic, rather than translating everything on day one.

Which markets justify a third language?

Add a language when there is a reader for it, not because the site can.

  • Chinese for a Singapore business is often justified by its own local customers before any overseas market.
  • Bahasa Indonesia is justified when the business sells to Indonesian companies or operates there, and it opens a search market with far less competition than English.
  • Each language carries a cost per page for review and for keeping it current. Three languages means every page is maintained three times.

A trilingual site is a build decision: URL structure, hreflang, schema and the content files have to be designed for it. Adding a language to a site that was not built for it is a rebuild. For a site designed for three languages from the first page, see a website built in three languages.

Frequently asked questions

Will three language versions be seen as duplicate content?

Not when hreflang is complete and reciprocal and each version has its own self-referencing canonical. Without hreflang, yes.

Should the Chinese version use Simplified or Traditional characters?

For Singapore and mainland China readers, Simplified. Use the zh-Hans code. Traditional is for Taiwan and Hong Kong and would be a separate version.

Can I launch with English and add languages later?

Yes, if the site is built with the language structure from the start, even with only English live. Adding the structure later is the expensive part.

Checked October 2026.

Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.

Start Building →

Every workflow is custom built for you

Want this running in your business?