International SEO
International SEO is the practice of optimizing a site so that the right language and regional version surfaces in search for each user across multiple countries and languages. Its core building blocks are hreflang annotations, URL structure (ccTLD, subdirectory, or subdomain), and content localization.
- International SEO optimizes a site so that the version best suited to each user's country and language is the one that surfaces in search.
- Google determines a page's language from its visible content, so what you need is genuinely translated content, not a lang attribute or a URL signal.
- hreflang annotations declare which language and region each page targets, and bidirectional links in which every version points back to all the others are mandatory.
- URL structure is a choice among ccTLD (example.de), subdirectory (example.com/de/), and subdomain (de.example.com), weighed against operational cost and geotargeting signal strength.
- Industry analyses find that a large share of hreflang implementations contain errors, and a single error within a cluster can cause the whole thing to be ignored.
Overview
International SEO is the practice of optimizing a site so that users across different countries and languages each see the version meant for them in search results. Google distinguishes sites along two axes. One is the multilingual site, which serves multiple languages; the other is the multi-regional site, which targets a specific country or region. A site built for Canada that offers both French and English versions, for example, is both at once.
Three things are essential. First, each language version should live at its own URL. Rather than swapping languages at the same URL via cookies or browser settings, Google recommends a unique URL per language. Second, hreflang annotations should declare the language and region each page targets. Third, you need localization that goes beyond plain translation to match currency, addresses, and local idiom. This matters because Google judges a page's language from its visible content and does not rely on code-level signals such as the lang attribute or the URL.
URL Structure Comparison
Google lays out three broad URL structures for organizing region-specific sites. They differ in the strength of their geotargeting signal and in operational cost.
| Structure | Example | Pros | Cons |
|---|---|---|---|
| Country-code domain (ccTLD) | example.de | Strongest geotargeting signal; server location irrelevant | High operational cost and infrastructure burden; domain authority must be built from scratch |
| Subdomain (gTLD) | de.example.com | Easy to set up; server location can be separated | Geotargeting is not clear from the URL alone; tends to behave like a separate site in practice |
| Subdirectory (gTLD) | example.com/de/ | Easy to set up and low maintenance (same host); consolidates domain authority in one place | Single server location; weak regional intent signal from the URL alone |
| URL parameter | example.com?loc=de | - | Not recommended by Google |
A ccTLD sends both users and search engines a strong signal that a site targets a given country, but authority has to be rebuilt for each domain. A subdirectory consolidates domain authority into a single asset and keeps operations simple, which generally makes it the preferred choice when entering a new market, absent technical constraints.
hreflang Code Example
hreflang annotations tell Google which language and regional variants of the same content exist. There are three ways to implement them — HTML link tags, HTTP headers, and sitemaps — and from Google's standpoint all three are equivalent. Language codes follow ISO 639-1, and region codes optionally follow the ISO 3166-1 Alpha 2 format.
<link rel="alternate" hreflang="en-gb" href="https://en-gb.example.com/page.html" />
<link rel="alternate" hreflang="en-us" href="https://en-us.example.com/page.html" />
<link rel="alternate" hreflang="de" href="https://de.example.com/page.html" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com/" />Here x-default is a reserved value that designates the fallback version to show when no language or region matches the user's browser settings. The most important rule is the bidirectional link: if two pages do not point to each other, the tag is ignored. Each language version must reference every version, including itself.
Rationale
Google Search Central states that when you use different URLs per language, hreflang annotations should be used to connect the correct language version to search results. Google also explains that it does not detect regional variants by varying the crawler's location and does not use geolocation meta tags, so a site must declare its variants explicitly.
Implementation difficulty is not to be underestimated either. According to industry analyses such as Ahrefs, a large share of hreflang implementations contain errors like missing return tags, broken URLs, and incorrect ISO codes. Because a single error anywhere in an hreflang cluster can lead Google to ignore the entire cluster, the whole implementation effort risks being nullified.
Implementation Checklist
- Define the site's nature first — multilingual, multi-regional, or both.
- Serve each language and regional version at its own URL, and do not rely on automatic switching based on cookies or browser settings.
- Choose among ccTLD, subdirectory, and subdomain by weighing operational cost against geotargeting signal.
- Apply hreflang consistently through one method: HTML tags, HTTP headers, or sitemaps.
- Verify that every variant has bidirectional links pointing to one another, including to itself.
- Designate an
x-defaultversion for users whose language matches none of the available options. - Confirm that language and region codes conform to the ISO 639-1 and ISO 3166-1 Alpha 2 formats.
- Localize beyond plain translation — down to currency, addresses, and local expressions — so that the visible content is genuinely in the target language.