International SEO helps search engines serve the right version of your pages to the right users across countries and languages. If you are doing SEO marketing in Singapore and targeting audiences outside the country, this setup matters. Your aim is to make it clear which URL is intended for each audience, and to ensure Google can crawl and index every version without confusion.
How Google Determines a Target Locale
Google uses several signals to identify which audience your content targets. Some signals are stronger and more reliable than others.
Strong Signals Google Uses for International Targeting
These are signals you can implement directly and that Google can interpret with less ambiguity. They tend to have the highest impact on correct targeting.
Country-code top-level domains (ccTLDs)
Using ccTLDs such as .sg or .my sends a strong country targeting signal to users and Google. Scroll down to the FAQ section if you have any questions about registering a .sg ccTLD in Singapore.
Hreflang Annotations
Hreflang is a direct method to declare language and optional region variants of the same content. You can place hreflang in the HTML head, in XML sitemaps, or via HTTP headers (for non-HTML). More on it later.
Weaker Signals Google May Use
These signals can reinforce your targeting, but they are easier to misread and can conflict with each other. Use them to support your primary targeting method.
Server Location (IP address)
The physical location of your server is often near your users and can signal your intended audience. However, some websites use distributed content delivery networks (CDNs) or are hosted in countries with better infrastructure. This makes server location less reliable than URL structure and hreflang.
Other Contextual Signals
Google may also use the following signals where available:
- local addresses
- phone numbers
- page language
- currency
- backlinks from local sites,
- Google Business Profile
These signals are useful but should not be relied upon as your primary targeting method.
What Google Doesn’t Do
Google does not attempt to vary the crawler location used for a single site to find different versions of your content. Make sure you explicitly tell Google about any locale or language variation using methods like hreflang entries or ccTLDs.
Google ignores locational meta tags like geo.position or distribution, and does not use geotargeting HTML attributes.
Generic Top-Level Domains and Country Targeting
If your site uses a generic top-level domain (gTLD) such as .com, .org, .edu, or .gov, Google treats these as having no specific country association. You must explicitly set a country target using hreflang or other targeting methods described in this article.
Google also treats some country code TLDs as generic domains when they are commonly used for purposes other than country targeting. Examples include .tv, .me, .io, .co, and others.
How to Implement Hreflang for Multi-Language Sites?
Google supports three equivalent ways to declare localised variants. Pick the one that is easiest for your CMS and workflows, then keep it consistent. Below are the three options you can use:
HTML Link Tags
Use <link rel="alternate" hreflang="..." href="..."> inside the <head> section. This is the simplest and easiest method to maintain for most websites.
According to Google’s documentation on managing international and multilingual sites, every page variant must contain the same complete set of hreflang annotations, including a self-referential tag pointing to itself. This is very important.
Example:
<head>
<link rel="alternate" hreflang="en-gb" href="https://example.com/en-gb" />
<link rel="alternate" hreflang="en-us" href="https://example.com/en-us" />
<link rel="alternate" hreflang="de" href="https://example.com/de" />
</head>According to Google’s documentation on managing international and multilingual sites, every page variant must contain the same complete set of hreflang annotations, including a self-referential tag pointing to itself. This is very important.
Option 2: HTTP Headers
This method is useful for non-HTML assets such as PDFs, where you cannot add tags to an HTML head section.
The format uses the Link HTTP header:
Link: <https://example.com/file.pdf>; rel="alternate"; hreflang="en",
<https://de.example.com/file.pdf>; rel="alternate"; hreflang="de"Each URL must include surrounding angle brackets, and you must specify all variants including the current file. You can find more information on how to apply hreflang using HTTP headers on Google Search Central.
Option 3: XML Sitemap Annotations
This method is useful when you prefer central management in a parent sitemap, or when editing templates is difficult.
You must specify the xhtml namespace in your sitemap:
xmlns:xhtml="http://www.w3.org/1999/xhtml"Then create a separate <url> element for each page URL, and within each element, include <xhtml:link> entries for all language and region variants including itself.
XML Sitemap Example
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>https://example.com/en</loc>
<xhtml:link rel="alternate" hreflang="en" href="https://example.com/en"/>
<xhtml:link rel="alternate" hreflang="de" href="https://example.com/de"/>
</url>
<url>
<loc>https://example.com/de</loc>
<xhtml:link rel="alternate" hreflang="en" href="https://example.com/en"/>
<xhtml:link rel="alternate" hreflang="de" href="https://example.com/de"/>
</url>
</urlset>
You can find more information on how to apply hreflang using XML sitemap on Google Search Central.
No Benefit to Using All Three Hreflang Methods at Once
From Google’s perspective, all three methods are equivalent, and you should only be using 1 of the method. Using multiple methods at the same time adds operational complexity without improving search performance.
Hreflang Best Practices for Global Websites
Here are some of the best practices you should follow when it comes to applying hreflang on your site.
1. Use Fully-Qualified URLs
When applying hreflang using any of the three methods, each alternate URL must be fully-qualified, including the protocol.
Example: use https://example.com/sg rather than /sg or //example.com/sg. so that Googlebot will know the precise URL you indicated.
2. Use Two-way Linking and Include Every Version
Each language or region version must list:
-
itself
-
all other variants
Hreflang works best when annotations are reciprocal. If page A references page B, page B must reference page A. If the pages do not point to each other, Google may ignore those tags.
Example on Good Hreflang Practice
For tip 1 and 2, Booking.com is good example on good hreflang practice. To look at how they structure their hreflang using HTML, go to their site, right click on your mouse, and press inspect. Search “hreflang”, and you will see a list of alternate websites they are using for different countries.
3. Variants Can Be on Different Domains
Alternate URLs do not need to be on the same domain. This supports setups like ccTLDs, subdomains, or entirely separate domains.
4. When Full Linking Is Hard, Prioritise the Strongest Reference
If maintaining full two-way linking across every locale is difficult, Google can still use matching links that exist.
When you add a new locale, ensure it connects both ways with the strongest existing version first. This means linking the new locale to your original or dominant language version (such as your Singapore .sg site) before expanding to link with other variants. The strongest version often acts as the primary reference point for Google.
5. Keep Robots Rules Consistent Across Locales
If you use robots meta tags or robots.txt, make sure each locale version is crawlable and indexable unless there is a clear reason to restrict it.
Unintentional differences in robots.txt or noindex directives can block one locale from being crawled while others remain accessible. This can limit your international SEO visibility and weaken your localisation coverage in Google.
Language and Country Codes in Hreflang Tags
Hreflang values use standardised codes. Follow these rules or Google will not recognise your hreflang.
Language Is Mandatory and Region Is Optional
You cannot specify a country code by itself. Google does not derive language from a country code. The hreflang attribute uses language codes in ISO 639-1 format, optionally followed by a region code in ISO 3166-1 Alpha 2 format.
Example of An Incorrect Hreflang HTML Format
<link rel="alternate" hreflang="sg" href="https://example.com/sg/" />
This is incorrect because:
sgis only a country code (ISO 3166-1 Alpha 2).-
Hreflang requires a language code first.
Example of A Correct Hreflang HTML Format
<link rel="alternate" hreflang="en-sg" href="https://example.com/sg/" />
This is correct because:
-
en= English language (ISO 639-1). -
sg= Singapore country code (ISO 3166-1 Alpha 2).
Use Script Codes when Language Scripts Differ
For languages with script variants, specify the script using ISO 15924 when needed:
-
zh-Hantfor Traditional Chinese -
zh-Hansfor Simplified Chinese
You can combine language, script, and region for precision:
zh-Hant-SGfor Traditional Chinese in Singaporezh-Hans-CNfor Simplified Chinese in China
Using X-Default for Users That Do Not Match Your Locale Set
The x-default value is a fallback for users whose language or region settings do not match any of your defined variants.
You do not need to specify a language code for x-default. The page targets users with unmatched settings, so the page language is not relevant to the x-default declaration itself.
When X-Default Is Useful
X-default is most useful for:
- A country or language selector page
- An international fallback page such as a global English version
This reduces the risk of users landing on a page they cannot understand.
X-Default Implementation in HTML
The image below shows how X-default should be implemented in your HTML.
Common Hreflang Implementation Mistakes
These are some of the common hreflang mistakes that can cause Google to ignore your annotations.
Missing Return Links
If page X links to page Y, page Y must link back to page X. Without return links, Google may ignore the relationship.
Incorrect Language Code
Language codes must be valid ISO 639-1 codes. You cannot use a region-only value like uk or sg as these are not language codes.
Incorrect Region Codes
Region codes must be officially assigned ISO 3166-1 Alpha 2 codes. If you use reserved codes like EU, UN, or UK in your hreflang annotations, Google Search will ignore that part of the annotation.
Handling Duplicate Content with Multi-Regional Versions
If you provide similar or duplicate content on different URLs in the same language as part of a multi-regional site, pick a preferred version and use the rel=”canonical” element along with hreflang tags.
Localised versions of a page are only considered duplicates if the main content of the page remains untranslated. If you translate the main content but keep navigation and footer in a single language, these are not considered duplicates.
Why Locale-Adaptive Pages Hurt International SEO
I will always recommend my clients to apply hreflang when optimising for international SEO instead of using local-adaptive pages. Locale-adaptive pages serve different content depending on the visitor’s perceived location or preferred language. This approach can prevent Google from crawling, indexing, or ranking all of your localised content.
Google now crawls with IP addresses from various locations around the world, including outside the USA. However, the Googlebot crawler sends HTTP requests without setting Accept-Language in the request header.
If your site changes content based on IP location or Accept-Language headers, Google may only see one version, which leaves other locale versions invisible in search.
Geo-Distributed Crawling Considerations
When Googlebot appears to come from a certain country, treat it like you would treat any other user from that country. If you block USA-based users from accessing your content but allow visitors from Australia to see it, your server should block Googlebot if it appears to be coming from the USA, but allow access if it appears to come from Australia.
You can verify Googlebot’s geo-distributed crawls using reverse DNS lookups.
Practical International SEO Best Practices for Your Business
For most international sites, a stable URL structure with clear localisation signals tends to be the safest setup.
1. Use Dedicated URLs per Locale
Avoid serving different content from the same URL. Use separate URLs per language and region so each version can be crawled and indexed independently.
2. Choose One Hreflang Method and Operationalise It
Most sites use HTML link tags because they are visible, testable, and straightforward. If your site has many variants and template changes are risky, sitemap-based hreflang can be easier to manage centrally.
Pick one method and implement it consistently across all pages.
3. Validate and Monitor Using a Checklist Regularly
Use a technical QA checklist whenever you launch a new locale:
- Hreflang tags are in the HTML head or sitemap
- Every page has a self-referencing hreflang
- All variants are included in each page’s hreflang set
- Return links are correct and reciprocal
- Robots rules are consistent across locales
Test your implementation using Google Search Console and third-party hreflang validation tools.
Making International SEO Work for Your Business
International SEO works best when each market has its own stable, crawlable URL and your locale signals stay consistent.
Prioritise strong signals such as ccTLDs and correctly implemented hreflang, then reinforce them with on-page and off-page localisation cues. Keep implementation simple by choosing one hreflang method and using x-default to guide users whose settings do not match your supported locales.
This improves the likelihood that the right pages rank in the right countries and languages, which is important if you are managing SEO marketing in Singapore and planning to expand overseas.
FAQs on International SEO for Businesses in Singapore
These FAQs cover some of the questions on international SEO I often get from clients and non-technical colleagues. If you still have any more questions regarding international SEO best practices, feel free message me on my LinkedIn.
How to register for .sg domain?
For .sg domains, you must be a citizen/permanent resident with an NRIC/FIN. Foreigners will need a local agent with a valid Singapore postal address.
How to register for .com.sg domain?
For .com.sg domains, will need to be either registered, or in the midst of registering, with the Accounting & Corporate Regulatory Authority (ACRA), Enterprise Singapore or any professional body in Singapore.
A foreign company may apply for a .com.sg domain name if it appoints a local agent as the administrative contact, with a valid Singapore postal address.
What is the registration process for .sg CCTLD?
If you’re eligible to register for a Singapore CCTLD, you’ll need to engage with a SGNIC accredited registrar, like GoDaddy or Vodien.
How do I check whether the name I intend to register is available for registration?
To check the availability of the domain name you intend to register, you can visit www.sgnic.sg and key in the domain name in the WHOIS function. If the search returns a “Domain Not Found”, it means the domain name is available for registration.
