Singapore is one of the few markets where a small business can reasonably serve customers in four languages. A tuition centre may publish parent guides in English and Chinese, a clinic may offer patient information in Malay and Tamil, and a property developer may run separate pages for local and overseas buyers. Once those pages exist, Google needs a way to tell which version to show to which searcher.
That is the job of hreflang. It is a small piece of code, but it is easy to get wrong, and mistakes can mean your Chinese page appears for English searches or your English page outranks the Malay version you built for Malay-speaking readers. This guide explains how hreflang for multilingual websites works, which language and region codes make sense in Singapore, how to implement it on WordPress and other platforms, and how to test it.
What hreflang does, and what it does not do
Hreflang is an annotation that tells Google “this page has equivalent versions in other languages or for other regions, and here they are”. Google’s documentation on localised versions of your pages describes it as a way to help Google point users to the most appropriate version of a page by language or region.
A few points are worth being clear about from the start:
- It is a signal, not a command. Google may still show a different version if it judges that more relevant.
- It does not translate anything. You still need genuinely translated, useful pages in each language.
- It does not improve rankings on its own. It helps the right version appear; it does not make a weak page stronger.
- Google identifies language from visible content. Google’s guide to managing multi-regional and multilingual sites says it uses the visible content of a page to determine its language, not code-level attributes such as the HTML
langattribute. Keep each page in one main language.
Other search engines treat these signals differently. Bing, for example, has historically put more weight on content-language signals than on hreflang, so if Bing traffic matters, check its own guidance in Bing Webmaster Tools.
Do you need hreflang at all?
Many Singapore SME websites do not. If your site is only in English and targets Singapore, hreflang adds nothing. Use it when at least one of these is true:
- You have the same page in two or more languages, such as English and Simplified Chinese versions of a service page.
- You have the same language for different regions, such as separate English pages for Singapore and Malaysia with different prices, delivery terms or contact details.
- You see the wrong language version appearing in search, or Search Console shows the versions competing with each other.
If you only translated a handful of pages, add hreflang to those pages and leave the rest alone. Hreflang works page by page, not site-wide. Choosing whether to target one country or several is a strategic question first; our comparison of local and global SEO helps with that decision.
Language and region codes for Singapore websites
An hreflang value starts with a language code in ISO 639-1 format, optionally followed by a region code in ISO 3166-1 Alpha 2 format. Google also accepts a script code for languages written in more than one script, such as Chinese. A region code on its own is not valid.
| Audience | Example value | Notes |
|---|---|---|
| English, any region | en | Use when one English page serves everyone |
| English readers in Singapore | en-SG | Useful only if you also have English pages for other regions |
| Chinese readers in Singapore | zh-SG or zh-Hans-SG | Singapore uses Simplified Chinese; pick one format and use it consistently |
| Simplified Chinese, any region | zh-Hans | Good if the same Chinese page serves Singapore, Malaysia and mainland readers |
| Malay readers in Singapore | ms-SG or ms | Use ms, not my (which is Burmese) |
| Tamil readers in Singapore | ta-SG or ta | Tamil is an official language of Singapore |
| Fallback for everyone else | x-default | Usually your main English page or a language selector |
Common code mistakes
- Using a country code as the language, such as
sgorcnon its own. - Using
en-UKinstead ofen-GB, ormyfor Malay. - Mixing
zh-SGon some pages andzh-Hanson others for the same audience. - Labelling a page
zhwhen it is actually written in English with a Chinese headline.
How to implement hreflang: three methods
Google supports three ways to declare localised versions. Choose one per site and stick to it, because mixing methods makes errors harder to trace.
| Method | Best for | Watch out for |
|---|---|---|
HTML <link> tags in the page head | Most WordPress and CMS sites | Every page must carry tags for all its versions |
| HTTP headers | Non-HTML files such as PDF brochures | Needs server or CDN configuration |
| XML sitemap entries | Large sites, or when you cannot edit page templates | Sitemap must stay in sync with live URLs |
The HTML method in practice
Imagine an illustrative tuition centre with an English and a Chinese page about its Primary 6 programme. Both pages carry the same block of tags in the <head>:
<link rel="alternate" hreflang="en-SG" href="https://example.com.sg/p6-programme/" /><link rel="alternate" hreflang="zh-SG" href="https://example.com.sg/zh/p6-programme/" /><link rel="alternate" hreflang="x-default" href="https://example.com.sg/p6-programme/" />
Three rules make this work. First, each page lists itself as well as its alternatives. Second, the links are reciprocal: if the English page points to the Chinese page, the Chinese page must point back, otherwise Google may ignore the pair. Third, every URL is a full, absolute address including https.
Where x-default fits
x-default tells Google which page to show when none of your listed languages or regions matches the searcher. On most Singapore sites, that is the main English page. If you have a language-selection page, that can be the x-default instead.
Structuring multilingual URLs
Hreflang works with any URL structure, but a clear structure makes it easier to maintain. For most SMEs, language subfolders on one domain are the simplest option.
| Structure | Example | Pros | Cons |
|---|---|---|---|
| Subfolders | example.com.sg/zh/ | One domain to maintain; simple to set up on WordPress | Less separation if you later target other countries |
| Subdomains | zh.example.com.sg | Can be hosted separately | Often more work to manage and measure |
| Separate domains | example.com.sg and example.com.my | Strong country signal | Several sites to maintain, each building its own authority |
| URL parameters | example.com.sg/?lang=zh | Quick to add | Google advises against it; harder to crawl and share |
Whatever you choose, keep slugs readable in each language and be consistent. Our guides to SEO-friendly URL structure and site structure cover the wider principles.
Hreflang, canonicals and translated content
Hreflang and canonical tags must agree. Each language version should have a canonical tag pointing to itself, not to the English page. If the Chinese page declares the English page as canonical, you are telling Google the Chinese page is a duplicate, and hreflang cannot overrule that. The guide on duplicate content and canonical tags explains canonicals in more depth.
Pages in the same language for different regions, such as en-SG and en-MY, can look like duplicates. Hreflang helps Google understand they are intentional, but it helps even more when the pages genuinely differ: local prices in SGD or MYR, local phone numbers, delivery areas and relevant examples.
Translation quality matters too. A page that has been machine-translated and never reviewed by a fluent speaker is a poor experience for readers, and Google’s spam policies warn against producing large volumes of low-value pages. Have each language version checked by someone who speaks it, especially for terms such as school levels, medical services or financial products.
Hreflang on WordPress and other platforms
You rarely need to write hreflang tags by hand. Most multilingual plugins for WordPress, such as WPML, Polylang and TranslatePress, add hreflang tags automatically once you link translations together. Shopify Markets and several website builders also generate them. Check three things after setup:
- Each translation is actually linked to its source page in the plugin, not just published separately.
- The language codes match your table above, including the region if you use one.
- Pages without a translation do not point to a missing or placeholder version.
Avoid automatically redirecting visitors to a language based on their IP address or browser settings. Google’s guidance recommends against automatic language redirects because they can stop both users and Googlebot from reaching every version. A visible language switcher that links to the equivalent page, not just the home page, is a better choice.
A step-by-step hreflang rollout plan
- Week 1 – Inventory (marketing lead). List every page that exists in more than one language or region, with its URL for each version.
- Week 1 – Choose codes and x-default (marketing lead and developer). Fix one code per audience and document it.
- Week 2 – Implement (developer). Configure the plugin, template or sitemap. Confirm each page is self-referencing, reciprocal and uses absolute URLs.
- Week 2 – Align canonicals and sitemaps (developer). Each version canonicalises to itself; every version is in the XML sitemap.
- Week 3 – Review translations (native speakers). Check meaning, tone and local terms on priority pages.
- Week 3 – Test (marketing lead). Use a crawler or hreflang checker to find missing return links and invalid codes; spot-check pages with URL Inspection.
- Monthly – Monitor (marketing lead). Review Search Console performance by page and country, and re-test after any redesign or plugin update.
Search Console no longer offers its old International Targeting report, so testing relies on crawlers, hreflang validation tools and performance data. Include an hreflang check in every SEO audit and in any site migration.
How AI can help with multilingual SEO
AI is genuinely useful here, as long as people stay in control. Translation models can produce a first draft of a Chinese, Malay or Tamil page quickly; a fluent reviewer then corrects terminology and tone. AI tools can also compare language versions to flag pages that exist in one language but not another, check hreflang tags across a crawl export, and draft localised meta titles and descriptions.
Marketing2u’s AI SEO Agent runs technical checks such as canonicals, sitemaps and status codes, and can apply approved, low-risk fixes such as meta descriptions and SEO titles. The AI Content Agent drafts and refreshes content for human approval before anything is published.
The limits matter. AI translation can miss cultural context, misread Singlish or produce stiff phrasing, and it cannot judge whether a Malay-speaking customer would trust the page. Do not publish unreviewed machine translations, and do not let a tool change hreflang settings site-wide without testing first.
Common hreflang mistakes to avoid
- Missing return links. One-way hreflang annotations are a frequent reason Google ignores the tags.
- Canonicalising translations to the English page. This contradicts hreflang and can keep translations out of the index.
- Pointing hreflang at redirected, noindexed or broken URLs. Every URL in the set should return 200 and be indexable.
- Half-translated pages. A Chinese page with English body text confuses both users and Google.
- Forgetting x-default. It is optional, but it gives Google a sensible fallback for everyone else.
- Setting it and forgetting it. New pages, deleted translations and plugin updates break hreflang quietly.
Conclusion: make every language version easy to find
Hreflang for multilingual websites is a straightforward idea that rewards careful execution. Pick clear language codes for your Singapore audiences, implement them with one method, keep every set self-referencing and reciprocal, align canonicals, and test after every change. Most of all, make sure each language version is worth finding: a properly translated page with local details will serve your English, Chinese, Malay and Tamil-speaking customers far better than any tag on its own.
Frequently asked questions
Is hreflang a ranking factor?
Hreflang does not boost rankings by itself. It helps Google show the right language or regional version to the right searcher, which can improve relevance and click-through. The page still needs to be useful and well optimised.
Should I use zh-SG or zh-Hans for Singapore Chinese pages?
Both are valid. Use zh-SG if the page is written specifically for Singapore readers, or zh-Hans if the same Simplified Chinese page serves several regions. The key is to pick one format and use it consistently across the site.
Do I need hreflang if my site is only in English?
Usually not. Hreflang is only needed when equivalent pages exist in more than one language or for more than one region. An English-only site targeting Singapore can skip it.
How long does hreflang take to work?
Google has to recrawl every page in a set before it can connect them, so changes can take from days to several weeks to show. Monitor search performance by country and page rather than expecting an instant change.
Sources and further reading
- Google Search Central: Tell Google about localised versions of your page
- Google Search Central: Managing multi-regional and multilingual sites
- Google Search Central: Canonicalisation and duplicate URLs
- W3C Internationalization: Language tags in HTML and XML
- Google Search Central: Spam policies for Google web search
Related guides
- Duplicate Content and Canonical Tags Explained
- SEO-Friendly URL Structure: Best Practices for 2026
- Local SEO vs Global SEO: Which Strategy Does Your Business Need?
- 20 Practical Strategies To Rank Nationally In SEO (With Examples)
- How To Do An SEO Audit: 9 Things To Check For
Browse every article in our SEO guides.