Hreflang for E-Commerce Multi Language Product Pages

Handling variants without breaking the cluster

A product sold in six countries at different prices but with identical descriptions still needs six separate URLs with hreflang connecting them, because price and currency are exactly the kind of localisation Google expects hreflang to route between. Do not try to solve this with a single URL that changes currency based on IP detection — Googlebot won't see the localised version and every market except the one Googlebot appears to crawl from will be misrepresented in search results.

Out-of-stock handling needs a policy: if a product is permanently discontinued in one market but still sold in others, remove that market's hreflang reference rather than leaving a dead link in the cluster, and 301 redirect the discontinued URL to the closest relevant category page in that market.

Pagination and faceted URLs in hreflang clusters

Paginated category listings (page 2, page 3) in each market should hreflang to the equivalent page number in other markets, not to page 1 of the other markets — linking every paginated URL back to only the root page creates a many-to-one relationship Google may treat as inconsistent. Faceted or filtered URLs (colour=red, size=large) generally should not carry hreflang at all if they're already handled by canonical tags pointing to the unfiltered version; adding hreflang to filtered URL variants multiplies your cluster size for no benefit and increases the chance of errors.

At scale, generate hreflang for product and category URLs directly from your product feed's market/locale mapping so that adding a new country automatically produces correctly reciprocated tags across the whole catalogue instead of requiring per-template edits.

• Give price/currency-only variants their own URLs plus hreflang
• Never rely on IP-based currency switching instead of separate URLs
• Match paginated page numbers across markets, not just page 1
• Skip hreflang on faceted/filtered URLs already handled by canonical

Key takeaways

• ✓Currency-only differences still need separate URLs with hreflang
• ✓Never substitute IP-based localisation for real hreflang URLs
• ✓Keep paginated hreflang pointing to matching page numbers
• ✓Generate catalogue-scale hreflang from the product feed, not templates

Why this lesson matters

This lesson belongs to Monitoring, localisation and content strategy, the part of International SEO where the goal is: keep hreflang healthy over time and decide how deeply to localise content, links and analytics by market.

Read it once, then do it straight away on a real site inside RankTracker. Nothing here is theory for its own sake — every step produces something you can show a client.

Do it now

1. 1Open RankTracker with sample data already loaded, so you are not stuck on setup.
2. 2Track the keywords from this lesson.
3. 3Set up a recurring RankTracker crawl schedule for your hreflang clusters and route alerts to whoever owns each regional site section.