If your business sells in more than one country or serves people who speak different languages, having a translated website isn’t enough. Google needs clear signals to understand which version of the site to show each user. That’s what international SEO is about: it combines technical, architecture and content decisions to rank well in several markets.

In this article we explain how to structure a multilingual site, what hreflang is and how to implement it properly, which URL structure to choose and why translation alone doesn’t guarantee results.

What is international SEO?

It’s the set of techniques that help a site rank in several countries or languages, adapting to how people search in each market. It takes into account:

  • The language and its variants. British English is not the same as American or Australian English.
  • The country. Searches, competitors, currency and even what you can sell all change.
  • Site architecture. Domains, subdomains or subfolders.
  • hreflang annotations, which tell Google which version belongs to each user.
  • The experience in each market. Prices, formats, payment methods and references.

One common misunderstanding is worth clearing up: a page translated into another language is not duplicate content for Google, and there’s no “penalty” for having your site in several languages. The real problem is different: without a clear structure, Google may show the wrong version, for example the English page to someone searching in Spanish, or one country’s prices to a user in another. Where there is real similarity is between versions in the same language for different countries: there Google may group them together and pick just one to show.

hreflang: the key signal for multilingual sites

hreflang is an annotation that tells Google how the different versions of the same page relate to each other, by language and, optionally, by country. It can be declared in the HTML, in HTTP headers or in the sitemap.

What is it for?

  • It shows the right version. Someone searching from the UK sees the UK version, not the US or the Australian one.
  • It sorts out similar versions. If you have the same page in English for three countries, hreflang explains to Google that they’re alternatives for different audiences, not copies.
  • It keeps your versions from competing with each other in the same results.

What it doesn’t do: it doesn’t improve rankings on its own. It’s a signal, not a directive, and Google combines it with others.

Basic syntax

<link rel="alternate" hreflang="en" href="https://example.com/" />
<link rel="alternate" hreflang="es" href="https://example.com/es/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

The x-default value indicates which version to show when none of the others match the user’s language or region. It usually points to the main version or to a page with a language selector.

Most common codes

Code Language / region
en English (no country)
en-US English for the United States
en-GB English for the United Kingdom
es Spanish (no country)
es-ES Spanish for Spain
es-MX Spanish for Mexico
es-AR Spanish for Argentina
pt-BR Portuguese for Brazil

The language code always comes first and the country code is optional. Two classic mistakes: using en-UK (the United Kingdom’s code is GB) and putting only a country, with no language. There’s also no region code for “Latin America” among the ones Google documents: if you want a single version for all Spanish-speaking countries, es is enough.

Where to implement it

There are three valid methods, and it’s best to pick just one:

  1. In the <head> of each page, with <link> tags.
  2. In HTTP headers, useful for non-HTML files such as PDFs.
  3. In the XML sitemap, practical on large sites or when you can’t touch the page code.

The three rules that get broken most

  • Reciprocity. If the English page points to the Spanish version, the Spanish version has to point back to the English one. If the return link is missing, Google may ignore that annotation.
  • Self-reference. Each page has to include itself in the list, as well as its alternatives.
  • Valid URLs. They all have to respond correctly, be indexable and be the canonical version. An hreflang that points to a redirect, a 404 error or a page with noindex is useless.

URL structures for multilingual sites

The structure you choose affects rankings, cost and maintenance. These are the three usual options.

1. Subfolders

Example: example.com/en/, example.com/es/, example.com/fr/

Advantages

  • Everything lives on one domain, which builds a single reputation.
  • It’s the easiest option to manage and maintain.
  • It lets you start without a large investment.

Disadvantages

  • The geographic signal is less explicit: country targeting depends on hreflang and on the content.

It’s the structure we use on this very site: Spanish at the root and English under /en/, with reciprocal hreflang on every page and in the sitemap.

2. Subdomains

Example: en.example.com, es.example.com, fr.example.com

Advantages

  • Clearly separates each language or region.
  • Lets you host each version on different infrastructure if needed.

Disadvantages

  • Each subdomain tends to work like a separate site, with its own configuration and its own ranking effort.
  • More technical and maintenance complexity.

3. Country domains (ccTLDs)

Example: example.es, example.mx, example.fr

Advantages

  • It’s the strongest geographic signal: the domain is tied to the country.
  • It usually builds more trust with local users.

Disadvantages

  • Higher cost: you have to register and maintain several domains.
  • Each domain’s reputation is built separately.
  • Some countries require legal conditions or a local presence to register the domain.

Which one should you choose?

It depends on your budget, your team and your goal. For most companies starting out with international SEO, subfolders are the most efficient option. Country domains make sense when you have real operations in each market and the resources to sustain several sites. If you’re still deciding on the domain, see how to choose a web domain.

Technology matters too: not every platform handles languages the same way. We look at it in our WordPress vs Astro comparison.

Translation vs. localisation: they’re not the same

  • Translating is moving a text from one language to another while keeping the meaning.
  • Localising is adapting the content to the cultural, linguistic and search context of the market you’re targeting.

An example

Say you sell sports footwear. In the United States people search for “sneakers”, in the United Kingdom for “trainers”, and in Spanish the same product is “zapatillas” in Argentina and Spain but “tenis” in Mexico. Same product, different searches. One text for every country leaves traffic on the table in most of them.

Localisation best practices

  • Research keywords in each market. Don’t assume they work the same in every country that shares a language. The method is in how to choose keywords.
  • Adapt currency, date formats, measurements and cultural references.
  • Work with someone who knows the target market, not just a machine translator.
  • Review anything you generate with AI. It tends to drift towards a neutral variant of the language, or the dominant one.
  • Localise the metadata too: title, meta description, image alt text and, where possible, the URL.

Common international SEO mistakes

1. Publishing unreviewed machine translation

The result is unnatural text, with context errors and poorly adapted keywords. That content offers little to the user and is unlikely to rank. If it’s also published in bulk, Google may consider it scaled content with no value.

2. Not implementing hreflang, or getting it wrong

The typical errors are missing reciprocity, invalid codes and URLs that redirect or return an error. Google ignores annotations it can’t validate, so the effort is lost on exactly the pages that fail.

3. Mixing languages on the same URL

A page with Spanish and English content on the same URL confuses both Google and people. Each language needs its own URL.

4. Redirecting by IP or browser language

Automatic redirection is bad practice. Googlebot crawls mostly from the United States and doesn’t send a language preference, so it may never get to see the other versions. It’s annoying for users too: someone travelling, or who prefers another language, gets stuck on a version they didn’t choose. It’s better to show a visible language selector, or at most suggest the other version with a notice, and let hreflang take care of the search results.

5. Neglecting the technical foundation

Without a good URL structure, a correct sitemap and clean hreflang, content work delivers less. If you need to strengthen that foundation, see what technical SEO is.

How to audit your multilingual site

If your site is already in several languages, it’s worth reviewing it from time to time. These are the key points:

  • hreflang validation. Run the site through an SEO crawler or an hreflang validator to detect missing return links, invalid codes and URLs with errors.
  • Performance by country. In Search Console, filter the performance report by country and by language folder to see which version appears in each market. The old International Targeting report no longer exists.
  • Canonicals. Each version needs its own canonical URL. If the English version declares the Spanish one as canonical, Google won’t show it.
  • Local keywords. Check whether the queries you appear for in each market are the ones people in that country really use.
  • Speed. If your users are far from the server, a CDN helps the site load fast in every market.

If you’d rather have someone external review it, in what an SEO audit reviews we explain what it includes and what you should receive.

A multilingual site stands on three things: properly implemented hreflang, a coherent URL structure and content that is truly localised. If one fails, the other two deliver less.

If you’re thinking about launching or improving a site in several languages, take a look at our SEO, GEO & AI and web development services, and get in touch.