Key takeaways
- International SEO means giving each market its own crawlable URL, telling Google how those versions relate, and building relevance in each country separately.
- Subfolders on one domain are the easiest structure for most companies; ccTLDs give the strongest local signal but cost the most to run.
- Hreflang only works when every version lists itself and all the others, with fully qualified URLs and valid ISO codes.
- Translation is not localisation. Each market needs its own keyword research, pricing, examples and links.
What international SEO actually involves
International SEO is the work of making the right version of your site rank in the right country or language. It covers three things: a URL structure that separates markets, technical signals such as hreflang that connect the versions, and content and links that make each version relevant locally.
Most problems I see come from treating a new market as a copy-and-paste job. A company launches a German or French version, translates the pages, and expects rankings to follow. Google then shows the English page to German users, or treats the new pages as thin duplicates, and the launch stalls.
Before any technical decision, answer two questions. Are you targeting languages, countries, or both? And do you have the budget to maintain separate content for each market for years, not months? The answers decide almost everything that follows.
Language targeting vs country targeting
Language targeting means one version per language, for example English, German and Spanish, regardless of where the reader lives. Country targeting means separate versions for markets that may share a language, such as the US, UK and Australia, usually because prices, currency, shipping or legal terms differ.
If your offer is the same everywhere, language targeting is simpler. If you sell physical products, quote in local currency or have country-specific regulation, you need country targeting for at least some markets.
Choosing a URL structure
The best URL structure for most businesses is subfolders on a single generic domain, such as example.com/de/ and example.com/fr/. It keeps all authority on one domain, is cheap to run, and is easy to track. Google's own documentation describes the main options and their trade-offs, and none of them is required to rank.
| Structure | Example | Pros | Cons |
|---|---|---|---|
| Country-code domain (ccTLD) | example.de | Clearest country signal, high local trust | Each domain builds authority from scratch, higher cost, more admin |
| Subdomain | de.example.com | Easy to host separately | In my experience shares authority with the main domain less reliably than a subfolder |
| Subfolder | example.com/de/ | Shares domain authority, one setup to maintain | Weaker local signal than a ccTLD, a single server location for all markets |
| URL parameter | example.com/?lang=de | Quick to build | Not recommended by Google, hard to segment and easy to break |
In my experience, ccTLDs make sense when you have a local team, a local brand presence and a budget to earn links in each country. For everyone else, subfolders win. Whatever you choose, avoid serving different languages on the same URL based on cookies or browser settings, because Googlebot will usually see only one version.
Avoid forced redirects by location
Automatically redirecting visitors based on IP address causes problems. Googlebot crawls mostly from US IP addresses, so it may never reach your other versions. Show a suggestion banner ("Looks like you're in Germany – switch to the German site?") instead, and let users and crawlers reach every version directly.
How hreflang works
Hreflang is an annotation that tells Google which URLs are language or regional versions of the same page, so it can show searchers the right one. It does not boost rankings on its own. It helps Google swap in the correct version where your site already ranks.
You can add hreflang in one of three ways, which Google treats as equivalent:
- HTML link elements in the
<head>of each page. - HTTP Link headers, useful for non-HTML files such as PDFs.
- XML sitemap entries, often easiest for large sites because nothing changes in page templates.
Pick one method. Using all three adds no benefit and makes mistakes more likely, because the annotations can drift out of sync.
The rules that matter
- Every version lists every version, including itself. The set of annotations should be identical on each page in the group.
- Return links are required. If page A points to page B but B does not point back to A, Google may ignore the annotation.
- Use fully qualified URLs including
https://. Relative URLs are not valid. - Use valid codes. Language comes from ISO 639-1 (for example
de), and the optional region from ISO 3166-1 Alpha 2 (for examplede-AT). A region on its own is not allowed, soatdoes not mean Austria. - Watch the classic mistake with the UK. The correct code is
en-GB, noten-UK. - Point to canonical, indexable URLs. Hreflang pointing at redirected, noindexed or canonicalised pages sends conflicting signals.
What x-default does
The x-default value tells Google which page to show when a searcher's language or region matches none of your versions. It is meant for a language selector page or a home page that picks a version automatically, but many sites simply point it at their main English version. A small example for a page available in US English, UK English and German:
<link rel="alternate" hreflang="en-US" href="https://example.com/us/pricing/" /><link rel="alternate" hreflang="en-GB" href="https://example.com/uk/pricing/" /><link rel="alternate" hreflang="de" href="https://example.com/de/preise/" /><link rel="alternate" hreflang="x-default" href="https://example.com/us/pricing/" />
The same four lines go on all three pages. If you are setting this up on a large site, it belongs in your technical SEO checklist and should be tested before launch, not after.
Common hreflang errors and how to find them
The most common hreflang errors are missing return links, wrong codes and annotations pointing at non-canonical URLs. They are easy to make and hard to spot by eye, because nothing looks broken to a human visitor.
- Missing return links, usually because one market added a page and the others were never updated.
- Invalid codes such as
en-UK,es-LAor a country code used alone. - Canonical conflicts, where the German page has a canonical pointing to the English page. That tells Google the German page is a duplicate, and hreflang cannot fix that.
- Hreflang on untranslated pages, where the "German" version is still in English.
- Different sets on different pages, often caused by a CMS plugin that only knows about some markets.
To find them, crawl the whole site with a tool that reports hreflang (Screaming Frog, Sitebulb or similar) and check reciprocity and status codes for every annotated URL. Then look at Search Console performance by country to see whether the right versions get impressions in each market. This is a standard part of any SEO audit for a multi-market site.
Translation vs localisation
Translation turns your words into another language; localisation makes the page fit how people in that market search and buy. Google can rank a well-translated page, but a localised page is the one that converts and earns links.
Start with separate keyword research for each market. People in different countries use different terms for the same product, and a direct translation of your English keyword is often not what they type. The same method from our keyword research guide applies, just run it with native speakers and local data.
Then localise what surrounds the keywords:
- Currency, prices, units, date formats and phone numbers.
- Shipping, returns, payment methods and legal information that apply in that country.
- Examples, case references and screenshots that make sense locally.
- Titles and meta descriptions written for the local query, not translated from English.
Machine translation is fine as a first draft. In my experience it should always be edited by a native speaker who knows the industry, because small errors in terminology make a page look untrustworthy very quickly.
Building local authority and links
A new language version starts with almost no relevance signals in its market, even on a strong domain. To rank, it needs local links, local mentions and, where relevant, a local business presence.
- Local links from industry media, associations, partners and directories in that country. A link from a respected German trade site does more for your German pages than another link from a US blog.
- Digital PR with local angles, such as data about that market or commentary on local regulation.
- Google Business Profile if you have a physical office in the country.
- Internal links from strong pages to each market's key pages, plus a clear language switcher linking equivalent pages, not just home pages.
The principles are the same as in our link building guide. The difference is that you run the work separately for each market and accept that each one takes time.
Where to start
Start by choosing your markets and your structure, then get hreflang right before you scale content. A clean setup for two markets is worth more than a broken one for ten.
- Decide on language or country targeting for each market.
- Pick a URL structure, usually subfolders, and keep it consistent.
- Implement hreflang with one method, including self-references, return links and x-default.
- Run local keyword research and localise your most important pages first.
- Build local links and track performance by country in Search Console.
If you are planning an expansion or your current setup shows the wrong pages in the wrong countries, our international SEO service covers the audit, hreflang implementation and market-by-market content plan.
Frequently asked questions
Does hreflang improve rankings?
Not directly. Hreflang helps Google show the right language or regional version of a page where your site already ranks, which usually improves click-through and conversions in each market.
Is en-UK a valid hreflang code?
No. The ISO 3166-1 code for the United Kingdom is GB, so the correct value is en-GB.
Do I need x-default?
It is optional but recommended. It tells Google which page to show to searchers whose language or region does not match any of your listed versions.
Should I use subfolders or country domains?
For most companies subfolders on one domain are easier and keep authority in one place. Country domains make sense when you have local teams and budget to build each site separately.