Skip to content
XpandShow Me What To Fix First
Five decisions every multi-market expansion runs into
  • 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
Get any one of these wrong and an otherwise promising expansion can stall. The plan has to fit the market, the site, and the commercial case.
International SEO Services

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.

Market-specific structure · Localization · Measured implementation
What multi-market expansion actually looks like
5
decisions every expansion has to make before content gets translated
Hreflang
language and country signals checked against canonicals and indexation
3
non-Google search engines that matter. Baidu, Yandex, Naver
Market
search behavior, localization, payments, and regulation reviewed separately
Definition

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.

The five decisions

Five international SEO decisions every business expanding internationally has to make.

Decision 01

URL structure: gTLD + subdir vs ccTLD vs subdomain

Authority budget vs market signal

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.

Decision 02

hreflang implementation

The international SEO graveyard

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.

Decision 03

Translation vs cultural localization

Two different investments

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.

Decision 04

Multi-engine strategy

Google + Baidu / Yandex / Naver

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.

Decision 05

Currency, payment, and regulatory localization

Page-level signals beyond language

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.

Four expansion archetypes

Each market combination needs its own plan.
The decisions below show why.

Easiest expansion

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.

Bilingual leverage

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.

Full localization required

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.

Multi-engine discipline

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.

The fifth archetype. XD's home turf

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.

The hreflang graveyard

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.

Why hire us, specifically, for international SEO

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.

What's included
  • 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
Common questions

What multi-market operators ask before scoping the expansion.

It depends on three factors: domain authority budget, technical complexity tolerance, and long-term market commitment. Subdirectories (example.com/de/) inherit the authority of the parent domain: fastest path to ranking, lowest technical overhead, but weaker country-specific ranking signals. ccTLDs (example.de) send the strongest country-specific signal to Google and are mandatory for some markets (China, Russia) but require building authority from zero per market. Subdomains (de.example.com) are a middle ground: more separable than subdirectories, less authority-isolated than ccTLDs, but Google has historically treated them more like separate sites than most operators expect. Our default recommendation for businesses entering 2-5 markets is gTLD + subdirectory (example.com/de/, example.com/fr/) with proper hreflang. We move to ccTLDs when a market becomes strategically dominant or when local-market trust signals (a .de domain in Germany) materially affect conversion rate. There's no universally correct answer: there's a correct answer for your specific commercial roadmap.

Hreflang is detail-heavy and its failure mode can be silent. Common failures include invalid language codes, missing return tags, an incorrect x-default, conflicts with canonical URLs, annotations that point to noindexed or missing pages, and inconsistent implementation across XML sitemaps, HTML heads, and HTTP headers. A useful audit pulls every annotation, validates language and country codes, checks return-tag completeness, cross-references canonical and indexation states, and reports breakage with prioritised fixes. The right monitoring cadence depends on how often templates, content, and markets change. Hreflang should be treated as a maintained technical system, not a deploy-and-forget task.

Translation is a content operation. Localization is a strategy operation. Translation handles the words on the page; localization handles everything else: currency display, 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 journey. The right answer depends on commercial weight per market. For low-commitment markets where you're testing demand (early-stage ecommerce expansion, a single market test), high-quality machine translation with human editorial review is enough. For markets you've decided are strategic priorities, full localization is required, and full localization means rewriting content for that market's buyer, not translating content written for a different market. We sequence the investment: machine translation plus editorial pass for proof of demand, then a localization rebuild once the market warrants it. Skipping the localization step in priority markets is the most expensive false economy in international SEO.

It depends entirely on the markets you are entering. Google is the priority across many markets, but China, Russia, and Korea require a separate review of Baidu, Yandex, and Naver respectively. Each has different technical, hosting, content, and ecosystem requirements. Japan also warrants a market-specific search review rather than a blind copy of a US plan. The useful first step is to confirm where buyers actually search in each target market, then scope engine-specific optimization only where the commercial opportunity warrants it.

GDPR adds a layer of technical and content requirements that most US-headquartered businesses underestimate when expanding into EU markets. The SEO-relevant pieces: cookie consent banners must be implemented before any tracking fires (which affects how Google Analytics 4 measures EU traffic, and therefore affects your data quality), privacy policies must be GDPR-compliant and accessible per locale (often requiring per-country variants), data subject access rights have implications for how you handle email capture forms and CRM data, and country-specific regulators (Germany's Bundesnetzagentur for telecommunications, Italy's AGCOM, the UK's ICO post-Brexit) have their own enforcement priorities. The content overlay: terms and conditions, returns policies, warranty disclosures, and consumer rights notices must comply with each EU member state's specific consumer protection regime: not just the EU directive. There's also the cookie banner UX problem (aggressive consent banners hurt engagement and therefore SEO performance), which we engineer around with TCF-compliant solutions that don't tank Core Web Vitals. We coordinate with your privacy/legal counsel on the regulatory layer; the SEO work runs in parallel.

The US can be a logical expansion market for an Australian business because the language overlap reduces some localization work, but the search market, competitive density, city structure, pricing, payments, fulfilment, and regulation still require a separate plan. Spelling normalization also matters: per-market variants should be published without creating canonical conflicts. The decision should begin with demand, competitive evidence, unit economics, and fulfilment readiness, not the assumption that an Australian SEO program can simply be copied into the US.

Outrigger, a separate joint venture involving Joel House and Andrew, can be configured to observe AI-engine answers across selected markets and languages. The useful comparison is prompt-level: which brands appear, how they are described, and which sources are cited for the same buyer questions in each market. Because answers vary by prompt, model, language, and date, the output should be treated as a repeated visibility sample rather than a permanent rank or guaranteed citation result.

There is no responsible universal timeline. A subdirectory can inherit more of the parent domain's authority, while a new country-code domain begins with less existing authority. Market competition, localization depth, technical health, content quality, links, brand demand, and the speed of implementation all affect the result. The engagement should establish a market-specific baseline, agree the leading and commercial indicators to watch, and report progress against those indicators without promising a fixed ranking date.

Hire the operator that runs the playbook on both ends

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.