Businesses serving customers across several countries or languages need more than a translated website. Without the right setup, Google may show the English version to a searcher in Jakarta, treat similar versions as duplicates, or not index some pages at all.
This guide covers how hreflang works, URL structure options, the most common mistakes, and how we apply all of this on Venti Digital's own website, which currently has 14 language and region versions.
Key Takeaway: What Does Multilingual SEO Require?
Multilingual SEO requires three things: separate URLs for each language or region version, complete, reciprocal hreflang annotations so Google understands how versions relate, and content that is genuinely translated and adapted, not just translated menus and buttons. Add x-default as a fallback for visitors whose language matches no version.
How Google Determines a Page's Language
One common misconception: Google's documentation says Google determines a page's language from its visible content, not from code-level information such as the lang attribute or the URL. A page written in Indonesian with lang="en" is still treated as Indonesian.
The lang attribute still matters for accessibility and browsers, but what counts for Google is the content. That is why language versions that translate only menus while the main content stays in one language do not work well. Google specifically notes that this practice can create a poor user experience.
Choosing a URL Structure
Google describes several URL structure options for multi-regional sites:
| Structure | Example | Pros | Cons |
|---|---|---|---|
| Country domain (ccTLD) | example.de | Very clear country signal | Expensive, many domains to manage |
| Subdomain | de.example.com | Easy to separate technically | Users cannot tell the target country from the URL |
| Subdirectory | example.com/de/ | Easy to maintain on one host | Less separation between versions |
| URL parameter | example.com?loc=de | Easy to create | Not recommended by Google |
An important note on country domains: Google says ccTLDs give a strong signal that a site is intended for a specific country. That helps if you only target one country, but it can be a constraint if you use a country domain to target others. Some ccTLDs, such as .tv and .me, are treated by Google as generic domains.
For most businesses, subdirectories on a single domain are the most practical choice, because domain authority stays in one place and management is simpler.
How Hreflang Works
Hreflang tells Google that several pages are language or region versions of the same content, so Google can show the right version to each searcher.
There are three ways to implement it:
linktags in the HTMLhead.- HTTP headers, usually for non-HTML files such as PDFs.
- An XML sitemap.
The most important rules:
- Each version must list itself and every other version. The set of links is identical on every version.
- Links must be reciprocal. If page A lists page B as an alternate, page B must link back to A. Otherwise, Google ignores the annotations.
- Language codes use ISO 639-1, such as
id,en, orko. Region codes are optional and use ISO 3166-1 Alpha 2, such asen-GBoren-SG. - A region code alone is not valid. For example,
IDwithout a language code will not work. - Use
x-defaultfor a fallback page, such as a language selector or global version.
An example of annotations in the head:
<link rel="alternate" hreflang="x-default" href="https://example.com/" />
<link rel="alternate" hreflang="en" href="https://example.com/" />
<link rel="alternate" hreflang="id" href="https://example.com/id/" />
<link rel="alternate" hreflang="ko" href="https://example.com/ko/" />
Case Study: Venti Digital's 14-Version Website
Venti Digital's website serves visitors from many countries, so we apply the principles above on our own site. Here is how it is set up:
| Decision | Implementation on ventidigital.id |
|---|---|
| URL structure | Subdirectories on one domain, such as /id/, /ko/, /ja/, and /ar/ |
| Versions | 14 versions: global English, English for the US, UK, Australia, and Singapore, plus Indonesian, Malay, Korean, Japanese, Chinese, German, French, Spanish, and Arabic |
| x-default | The global English version on the homepage |
| Hreflang | In the head of every page and in the sitemap, with each version listing every version including itself |
| Content | Every version is fully translated, including titles, meta descriptions, and FAQ structured data |
| Technical | A lang attribute matching each language, and right-to-left text direction for Arabic |
A few lessons from this setup:
- Regional versions in the same language need real differences. We differentiate the English versions for several countries through regional adjustments, but their content remains similar. Hreflang helps Google pick the right one, but the more the content differs, the stronger each version's case for standing on its own.
- The domain sets limits. A
.iddomain sends a strong signal for the Indonesian market. For other language versions, we rely on genuinely localized content and other signals, because hreflang handles language; it does not remove a domain's country signal. - Consistency needs a system. With 14 versions, adding or changing one page means updating every annotation. We generate pages and the sitemap from a single translation source so hreflang stays complete and reciprocal.
The Most Common Hreflang Mistakes
| Mistake | Effect | Fix |
|---|---|---|
| No return links | Google ignores the annotations | Make sure every version lists every other version |
Wrong region code, such as en-UK | No effect; Google says codes like UK have no impact | Use en-GB |
Country code only, such as ID alone | Not valid | Always start with a language code |
| Canonical pointing to another language version | That version is not indexed | Each version uses a self-referencing canonical |
| Hreflang pointing to redirected, broken, or noindexed pages | Annotations do not work | Use final, indexable URLs |
| Automatic redirects based on location or browser language | Google and users cannot reach every version | Offer a language choice instead of forcing a redirect |
| Translating only menus and buttons | Versions seen as low value, poor user experience | Translate and localize the main content |
Google specifically advises avoiding automatic redirects from one language version to another based on a user's perceived language or location, because they can stop users and search engines from seeing all versions of a site.
Localization, Not Just Translation
Hreflang only tells Google which version is for whom. For each version to compete in its market, the content needs to be localized:
- Use the terms local searchers use. Do separate keyword research for each language, because direct translations often differ from how people actually search.
- Adapt currency, date formats, examples, and local references.
- Adapt proof and contact details, such as clients, addresses, or phone numbers relevant to that market.
For AI engines, well-localized language versions also make it easier for assistants to cite the right page when a user asks in a given language.
Multilingual SEO Checklist
| Area | What to confirm |
|---|---|
| URL structure | Each version has its own URL, ideally a subdirectory |
| Hreflang | Complete, reciprocal, and self-referencing |
| Codes | Language in ISO 639-1, region in ISO 3166-1 Alpha 2 |
| x-default | Set for the fallback version |
| Canonical | Each version canonicalizes to itself |
| Redirects | No automatic redirects based on location |
| Content | Fully translated and localized, including titles and meta descriptions |
| Keyword research | Done separately for each language |
Conclusion
Successful multilingual SEO is not about adding as many tags as possible. It is about giving each version its own URL, describing the relationships between versions with correct hreflang, and making the content genuinely for readers in each market. With that foundation, Google can show the right version to each searcher, and each version has a real chance to compete in its own market.
If you are planning a multilingual website or expanding into new markets, talk to the Venti Digital team.
Frequently Asked Questions
Does the HTML lang attribute determine a page's language in Google?
No. Google's documentation says it determines language from visible content, not from the lang attribute or URL. The attribute is still useful for accessibility and browsers.
Does hreflang have to be reciprocal?
Yes. If two pages do not link to each other, Google ignores the annotations.
Which URL structure is best for a multilingual website?
For most businesses, subdirectories on a single domain are the most practical. Country domains send a strong country signal but are more expensive and complex to manage.
Can we automatically redirect visitors to a language version based on their location?
Google advises against it, because it can stop users and search engines from reaching every version. Offer an easy-to-find language selector instead.
Sources and References
- Google Search Central: Tell Google about localized versions of your page
- Google Search Central: Managing multi-regional and multilingual sites
- ISO: ISO 639 Language codes
- ISO: ISO 3166 Country codes
- Google Search Central: Consolidate duplicate URLs (canonical)