Map language, region and commercial requirements
Give each market URL a defined language, currency, product specification and fulfilment responsibility. The US, UK and France examples require different commercial checks even when their photographs match. Treat equivalent-page annotations as a later validation step against real published destinations rather than a substitute for market readiness.
Worked example — illustrative data.
| Destination | Language and currency | Commercial check |
|---|---|---|
| /en-us/lamps/arc/ | English; USD | US delivery and electrical specification |
| /en-gb/lamps/arc/ | English; GBP | UK delivery and compatible plug |
| /fr-fr/lampes/arc/ | French; EUR | Translated content and France delivery |
Start with the markets the business actually serves. Give each version an owner for translation, catalog, policy and price maintenance. Record which URLs are equivalent and which products are unavailable in a market. A language selector should let the shopper reach the relevant version deliberately. Review annotations against the real published destinations after the pages exist, rather than generating them from a list of country names.
Similar photographs can hide incompatible market products
The US product may have no compatible UK equivalent. Do not claim the pages are interchangeable merely because the photographs match. Explain the restriction and offer a useful alternative or market destination.
Approve the three destinations only when product fit, fulfilment and language support are confirmed. Keep an unsupported country out of the selector until its buyer journey is defined.
Continue with Guides for stores, software teams and local businesses, International SEO for online stores and SaaS and Plan Adobe Commerce store views.
For regional and language destinations, see Google multilingual-site guidance (checked November 2026).