Regions
Sell in multiple countries with local currencies, languages, and domains.
Regions let you serve different countries from a single storefront channel. Each region has its own country, language, currency, and domain or URL prefix.
How regions work
A region belongs to one storefront channel. When a customer visits your site, the system detects which region to show based on the domain and URL path. Prices display in the region's currency, and content appears in the region's language.
For example, a retail channel might have three regions:
| Region | Domain | Currency | Language |
|---|---|---|---|
| UK | yourstore.co.uk | GBP | English |
| US | yourstore.com | USD | English |
| Spain | yourstore.com/es-es | EUR | Spanish |
Adding a region
Go to Channels, select your storefront channel, and click Add region. Choose the country, language, currency, and assign a domain.
URL structure
The system generates URLs automatically based on your region setup:
- One region on a domain: No prefix.
yourstore.co.uk/browse/rings - Multiple regions on one domain: A prefix like
/es-es/is added for non-default regions.yourstore.com/es-es/browse/rings - Each region on its own domain: No prefix needed. The domain identifies the region.
You choose the domains. The system handles the rest.
Default region
Every store has one default region. This is the fallback when no other region matches, and it provides the canonical URLs for search engines. The default region never gets a URL prefix, even on a shared domain.
Currency conversion
Prices are converted to each region's currency using exchange rates plus the conversion margin you set. Converted prices are baked into the page at build time, so customers see local prices instantly with no loading delay.
See Currency for details on conversion settings.
SEO and search engines
The system handles international SEO automatically. You do not need to configure any of this, but understanding how it works helps you verify your regions are indexed correctly.
Canonical URLs
Every region page is canonical to itself. The UK page for "Rings" points its canonical tag to the UK URL, the Spain page points to the Spain URL, and so on. Search engines treat each region as a distinct page because the content differs (language, currency, or both).
A region page never sets its canonical to another region. That would tell Google to ignore the local version, which defeats the purpose of having regions.
hreflang tags
Every page includes hreflang tags that link all region variants of that page together. These tags tell search engines which version to show for each country and language.
For example, your UK rings page would include tags pointing to the US version, the Spain/Spanish version, and the Spain/English version. Every region's page includes the same complete set of tags, including a tag pointing to itself.
This is how Google knows that yourstore.co.uk/browse/rings and yourstore.com/browse/rings are the same page for different audiences, rather than duplicate content.
x-default fallback
One special tag, x-default, tells Google which page to show when a visitor's language or country does not match any of your regions. This always points to your default region.
Sitemaps
Each domain gets its own sitemap with hreflang annotations baked in. If you have regions on two domains, both sitemaps cross-reference each other so Google can verify the relationships.
What you should check
After setting up regions, verify in Google Search Console under the International Targeting report that Google recognises your hreflang tags. Changes can take 3 to 7 days to appear. If you see warnings about missing return links or invalid tags, contact support.