- Give each target market its own crawlable URL, usually a subfolder such as
/en-ca/, with prices, currency, shipping and returns that match that market. Do not rely on geolocation to swap content on one URL, because Googlebot usually crawls from the U.S. and will mostly see the U.S. version. - Use hreflang to tell Google which URL serves which language and country. Every version must list itself and all the others, with valid ISO codes and an x-default. Shopify Markets generates this for you; other platforms usually need a plugin or custom code.
- Keep each market consistent across the page, the structured data and the Merchant Center feed: same price, same currency, same availability. Then measure each market separately in Search Console and GA4.
When does a U.S. store need international SEO?
You need it once you build a version of the store for another country or language. Signs it is time:
- Search Console’s Performance report, filtered by country, shows steady impressions and clicks from outside the U.S.
- GA4 shows international sessions that convert poorly, often because prices are in USD, shipping is unclear or the product is not available there.
- You have decided to ship to a new country with local pricing, duties handled and a returns process.
If you only ship abroad occasionally, with USD prices and no local version, you need clear shipping information, not hreflang.
Which URL structure should an international store use?
Google’s documentation lists four options. Shopify Markets supports the first three.
| Structure | Example | Strengths | Trade-offs |
|---|---|---|---|
| Subfolder on your main domain | example.com/en-ca/ |
Shares the main domain’s authority; easy to set up and maintain | Weaker local signal than a country domain |
| Subdomain | ca.example.com |
Easy to set up; can be hosted separately | May be treated more like a separate site; users may not know if “ca” means a language or a country |
| Country-code domain | example.ca |
Clearest country signal | Costly; each domain is managed separately and builds its own authority |
| URL parameter | example.com?loc=ca |
None worth having | Google does not recommend it |
For most U.S. stores expanding abroad, subfolders are the practical default. Shopify recommends them for most stores, and they share the authority your main domain already has.
How does hreflang work, and what are the rules?
Hreflang tells search engines which URL is meant for which language, and optionally which country, so Google can show the Canadian page in Canada and the U.K. page in the U.K. Google says it does not use hreflang to detect a page’s language, so the content itself must be in that language.
The rules from Google’s documentation:
- Pick one method. HTML link tags in the head, HTTP headers, or the XML sitemap. Google treats them as equivalent, and using more than one adds nothing.
- Every version lists itself and all others. If page A points to page B but B does not point back, the annotations can be ignored.
- Use valid codes. Language in ISO 639-1 format, optionally followed by a region in ISO 3166-1 Alpha 2 format. A region on its own is not allowed.
- Add x-default. It names the fallback page for users whose language or country matches none of your versions, often your main store or a country selector.
- Use fully qualified URLs, including https.
Here is an illustrative set for a product sold in the U.S., Canada (English and French) and the U.K.:
<link rel="alternate" hreflang="en-us" href="https://example.com/products/wool-throw" />
<link rel="alternate" hreflang="en-ca" href="https://example.com/en-ca/products/wool-throw" />
<link rel="alternate" hreflang="fr-ca" href="https://example.com/fr-ca/products/wool-throw" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/en-gb/products/wool-throw" />
<link rel="alternate" hreflang="x-default" href="https://example.com/products/wool-throw" />
The same block appears on all four pages. Note en-gb, not en-uk: the ISO code for the United Kingdom is GB.
How does hreflang interact with canonical tags?
Each market version should carry a self-referencing canonical tag, and hreflang should point only to those canonical, indexable URLs. If the Canadian page canonicalizes to the U.S. page, you are telling Google they are the same page while hreflang says they are alternatives. Shopify Markets sets a self-referencing canonical for each market version, so market pages are treated as related but distinct.
What does Shopify Markets do for international SEO?
Based on Shopify’s help center:
- Hreflang is automatic. Shopify generates hreflang tags from your market and language settings and adds them to every page. It includes a language-only tag per market and an x-default. It can be turned off in Online Store preferences, but Shopify warns this can hurt SEO unless you replace it.
- URLs per market. Each market can use a subfolder, a subdomain or a country domain.
- New markets may share your main URLs. Since May 2023, new single-country markets default to the same URL structure as the primary market. That means no separate URL and no hreflang for that market until you set up a subfolder or domain for it. If you want a market to rank on its own, give it its own URL.
- Canonicals and sitemaps. Each market version gets a self-referencing canonical, and the sitemap includes market URLs with hreflang annotations.
- Product availability per market. A product excluded from a market returns a 404 at that market’s URL, for shoppers and crawlers.
- Redirects spare crawlers. Shopify’s automatic redirection applies to customers; known search engine crawlers get the URL they asked for.
- Local currency needs the right payment provider. Shopify says selling in local currencies is only supported with Shopify Payments or Adyen, and manual exchange rates require Shopify Payments.
Translate with Shopify’s Translate & Adapt app or a translation app, and review machine translations. For English-language markets, adapt spelling, sizes, units, shipping promises and return terms.
What about WooCommerce and Magento?
WooCommerce has no built-in hreflang. Multilingual plugins such as WPML or Polylang add language versions and hreflang, and multi-currency usually comes from another plugin. Check that currency switching does not create crawlable parameter URLs.
Magento / Adobe Commerce uses store views for countries and languages, and hreflang typically comes from an extension or custom code. On either platform, crawl one product per market after setup and confirm the hreflang set is complete and reciprocal.
How should prices and currencies appear to search engines?
Keep price, currency and availability the same everywhere Google reads them.
- On the page: show the local price and currency in the HTML, not only after a script runs.
- In structured data: the Offer’s
priceandpriceCurrencymust match the page, for example CAD on the Canadian version. See our guide to product schema for ecommerce. - In Merchant Center: each target country needs product data with the right price, currency and landing page URL in Google Merchant Center. Our guide to Google Shopping feed optimization covers feed setup.
- No IP-based content swaps. Google advises against using IP analysis to adapt content and against automatically redirecting users between language versions. Googlebot usually crawls from the U.S. If the Canadian price only appears after IP detection, Google may never see it. Use a banner that suggests the right version and lets the shopper choose.
Which international SEO errors are most common?
| Error | What happens | Fix |
|---|---|---|
| Missing return links | Hreflang annotations can be ignored | Generate the full set on every version |
Invalid codes such as en-uk |
Tag is ignored | Use ISO 639-1 plus ISO 3166-1 Alpha 2, such as en-gb |
| Hreflang points to redirected or noindexed URLs | Conflicting signals | Point only to canonical, indexable 200 URLs |
| Market version canonicalizes to the U.S. page | Market page may not be indexed | Self-referencing canonical per market |
| IP redirects on every visit | Crawlers and travelers see only one version | Suggest, do not force; exclude crawlers |
| Same-language pages identical except for currency | Google may pick one version | Localize prices, shipping, returns and spelling, and keep hreflang |
Worked example: adding Canada and the U.K. to a U.S. Shopify store
All numbers are illustrative.
A U.S. home goods brand gets 8% of organic clicks from Canada and 5% from the U.K., with weak conversion because prices show in USD. It decides to sell in both with local pricing.
- Markets: create Canada and United Kingdom markets, with subfolders
/en-ca/,/fr-ca/and/en-gb/. - Payments: confirm Shopify Payments is active so local currencies work, and decide which products get fixed local prices instead of converted ones.
- Catalog: exclude three oversized products that cannot ship to the U.K. Their U.K. URLs will return 404, so remove links to them there.
- Content: translate the Canadian French version and review it. Adapt U.K. spelling, sizes and delivery promises.
- Checks: crawl one product, one collection and the homepage in each market. Confirm the full hreflang set (every market version plus x-default), self-referencing canonicals, local prices in the HTML and matching
priceCurrencyin the markup. - Feeds: add Canada and the U.K. as target countries in Merchant Center with local prices.
- Measure: filter Search Console by country and by subfolder, and compare each market’s organic revenue in GA4 against the cost of serving it.
International eCommerce SEO checklist
- [ ] Each target market has its own crawlable URL, ideally a subfolder.
- [ ] Hreflang comes from one source, lists every version on every page and includes x-default.
- [ ] All codes are valid ISO language plus optional region codes.
- [ ] Each market version has a self-referencing canonical.
- [ ] Hreflang targets return 200 and are indexable.
- [ ] Local prices and currency appear in the HTML, the markup and the Merchant Center feed.
- [ ] Shipping, duties and returns are explained for each market.
- [ ] No forced IP redirects; crawlers get the URL they request.
- [ ] Translations are reviewed by a fluent speaker.
- [ ] Search Console and GA4 reports are segmented by market.
FAQ
Do I need hreflang if every version is in English?
Yes, if you have separate U.S., Canadian and U.K. versions. Without it, Google may treat them as near-duplicates and show the wrong country’s page. Hreflang, plus real differences in price, currency and shipping, helps it choose.
Will a subfolder for Canada take traffic from my U.S. pages?
Hreflang is meant to show each country its own version, not to split rankings. Watch Search Console by country after launch to confirm.
Is automatic currency conversion enough for SEO?
Converting prices on one URL by visitor location gives Google little to work with, because Googlebot usually crawls from the U.S. Separate market URLs that show local prices in the HTML are clearer for search engines and for shoppers.