Multilingual Websites in Malaysia: BM, English and Chinese Done Properly

Most Malaysian business websites start in one language, usually English, and the question arrives later: should we add Bahasa Malaysia, Chinese or both? It often comes from a customer asking "do you have this in Chinese?" or a sales rep translating the same price list by hand. Adding languages is the right move for some businesses and a maintenance burden for others, and the difference is rarely the translation itself. It is the structure around it: which pages exist in which language, whether each has its own address, whether visitors can find the switch, who checks the wording, and who updates the Malay and Chinese versions when the English changes. This guide is about doing that part properly. It is general information for site owners, not a promise about any search ranking.

Does a second language earn its keep? Start with evidence

Malaysia uses several languages in daily business, but that does not mean your website needs all of them. A multilingual site is a promise: every language you add is one you must keep correct, answer enquiries in and update. So add one when you can point to evidence from your own business rather than from a general statistic. Good sources are close at hand:

• Enquiries and messages. Go through last quarter's WhatsApp messages, calls and emails. How many arrived in Malay or Chinese, or asked whether there is a version in that language?
• Hand translation by staff. If your team already rewrites the same price list or quotation in another language every week, that page is the first candidate.
• Analytics. If you use analytics, its language report shows the browser language of visitors. Treat it as a hint only: many people keep their phone set to English even when they would rather read Malay or Chinese, so the figure may understate demand.
• Who actually buys. A supplier selling to government-linked buyers may be expected to provide Bahasa Malaysia; a retailer in a Chinese-majority town may get more from Chinese than from Malay. Neither is a rule. It depends on your customers.

Be wary of weak reasons such as "Malaysia is multilingual", "a competitor has a language button" or unsourced vendor statistics: none tells you whether your customers will use the page. Before committing, ask three questions: who will answer enquiries that arrive in this language, who will review the translation, and who will update it every time the English changes? If you cannot name a person for each, start smaller.

Three levels of multilingual: pick the smallest one that works

"Multilingual" is not all or nothing. Most small businesses sit at the second level.

Moving up a level later is easy; moving down is awkward, because removed pages may already be shared and bookmarked. Start at level 2 with a short list and expand when the evidence says so.

What to translate first, and what can wait

The order matters more than the total. A visitor who finds the pages that answer "what do you do, how much, how do I reach you" in their own language gets most of the benefit, even if the rest of the site is in English.

If a page has no translation, decide what the switcher does. The cleanest answer is to link to that language's home page, or to leave the switch out on that page. Never leave a link that goes nowhere.

One page per language, each with its own address and a switcher people can find

The technical heart of a good multilingual site is simple: every language version is a separate page with its own URL. Google's documentation on multilingual sites recommends a separate URL for each language version rather than showing different languages at the same address based on cookies or browser settings, partly because a search crawler may only ever see one of them. It also advises against redirecting visitors automatically by their perceived language, so people and crawlers can reach every version. A tidy pattern is a folder per language, with the same path inside each:

Gotka's own site uses this pattern: English at the root, Malay under /ms/ and Simplified Chinese under /zh/, with EN, BM and 中文 links in the header of every page that lead to the same page in the other language. Keeping the paths identical makes the switcher and the annotations below easy to maintain.

Tell search engines how the versions relate with hreflang annotations. Google documents that each version should list itself and every other version, that the links should be reciprocal, and that an x-default entry can name a fallback page for visitors whose language you do not cover. The annotations can sit in the page head, in HTTP headers or in the XML sitemap. Treat them as a hint, not a guarantee, and check Google's current documentation when you set them up. Each language page should normally name itself as its canonical address, since a canonical pointing every translation at the English page invites search engines to ignore the translations. Keep each page in one language only, because Google says it works out a page's language from its visible text, and still set the lang attribute, which helps screen readers and browsers.

The switcher itself deserves as much care as the markup:

• Visible. Put it in the header on every page, not buried in the footer. Visitors do not hunt for it.
• Labelled in its own language. Write English, Bahasa Malaysia (or BM) and 中文, whichever page the visitor is on.
• No flags. A flag stands for a country, and English, Malay and Chinese each belong to more than one.
• Page to page. The Malay link on the pricing page should open the Malay pricing page, not the Malay home page, whenever that page exists.
• Plain links. Use ordinary links rather than a script-only menu, so it works for every visitor and crawler.

Who should translate: people, not widgets

A translation tool can produce a useful first draft. It cannot tell that your price changed last week, that a service name should stay in English, or that a phrase sounds stiff to a Malaysian reader. Google's spam policies warn about content produced at scale by automated means, translation included, that adds little value for readers, and its guidance on automated content stresses human review. The stronger reason is trust: clumsy Malay or Chinese makes a business look careless. The rule is simple: publish nothing that a competent human reader of that language has not read in full.

• Malay for Malaysia. Malaysian Bahasa Malaysia differs from Indonesian in spelling and vocabulary, so choose a translator or reviewer who writes for Malaysian readers. Use a courteous business register, with "anda" for "you".
• Simplified or Traditional. Malaysia has no single official script for Chinese. Simplified is widely used and common among younger readers; some communities still use Traditional. We found no readership study, so look at your own customers' name cards, signboards and WhatsApp messages. Choose one script per version, and do not run an automatic converter over Simplified text to produce Traditional, because vocabulary differs as well as characters.
• Names. Keep your registered company name as registered. If you use a Chinese business name on signs and name cards, use that same form everywhere. Product and technical names such as WhatsApp or cPanel normally stay in Latin letters.
• Prices and legal terms. Numbers and the RM sign should match the source page exactly. Terms, warranty, refund and tax wording should be checked by someone who understands what they commit you to. A statement about which version prevails if the languages differ is one for a lawyer to word.
• A short brief. Give the translator a glossary, your preferred tone and the page layout, and ask for natural writing, not word-for-word. Malay text is often longer than English and Chinese more compact, so test that buttons and tables still fit.

Names, prices, dates and addresses across languages

Small formatting differences between versions make a site feel stitched together. Settle each item once and apply it everywhere:

Forms, confirmations and email replies in the visitor's language

An untranslated form on a translated page is the most common half-finished job. A visitor reads your Malay page happily, then meets an English "Submit" button and an "Invalid email address" error, and leaves. Treat the whole journey as part of the translation:

• Everything on the form. Field labels, placeholder text, validation and error messages, the button, the anti-spam prompt and the thank-you page.
• The privacy line. The short notice beside the form, and the link to the full notice, should be in that language.
• The confirmation email. One template per language, sent in the language of the page the visitor used. Ask your developer or form tool whether the page language can be passed along with the enquiry so that staff also see which language to reply in.
• The WhatsApp button. If it opens a pre-filled message, write it in the page's language.
• A person who can reply. If nobody on the team can answer in Chinese, do not invite Chinese enquiries without saying so. Say plainly which languages you reply in, and avoid promising a reply time you cannot meet in that language.

For the choice between a form and a WhatsApp link, see enquiry form or WhatsApp button. Whichever you use, test it in each language yourself: submit a real enquiry from each version and read the page, the errors, the thank-you message and the email that arrives.

Keeping every version in step after an edit

Launch is the easy part. The usual failure is drift: the English page gets a new price, the Malay page keeps the old one and the Chinese page is never touched. A stale price in a second language is worse than no second language, because it is a promise you may have to break. Build a routine from the start:

• Name the source language. Usually the one you edit first. Every change starts there, and no content change goes live in one language only unless it is truly specific to that language.
• Keep a page register. A simple spreadsheet with a row per page and columns for the English, Malay and Chinese update dates and an owner. Anyone can see at a glance which version is behind.
• Treat prices, hours and contact details as high risk. Update all versions in one sitting. Festive notices and promotions follow the same rule: all languages or none.
• Count the work honestly. Each text change is separate work in each language, so three languages mean three edits.
• Retire what you cannot maintain. If a translated page is stale and nobody will fix it, remove it and point its address to the language home page.

The same applies to the technical layer: when you add, rename or remove a page, update the switcher links, hreflang annotations and sitemap in the same change.

Common mistakes

• Relying on an automatic translation widget. A widget that translates inside the visitor's browser typically leaves search engines with no separate page to index, and nobody has checked the result. Browsers already offer their own translation tools for readers who want them.
• Mixing languages on one page. A Malay heading over English paragraphs, or English and Chinese side by side, confuses readers and makes the page's language unclear to search engines. Brand names and technical terms inside a sentence are fine; whole blocks in another language are not.
• Leaving forms, buttons and emails untranslated. See above.
• Using flags as language buttons. Flags are countries, not languages.
• Redirecting by IP address or browser setting. It strands travellers and can hide versions from crawlers.
• Forgetting the invisible text. Page titles, meta descriptions, image alt text, PDFs and the 404 page are all part of the language experience.

A launch checklist

Before you switch a new language on, check each of these:

1. Evidence. You can point to the enquiries, staff workload or reviews that justify the language.
2. Scope. You have a written list of pages to translate first and pages deliberately left out.
3. Reviewer. A native reader has read every translated page in full, including prices and legal wording.
4. Script and names. One Chinese script is chosen; company and product names are consistent.
5. Addresses. Each language has its own URL, with matching paths.
6. Switcher. It is visible in the header, labelled in each language and links page to page.
7. Annotations. Language codes, hreflang entries, self-referencing canonical addresses and sitemap entries are in place.
8. Forms. Every label, error, thank-you page, confirmation email and WhatsApp message is in the right language, and you have submitted a real test in each.
9. Formatting. Currency, phone numbers, addresses and dates follow the same rules everywhere.
10. Phone test. The pages have been read on a phone, where long text often breaks layouts first.
11. Upkeep. The page register exists, an owner is named, and a quarterly read-through is in the diary.

Where Gotka Technologies fits

Gotka's web design package builder lists extra language versions as add-ons: Bahasa Malaysia at +RM400 per page and Chinese (Simplified) at +RM400 per page. These are indicative starting prices, confirmed by a written quote, and because they are priced per page, the short list of pages from the "translate first" table is what decides your figure. The package inclusions do not describe a translation or review process, so ask for the detail in your written quote: who writes or reviews the Malay and Chinese text, who supplies prices and legal wording, and what happens to the translated pages when the English changes. If you need Traditional Chinese rather than Simplified, raise it at the same time. See Gotka's web design service, our guide to how many pages a small business website needs and how much a website costs in Malaysia. Because upkeep is the real cost of a second language, the optional Care plans, which include monthly content edits (up to 1 hour a month on Care Basic), are one way to keep it going.

Key terms used in this guide

• Multilingual website: a site that offers its content in more than one language, each version a real page rather than an on-the-fly translation.
• Localisation: adapting wording, formats and details to the readers of one language and place, beyond word-for-word translation.
• Language switcher: the visible control that takes a visitor to the same page in another language.
• hreflang: an annotation that tells a search engine which language version of a page is meant for which readers.
• x-default: an hreflang value naming a fallback page for visitors whose language is not covered.
• Canonical URL: the address a page declares as its preferred one; each language version normally names itself.
• Machine translation: text translated automatically by software, best treated as a draft for human review.
• Simplified and Traditional Chinese: the two written forms of Chinese; Simplified is the one Gotka's add-on lists.
• Bahasa Malaysia (Bahasa Melayu): the national language of Malaysia, written here with Malaysian spelling and vocabulary.
• Page register: a simple list recording each page, its languages, update dates and owner.