Give each language its own URL, keep each page in one language, link the versions together with hreflang, and let visitors choose their language rather than redirecting them automatically. That's the core of what Google recommends. Google works out a page's language from the words people can see, not from code or the URL, so a properly translated, separate page is what makes the second language findable.

Get those basics right and a Chinese or Malay version can do real work for you. Get them wrong and the translation may sit there, quietly invisible.

Is a second language worth it for your business?

Singapore is multilingual, but not every business needs a multilingual website. Some context: in the 2020 Census, English was the language most frequently spoken at home for 48.3% of residents aged 5 and over, up from 32.3% in 2010. Mandarin was 29.9%, Malay 9.2%, Chinese dialects 8.7% and Tamil 2.5% (SingStat Census 2020 infographic; SingStat literacy and home-language overview).

Home language isn't the same as the language people search in, so use your own evidence too:

  • Your conversations. Do enquiries, WhatsApp messages or walk-ins often come in Chinese or Malay?
  • Your Search Console. Look at the Queries report for searches in Chinese characters or Malay words. If you haven't set it up, here's how to set up Google Search Console.
  • Your customers' decision-makers. For example, adult children may research in English on behalf of parents who are more comfortable in Mandarin. Then a translated page might help the conversation more than the search.

If the answer is "a few key pages would really help", start there. A good translated service page beats a half-translated whole site.

How Google decides what language a page is in

This surprises people: Google doesn't take your word for it.

So a page with a Chinese headline over English body text is, to Google, mostly English. Google specifically recommends "avoiding side-by-side translations": keep the content and the navigation in one language per page (Google: multilingual sites).

You should still set the lang attribute (for example <html lang="zh-Hans">). Google does not use it to detect the page's language, but screen readers use it to pick the right pronunciation rules (W3C: Understanding WCAG 3.1.1 Language of Page).

Give each language its own URL

Google "recommends using different URLs for each language version of a page" rather than swapping the language with cookies or browser settings on the same URL (Google: multilingual sites). If the language changes dynamically at the same address, Google may not discover and crawl every version.

Your options, from Google's own comparison:

StructureExampleNotes
Subdirectoryexample.com/zh/Simple to run on one site and one domain. Usually the easiest choice for a small business
Subdomainzh.example.com"Easy to set up", per Google, but it's more like a second site to manage
Country domainexample.cnBuilt for targeting a country, not a language. Rarely the right fit for a Singapore business adding Chinese
URL parameterexample.com?lang=zhGoogle marks this "Not recommended"

For most Singapore small businesses, a subdirectory like /zh/ or /ms/ is the practical choice. Many website platforms and multilingual plugins set this up for you, but check what yours actually produces.

Link the versions together with hreflang

Hreflang is a small annotation that says "this page also exists in these other languages, at these addresses". It helps Google show the right version to the right searcher. It doesn't make Google rank either version higher.

Google's rules, in plain terms (Google: localized versions):

  • Three equivalent methods: HTML <link> tags in the page head, HTTP headers, or your XML sitemap. Pick one; Google says "the three methods are equivalent".
  • Every version lists itself and all the others. The English page lists English and Chinese; the Chinese page lists Chinese and English. "If two pages don't both point to each other, the tags will be ignored."
  • Use valid codes. Language codes come from ISO 639-1 (en, zh, ms), optionally with a region (en-SG) or a script for Chinese (zh-Hans for Simplified, zh-Hant for Traditional).
  • Consider x-default for visitors whose language doesn't match any version, usually pointing to your English page or a language chooser.

A simple example for one page, in the head of both versions:

<link rel="alternate" hreflang="en" href="https://example.com/services/deep-cleaning/" />
<link rel="alternate" hreflang="zh-Hans" href="https://example.com/zh/services/deep-cleaning/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/services/deep-cleaning/" />

Google says the most common mistakes are missing return links, wrong language codes and wrong region codes. A classic is using a country code where a language code belongs: cn isn't a language code, zh is.

Canonical tags: each language version should normally point its canonical tag at itself, not at the English page. Google recommends a same-language canonical when you use hreflang, and a self-referencing tag on the intended canonical page (Google: canonical URL guidance). A canonical is a preference signal, not a guarantee of which page Google will select. Our guide to canonical tags explains how to check what Google chose.

Let visitors choose: language switchers and redirects

  • Don't redirect automatically by browser language or location. Google advises you to "avoid automatically redirecting" users between language versions, because it can stop people and search engines reaching every version, and says "don't use IP analysis to adapt your content" (Google: multilingual sites). A gentle banner ("This page is also available in 中文") is fine.
  • Link to the equivalent page, not the home page. Someone reading your English deep-cleaning page who taps "中文" should land on the Chinese deep-cleaning page.
  • Label languages in their own words. "English / 中文 / Bahasa Melayu" is clearer than flags, which stand for countries, not languages.

Translating well: what Google says about machine translation

You can use machine or AI translation as a starting point. Machine translation is not automatically spam: Google's scaled-content policy concerns many pages made primarily to manipulate rankings rather than help people. Its examples include scraping content and transforming it through translation without adding value (Google spam policies). Reviewing translations before publication is our practical recommendation for quality.

The test isn't how it was translated; it's whether the result is useful and reads naturally to a native reader. In practice:

  • Have a fluent speaker review every translated page before it goes live.
  • Translate for meaning, not word for word. Prices, service names and local terms may need adapting.
  • Don't forget the hidden parts: title tags, meta descriptions, image alt text, buttons, form labels and error messages, and your WhatsApp pre-filled message.

For more on how Google treats AI-assisted writing generally, see is AI-generated content bad for SEO?

Hypothetical example: [Business name], a tuition centre, adds a /zh/ section with three useful pages: programmes, a combined fees-and-timetable page, and trial lessons. Each page is translated, then reviewed by a Chinese-speaking teacher, linked to its English twin with hreflang, and reachable from a "中文" link in the header. Nothing else on the site changes. That's a sensible, contained first step.

After launch: how to check it's working

  1. Inspect a translated URL in Search Console. The indexed report shows the last indexed snapshot and Google's selected canonical. Use the live test to check current accessibility and possible indexability; it cannot guarantee indexing or predict the selected canonical (Google: URL Inspection).
  2. Search in the language. Try a Chinese search your customers would use and see whether your Chinese page appears over time (results vary by person and device).
  3. Check the switcher on every translated page, on a phone.
  4. Keep versions in step. When your English prices or hours change, update the other languages the same day. Out-of-date translations erode trust quickly.

If you're moving to a new platform to add languages, our website redesign SEO checklist covers the redirects and checks that help protect existing traffic.

What's in your control, and what isn't

In your control: which pages you translate, the quality of the translation, the URL structure, hreflang, canonicals, and how visitors switch language.

Not in your control: which version Google shows a particular searcher, how quickly new pages are indexed, how much demand there is for searches in each language, and whether AI tools draw on your translated pages. Clear, separate language pages give search engines and AI tools the best chance of understanding them; nobody can guarantee rankings or citations.