Websites November 20, 2026 · 6 min read

Bilingual Website SEO With Hreflang, URLs and Localised Content

A bilingual site is two sites that share a domain. Search engines only treat them that way if your URLs, hreflang, canonicals and content tell the same story.

Bilingual Website SEO With Hreflang, URLs and Localised Content
Photo: Unsplash

Key takeaways

  • Give every language its own crawlable URL, ideally a subfolder such as /id/, and never serve two languages from one URL based on cookies or browser settings.
  • Hreflang must be reciprocal and self-referencing on every page, with an x-default pointing to the version for users who match neither language.
  • Each language version should have a self-referencing canonical, because canonicalising the Indonesian page to the English one tells Google to drop it.
  • Localised content that matches how each market searches ranks better than a literal translation of the same keywords.

Bilingual website SEO comes down to one principle: each language needs its own URL, and every technical signal on that URL must point to the same answer about which language and market it serves. In practice that means a clean URL structure (we prefer an /id/ subfolder for Indonesian), reciprocal hreflang tags including x-default, self-referencing canonicals, and content that is localised rather than translated word for word.

Most bilingual sites we audit get one or two of these right and break the rest. Below is the setup we use, and the mistakes we fix most often.

What URL structure works best for a bilingual website?

Search engines index URLs, not languages. If your English and Indonesian content live on the same URL and switch based on a cookie, browser language or IP address, Googlebot will usually see only one version, and the other never ranks.

You have three workable options:

Structure Example Good for Trade-off
Subfolder example.com/id/ Most companies, one CMS, shared authority Needs a CMS that handles language folders cleanly
Subdomain id.example.com Separate teams or platforms per language Authority builds more slowly, more setup
Country domain example.co.id Separate legal entity or business per market Most expensive to build and maintain

For nearly every client we recommend the subfolder. The English site sits at the root, the Indonesian site sits under /id/, and both mirror each other page for page: /services/ and /id/services/, /blog/post/ and /id/blog/post-in-indonesian/. Translated slugs are fine and often better, because the Indonesian URL then carries Indonesian keywords.

Two rules to keep:

  • Do not auto-redirect by IP or browser language. Suggest a language with a banner if you like, but let users and crawlers reach every version directly.
  • Keep the mirror complete. If a page exists only in English, do not link to a missing /id/ equivalent and do not add hreflang for it.

How do you set up hreflang with x-default correctly?

Hreflang tells Google which language and region each URL targets, and which pages are alternates of each other. For an English and Indonesian site, each page carries a set like this in the head:

“Two languages on one domain only work when every signal agrees.”
FOXA Digital
<link rel="alternate" hreflang="en" href="https://example.com/services/" />
<link rel="alternate" hreflang="id" href="https://example.com/id/layanan/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/services/" />

The same three lines appear on both the English and the Indonesian page. That is what makes it work:

  1. Self-referencing. Every page lists itself.
  2. Reciprocal. If the English page points to the Indonesian one, the Indonesian page must point back. One-way hreflang is ignored.
  3. Correct codes. Language uses ISO 639-1 codes, so Indonesian is "id", not "in" or "ind". Add a region only when you really target one, for example "en-AU" for an Australian price list.
  4. Absolute URLs that return a 200 status, are indexable and are the canonical version.
  5. x-default for everyone else. Visitors searching in Japanese or German should land somewhere sensible, usually the English site.

You can place hreflang in the HTML head, in HTTP headers (useful for PDFs) or in the XML sitemap. Pick one method and use it consistently; mixing methods is where conflicting signals creep in.

Translated or localised content, which one ranks?

A translation reproduces the English page in Indonesian. A localised page answers what an Indonesian searcher actually types and expects. The difference shows up in rankings.

Element Translated Localised
Keywords Literal translation of English terms Terms Indonesians search, often a mix of Indonesian and English
Examples and proof Same as English Local brands, local cities, local payment and delivery norms
Tone Formal, stiff Natural "Anda" or casual, matching the brand
Contact options Email form WhatsApp first, because that is how many Indonesian buyers reach out
Meta title and description Translated Rewritten for the local SERP

Indonesians often search with English marketing and tech terms mixed in, "jasa SEO", "landing page", "harga paket". Keyword research has to be done separately in each language. Do not assume the Indonesian volume sits on the translated phrase.

Canonicals, sitemaps and the language switcher

These three are where we find the most damage on otherwise decent sites.

Canonical tags. Each language version gets a self-referencing canonical. A common CMS default canonicalises /id/ pages to the English page, which tells Google the Indonesian version is a duplicate to drop. Then hreflang and canonical contradict each other and the Indonesian pages disappear from the index.

XML sitemaps. Include every indexable URL in both languages. If you choose sitemap-based hreflang, each URL entry lists its alternates with xhtml:link elements. Submit the sitemap in Search Console and check the indexed count per folder; a big gap between submitted and indexed /id/ pages is an early warning.

Language switcher. The switcher should link to the equivalent page, not the other language's homepage. A reader on /services/ who switches should land on /id/layanan/. Use plain crawlable links, label languages in their own language ("English", "Bahasa Indonesia") rather than flags, and keep the switcher in the same spot on every template.

Quick checklist:

  • [ ] Every page has its own URL per language
  • [ ] Hreflang is self-referencing, reciprocal and includes x-default
  • [ ] Canonicals point to the same language version
  • [ ] Both languages are in the sitemap and indexed
  • [ ] Switcher links page to page
  • [ ] The html lang attribute matches the page language
  • [ ] Internal links stay inside the same language

How FOXA builds bilingual websites

We plan the site map in both languages before design starts, so every English page has a mapped Indonesian twin with its own slug, title and keyword target. Hreflang, canonicals and sitemaps are generated from that map, not typed by hand, which keeps them in sync when pages are added. Then we write the Indonesian copy as a native piece, not a translation pass.

For Balimoon, a Bali liqueurs and spirits brand, we built an 18-page bilingual website and pair it with 20 SEO articles a month. The site earned 1.79M organic impressions in 2025. Structure was not the only reason, but without it the second language would have been invisible.

If you are building content on top of the structure, read our guide to an SEO content strategy that compounds and run the technical SEO checklist for company websites after launch. Clean bilingual pages also help AI assistants pick the right language version, which we cover in how to get your brand cited in AI search.

Launching or fixing a second language

Check your current site against the checklist above, starting with canonicals and hreflang return links, because those two cause the most silent losses. If you want us to audit or build your bilingual site, book a call and we will map out what needs to change.

Questions we get asked

Should I use a subfolder, subdomain or separate domain for a second language?

For most companies a subfolder such as example.com/id/ is the simplest choice. It shares the authority of the main domain, is easy to maintain on one CMS and is easy to configure in Search Console. Subdomains and country domains work too, but they take more effort to build authority and are usually only worth it when each market runs as a separate business.

What is x-default in hreflang?

The x-default value tells search engines which URL to show users whose language or region does not match any of your listed versions. On a bilingual English and Indonesian site it usually points to the English version or to a language selection page. It is optional, but we add it on every set because it removes guesswork for visitors from other markets.

Does Google translate my website automatically, so I do not need a second language?

Google can show machine-translated versions of some results, but you do not control that translation and it is no substitute for pages written in the language. If you want to appear for Indonesian searches, you need real Indonesian pages with their own URLs, titles and content written for how Indonesians search.

Can duplicate content penalties hit a translated website?

Translated pages are not treated as duplicate content, because the text is in a different language. Problems start when two versions in the same language compete, for example en and en-SG pages that are almost identical without hreflang. Correct hreflang and self-referencing canonicals let Google show the right version instead of picking one at random.

About FOXA DigitalFOXA Digital is a performance marketing agency in Jakarta, Indonesia. Since 2018 we have run paid media, tracking, SEO and content for apps, consumer brands, hospitality and attractions, judged on CAC, ROAS and leads.

Want us to look at your numbers?

30 minutes. No deck. You leave with three things to fix this week.

Book a strategy call