Let's Talk About Multi-Language Websites (and How to Do Them Right)


Hi everyone, this is Neo. A friend recently asked me to take a look at his site — he wanted to improve its Google SEO for non-English languages. When I opened it, I noticed something right away: the site could switch languages, but every language version shared the same URL.

A lot of people new to running independent sites have this misconception — they think that if a website can switch languages, it counts as a multi-language website. In reality, this confuses two very core concepts: internationalization and localization (a true multi-language site).

Let me explain with an analogy so it really clicks:

  • Internationalization: Imagine you own a restaurant. To serve foreign tourists, you translate the menu into English, Japanese, Korean, and more — all printed in the same menu. When foreign guests arrive, you can point them to the translation.
  • A multi-language website: Imagine you didn’t just translate the menu — you opened branch locations in different countries. Your Japanese branch in Tokyo uses a menu and storefront entirely in Japanese (xxx.jp); your French restaurant in Paris uses a menu and storefront entirely in French (xxx.fr).

See the difference? The core distinction comes down to:

Feature Internationalization Multi-Language Site (Localization)
Purpose Technical implementation: making the same website capable of displaying multiple languages so visitors from different backgrounds can browse. Market strategy: giving users in specific language markets an independent, localized site experience.
URL Usually one shared URL, with text switched dynamically via cookies or JS. Each language has its own unique URL (e.g. de.xxx.com or xxx.com/de/).
Impact on Google SEO Minimal or negative. Google gets confused about which version to index — or only indexes the default language. Huge. Google clearly recognizes and indexes each language version and shows it to users in the corresponding country.
Essence A feature. A website, or a family of websites.

My friend’s site was exactly the “internationalization only” case — convenient for visitors to browse, but nearly useless for Google SEO.

Why is the URL so critical for multi-language sites?

Google is a search engine that relies heavily on URLs to recognize and index pages. If your German, Russian, and Spanish content all share the same URL as your English content, what do you think Google does?

It treats them as just different versions of the same page — and it may even get confused by the duplicate content, unsure which version to index, or it indexes only the version it considers primary (usually English).

That means all the time you spent translating your content into other languages could go completely unindexed — and naturally, you’d see zero organic search traffic from those countries.

The right approach: give every language its own unique URL.

That way, Google clearly knows that www.example.com/de/ is German content and www.example.com/ru/ is Russian content, and it can index and rank each as an independent page.

The Three Main URL Structures for Multi-Language Sites

So how should you actually structure URLs for a multi-language site? The industry standard offers three approaches, ranked here from strongest to weakest SEO impact:

1. Country-Code Top-Level Domains (ccTLD)

  • Structure: www.example.de, www.example.ru, www.example.fr
  • Pros:
    • The strongest geotargeting signal: the .de suffix itself tells Google, “Hey, this site is built specifically for German users!” This can massively boost your rankings in that country.
    • The highest authority: Google treats each ccTLD as a completely independent website, giving it the most weight.
  • Cons:
    • Costly: you need to register and maintain multiple domains.
    • Complex to run: you’re essentially operating multiple independent sites, each needing its own SEO strategy.
  • Best for: large companies with deep pockets and serious plans to develop specific country markets.

2. Sub-domains

  • Structure: de.example.com, ru.example.com, fr.example.com
  • Pros:
    • Strong geotargeting signal: Google recognizes prefixes like de. and ru. and associates them with specific countries.
    • Relatively easy setup: you only need to add DNS records under your main domain — much more convenient than ccTLDs.
  • Cons:
    • Diluted authority: Google treats sub-domains as somewhat separate sites, so the main domain’s authority may not fully pass through.
  • Best for: the go-to choice for most B2B and B2C ecommerce sellers — a great balance between cost and results.

3. Sub-directories

  • Structure: www.example.com/de/, www.example.com/ru/, www.example.com/fr/
  • Pros:
    • Consolidated authority: all language versions live under one main domain, so they inherit the main site’s authority and credibility — new language pages get indexed and rank faster.
    • Simplest setup: whether on Shopify or WordPress, you can do it easily with a plugin or app.
  • Cons:
    • Weakest geotargeting signal: of the three options, this gives Google the least obvious geographic signal.
  • Best for: brand-new independent sites, or sites that want to use the main domain’s authority to quickly get their other-language content indexed.

Summary

Structure SEO Impact Cost & Difficulty Recommendation
ccTLD ★★★★★ ★★★★★ ★★★☆☆
Sub-domain ★★★★☆ ★★★☆☆ ★★★★★
Sub-directory ★★★☆☆ ★☆☆☆☆ ★★★★☆

For the vast majority of us running independent sites, sub-domains and sub-directories are the most practical, most commonly used options.

If you want to go deep in a specific country market and have some budget to spare, sub-domains are your best bet. If your budget is tight or you want to launch into non-English markets quickly, sub-directories are a great starting point too.

Most importantly, avoid the “fake multi-language” pattern of sharing one URL across all languages. From today, check your own site — make sure every language gets a home of its own.