International E-commerce SEO

Hreflang for product catalogues, currency and pricing signals, and geo-targeting strategies.

The Hreflang Challenge for Product Catalogues

A product available in multiple countries creates multiple versions: en-US version (USD pricing), en-GB version (GBP pricing), de-DE version (German product descriptions). Without hreflang markup, Google does not know which version is for which country. It might index the US version for UK searchers or mix versions together.

Hreflang tells Google: "This page is for Germany in German language. The equivalent English version for the USA is [URL]. The equivalent English version for the UK is [URL]." Google then shows the correct version to each audience.

Implementation: add hreflang tags in the <head> section of each regional version:

<!-- On US page (example.com/en-us/shoes) -->
<link rel="alternate" hreflang="en-US" href="https://example.com/en-us/shoes">
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/shoes">
<link rel="alternate" hreflang="de-DE" href="https://example.com/de-de/shoes">

<!-- On UK page (example.com/en-gb/shoes) -->
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/shoes">
<link rel="alternate" hreflang="en-US" href="https://example.com/en-us/shoes">
<link rel="alternate" hreflang="de-DE" href="https://example.com/de-de/shoes">

Hreflang is unidirectional. Each page must link to all its regional equivalents. A product with versions in 8 countries must have 8 hreflang links on each page.

Currency and Pricing Signals

Google can infer currency from the page content, but explicit signals help. Product schema should include priceCurrency: "USD", "GBP", "EUR". The page <html> tag should include lang="en-US" or lang="de-DE". Together, these tell Google: this page is in US English and prices are in USD.

Regional variations in product descriptions also signal to Google. If your en-US page says "Size 10" (US shoe size) and your en-GB page says "Size 8" (UK shoe size), these are distinct versions. This signals legitimacy — you are not just duplicating content.

Avoid the same price and currency across all regional versions. If a product costs $100 USD and £100 GBP (different real-world prices), make sure schema reflects this. Users notice immediately if pricing is identical across regions — it signals a mistake.

Domain Structure Options

Three structural approaches: country-specific domains (example.com.au for Australia), subfolders (example.com/au), or subdomains (au.example.com). Each has tradeoffs:

Country domains (.com.au, .co.uk, .de): Strongest geo-targeting signal. Highest authority per domain (link equity not shared). Downside: link equity is fragmented across domains; new domains start with zero authority.
Subfolders (/au/, /uk/, /de/): Recommended for most. Link equity concentrates on the main domain. Easier to manage. Google treats subfolders as part of the main site. Geo-targeting works (set in GSC).
Subdomains (au.example.com): Treated more independently than subfolders. Do not pool link equity as efficiently. Generally not recommended.

For small operations, subfolders are best. For large international operations with significant regional investment, country domains are acceptable if you have resources to manage separate link building per domain.

Duplicate Content Across International Versions

A product has one canonical description. Translating it to 8 languages is necessary, not duplicate content. Google understands and expects this. But if you copy/paste the English description to your French page, that is duplicate content.

Proper internationalization: each language version has unique, native-speaker content. French pages are written by French speakers for French users. German pages are written for German markets, not machine-translated from English.

This is a quality signal. Google recognises legitimate translations and localisation. It detects lazy, automated translations. The tradeoff is real: proper localisation costs more but performs better.

Common Mistake

Hreflang without proper regional content is ineffective. If all hreflang variants point to content that is literally identical except for the URL, Google views this as a signal problem. Hreflang should point to substantively different content (different language, different currency, different regional details).

Tax, VAT, and Compliance Display

Different regions have different tax requirements. EU requires VAT (value-added tax) to be displayed and collected per region. US has state-based sales tax. This affects pricing display significantly. A product shown as "$100" on a US site must show as "€92 (incl. 21% VAT)" on an EU site.

From an SEO perspective, ensure product schema priceCurrency and price match the displayed price. If users see one price on the page and schema says another, this is a trust signal failure and a technical issue.

Monitoring International Rankings

Set up Search Console properties for each regional domain or subfolder. Monitor rankings and CTR per region. A product ranking well in the US but poorly in the UK signals either a hreflang issue, a content quality issue, or a market-specific demand difference.

Hreflang errors are common. Use tools like Semrush or Screaming Frog to audit hreflang on large sites. Look for: missing hreflang links (a page missing hreflang to one of its regional versions), incorrect URLs in hreflang (pointing to non-existent pages), and cross-domain hreflang errors.

Actionable Step

If operating in 3+ countries, audit your hreflang implementation now. A single hreflang error on 10,000 product pages creates 10,000 instances of incorrect geo-targeting. Fixing hreflang can recover significant traffic immediately.

How This Connects

International e-commerce requires both technical precision (hreflang, schema, lang attributes) and content quality (localisation, currency, regional product variations). Getting this right multiplies your market reach and prevents the chaos of misattributed traffic.