International SEO

Core Concept

International SEO optimizes sites for users in different countries and languages. It requires correct implementation of URL structure, hreflang tags, localization, and market-specific technical configurations.

This lesson covers the ten international SEO areas (leaves 7.3.1–7.3.10): country and language targeting, hreflang implementation, international URL structure, localization and transcreation, international keyword research, international technical SEO, regional SERP analysis, international link building, market-level reporting, and localized UX and conversion signals.

Learning Focus

After this lesson you can implement hreflang tags, choose international URL structures, localize content per market, and run per-country keyword research to reach audiences across multiple languages and regions.

Country and Language Targeting

Choose the targeting strategy for each market.

Targeting configuration options:

Configuration	URL Example	Best For	Strengths	Weaknesses
ccTLD (country code TLD)	example.fr, example.de	Large markets with local teams	Strongest geotargeting signal	Expensive, harder to manage
Subdomain with gTLD	fr.example.com, de.example.com	Mid-sized markets	Easy to set up	Weaker geotargeting signal
Subfolder with gTLD	example.com/fr/, example.com/de/	Mid-sized markets	Easy to manage, consolidated authority	Single country site structure needed
URL parameters	example.com?lang=fr	Not recommended	Weakest targeting, can cause duplicates

Hreflang Implementation

Hreflang tags tell Google which language/regional version of a page to show in each market.

Hreflang syntax:

hreflang-tags.html

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

Hreflang rules:

Rule	Implementation
Bidirectional	Each page in the set must link to all other versions
Self-referencing	Each page must include its own hreflang tag
x-default	Use x-default for the fallback page (usually English)
Language-region format	en-us, en-gb, fr-ca, fr-fr
Consistent URL structure	All versions use the same URL structure pattern
Validate	Use GSC URL Inspection on international pages to verify hreflang annotations

International URL Structure

Choose a URL structure that supports your targeting strategy.

URL structure by approach:

Approach	URL Example	SEO Impact
Subfolder	example.com/fr/blog/	Strong — country targeting via GSC, consolidated authority
Subdomain	fr.example.com/blog/	Good — separate subdomain, still on same root domain
ccTLD	example.fr/blog/	Strongest geotargeting but considered separate domain
Language parameter	example.com?lang=fr	Weak — avoid

Localization and Transcreation

Localization goes beyond translation to adapt content for cultural relevance.

Localization depth:

Level	Description	Effort	SEO Value
Machine translation	Google Translate or similar	Low	Low — poor quality
Human translation	Professional translator	Medium	Medium
Localization	Translated + culturally adapted	Medium-High	High
Transcreation	Recreated for local market	High	Highest

Localization requirements for SEO:

Element	Must Be Localized
Meta tags (title, description)	Yes — never leave in original language
Headings	Yes
Body content	Yes
URL slugs	Yes (for subfolder approach)
Schema markup	Yes — use local language
Images	Localize where relevant (currency, cultural references)
Reviews	Local language reviews

International Keyword Research

Keywords must be researched per market, not translated from the primary market.

Per-market keyword research:

Method	Implementation
Local keyword tools	Use country-specific keyword research tools
Local search console	Review GSC for each target market
Local competitor analysis	See which keywords competitors target in each market
Social listening	Understand local search behavior
Local team input	Native speakers provide query insights

Common pitfall: Translating keywords from your primary language often yields low-volume or unnatural search terms. Research each market independently.

International Technical SEO

International technical SEO manages hreflang, sitemaps, canonicalization, and crawl optimization across markets.

Technical requirements:

Element	Requirement
Hreflang sitemap	Include hreflang annotations in sitemaps (alternative to HTML link tags for large sites)
Sitemap organization	Separate sitemap per language/country, or include all versions in one index
Canonical tags	Set to the correct language/country version
Content delivery	Use CDN with edge servers in target countries
Page speed	Optimize for local network conditions (may be worse or better than primary market)
Robots.txt	Ensure critical pages are not blocked in any market

Regional SERP Analysis

SERP behavior varies significantly by country and language.

What varies by market:

SERP Element	Variation
Dominant search engine	Google dominates globally, but Yandex (Russia), Baidu (China), Naver (Korea), Seznam (Czechia) are significant in specific markets
SERP features	Availability of features varies by country
Organic vs paid ratio	Varies by market competitiveness
Local vs global results	Local businesses dominate local SERPs more in some markets
Featured snippet usage	Varies by language and query type

Per-market SERP analysis: Run SERP analysis independently for each target market.

International Link Building

Links from local domains in the target country strengthen local relevance.

International link acquisition:

Strategy	Implementation
Local press coverage	PR targeting local journalists
Local partnerships	Partnerships with local businesses
Local directories	Country-specific directories
Local guest content	Guest posting on local industry sites
Local social media	Engage with local influencers

Country-specific linking: For ccTLDs, links from local domains (same ccTLD) provide the strongest local relevance signal.

Market-Level Reporting

Track performance per market separately.

Market reporting structure:

Metric	Per-Market Requirement
Organic sessions	Track by country in GA4
Organic revenue	Track by country in GA4
Ranking positions	Track per-country positions
Hreflang validation	Monitor via GSC URL Inspection on international pages
Indexation	Monitor indexed pages per country
Search Console	Set up separate GSC property per country (for ccTLDs) or filter by country (for subfolders)

Localized UX and Conversion Signals

Local user experience and trust signals must be adapted per market.

Localization for UX:

Element	Localize Per Market
Currency display	Local currency symbol and format
Date and time format	Local conventions (MM/DD vs DD/MM)
Payment methods	Local preferred payment options
Shipping information	Local shipping options and costs
Customer support	Local language support hours
Trust signals	Local certifications, security badges

Workflow

1. Define the targeting strategy: ccTLDs for strongest geotargeting, subfolders for shared domain authority, or subdomains as an intermediate option.
2. Establish URL structure per market. Map every piece of content to its language/region variant.
3. Implement bidirectional, self-referencing hreflang tags across all language/region versions. Include x-default for the fallback page.
4. Localize all metadata, headings, body content, URL slugs, schema, and images per market. Use professional translation or transcreation — not machine translation.
5. Conduct per-market keyword research independently (do not translate keywords). Set up per-market GSC properties or filters. Monitor per-market organic performance monthly.

Common Mistakes

warning

Hreflang must be bidirectional — if page A links to page B but B does not link back to A, hreflang is invalid and will be entirely ignored by Google. Every page in the language set must link to every other version, including itself.

• Non-bidirectional hreflang: If page A links to page B but B does not link back to A, hreflang is invalid and will be ignored. Every page in the language set must link to every other page (including itself).
• Using machine translation for content: Auto-translated content reads poorly, lacks cultural nuance, and violates helpful content standards. Use professional human translation or transcreation.
• Translating keywords instead of researching per market: Direct keyword translation misses local language patterns and often targets zero-volume terms. Research each market independently using local keyword tools.
• Wrong language-region codes: Using hreflang="en-uk" instead of hreflang="en-gb" or hreflang="de" when de-de is needed. Always use ISO 639-1 language codes and ISO 3166-1 Alpha 2 region codes.
• Missing x-default: Without an x-default page, Google must guess which version to show to users in unlisted regions. Always define a default fallback page.

Checklist

• Choose URL structure per market (ccTLD, subfolder, or subdomain)
• Implement bidirectional hreflang tags on every page in the language set
• Include self-referencing hreflang and x-default on every page
• Validate hreflang with GSC URL Inspection on international pages
• Localize metadata, content, URLs, schema, and images per market
• Conduct independent keyword research for each target market
• Set up per-country GSC tracking (property or filter)
• Submit separate sitemaps or hreflang-annotated sitemaps per market
• Monitor per-market organic traffic, rankings, and conversions monthly

What's Next

• News, Publisher & Media SEO
• Module Overview

References

• Google Search Central: International SEO
• Google Search Central: Hreflang
• Google Search Central: Manage multi-regional sites