International Ecommerce SEO Guide

Selling internationally means more than translating your product pages and adding a currency converter. International ecommerce SEO requires deliberate technical architecture, localised content, and a clear understanding of how Google handles multi-regional sites.

I've helped ecommerce brands expand from single-market to 10+ countries. Here's what works, what doesn't, and what most guides get wrong.

Domain Structure: ccTLD vs Subfolder vs Subdomain

This is the first and most consequential decision in international ecommerce SEO. Your options:

ccTLDs (Country-Code Top-Level Domains)

Example: yourstore.com.au, yourstore.co.uk, yourstore.de

Pros:

Strongest geo-targeting signal
Users trust local domain extensions
Clear separation of markets

Cons:

Each domain starts with zero authority — you're building SEO from scratch per market
Link equity doesn't transfer between domains
Higher cost and complexity (separate hosting, SSL, management)
Not practical for 10+ markets

Subfolders (Subdirectories)

Example: yourstore.com/au/, yourstore.com/uk/, yourstore.com/de/

Pros:

All markets benefit from the root domain's authority
Link equity consolidation — backlinks to any market help the entire domain
Simpler to manage technically
Scales well to many markets

Cons:

Weaker geo-targeting signal than ccTLDs (offset by hreflang and Search Console settings)
All markets share the same server infrastructure

Subdomains

Example: au.yourstore.com, uk.yourstore.com

Cons outweigh pros: Google treats subdomains as semi-separate entities, so you get the complexity of ccTLDs without the strong geo-targeting signal. I almost never recommend this approach for ecommerce.

My Recommendation

For most ecommerce brands, subfolders are the right choice. You inherit the parent domain's authority, link equity compounds across all markets, and the technical overhead is manageable. Reserve ccTLDs for markets where local domain trust is critical to conversion (e.g., .de in Germany, .co.jp in Japan).

Hreflang Implementation for Ecommerce

Hreflang tags tell Google which version of a page to serve to users in different languages or regions. Getting this wrong is one of the most common international SEO errors — and ecommerce makes it harder because of the sheer page volume.

Hreflang Basics

Every page that has regional or language variants needs hreflang annotations pointing to all versions, including itself.

Example for a product page available in Australia, UK, and US:

<link rel="alternate" hreflang="en-au" href="https://yourstore.com/au/product-name/" />

<link rel="alternate" hreflang="en-gb" href="https://yourstore.com/uk/product-name/" />

<link rel="alternate" hreflang="en-us" href="https://yourstore.com/us/product-name/" />

<link rel="alternate" hreflang="x-default" href="https://yourstore.com/product-name/" />

Ecommerce-Specific Hreflang Challenges

Products not available in all markets: If a product is only sold in Australia and the UK, don't include hreflang pointing to the US version — there shouldn't be one. Let the x-default handle users from other regions.

Different product catalogues per market: This is common. Your Australian store might carry 5,000 products while your UK store has 3,000. Only add hreflang annotations for products that exist in both markets. Non-overlapping products should have a single-market page with no cross-market hreflang.

Category page differences: If your category structure varies by market (different brands, different product groupings), don't force hreflang connections between non-equivalent pages. Only link category pages that genuinely serve the same purpose.

Implementation Method

For ecommerce sites with thousands of products, XML sitemap hreflang is the only practical approach. Adding hreflang to the HTML head of every product page creates massive code bloat and maintenance nightmares.

Create separate sitemap files per market and include hreflang annotations within the sitemap XML. This keeps your HTML clean and makes hreflang management programmatic.

Localised Product Content

Translation is not localisation. I've seen ecommerce brands translate their product descriptions word-for-word and wonder why they don't rank in the target market.

What Needs to Be Localised

Product names — The same product might be searched differently. "Trainers" (UK) vs "Sneakers" (US) vs "Runners" (Australia).
Descriptions — Adapt to local language, spelling conventions, and cultural context. Not just translation.
Measurements — Metric vs imperial. Clothing sizes (AU vs US vs EU sizing).
Pricing — Display in local currency with local tax handling.
Shipping information — Delivery times, costs, and courier options specific to each market.
Reviews — Ideally show reviews from the local market. At minimum, filter for language-appropriate reviews.

Keyword Research Per Market

Even in English-speaking markets, search behaviour varies significantly. Run keyword research independently for each target market.

Examples of variation:

"Jumper" (AU/UK) vs "Sweater" (US)
"Nappy" (AU/UK) vs "Diaper" (US)
"Thongs" (AU) vs "Flip Flops" (UK/US)
"Boot" (AU — car trunk) vs "Boot" (UK/US — footwear, primarily)

Use local Google domains (google.com.au, google.co.uk) when researching keywords. Ahrefs and Semrush both allow you to filter keyword data by country.

Multi-Currency and Pricing

Currency handling affects both SEO and conversion.

Technical Considerations

Display local currency by default — Auto-detect the user's location and show local pricing. Don't make users convert currencies manually.
Include currency in structured data — Your Product schema must specify the priceCurrency property correctly for each market version.
Handle tax correctly — Australian prices are GST-inclusive. US prices are often tax-exclusive. UK prices include VAT. Your displayed price and schema price should match local convention.

Pricing Strategy Impact on SEO

If your prices are significantly higher in one market due to shipping or import costs, this affects conversion rate — which affects rankings. Google's Shopping algorithm is particularly sensitive to pricing competitiveness.

Consider whether market-specific pricing strategies (absorbing some cost to remain competitive) make sense from an overall customer acquisition perspective.

Technical SEO for International Ecommerce

Google Search Console Configuration

If using subfolders, add each country subfolder as a separate property in Search Console and set the geographic target. This reinforces the hreflang signals.

CDN and Server Location

Use a CDN with edge locations in your target markets. While Google says server location isn't a ranking factor, page speed is — and a CDN reduces latency for international users, directly improving Core Web Vitals.

Cloudflare, Fastly, or AWS CloudFront all work well for multi-region ecommerce delivery.

Redirects and Geo-Detection

Do not auto-redirect users based on IP location. Google crawls from the US, so auto-redirecting US IPs to your US subfolder means Googlebot may never see your other market versions.

Instead:

Show a non-intrusive banner: "It looks like you're in Australia. Visit our Australian store?"
Let users choose their market with a visible language/region selector
Set a cookie to remember their preference

Canonical Tags Across Markets

Each market version should self-canonicalise. Your Australian product page should have a canonical pointing to itself, not to the US or default version. This is a common mistake that deindexes entire market versions.

International Link Building

Backlinks from country-specific domains strengthen your geo-targeting signals. A link from a .com.au site reinforces your Australian market presence more than a link from a .com site.

Strategies for international link building:

Local PR and media outreach — Pitch to media outlets in each target market
Local business directories — Register in market-specific directories
Partnerships with local influencers — Market-specific influencer collaborations generate local links and brand awareness
Localised content marketing — Create market-specific buying guides, trend reports, or research that local publishers want to reference

Common International Ecommerce SEO Mistakes

These are the errors I see most frequently when auditing international ecommerce sites:

Using Google Translate for product content — Machine translation produces unnatural content that ranks poorly and converts worse. Use native speakers or professional localisation services.
Missing hreflang self-references — Every page must include a hreflang tag pointing to itself. Missing self-references break the entire hreflang cluster.
Inconsistent hreflang across page types — Category pages have hreflang but product pages don't. Or vice versa. Both need complete implementation.
Not localising meta titles and descriptions — Translating page content but leaving English meta tags is wasted opportunity. These are your SERP listing — they must be in the local language.
Ignoring local competitors — Your ecommerce SEO strategy needs to account for local market leaders in each country, not just global competitors.
Same content, different currency — If two market pages have identical content except for the currency symbol, Google may treat them as near-duplicates. Localise the content, not just the price.

AI Search and International Ecommerce

AI search tools are inherently multi-lingual. ChatGPT, Perplexity, and Google's AI features can process queries in any language and surface results from any market. This has implications for AI search optimisation:

Your product data needs to be comprehensive in each language — AI tools synthesise information from your structured data
Local reviews and testimonials help AI tools make market-specific recommendations
Clear shipping and availability information per market helps AI tools give accurate answers

Frequently Asked Questions

Should I use subfolders or ccTLDs for international ecommerce?

Subfolders for most brands. They inherit the root domain's authority, consolidate link equity, and scale better. Only use ccTLDs when local domain trust is essential for your market (Germany and Japan are common examples where ccTLDs significantly impact user trust).

Do I need unique content for each country in the same language?

Yes. Even if Australia, UK, and US all speak English, search behaviour differs. Product terminology, spelling conventions, and competitive landscapes vary by market. At minimum, localise product names, key features, and meta data for each market.

How do I handle products that aren't available in all markets?

Only create pages in markets where the product is available. Don't create placeholder pages or redirect to alternatives — this creates a poor user experience and confuses search engines. Let your x-default page handle users from markets where the product isn't sold.

What's the most common international ecommerce SEO mistake?

Incorrect hreflang implementation. Specifically, missing self-referencing hreflang tags, inconsistent hreflang across page types, and pointing hreflang tags at non-equivalent pages across markets. Validate your hreflang with Ahrefs Site Audit or Screaming Frog before launch.

How long does it take to rank in a new international market?

With subfolders on an established domain, expect 3-6 months to see meaningful organic traffic in a new market. With a new ccTLD, expect 6-12 months. The timeline depends on competition in the target market, content quality, and local link building efforts.