International SEO isn't translation. It's hreflang, ccTLDs, currency, and multi-engine optimization.

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 the international SEO graveyard. Most sites get it wrong because the implementation is detail-heavy and the failure mode is silent — Google just serves the wrong language version to the wrong audience and you watch international conversion rates inexplicably underperform. The common failures: language codes that don't match ISO 639-1 (using 'en-uk' instead of 'en-GB'), missing return tags (German page references English page but English page doesn't reference back), x-default missing or pointing at the wrong fallback, hreflang URLs that conflict with canonical URLs, hreflang tags pointing at noindexed or 404 pages, and inconsistent implementation across XML sitemap, HTML head, and HTTP headers. We audit hreflang monthly, not quarterly — the breakage rate is high enough that monthly is the right cadence. The audit pulls every hreflang annotation, validates language and country codes, checks for return-tag completeness, cross-references against canonical and indexation, and reports breakage with prioritised fixes. Most agencies treat hreflang as a deploy-and-forget operation. It's a maintenance discipline.

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.

Depends entirely on the markets you're entering. For Western Europe, Latin America, India, the UK, Canada, Australia, and most of Africa, Google holds 90%+ market share and the multi-engine question is largely academic — Google plus AI engine optimization (ChatGPT, Perplexity, Gemini) is the right strategy. For China, Baidu is the dominant search engine and Google is functionally inaccessible — Baidu has its own ranking factors, requires an ICP license to host content on Chinese servers (often requiring a Chinese business entity), penalises foreign-hosted sites, and rewards Chinese-language content with local cultural alignment. For Russia, Yandex is dominant and has unique ranking factors around behavioral metrics and link freshness. For Korea, Naver is the dominant engine with ranking weights very different from Google — content within Naver's own ecosystem (Naver Blog, Naver Cafe) outranks external content for many queries. For Japan, Google is dominant but Yahoo Japan still has meaningful share with its own quirks. The decision tree: if you're entering China, Russia, or Korea as a strategic priority, you need engine-specific optimization that's a different discipline from Google SEO. We scope this at the start of any engagement — the wrong assumption here can sink an APAC or Eastern European expansion before it starts.

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 is the natural expansion target for most successful Australian businesses — same language, similar legal frameworks, dramatically larger TAM, and the AU brand often reads as a quality signal in the US (Australian operations imply a serious operator). The complications most AU founders underestimate: keyword volume and competitive density are 10-15x higher in equivalent US categories, which means SEO that worked in AU often fails in the US without a 5-10x increase in content velocity and link-building investment. Spelling normalization matters more than expected (organisation vs organization, optimise vs optimize) — we publish per-market spelling without breaking the AU canonical. Google's local-pack ranking in the US is significantly more competitive and metropolitan area boundaries are different (US cities aren't single local-pack zones the way most AU cities are). Currency, payment methods, and shipping logistics affect on-page conversion signals that feed back into ranking. We've run the AU-to-US transition for multiple clients — the playbook is real, but it's a 12-18 month build, not a 90-day port. Operating dual offices US (LA) + Australia (Brisbane) means we run this transition with first-hand market awareness on both ends.

Yes — Mention Layer monitors AI engine visibility (ChatGPT, Perplexity, Gemini, Claude, Google AI Overview) across markets and languages. The cross-market dimension matters because LLMs handle multilingual queries differently than Google. ChatGPT and Perplexity will often answer a German query by citing English-language sources if the German-language corpus is sparse for that topic, which means your English-language authority can leak into German-market AI visibility — a leverage point most agencies miss. Conversely, in markets where you've invested in local-language authority (German press citations, Spanish-language original-data studies), Mention Layer surfaces the citation share you've built within the target language and tracks it weekly. The cross-market data feeds the content roadmap: when German-language citation share lags, we know to invest in German-language authority assets; when English-language citations are leaking into German-market AI answers, we leverage that bridge while building the German-language depth. The reporting is per-market and per-language so you can see exactly where your AI visibility is strong and where it's underbuilt.

Depends on the market and the URL structure decision. For subdirectory expansions (example.com/de/) into markets with shared language families (US into UK, US into Canada, US into Australia, US into other English-speaking markets), measurable rankings and traffic typically land in 60-120 days because the parent domain authority transfers immediately. For full-localization expansions into priority markets (US into Germany, US into France, US into Japan), expect 6-9 months to achieve baseline ranking presence and 12-18 months for the market to compound to material commercial scale. For ccTLD expansions where you're starting from zero domain authority (a brand new example.de domain), expect 9-15 months for baseline rankings and 18-24 months for category presence. AI engine citations tend to land faster than Google rankings — often within 60-90 days of structural site upgrades — which is increasingly the way buyers discover brands in new markets. We benchmark expected timelines against the specific market dynamics at the start of every engagement, and we hold ourselves to those benchmarks in monthly reporting.