International SEO is the practice of structuring and optimising your website so search engines serve the right language and country version to the right user. It is roughly 80% architecture and signals — URL structure, hreflang, geotargeting — and 20% translation. Get the plumbing wrong and even flawless content ranks in the wrong market or not at all.
This guide covers the full stack: when you actually need international SEO, how to choose a URL structure, how hreflang works, how to configure geotargeting, and how to localise content and build authority in each country. There is a launch checklist at the end.
What international SEO is and when you need it
International SEO helps Google and Bing understand two separate things about your pages: what language they are written in, and what country or region they target. Those are independent. A Spanish-language page can target Spain, Mexico or the US Hispanic market — three different SEO jobs.
You need international SEO when at least one of these is true:
- You sell or serve customers in more than one country.
- You publish the same language for multiple regions (English for the US, UK and India).
- You publish in multiple languages.
- Your analytics show meaningful organic traffic from countries you do not yet optimise for.
If you run a single-language site for a single country, you do not need any of this — a clean canonical setup is enough. Don't add hreflang complexity you don't have to maintain.
Choosing your URL structure: ccTLD, subdomain or subdirectory
This is the decision that shapes everything else, and it is hard to reverse. You have three options, and there is no universally correct answer — only trade-offs.
| Structure | Example | Geotargeting | Authority | Cost | Best for |
|---|---|---|---|---|---|
| ccTLD | example.de | Strongest, automatic | Split across domains | High | Big brands, high local-trust needs |
| Subdomain | de.example.com | Manual in Search Console | Partially separate | Medium | Distinct regional teams/infra |
| Subdirectory | example.com/de/ | Manual in Search Console | Consolidated on one domain | Low | Most teams, fastest to rank |
Subdirectories are the pragmatic default. They inherit your main domain's link equity, are cheapest to run, and let one site's authority lift every market. The catch: you geotarget them manually and they can feel less "local" to users than a native domain.
ccTLDs send the clearest possible country signal — Google treats example.fr as inherently French — and users trust them more in many markets. But every ccTLD is effectively a separate site that must earn its own backlinks and authority. That is expensive and slow.
Subdomains sit in between and are usually the weakest choice unless you have a genuine infrastructure reason (separate regional teams, different CMS, compliance isolation). For a deeper breakdown, see ccTLD vs subdomain and the wider guide to SEO for multiple countries.
Hreflang: telling Google which version to serve
Hreflang is an annotation that tells search engines: "this URL has an equivalent version for this language and/or region." It does not change rankings directly. What it does is prevent Google from showing your .com page to a UK user when a /uk/ page exists, and stop near-identical language variants from competing as duplicates.
The attribute uses ISO 639-1 for language and optional ISO 3166-1 alpha-2 for region: en (English, any country), en-gb (English, UK), pt-br (Portuguese, Brazil). You can specify language alone, or language plus region — never region alone.
Three rules break most hreflang setups:
- Self-reference. Every page must include an hreflang tag pointing to itself. Miss this and Google may ignore the whole cluster.
- Return tags must be reciprocal. If page A points to page B, page B must point back to page A. One-way references are invalid.
- Always add
x-default. This is the fallback for users whose language/region you don't explicitly cover — usually your global or English page.
You can place hreflang in the HTML <head>, in the HTTP header, or in an XML sitemap. Sitemaps are usually easiest to maintain at scale because you manage all annotations in one file. Full implementation detail lives in the hreflang tags guide.
A minimal hreflang example
For an English page targeting the UK, its US equivalent, and a global fallback, each page carries:
hreflang="en-gb"→ the UK URLhreflang="en-us"→ the US URLhreflang="x-default"→ the global URL
Wrong hreflang is worse than none — it actively tells Google to serve pages you didn't intend. Validate after every deploy.
Geotargeting and Search Console settings
Hreflang handles which version to serve. Geotargeting tells Google which country a whole section of your site is for.
With ccTLDs, geotargeting is automatic — .de is Germany, .in is India — and you cannot and should not override it. Generic TLDs (.com, .org, .io) and subdirectories/subdomains are geographically neutral by default, so you send the signal yourself:
- Server and CDN location carry a weak signal; a fast local response still helps users.
- Local backlinks from in-country domains are one of the strongest geographic signals you can build.
- Local business details — address, phone, currency, language — reinforce the target market.
Google retired the old manual "International Targeting" country setting in Search Console, so today geotargeting for gTLD sites is driven by hreflang, content signals and links rather than a single toggle. Verify each version as its own property so you can monitor performance per market. See the geotargeting in Google guide and the multiregional website SEO walkthrough for the operational detail.
Translation vs localisation for international content
Translation converts words. Localisation adapts the entire experience — currency, date formats, examples, imagery, tone, legal disclaimers, and crucially the keywords people actually search. Localisation is what ranks and converts.
A classic failure: translating "mobile phone" literally into a market where buyers search for "handy" (Germany) or "mobile" vs "cell phone" (UK vs US). The dictionary answer loses you the search volume.
Do this for every market:
- Have a native speaker edit or write, never raw machine output.
- Adapt prices to local currency and payment methods; a jarring currency and language selector hurts trust and conversions.
- Rewrite examples, case studies and testimonials to be locally relevant.
- Match the search intent of the local SERP, which can differ market to market.
More on this in the translating a website for SEO guide and the broader global content strategy playbook.
International keyword research across markets
Never translate your existing keyword list and call it research. Start each market from zero, because volume, phrasing and intent shift across borders even within the same language.
A repeatable process per country:
- Seed with native terms. Ask local speakers or use local autocomplete for how people actually phrase the query.
- Pull local search volume. Use country-specific data, not global averages — a keyword can be huge in one market and dead in another.
- Read the local SERP. Check what ranks: intent, content type, and which local competitors dominate.
- Prioritise by volume × commercial value ÷ difficulty for that specific country.
A term that looks weak globally may be a top opportunity in one country. Run this properly with the international keyword research guide, and track how each market's terms perform over time with DeployFlare's rank tracker so you can see rankings segmented by country rather than a blended global average.
Building authority in each target country
Here is the uncomfortable truth: hreflang and localisation get you eligible to rank, but you still need links and trust in each market to actually rank. This is where most international projects stall.
Focus on geographically relevant authority:
- Earn links from in-country domains (local
.de,.fr,.insites), which are strong geographic and trust signals. - Get listed in local directories and industry bodies relevant to that country.
- Pursue local digital PR and partnerships with regional publications.
- Build a genuine local presence — reviews, local social, community — that Google reads as market relevance.
A ccTLD strategy makes this harder because each domain builds authority from scratch; a subdirectory strategy lets in-country links strengthen your whole site. The international link building guide goes deep on tactics.
An international SEO launch checklist
Before you call a new market "launched," every row below should be green.
| Area | Do | Don't |
|---|---|---|
| Structure | Commit to one model (subdirectory as default) | Mix ccTLDs and subfolders inconsistently |
| Hreflang | Add self-reference, reciprocal return tags, x-default | Ship region-only codes or one-way tags |
| Geotargeting | Verify each version, build local links | Rely on server location alone |
| Content | Localise currency, examples, keywords | Publish raw machine translation |
| Keywords | Research native terms with local volume | Translate your existing keyword list |
| Authority | Earn in-country backlinks | Point only global links at local pages |
| Tracking | Monitor rankings per country | Judge success on blended global metrics |
Work the list top to bottom. The two most common launch failures are broken hreflang (breaking silently, so nobody notices) and thin, translated-not-localised content that never earns local links. Fix structure and signals first, then pour effort into localisation and authority — and measure every market on its own rankings, not a global blur.
International SEO rewards patience and precision. Ship the architecture correctly once, localise honestly, build local trust, and each new market compounds on the last.