- URL structureccTLD vs subdir vs subdomain
- hreflang implementationThe graveyard most miss
- Translation vs localizationTwo different investments
- Multi-engine strategyBaidu / Yandex / Naver where it matters
- Currency + regulatoryPage-level signals beyond language
International SEO isn't translation. It's hreflang, ccTLDs, currency, and multi-engine optimization.
Most US agencies sell international SEO as “translate the content.” That's why expansions fail. Going from US to UK is simple. US to Germany is a project. US to Japan is a different discipline. The work has to be scoped market by market, not copied from a domestic SEO plan.
What international SEO actually is.
International SEO is the discipline of optimizing websites for multiple countries, languages, currencies, and search engines simultaneously under one coherent technical and editorial plan that doesn't cannibalise itself across markets.
It's a different practice from translation, which is just content. International SEO is technical (URL structure decisions, hreflang implementation, geo- targeting in Google Search Console, server location and CDN routing), editorial (cultural localization beyond translation), commercial (currency display, payment methods, regulatory disclosures), and strategic (which markets warrant ccTLDs, which work as subdirectories, which require multi-engine optimization).
The work is multi-decision before it becomes multi-content. Most expansions fail because the operator starts with translation, which is the easy bit, and skips the structural decisions that determine whether Google ever serves your German page to a German searcher in the first place.
We run international SEO with the structural decisions first, the content second, and the multi-engine extension layered on top where the target market warrants it. The order matters.
Five international SEO decisions every business expanding internationally has to make.
URL structure: gTLD + subdir vs ccTLD vs subdomain
The first decision and the one that locks in the most. Subdirectories (example.com/de/) inherit parent domain authority: fastest path to ranking, lowest technical overhead, weaker country-specific signal. ccTLDs (example.de) send the strongest country signal and are mandatory for some markets (China, Russia) but build authority from zero per market. Subdomains (de.example.com) sit in the middle. Our default for 2-5 market expansions is subdirectories with proper hreflang. We move to ccTLDs when a market becomes commercially dominant or when local-domain trust signals materially affect conversion.
hreflang implementation
Hreflang can fail through wrong language codes, missing return tags, an incorrect x-default, canonical conflicts, annotations pointing to noindexed or missing pages, or inconsistent implementation across sitemaps, HTML heads, and HTTP headers. It should be rechecked after launches, template changes, migrations, or other material updates. The monitoring cadence is agreed in scope.
Translation vs cultural localization
Translation is a content operation: words on the page. Localization is a strategy operation: currency, payment methods, regulatory disclaimers, units of measurement, date formats, address formats, regional schema markup, culturally appropriate imagery, idiom replacement, and content priorities specific to that market's buyer. For low-commitment market tests, machine translation with editorial review is enough. For strategic priority markets, full localization is required, and that means rewriting for the target market's buyer, not translating from a different market's content. Skipping localization in priority markets is the most expensive false economy in international SEO.
Multi-engine strategy
Google is the priority across many markets, while China, Russia, and Korea require a separate review of Baidu, Yandex, and Naver. Each has different technical, hosting, content, and ecosystem requirements. The decision starts with where your buyers actually search in each target market, then scopes engine-specific optimization only where the commercial opportunity warrants it.
Currency, payment, and regulatory localization
International SEO doesn't end at language. Currency display affects conversion rate (and therefore behavioral signals that feed back into ranking). Payment methods vary dramatically (SEPA in Europe, iDEAL in Netherlands, Bancontact in Belgium, Boleto in Brazil, AliPay in China) and missing the local payment standard tanks conversion. GDPR overlay in EU markets adds cookie consent, privacy policy variants, and consumer protection compliance per member state. Tax inclusion in displayed pricing varies (UK shows VAT-inclusive, US shows tax-exclusive). Address format, date format, units of measurement (metric vs imperial) all signal local-market alignment. Each is a small thing. Together they decide whether the market trusts the page enough to convert.
Each market combination needs its own plan.
The decisions below show why.
US → English-speaking markets
UK, Canada, Australia, New Zealand. The shared language family can reduce translation overhead, but the work still includes per-market spelling, currency and payment handling, local-search signals, and hreflang that helps search engines serve the right regional variant. A subdirectory may preserve more existing domain authority, but the right structure depends on the commercial plan and technical constraints.
US → Spanish-speaking markets
Mexico, Spain, Latin America, and US Hispanic audiences require more than one generic Spanish translation. The scope can include regional language review, cultural localization, market-specific hreflang, localized products and payments, and native review before publication. Each market is assessed against its own buyer behavior and search evidence.
US → European markets
Germany, France, Netherlands, Italy, Spain. Translation alone is rarely enough for a priority market. The work includes native-quality content written for the market, hreflang across language and country combinations, privacy and consumer-protection requirements, local tax presentation, payment methods, schema, and regulatory disclosures. Subdirectories can support a market test, while a country-code domain may make sense once the market is commercially important.
US → APAC markets
Japan, Korea, Singapore, Australia, China. The most fragmented archetype: different dominant engines per market. Japan is Google-dominant with Yahoo Japan share, requiring full localization and Japanese-language native content. Korea requires Naver optimization (different ranking logic, Naver ecosystem content priority). Singapore is largely Google but multilingual (English, Mandarin, Malay, Tamil). Australia is English-language but local-pack different from US. China requires Baidu plus an ICP license and Chinese-hosted content: a different engagement entirely. We scope APAC market-by-market because a single APAC playbook doesn't exist.
AU → US (or international). Australian businesses expanding into the US: the playbook we run first-hand.
The natural target for most successful Australian businesses: same language, similar legal frameworks, a much larger addressable market. The complications most AU founders underestimate include different keyword demand and competitive density, per-market spelling normalization (organisation vs organization), local-pack ranking dynamics that don't map to AU city structure, currency and payment localization, US state-level regulatory differences. We run this transition as a separate market entry plan, with its own evidence, priorities, and implementation sequence. It is not a domestic SEO program with the spelling changed.
Most international SEO failures trace back to broken hreflang implementation.
It's the detail-work that determines whether Google serves your German page to German searchers, or your English page to German searchers, while your German page sits ignored. The failure mode is silent. You don't get an error message. You just watch international conversion rates inexplicably underperform while you assume the content needs more work.
The common breakages we audit out of inherited sites: language codes that don't match ISO 639-1 (using 'en-uk' when the standard is 'en-GB'), missing return tags (the German page references the English page but the English page doesn't reference back, which invalidates the entire pair), x-default missing or pointing at the wrong fallback, hreflang URLs conflicting with canonical URLs, hreflang annotations pointing at noindex or 404 pages, and inconsistent implementation across XML sitemap, HTML head, and HTTP headers (Google reads all three and treats them as contradictory if they disagree).
Most agencies treat hreflang as a deploy-and-forget operation. The monitoring cadence should match the pace of CMS migrations, content updates, template changes, and new-market releases. The scope is agreed before work begins, so the team knows what will be checked and when.
Market-specific technical judgment.
Localization that goes beyond translation.
Decisions your team can inspect.
International SEO is useful only when the technical structure, content, and commercial plan agree. You get a clear recommendation on URL structure, hreflang, localization depth, and the search engines that matter in each market.
Language variants are not interchangeable. Spanish for Mexico, Spain, and Argentina can require different vocabulary, offers, proof, payments, and disclosures. The same principle applies across every multilingual expansion: write for the buyer in that market and use hreflang to keep the variants distinct.
Joel's published work and the team's decision process are available to inspect on the About page. Where AI visibility measurement is relevant, Outrigger is identified accurately as a separate joint venture and used as a measurement input, not as a guaranteed result.
- URL structure recommendationccTLD vs subdir vs subdomain decision
- hreflang implementationRechecked after material releases on an agreed cadence
- Per-market localizationTranslation + cultural + commercial
- Multi-engine optimizationWhere Baidu / Yandex / Naver matter
- Cross-market AI trackingOptional dated samples by agreed market and language
- Currency + regulatory layerGDPR / VAT / payment / consumer rights
Adjacent disciplines for expansion-stage operators.
What multi-market operators ask before scoping the expansion.
Most US agencies sell international SEO as translation.
We sell it as multi-market expansion.
Start with a working conversation about your current international footprint, URL structure, hreflang decisions, and which markets warrant full localization versus which can run on subdirectories. No deck. No pretending the German market works the same as the UK.