Technical SEO
International SEO Operating System
Plan international SEO across market selection, locale architecture, localization quality, hreflang, internal links, and measurement.
International SEO is the system for helping users and search systems find the right language, country, or regional version of a site.
The work starts before translation. It requires market selection, URL architecture, localized search research, page equivalence rules, hreflang, canonicals, internal links, content quality, and segmented measurement.
Download the working file: International SEO launch matrix CSV.
Decide whether a market deserves a locale
Create a locale only when the market has enough value and the team can maintain it.
| Question | Why It Matters |
|---|---|
| Is there search demand in the local language or country? | Direct translation can miss how people actually search. |
| Is the offer different by market? | Pricing, shipping, legal terms, service coverage, and support can change. |
| Can the team localize and maintain content? | Stale or machine-only translations can damage trust. |
| Is there a conversion path for the market? | Users need local currency, contact, payment, delivery, or support expectations. |
| Can reporting separate the locale? | Global totals hide broken local experiences. |
Do not launch locales only because competitors have them. Launch when the site can serve the audience.
Define the locale model
Separate language targeting from country targeting.
| Model | Example | Use When |
|---|---|---|
| Language-only | /es/ | Spanish content serves multiple Spanish-speaking markets with the same offer. |
| Country-specific | /mx/ | Mexico has different pricing, shipping, inventory, legal, or support needs. |
| Language-country | /es-mx/ | The language and country both matter. |
| Global selector | /international/ or root page | Users need to choose a market or language. |
The model should match real differences in user needs, not internal organization.
Build the locale inventory
Before implementation, list:
- Source URL.
- Target locale URL.
- Language and region code.
- Page type.
- Search intent.
- Localization owner.
- Canonical URL.
- Hreflang alternates.
- x-default decision.
- Localized title and meta description.
- Local proof or market-specific data.
- Currency, shipping, legal, and support differences.
- Internal-link changes.
- Sitemap inclusion.
- Measurement property or segment.
This inventory becomes the launch source of truth.
URL architecture rules
Choose one structure and use it consistently.
| Structure | Strength | Risk |
|---|---|---|
| ccTLD | Strong country signal and local brand fit. | More domains, authority split, operational cost. |
| Subdirectory | Easier management and consolidated authority. | Requires clean architecture and locale routing. |
| Subdomain | Operationally flexible. | Can fragment management and signals. |
| Parameter | Easy technically. | Usually weaker for users, tracking, and crawling. |
The best structure is the one the team can maintain without inconsistent canonicals, hreflang, links, and sitemaps.
Page equivalence rules
Hreflang works for alternate versions of equivalent pages. Decide what counts as equivalent.
Equivalent pages usually:
- Serve the same core task.
- Represent the same product, service, category, guide, or policy.
- Are localized for language or market.
- Have matching user intent.
Non-equivalent pages should not be forced into a hreflang cluster. A country-specific product line, different legal offer, or market-only landing page may need its own search strategy.
Implementation sequence
- Select markets and define the locale model.
- Choose URL architecture.
- Build the locale inventory.
- Localize keyword research and SERP review.
- Localize content, metadata, proof, pricing, policies, and conversion paths.
- Implement self-canonicals.
- Implement reciprocal hreflang and x-default where appropriate.
- Update internal links and language switchers.
- Update XML sitemaps.
- Validate crawl, render, indexability, and measurement.
Do not wait until the end to think about internal links and measurement.
Launch validation
Before launch, sample every important template and locale.
Check:
- Status code is
200. - Page is indexable.
- Canonical points to the same locale URL.
- Hreflang is reciprocal and uses valid codes.
- Hreflang points to final URLs.
- x-default is appropriate.
- Content language matches the target.
- Currency, shipping, contact, legal, and support details match the market.
- Internal links keep users in the same locale where useful.
- XML sitemaps include canonical locale URLs.
- Search Console, analytics, and CRM can segment the market.
International issues are often template-wide, so a small sample can reveal a large problem.
Measurement
Track by locale:
- Indexed pages.
- Organic clicks and impressions.
- Query language and market fit.
- Pages receiving traffic in the wrong country or language.
- Hreflang/canonical QA issues.
- Conversion rate, leads, revenue, calls, or bookings.
- Local backlinks, mentions, citations, or reviews.
- Content freshness and translation maintenance.
International SEO is successful when the right market sees the right page and can convert naturally.
Common mistakes
- Translating without local keyword research.
- Launching markets without local conversion support.
- Cross-canonicalizing localized pages to the source language.
- Forcing non-equivalent pages into hreflang clusters.
- Using automatic IP redirects with no user choice.
- Mixing languages in navigation and body links.
- Reporting global organic traffic instead of locale performance.
- Treating hreflang as a ranking boost instead of routing support.
Useful source references
- Google Search Central: Managing multi-regional and multilingual sites
- Google Search Central: Localized versions of your pages
- Astro docs: Internationalization routing
Use International Site Structure and Locale Targeting for URL decisions, then use the Hreflang QA Checklist before launch.