Multilingual SEO for Malaysia and India

Which languages to build for

Start from what your customers search in, not from what feels inclusive. A clinic in Johor Bahru whose patients search in Malay and Chinese needs both; a B2B software company whose buyers search in English may need only English.

Both markets are moving towards local-language search. Google added Malay to AI Overviews in its May 2025 expansion, and in October 2025 brought AI Mode to Bengali, Kannada, Malayalam, Marathi, Tamil, Telugu and Urdu, on top of Hindi. If your customers ask Google in Tamil, an English-only site can't be the answer.

Add languages one at a time. Each one is a second site's worth of content to write, check and keep updated, so start with the language that covers the most customers you don't reach today.

Give every language its own URL

This is the rule most multilingual sites in both markets break. Google's guide to multilingual sites recommends different URLs for each language version, and says not to switch languages with cookies or browser settings.

The same guide is clear on three more points:

• Google reads the visible content to work out a page's language. It doesn't use the lang attribute or the URL for that.
• Don't redirect automatically based on a guess about the visitor's language. Let people choose, with a visible language switcher.
• One language per page. Avoid side-by-side translations, and don't translate only the menus while the body stays in English.

A site that shows Malay or English at the same URL depending on a cookie has, as far as Google is concerned, one version. The other one never gets indexed.

Choose a URL structure

For most businesses, folders on one domain work best: example.com/ms/, example.com/zh/, example.com/ta/. They're easy to set up, share one domain's authority, and live on one codebase.

Separate country domains, such as .com.my and .in, are a signal about country, not language, and Google notes a country domain can only target a single country. Use them if you're splitting by market; use folders if you're splitting by language. Our domain name guide covers that choice.

If you serve the same language in both countries with different prices or payment methods, combine the two: /en-my/ and /en-in/, each with local content.

Hreflang tags, done right

Hreflang tells Google which page is which language and region, so it shows Malaysian searchers the Malaysian page. Google's hreflang documentation sets the rules:

• Codes: a language code from ISO 639-1, optionally followed by a region code from ISO 3166-1 Alpha 2. So ms-MY, en-MY, zh-MY, ta-MY, en-IN, hi-IN and ta-IN are all valid.
• No region on its own. MY or IN alone doesn't work; it must follow a language.
• Scripts when needed. You can add an ISO 15924 script code, such as zh-Hant for Traditional Chinese.
• A fallback. x-default marks the page for visitors whose language matches none of your versions.
• Every version lists every version, including itself. If page A points to page B but B doesn't point back, Google ignores the tags.

Here's what the head of a Malay page on a three-language Malaysian site looks like:

• <link rel="alternate" hreflang="ms-MY" href="https://example.com/ms/" />
• <link rel="alternate" hreflang="en-MY" href="https://example.com/en/" />
• <link rel="alternate" hreflang="zh-MY" href="https://example.com/zh/" />
• <link rel="alternate" hreflang="x-default" href="https://example.com/en/" />

The English and Chinese pages carry the same four lines. Google says HTML tags, HTTP headers and sitemap entries are equivalent, so on a large site, putting hreflang in the sitemap is often easier to keep correct.

Write each language for how people search in it

Translation is where multilingual SEO is won or lost. A direct translation of English keywords often misses what people type.

Malaysian searches mix languages constantly: "klinik gigi near me", "aircond service Shah Alam", "harga renovate dapur". Indian searches in Hindi often mix Devanagari and English words too. Do keyword research in each language, using real customer questions from WhatsApp and sales calls, and let the page in each language target its own terms.

Be careful with machine translation at scale.

Google's spam policies list mass-producing pages through automated transformations, including translating, as a form of scaled content abuse. Machine translation as a first draft is fine; publishing hundreds of unreviewed translated pages isn't. Have a fluent speaker review every page before it goes live.

Common multilingual SEO mistakes in Malaysia and India

These come up again and again on bilingual sites in both markets:

1. A Google Translate widget instead of real pages. The translated version isn't indexable, so it brings no search traffic.
2. Hreflang without return links, usually because only the English pages were updated.
3. Translated pages with English titles and meta descriptions. The search result shows English to someone searching in Malay.
4. Fonts that don't support the script. Tamil, Devanagari and Chinese need fonts that cover them; our brand guidelines checklist covers choosing them.
5. Different content in each language with no clear match. Hreflang links equivalent pages; if the Chinese page doesn't match the English one, don't pair them.

How to check your setup works

Once the language versions are live, check them the way Google sees them:

• View the source of one page in each language and confirm every hreflang line is present, points to a page that loads, and that the page lists itself.
• Check indexing per language. In Google Search Console, inspect a page from each language folder and confirm it's indexed and that Google picked the URL you expected as canonical.
• Watch performance by country. Search Console's Performance report can be filtered by country and by page, so you can see whether Malaysian searchers land on /ms/ and Indian searchers on /hi/.
• Search the way a customer would, in each language, from each country if you can, and see which version appears.

If the wrong version keeps showing, the cause is almost always a missing return link or two pages that don't match closely enough to be treated as translations of each other.

What it costs to go multilingual

The build is the smaller cost. A site set up for multiple languages from the start, with folders, a language switcher and hreflang in the templates, costs little more than a single-language site.

Content is the real expense. Every page needs writing, reviewing and updating in each language, and our SEO cost guide notes that a second language roughly doubles the content budget. Retrofitting languages onto a site that wasn't built for them costs far more than planning them in.

If you're planning a multilingual site, our web development and SEO and analytics work covers the structure and hreflang setup together. Tell us which languages you need.