How to make a multilingual website for Malaysia's four main languages

How to make a multilingual website for Malaysia in Malay, English and Chinese: URLs, hreflang, fonts, CMS prices, PDPA notices and a checklist.

Summarize with
Three text cards with the same layout, the text longer in one and more compact in another

A multilingual website in Malaysia usually means English and Bahasa Melayu, plus Simplified Chinese if you sell to Chinese-speaking customers and Tamil if your audience calls for it. Here is how to make a multilingual website that works: build one site with a subfolder per language, link each page to its translations with hreflang, have a Malaysian native speaker review everything, and design for the longest language (in my test, Malay set about a quarter wider than English and Tamil nearly twice as wide).

Two rules are fixed. The Personal Data Protection Act requires your privacy notice in Malay and English whatever languages your site uses, and Google judges a page's language by its visible text, so half-translated pages hurt.

It is for founders and marketing leads, and covers the key decisions, from URLs and fonts to platform prices, cost and a launch checklist.

Which languages your Malaysian website needs

Malay is the national language under Article 152 of the Federal Constitution, English carries much of business, and Chinese and Tamil have their own schools and press. What matters is the language your buyers choose.

SignalWhat it shows
Citizens, 2026 (DOSM, preliminary)Bumiputera 70.7% (Malay 58.4%), Chinese 22.0%, Indian 6.5% of 31.0 million
Highest Chinese share (Census 2020)Pulau Pinang 44.9%, Kuala Lumpur 41.6%, Johor 32.8%
Highest Indian share (Census 2020)Negeri Sembilan 14.3%, Perak 11.5%, Selangor 11.3%
Vernacular schools, May 202641,133 Malay pupils were 9.01% of Chinese-school enrolment (about 456,000 pupils); 320 were 0.41% of Tamil-school enrolment (about 78,000)
EnglishEF's 2025 index scores Malaysia 581, 24th worldwide, in the "high" band

The census counts ethnicity, not reading preference, and EF's sample chose to take its online test, so treat both as signals:

Your situationStart withAdd with evidence
B2B or professional buyersEnglishMalay for SME buyers
Government, GLC or tendersMalay, EnglishChinese
Consumer brand in the Klang Valley, Penang or JohorEnglish, Malay, ChineseTamil for campaigns
Services for Indian Malaysian communitiesEnglish, Malay, TamilChinese

Then check what customers search in, what your team can answer in and what you can keep current. A Chinese page leading to an English-only call breaks its promise.

URL structure: subfolders, subdomains or a .my domain

Google recommends a separate URL for each language version, never cookies or browser settings.

StructureExampleVerdict
Subfoldersexample.com.my/ms/Best for almost everyone: one site, shared authority, supported everywhere
Subdomainsms.example.com.myOnly if separate teams or systems run each language
Separate domainsexample.my and example.com.myRarely worth it within one country
URL parametersexample.com.my/?lang=msGoogle advises against them

A .my or .com.my domain is a strong country signal. Search Console's country targeting is retired, so on a .com your signals come from hreflang region codes, local addresses, ringgit prices and local links. Localised slugs are fine in UTF-8: /ms/perkhidmatan/ beats /ms/services/.

Hreflang done right for Malay, English and Chinese

Google's rules, in practice:

  1. Each page lists itself and every translation. Links must be reciprocal, or Google ignores them.
  2. Valid codes only: an ISO 639-1 language, optionally a script and a region. Beware "my": as a language code it means Burmese, not Malaysia.
  3. Add x-default, usually the English page.
  4. Keep each canonical in its own language, never pointing Malay at English.
  5. Use one method: tags in the head, HTTP headers or the XML sitemap.
Versionhreflanglang on the html element
Englishen-MYen
Malayms-MYms
Simplified Chinesezh-Hans-MYzh-Hans
Tamilta-MYta
Fallbackx-defaultnone

The W3C advises short tags, hence no region in lang. Avoid zh-CN (Chinese as used in China), which Malaysian Chinese news sites I checked still declare. And because Google reads visible text, a /ms/ page whose body is still English counts as English and competes with your English page.

Translation, transcreation and who reviews it

ApproachUse it forRisk
Machine translation onlyInternal draftsWrong tone and terms; Google's spam policy covers scaled auto-translation
Machine draft, native editHelp pages, blog postsOnly as good as the editor's time
Translation, then review by a second linguistService pages, legal text, forms, emailsSlower; needs a glossary
Transcreation: rewritten for the readerHomepage, headlines, campaignsCosts more; needs a clear brief

Transcreate the pages that sell; translate and review the pages that inform. Give each language an internal owner who signs off, keep a glossary from day one (product names, terms left in English, anda or awak, 您 or 你), and review on staging, in context: a correct sentence can still break a button.

Simplified Chinese, Malaysian vocabulary

Sin Chew Daily and China Press, Malaysian Chinese news sites I checked on 2 October 2026, publish in Simplified characters. Use Simplified, and keep Traditional for Hong Kong or Taiwan.

Vocabulary matters more than script. Malaysian Mandarin borrows from Malay and the dialects: ringgit is 令吉, a market is 巴刹, the title Datuk is 拿督. A translator in Shanghai writes correct Chinese that reads foreign in Ipoh, so hire Malaysians, and for Malay, Malaysian rather than Indonesian.

Typography for Malay, Chinese and Tamil scripts

Malay uses Latin script (Unicode's default for Malay in Malaysia), so your brand typeface covers Malay and English; Chinese and Tamil need their own fonts. I set the Universal Declaration of Human Rights, from the UDHR in Unicode project, in Noto Sans, Noto Sans SC and Noto Sans Tamil at 16px in Chrome:

SampleEnglishMalaySimplified ChineseTamil
Article 1 on one line1,299px1,614px (24% wider)688px (47% narrower)2,320px (79% wider)
All 30 articles in a 680px column114 lines147 lines (29% more)77 lines (32% fewer)181 lines (59% more)
The same sentence in English, Malay, Simplified Chinese and Tamil, measured at 16px.
The same sentence in English, Malay, Simplified Chinese and Tamil, measured at 16px.

It is one formal text, and short strings expand more: IBM figures quoted by the W3C put growth at 200 to 300% for text of up to 10 characters, so buttons break first.

ScriptOn Google Fonts (1,950 families)One regular weightNotes
Simplified Chinese10 families, mostly display; Noto Sans SC for textNoto Sans SC: 101 files, about 2.4 MB in all, loaded in slicesNo italics; full-width punctuation
Tamil17 families, such as Noto Sans Tamil and Mukta MalarNoto Sans Tamil: 3 files, about 32 KBTall vowel signs need more line height
  • Declare lang on the page and on mixed passages: browsers use it to pick fonts and Chinese glyph shapes, screen readers to pick a voice.
  • Never ship the whole Chinese font: slice it, use a service that does, or use system fonts.
  • Space mixed text: the W3C's Chinese layout rules suggest at most a quarter of a Han character's width between Chinese and Latin.
  • No letter-spacing on Tamil. The W3C's Tamil gap analysis notes that browsers then split conjuncts, none hyphenate Tamil by default, and underlines can hit vowel signs.

My Bangla interface typography guide covers Indic detail that applies to Tamil too.

Language switcher UX and the redirect question

  • Name each language in itself: English, Bahasa Melayu, 中文, தமிழ், each with its own lang attribute (the WCAG 2.2 example for criterion 3.1.2).
  • No flags. A flag is a country, and all four languages are used beyond Malaysia. Singapore, for one, has all four as official languages; see my UI/UX design for Singapore startups for products launching across the region.
  • Plain links near the top right, which the W3C prefers to a drop-down for a handful of languages.
  • Open the same page in the other language, or say that no translation exists.
  • No automatic redirects, which Google advises against. Framer's Automatic Locale and Webflow's automatic routing do this when switched on; leave them off and offer a small banner instead.
  • Remember the choice, but let the URL decide.

Forms, names and PDPA notices

Translate every label, error, confirmation, auto-reply and WhatsApp template, and store each lead's language for follow-up.

Names. The W3C advises a single full-name field and warns against requiring a family name. Malay names use bin or binti before the father's name, many Indian Malaysian names use a/l or a/p, and Chinese names put the family name first. "First name" and "Last name" break all three.

MyKad numbers are 12 digits, with optional hyphens. Ask only if you need one: the Act requires data that is "adequate but not excessive" for its purpose. Keep FPX and DuitNow, PayNet's payment services, under their own names.

The notice. Section 7(1) lists what it must cover: what is processed and why, its source, rights of access and correction, who receives it, the choices offered and whether supplying it is obligatory. Section 7(3) says it "shall be in the national and English languages", as must the means to exercise those choices. A Chinese landing page with a form still needs both.

The 2024 amendment renamed data users "data controllers" and, from 1 April 2025, raised the maximum penalty for breaching the principles from RM300,000 and two years to RM1 million and three years. Data protection officers, breach notification and portability followed on 1 June 2025. Have a lawyer approve your wording.

Choosing a CMS for a multilingual website in Malaysia

Prices on 2 October 2026, at Bank Negara Malaysia's noon rates (RM4.09 to the US dollar, RM4.60 to the euro):

PlatformHow languages workPriceWatch for
WordPress with WPMLFolders, subdomains or domains; automatic hreflang€39 a year, one site (about RM179); €99 for three sites with WooCommerce support (about RM455)Plugin and theme updates
WordPress with PolylangAs WPMLFree core; Pro €99 a year (about RM455) adds translated slugs and DeepLDeepL needs your own key
Webflow LocalizeA subfolder per locale; CMS and static pagesUSD 9 a month per locale, up to three (Essential), or USD 29, up to ten (Advanced), on top of a site plan: Basic USD 15 a month without CMS, Premium USD 25, billed yearlyTranslated URLs and per-locale images need Advanced
FramerLocale paths, translated slugs, automatic hreflangUSD 20 a month per locale, up to 20, plus Basic (USD 10) or Pro (USD 30) billed yearlyhreflang cannot be edited
Shopify MarketsSubfolders or domains; automatic hreflangFrom USD 19 a month billed yearly; free Translate & Adapt app auto-translates two languages; up to 20 languages"products" in URLs stays English
Headless: Sanity or Strapi with Next.jsDevelopers build /[lang]/ routesSanity: unlimited locales on every plan; Strapi 5 localisation is freeYou own hreflang, sitemaps, switcher
  • Marketing site, small team: Webflow or Framer (my Framer, Webflow or Next.js comparison covers the trade-offs).
  • Content-heavy, or already on WordPress: WPML or Polylang, with maintenance.
  • Online shop: Shopify Markets.
  • Site tied to a product: headless with Next.js; Sanity's document-level localisation lets each language publish separately.

SEO per language and keeping translations in sync

Research keywords in each language rather than translating English ones, with Keyword Planner set to Malaysia and the language and Search Console filtered by /ms/ or /zh/. Translate everything search engines read: titles, descriptions, slugs, alt text, structured data and sharing text.

To keep versions in step:

  1. Name one source language, usually English.
  2. When a source page changes, flag its translations as outdated in a CMS status field or shared sheet.
  3. Keep a glossary and translation memory, so repeated phrases are not paid for twice.
  4. Ship translations weekly, and keep shared content such as prices in one component per language.
  5. Once a month, list missing or outdated pages in each language.

What a second or third language costs

Published ringgit rate cards, checked on 2 October 2026: one Kuala Lumpur firm lists RM0.35 a word for English into Malay, Chinese or Tamil; another RM0.50 for English into Malay (RM0.60 technical), with editing at half the translation fee; a third starts at RM0.50 standard and RM0.75 technical. These are firms' own prices, not a survey.

A worked example: 12 pages with 6,000 English words (my assumption) into Malay and Chinese is 12,000 words, or RM4,200 to 9,000, plus RM2,100 to 4,500 for review at half the fee. Two Webflow Essential locales add about RM880 a year, two Framer locales about RM1,960. Each 1,000-word blog post in two more languages costs RM700 to 1,500.

Design and build grow too, as every template is checked in each script; my guide to website costs in Malaysia has the wider ranges. My own rates sit above typical Malaysian ones. Every project starts with a free 30 minute intro call, then a written scope and one fixed quote, with no retainer.

How to make a website multilingual, step by step

  1. Collect evidence for each language.
  2. Decide coverage: key service pages in every language, not every post.
  3. Fix the structure and codes.
  4. Choose the platform.
  5. Write the source copy and glossary before design is final.
  6. Design with real copy in every language, longest beside shortest.
  7. Translate, transcreate and review on staging.
  8. Build hreflang, sitemaps, switcher, forms, emails and notices.
  9. Run the checks below, launch, watch each folder in Search Console and start the weekly translation cycle.
CheckHow to test it
Hreflang, canonical and lang correct on every pageCrawl the site; Search Console indexing per folder
No English left behindSubmit forms; trigger errors, 404, cookie banner, emails
Layout holds at 320px in the longest languageA real phone, in Tamil or Malay
Chinese fonts load only where neededNetwork panel on an English page
Switcher and Malay and English PDPA notice on every templateClick through each language

Common mistakes to avoid

  • Redirecting by IP or browser language: visitors and Google's crawler may never see the other versions.
  • Flags, or a switcher that drops people on the homepage.
  • Canonicalising translations to English, which tells Google they are duplicates.
  • Raw machine translation or a mainland translator on pages that sell.
  • A CRM that cannot store Chinese or Tamil names.
  • A PDPA notice only in the page's language.
  • A language nobody can answer enquiries in.

Frequently asked questions

Do I need a Malay version of my website in Malaysia?

I know of no general rule requiring a private company's pages to be in Malay, but your PDPA notice must be in Malay and English wherever you collect personal data. Malay matters most for government, GLC, SME and mass consumer audiences; if your buyers work in English, start there and add Malay when data shows demand.

Should I use Simplified or Traditional Chinese for Malaysia?

Simplified. The main Malaysian Chinese news sites publish in Simplified characters, so it is what your readers see every day. Tag the pages zh-Hans-MY in hreflang and zh-Hans in the lang attribute, and use a Malaysian translator who knows local terms. Keep Traditional for a separate Hong Kong or Taiwan version.

Can I use Google Translate or AI to translate my website?

As a first draft, yes. Published as is, no: tone, local terms and form wording go wrong, and Google's spam policy covers auto-translated pages made at scale with little value. Have a Malaysian native speaker edit every page in context, and transcreate the homepage and campaigns.

How much does it cost to translate a website in Malaysia?

Published rate cards start around RM0.35 to 0.75 a word, before review. A 6,000-word site into Malay and Chinese is 12,000 words, roughly RM4,200 to 9,000, plus review and platform fees such as USD 9 a month per locale on Webflow. Every update costs again, so budget monthly.

Should my website switch language automatically?

No. Google advises against redirecting people by perceived language, and its crawler may never see your other versions. Show a visible switcher with each language in its own name, link to the same page in the other language, remember the choice, and use a gentle banner to suggest a switch.

Do I need a Tamil version of my website?

Only with evidence. Indian Malaysians are 6.5% of citizens and Tamil primary schools teach roughly 78,000 pupils, but many Tamil speakers browse in English. Add it when you serve that community directly, in healthcare, education or community services for example, and someone can answer in Tamil.

My recommendation

Start with English and Malay on one domain with subfolders, add Simplified Chinese when your buyers are there, and add Tamil with evidence and someone to answer in it. Get hreflang and the bilingual PDPA notice right on day one, design with real copy, and budget translation monthly.

If you are planning one, see how I approach website design for Kuala Lumpur companies, or book a free 30 minute intro call about your languages and structure.

Sources and method

I collected every figure on 2 October 2026, converting at Bank Negara Malaysia's noon middle rates of RM4.0855 per US dollar and RM4.5968 per euro. The width test is my own: UDHR texts in Google Fonts' Noto families at 16px with 24px lines, measured in headless Chrome. Font sizes are the regular-weight WOFF2 files Google Fonts served that day; school totals are derived from the ministry's percentages. Data is thin on language preference: no official source measures which language Malaysians prefer online.

Tags: Malaysia, Multilingual, SEO, Localisation, Typography

Keep reading

Let’s look at your product.

A free 30 minute call. You leave with a clear next step, whether we work together or not.

Book a free intro call