International SEO: How to Expand Your Organic Reach Globally

International SEO is the practice of optimising your website to rank in multiple countries and/or languages. Done well, it expands your organic reach into new markets without cannibalising existing rankings. Done poorly, it creates duplicate content issues, confuses search engines, and dilutes domain authority.

This guide covers the key decisions and implementation requirements for international SEO.

The Core Decisions

Before implementing anything, three decisions shape your entire international SEO approach.

Decision 1: Which countries and languages to target?

Not all international markets are worth targeting simultaneously. Start by identifying where you already have customers, where demand signals exist (referral traffic from foreign IPs, brand mentions in target markets, sales team intelligence), and where organic search volume justifies investment.

Language targeting and country targeting are separate questions:

• Language targeting — serving Spanish content to Spanish speakers globally
• Country targeting — serving content specifically for searchers in Mexico vs Spain vs Argentina

Decision 2: URL structure

This is the most consequential technical decision in international SEO. The three main options:

Country-code top-level domains (ccTLDs) — example.de, example.fr, example.co.uk

• Strongest geotargeting signal to Google
• Each domain builds authority separately (no shared equity)
• Highest operational overhead (separate hosting, separate Search Console properties)
• Best for well-resourced businesses with strong local market commitment

Subdomain structure — de.example.com, fr.example.com, uk.example.com

• Moderate geotargeting signal (can be geo-targeted in Search Console)
• Partial authority sharing with root domain
• Lower operational overhead than ccTLDs

Subdirectory structure — example.com/de/, example.com/fr/, example.com/uk/

• Shares root domain authority directly
• Easier to maintain (single CMS, single hosting)
• Geotargeting via hreflang and Search Console property settings
• Recommended for most businesses — best balance of authority sharing and operational simplicity

Decision 3: Full localisation vs translation

Translation is converting text from one language to another. Localisation is adapting content for a specific culture, market, and user expectation.

For competitive international markets, translation-only content consistently underperforms properly localised content. Local idioms, examples, case studies, pricing (in local currency), local contact information, and references to local market context all improve performance.

Hreflang: The Technical Foundation

Hreflang is an HTML attribute that tells Google which version of a page to serve to users based on their language and/or country. Implementing it correctly is the most technically demanding part of international SEO.

Hreflang syntax

<link rel="alternate" hreflang="en-gb" href="https://example.com/en-gb/page/" />
<link rel="alternate" hreflang="en-us" href="https://example.com/en-us/page/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page/" />

The x-default tag designates the fallback URL — the version served when no other hreflang tag matches the user's language/country combination.

The bidirectionality requirement

This is the most common hreflang mistake: every page in an hreflang cluster must reference every other page in the cluster. If your UK page references your US page, your US page must reference your UK page. Missing reciprocal references break hreflang and cause Google to ignore the implementation.

For sites with many pages and multiple languages, hreflang management is best handled programmatically — with a script or CMS template that generates all required tags automatically.

Hreflang language codes

Use the correct ISO 639-1 language codes and ISO 3166-1 alpha-2 country codes. Common examples:

• en-gb — English, United Kingdom
• en-us — English, United States
• en-au — English, Australia
• de-de — German, Germany
• de-at — German, Austria
• fr-fr — French, France
• es-es — Spanish, Spain
• es-mx — Spanish, Mexico

Language-only tags (de, fr, es) target all speakers of that language regardless of country. Country + language tags are more precise.

Content Localisation

Keyword research per market

Search behaviour varies by market even within the same language. UK users search for "estate agents"; US users search for "real estate agents". UK users search "trainers"; US users search "sneakers". Each market needs its own keyword research, not a direct translation of UK/US keywords.

Use local search volume data (Ahrefs or Semrush allow market-specific keyword research) and supplement with local team or customer input.

Local content signals

Content that performs well in a target market includes:

• Local case studies and testimonials
• References to local regulations, standards, or practices
• Local pricing in local currency
• Local contact details and support options
• Content about locally relevant events, news, or contexts

Pure machine translation with no localisation is increasingly detected and penalised by both Google and AI search platforms.

Content creation vs translation workflow

For scalable international content production:

1. Create content in the primary language with localisation in mind (avoiding idioms that don't translate well)
2. Professional translation by native speakers in the target market
3. Local review for market-specific accuracy and naturalness
4. SEO review to verify keyword targeting is correct for the local market

Technical Considerations

Search Console configuration

Set up separate Search Console properties for each subdomain or ccTLD. For subdirectory structures, use the International Targeting settings in the existing property to assign country targeting. Set the geographic target for each subdirectory in Search Console's "International targeting" settings.

Canonical tags across languages

Content on different language versions of the same page should NOT cross-canonical to the English version. Each language version should have a self-referencing canonical. Hreflang establishes the relationship between language versions.

Avoid auto-redirecting users based on IP

Automatically redirecting users to a different language version based on IP geolocation blocks Googlebot (which crawls from US IPs) from accessing non-English versions. Instead, use an interstitial banner to suggest the local version without forcing a redirect.

Core Web Vitals by market

If you serve international markets from CDN nodes in specific regions, Core Web Vitals performance may vary by country. Test performance from representative locations in target markets using tools that allow geolocation selection.

International Link Building

Domain authority doesn't transfer cleanly across language versions or ccTLDs. Each version of your site benefits from its own local link building:

• Press coverage in local publications
• Local industry directory listings
• Links from local business associations and chambers of commerce
• Co-marketing with local partners

For ccTLD structures, this link building effort is entirely siloed per domain. For subdirectory structures, local links to subdirectory pages still benefit from the shared root domain authority.

International SEO and AI Search

AI search platforms index international content but with varying effectiveness by market. For international GEO:

• Ensure AI crawlers (OAI-SearchBot, PerplexityBot) are allowed for all language versions
• Implement Article schema with inLanguage property for each language version
• Consider an international llms.txt that references your key pages across languages

Local AI tools and regional variants of major platforms (e.g., Baidu's AI search in China, Yandex in Russia) have their own requirements that differ from global platforms.

FAQs

Should I use one website or separate websites for different countries? For most businesses, a subdirectory structure on a single domain is the best starting point — it concentrates authority and simplifies operations. ccTLDs are justified for businesses with very strong local market commitments and the resources to build authority on each domain independently.

Do I need a separate website for the UK now that Brexit has happened? No, UK SEO doesn't require a separate domain. A subdirectory (yoursite.com/uk/) with correct hreflang and Search Console geotargeting performs well for UK-specific content.

How do I know if my hreflang is working correctly? Use Ahrefs' site audit or Screaming Frog's hreflang validation to check for missing reciprocal links, incorrect language codes, and broken URLs. Google Search Console's International Targeting report also shows detected hreflang tags and any errors.

Can machine translation be used for international SEO? Modern machine translation (Google Translate, DeepL) has improved significantly but still underperforms human translation + local review for competitive markets. Using machine translation as a first draft with professional editing is a reasonable cost-quality compromise. Pure machine translation without human review consistently underperforms.

For a comprehensive international SEO strategy that covers URL structure decisions, hreflang implementation, and localised content creation, get in touch or start with a free audit.