International optimization

TL;DR

International SEO comes down to two questions: which URL architecture (ccTLD, subdomain, or subfolder) and whether hreflang is set up correctly. Default to subfolders on the primary domain. Ship self-referencing hreflang with return tags. Do real localization, not blind translation. Serve local currency and local date format on the page, and never auto-redirect users based on IP.

The surface, in one paragraph

International optimization is the discipline of serving the right version of a site to a user in a given country and language, and telling every search engine which version belongs to which market so they do not cannibalize each other. The technical mechanism is hreflang, a set of link elements that map every URL to its counterparts in other locales. The architectural mechanism is URL structure: country-code top-level domains (google.de), subdomains (de.example.com), or subfolders (example.com/de/). The content mechanism is localization: not just translation, but adapting currency, date format, imagery, product availability, legal disclosures, and reference points to match how the target market actually reads. Get any of these wrong and international traffic underperforms permanently. Get them right and the site earns organic reach in every market it operates in.

Where this fits in Search Everywhere Optimization

GLOBO is a multiplier on every other surface.

SEO scales per market. Each locale becomes its own competitive graph. Winning organic in Germany is a different game than winning in the US.

PFO extends across markets. Merchant Center feeds go per country with local currency and shipping. The feed strategy multiplies by market count.

KGO covers multilingual labels. Wikidata labels in every operating language reinforce entity recognition per locale.

E-E-A-T multiplies by market. Named local authors, local editorial standards, and market-specific corrections policies where the audience expects them.

VSO and VDO play by country. Alexa Skills and Google Actions vary by locale. YouTube's country-specific search behavior matters.

The five levers

1. URL architecture: subfolders as the default

Subfolders on the primary domain (example.com/de/, example.com/fr/) consolidate authority on one domain, are the cheapest to operate, and rank strongly in most markets. Subdomains (de.example.com) split PageRank, though Google says they should not. ccTLDs (example.de) send the strongest geographic signal and are best for markets where a country-code TLD is a trust cue (Germany, France, Japan, Australia), but they require the most infrastructure and content resources. I default to subfolders unless there is a specific market or legal reason for a different structure.

2. hreflang, correctly implemented

Every localized URL points to every other localized URL via hreflang, including a self-reference. Every hreflang uses the correct ISO 639-1 language code and, where relevant, the ISO 3166-1 region code (en-US, en-GB, en-AU, de-DE, de-AT, de-CH). Return tags reciprocate: page A points to B and B points back to A. x-default fallback set. Canonical tags do not conflict with hreflang. hreflang delivered via HTML link tags, HTTP headers, or XML sitemap; I pick sitemap for large sites and HTML for small ones.

3. Localization deeper than translation

Machine translation without human editing reads as low quality and gets downweighted. Real localization means: currency in the local unit, dates in the local format (23 July 2026 in Europe, July 23, 2026 in the US, 2026-07-23 in Japan for tech), addresses in the local convention (postal code before city in Germany, after in the US), phone numbers in local format with the local country code, imagery that reflects the market's demographics, references to holidays and events that resonate, and units (metric or imperial) that match. Legal disclosures per market: GDPR for EEA, CCPA for California, LGPD for Brazil, PIPL for China. Compliance is a locale property.

4. Local hosting and CDN for latency

A US-hosted site serving Australia takes hundreds of extra milliseconds. A global CDN with local edge caches gets LCP to the same threshold in every market. In markets with different networking regimes (China, Russia, Middle East), local hosting may be required legally or practically. CWV pass rates are inherently local.

5. Local search engine coverage where market share requires it

Google is dominant in most markets but not all. Baidu in China. Yandex in Russia and parts of Central Asia. Naver in South Korea. Seznam in the Czech Republic. Each has its own webmaster tools, structured data expectations, and ranking factors. Ignoring the local dominant engine in Russia or Korea is leaving 30 to 60% of the market on the table.

First 30 / 60 / 90 days

Days 1 to 30: audit and strategy

Market audit. Which markets the business currently serves. Which markets it wants to. Which markets the site accidentally attracts.

URL architecture audit. What structure exists now. Where authority is fragmented (subdomains, orphan sites, ccTLDs bought but idle).

hreflang audit. GSC international targeting report. Return tag errors. Missing self-references. Wrong codes.

Localization quality audit. Is content machine-translated. Are currencies and dates local. Are legal disclosures market-appropriate.

Local engine audit. If the target market has Baidu, Yandex, Naver, or Seznam presence, current state.

Deliverable at day 30: an architecture decision (subfolder, subdomain, or ccTLD), a hreflang fix scope, a localization content plan, and a compliance and legal map.

Days 31 to 60: implement

URL architecture consolidation or expansion. If subfolders are chosen and subdomains exist, migration plan with 301 redirects. If ccTLDs are being launched, DNS and hosting set up.

hreflang shipped. XML sitemap approach for large sites, HTML link tags for small. Self-references and return tags verified with Sitebulb or the international targeting tool.

Localization workflow set. Translation management system connected (Smartling, Phrase, Lokalise, or Contentful native). Human translators or MT-with-post-edit workflow agreed.

Currency and date discipline shipped. Site-wide component refactored to serve the correct locale.

Local hosting or CDN edge for target markets. Cloudflare, Fastly, Akamai, or AWS CloudFront geo-configured.

GDPR, CCPA, LGPD, PIPL compliance shipped per locale where required.

Deliverable at day 60: clean architecture, live hreflang, localized content on core pages, correct currency and date, edge coverage.

Days 61 to 90: expand and monitor

Content expansion. Prioritized pages translated. Locale-specific content that does not translate directly (regional case studies, local testimonials, market-specific FAQs) written from scratch.

Local search engine registration. Baidu Webmaster Tools, Yandex Webmaster, Naver Search Advisor, Seznam Webmaster where market share justifies.

Merchant Center feeds per market with local currency, shipping, tax, and language.

Reporting infrastructure. GSC per property (one per subfolder or ccTLD). Analytics segmented by market.

Local editorial or PR outreach. Backlinks from local publications carry more weight than international ones for local ranking.

Deliverable at day 90: multi-market coverage live, hreflang clean, local engine registrations submitted, per-market analytics, expansion roadmap.

Tools I use

• Google Search Console. International Targeting report, per-property performance.
• Bing Webmaster Tools. Bing's market share is higher in North America and parts of Europe than most think.
• Baidu Webmaster Tools, Yandex Webmaster, Naver Search Advisor. Local engines in specific markets.
• ScreamingFrog SEO Spider. hreflang audit and validation at scale.
• Sitebulb. hreflang cluster visualization and error diagnosis.
• hreflang.org test tool. Quick tag validation.
• Ahrefs, Semrush. Per-market keyword research and local ranking tracking.
• Smartling, Phrase, Lokalise, Contentful. Translation and localization workflow.
• Google Merchant Center. One feed per country with local currency and language.
• Cloudflare, Fastly, Akamai. Global CDN and edge caching per market.

What kills the program

IP-based auto-redirects. Break Googlebot's crawling and infuriate travelers. Use a banner and a manual switch.

Machine translation without post-edit. Reads as low quality. Downweighted in most markets. Worth doing right or not doing at all.

hreflang without return tags. Google throws the mapping out. GSC's report shows return-tag errors.

Canonical conflicting with hreflang. If the German page canonicalizes to the US page, hreflang breaks. Every localized URL canonicalizes to itself.

Duplicated content across en-US, en-GB, en-AU without differentiation. Same content, three URLs, no local signal beyond hreflang. It works, but leaves ranking on the table.

Currency and date mismatch. Serving USD to a Berlin buyer, or writing 4/5/2026 without knowing whether it is April 5 or May 4, kills conversion.

Ignoring local search engines. Baidu, Yandex, Naver dominate in their markets. Google-only strategy misses 30 to 60% of those countries.

Legal blind spots. Missing GDPR consent, CCPA privacy notice, or PIPL data localization is a compliance risk beyond SEO.

KPIs that matter

• Per-market organic impressions and clicks. GSC property per subfolder or ccTLD.
• hreflang error count. International targeting report.
• Per-market ranking on target keywords. Localized ranking trackers.
• Local engine coverage. Baidu, Yandex, Naver where applicable.
• Localization coverage percent. Pages fully localized versus machine-translated versus untranslated.
• Per-market CWV pass rate. Latency to end market.
• Per-market conversion rate. Real business KPI attribution.

FAQ

ccTLD, subdomain, or subfolder?

For most businesses, subfolders on the primary domain (example.com/de/) are the right answer. Subdomains split authority. ccTLDs (.de, .fr) are strongest for market signal but require the most infrastructure. I default to subfolders unless there is a legal or brand reason otherwise.

What is hreflang and why does it matter?

hreflang tells Google which page to serve to which locale. It prevents the German page from competing with the US page in the same SERP. Without hreflang, international pages cannibalize each other.

Do I need machine translation or human translation?

For product content, human translation or heavy MT post-editing. For editorial, human translation is table stakes. Raw machine translation reads as low quality and gets downweighted in most markets.

How do I handle x-default?

x-default is the fallback for locales you have not translated for. I point x-default to the English or primary language homepage. It stops Google from guessing when a user's locale is unmapped.

What kills hreflang setups?

Return tag errors (page A points to B but B does not point back to A), missing self-references, wrong language or region codes, and conflicts between hreflang and canonical tags. GSC's international targeting report flags most of them.

Should I geo-detect and redirect users?

No. Auto-redirects based on IP break Googlebot's crawling and frustrate travelers. Use a banner that suggests the local site with a manual switch. Let hreflang do the SERP work.

Related reading

• Product feed optimization (PFO): per-market Merchant Center feeds.
• Knowledge graph optimization (KGO): multilingual Wikidata labels support market recognition.
• Core Web Vitals: per-market latency is a CWV property.
• E-E-A-T playbook: local author credibility per market.
• Feed and Discover optimization (FEO): Discover is per-country.