What international SEO actually solves
When a business serves several countries or languages, search engines face a choice. Which version should a French-speaking searcher in Canada see? Should a buyer in Singapore see the Indian price list or the global one? International SEO answers these questions explicitly, so search engines do not have to guess.
It also prevents a quieter problem. Near-identical pages for several English-speaking markets can look like duplicates. Without clear signals, search engines may pick one version to show everywhere, and the others vanish. The core of international SEO is clarity about who each page is for.
Decide first: are you targeting languages, countries or both?
This sounds obvious and is frequently fudged. A Spanish-language site might target Spanish speakers everywhere, or specifically Spain, Mexico and the United States with different prices and regulations. The answer decides your structure, your content and your hreflang values.
Our rule: create a separate market version only where something meaningful differs. Different language, currency, pricing, legal terms, product range, delivery or contact details justify a version. A different flag on an otherwise identical page does not. Every extra version multiplies maintenance and the risk of errors.
Choosing a URL structure
There are three common ways to organise international versions, plus a fourth to avoid. Each has trade-offs in authority, cost and local signals.
| Structure | Example | Strengths | Weaknesses |
|---|---|---|---|
| Country-code domains | example.de, example.in | Strongest local signal; clear to users | Each domain builds authority separately; costly to run |
| Subfolders | example.com/de/, example.com/en-in/ | Shares one domain's authority; simplest to manage | Weaker standalone local signal; one hosting setup |
| Subdomains | de.example.com | Can host separately; flexible for organisations | Often treated more like separate sites; authority split |
| Parameters or cookies | example.com?lang=de | None for SEO | Hard to crawl and index distinct versions; avoid |
For most businesses expanding from one market, subfolders are the pragmatic default. They keep authority consolidated and are easiest to govern. Country-code domains make sense when a market is large enough to justify a separate brand presence, or where local trust in a national domain is strong.
Fig. 01 · Matrix
Tap to explore
Picking a structure
Hreflang: describing the alternates
Hreflang annotations tell search engines that a set of pages are equivalents for different languages or regions, and which is for whom. Google supports them; other search engines have historically placed more weight on signals such as the content-language meta tag, so check each engine's current documentation. Hreflang does not boost rankings. It helps the right version appear where the site already ranks.
Values use an ISO 639-1 language code, optionally followed by an ISO 3166-1 alpha-2 region code: en, en-GB, en-IN, hi-IN, es-MX. The region alone is not valid. An x-default value can name the page for users who match none of the listed versions, often a language selector or global page.
Compare scenarios
Three ways to implement hreflang
Link elements in each page's head listing every alternate, including itself.
- Simple for small sites
- Adds weight to every page
- Must be kept in sync across all versions
Alternates listed for each URL in the sitemap.
- Keeps page code clean
- Suits large sites
- Needs reliable sitemap generation
Alternates sent in response headers.
- Useful for PDFs and non-HTML files
- Rarely used for ordinary pages
- Harder to audit
Checklist
0/8Hreflang rules that are most often broken
Localisation, not translation
Machine translation has improved enormously, but a translated page is not a localised one. Searchers in different markets use different terms for the same thing, have different concerns, and expect different proof. Keyword research must be done per market, in the local language, rather than translating your home-market keywords.
- Terminology: the words people search, which may differ even between countries sharing a language.
- Commercial details: currency, prices, taxes, payment methods, delivery times and returns.
- Proof: local certifications, regulations, addresses and phone numbers that signal a real presence.
- Culture and seasons: holidays, festivals, climate and examples that make sense locally.
- Legal: privacy notices and terms that comply with local law.
Redirects and automatic switching
Automatically redirecting visitors by IP address or browser language is tempting and usually a mistake for SEO. Crawlers often come from a limited set of locations, so forced redirects can stop them seeing other versions at all. Travellers and expatriates get the wrong site with no way out.
A better pattern is to suggest rather than force: show a banner offering the likely better version, remember the user's choice, and let every version remain accessible by URL. Hreflang does the matching in search results; on-site suggestions handle everything else.
Rolling out a new market
Fig. 02 · Process
Tap to explore
Launching an international version
Set up separate reporting for each market version, for example by registering each subfolder or domain as its own property in Search Console. Watch for the wrong version appearing in a market, which is the clearest symptom of hreflang problems. If you are also selling across borders, read cross-border ecommerce.
Governance: who owns each market
International sites decay through small inconsistencies. A product is renamed in one market and not another, a page is retired in the global version but its alternates survive, a local team launches a campaign page with no hreflang at all. None of these is dramatic; together they produce versions that contradict each other.
Assign a clear owner for each market version and a central owner for the shared template, URL rules and hreflang generation. Publish a short playbook covering how new pages are created across markets, how pages are retired, and who checks that alternates still match. A monthly report of hreflang errors and wrong-market impressions gives everyone the same picture.
Also decide how content flows. Some pages should be identical in substance everywhere, with translation only; others, such as pricing, legal and case examples, should be written locally. Marking each template as global or local in advance prevents endless debate later.
When not to go international in search
International SEO multiplies work. If a market is untested, consider serving it from your main site first and watching organic demand from that country in your analytics. When demand is real and something meaningful must differ, build a version. Expanding into many markets at once with thin, translated pages is a reliable way to create a large, weak site.
There is also a middle path for markets that share a language and most of an offer: one version with clear information for international buyers, such as shipping, currency options and contact routes, rather than a full localised copy. It serves early demand without committing to a version you may not be able to maintain.
Migrating an existing site to a new international structure is a migration in every sense, with redirects and risk. Treat it with the discipline described in website migration SEO.
Key takeaways
- 01Create a separate market version only when something meaningful differs for that audience.
- 02Subfolders are the pragmatic default structure for most businesses expanding internationally.
- 03Hreflang must be complete, reciprocal, valid and point to canonical, indexable URLs.
- 04Localise keywords, commercial details and proof; translation alone is not enough.
- 05Suggest rather than force regional redirects, and keep every version crawlable.
Frequently asked
- What is hreflang?
- Hreflang is an annotation that tells search engines which pages are language or regional alternates of each other and which audience each serves. It helps search engines show the right version, such as en-IN rather than en-GB, to the right searchers. It does not raise rankings by itself.
- Should I use subfolders or country domains for international SEO?
- Subfolders suit most businesses because they keep authority on one domain and are simpler to manage. Country-code domains give the strongest local signal and suit large markets with dedicated teams. Subdomains sit between the two. Choose based on how different the markets are and your resources.
- Does duplicate content across countries cause a penalty?
- Search engines do not penalise legitimate regional versions, but near-identical pages may be grouped and only one shown. Hreflang helps them understand the versions are intended alternates. Localising prices, terms, contact details and examples also makes each version distinct and more useful.
- What is x-default in hreflang?
- x-default identifies the page to show users whose language or region does not match any listed version. It is commonly used for a language selector page or a global version. It is optional but useful for sites serving many markets with a general fallback.
- Should I redirect users based on their location?
- Forced redirects by IP or browser language can stop search engines crawling other versions and frustrate travellers. Instead, keep every version accessible, use hreflang for search results, and show a dismissible suggestion banner pointing visitors to the version that probably suits them better.
Published by Fabulous.Media, a network of specialist marketing agencies. Updated 9 October 2026. Platform features change often; check current official documentation before acting on platform-specific detail.
