Shopify Markets International SEO: The Complete hreflang Setup Guide

This happens on product pages, collection pages, and standard pages automatically — no additional theme code required.

### The three cases where automatic hreflang breaks

Case 3: Multi-store expansion store setups. If you are running separate Shopify stores for different markets — a common Shopify Plus pattern — each store renders hreflang only for its own domain. The cross-store reciprocal tags (US store pointing to UK store and vice versa) must be added manually, because no single store knows the URL structure of the other.

### Single-store Markets vs. multi-store expansion stores — which approach to use

Single-store Markets (one Shopify store, multiple Markets configured): Simpler to manage. hreflang is partially automated. Recommended for most merchants expanding to 2–5 international markets without fundamentally different catalog or pricing requirements per market.

Multi-store expansion stores (separate Shopify stores per major region): More control over pricing, inventory, and checkout experience per market. Required for some regulatory environments. Significantly more complex SEO management — each store needs its own hreflang setup, sitemap submissions, and Search Console properties. Recommended only when single-store Markets cannot meet your regional requirements.

The comparison of Shopify's platform architecture against alternatives is covered in our Shopify vs. WooCommerce SEO post.

---

## URL structure decisions that affect international SEO

This decision cannot be undone without a redirect migration. Make it deliberately before activating additional markets.

### Subdomain vs. subfolder vs. separate domain — SEO tradeoffs for each

Subfolder (yourstore.com/en-gb/): The Shopify Markets default. Shares domain authority with your primary store. Easier to manage in a single Shopify store. Google treats subfolders as part of the same site and pools domain authority effectively. This is the right choice for most merchants.

Subdomain (uk.yourstore.com): Supported by Shopify Markets with custom domain assignment per market. Each subdomain is treated somewhat independently by Google — it shares trust signals with the root domain but must build its own topical authority. Use when you have a genuine operational reason (separate checkout, separate legal entity) rather than for SEO.

Separate domain (yourstore.co.uk): Treated as a completely separate site by Google. Requires building domain authority independently. Justified when local market trust signals from a country-code TLD are worth the additional SEO work. Also the pattern used in full expansion store setups.

### How Shopify Markets structures URLs by default

In the default Shopify Markets configuration, locale-specific URLs follow this pattern:

You can assign a custom domain to a secondary market in Markets → [Market] → Domains. When you do, Shopify automatically reconfigures hreflang to reference the custom domain instead of the subfolder path.

### When to use language-only codes vs. language-region codes

- You have genuinely different content, pricing, or availability per country

- You are targeting multiple Spanish-speaking or Chinese-speaking markets with distinct storefronts

- You have one storefront for all speakers of that language regardless of country

- You are not targeting multiple variants of the same language

Do not mix language-only and language-region codes in the same tag set for the same language without an x-default. Google will interpret the ambiguity against you.

---

## Implementing hreflang for Shopify Markets (single store)

### Verifying that Shopify is auto-generating hreflang correctly

1. Enable at least one secondary market in Shopify admin → Markets → Add market

2. Navigate to a product page and view source

3. Search for "hreflang" in the source

If the tags are present and correct, Shopify is handling your hreflang automatically for standard pages. Your remaining tasks are: adding x-default (below) and validating in Search Console.

### Adding x-default — the one tag Shopify does not add automatically

x-default tells Google what to show buyers when no locale match exists — typically buyers from countries you have not configured a market for, or users with no detectable locale preference.

{%- comment -%}

x-default hreflang — points to the primary/default store URL.

Shopify does not add this automatically; it must be added manually.

{%- endcomment -%}

rel="alternate"

hreflang="x-default"

href="{{ canonical_url }}"

/>

### Where to place hreflang in theme.liquid for custom pages

For pages that should not be indexed in multiple locales (contact pages, login pages, etc.), you can omit hreflang entirely — Google does not require hreflang on every page, only on pages with genuinely localized content.

### Using Liquid conditionals for template-specific hreflang (product, collection, page, article)

If you need different hreflang behavior on different page types — for example, products have full locale coverage but some standalone pages are English-only — use Liquid template conditionals:

{% comment %} Only output hreflang for product and collection pages {% endcomment %}

{% if template.name == 'product' or template.name == 'collection' %}

{% endif %}

---

## Implementing hreflang for multi-store expansion setups

### Why each store needs reciprocal hreflang tags pointing to the others

This is the rule that most multi-store implementations get wrong. Google requires that hreflang tags be reciprocal: if Store A (US) declares "my UK equivalent is Store B (UK)," then Store B must also declare "my US equivalent is Store A (US)." If only one store declares the relationship, Google ignores the entire tag set.

In a two-store setup (US + UK):

In Store A (US store) theme.liquid:

In Store B (UK store) theme.liquid:

Both tag sets are identical. Both stores declare the full set of alternate locales. This is the correct pattern.

### Building hreflang with Liquid object handles across stores

In a multi-store Liquid implementation, you cannot reference product handles from other stores directly. The practical approach:

- Hardcode the other store's domain

{%- assign us_base = 'https://us.yourstore.com' -%}

{%- assign uk_base = 'https://uk.yourstore.com' -%}

{% if template.name == 'product' %}

href="{{ us_base }}/products/{{ product.handle }}" />

href="{{ uk_base }}/products/{{ product.handle }}" />

href="{{ us_base }}/products/{{ product.handle }}" />

{% elsif template.name == 'collection' %}

href="{{ us_base }}/collections/{{ collection.handle }}" />

href="{{ uk_base }}/collections/{{ collection.handle }}" />

href="{{ us_base }}/collections/{{ collection.handle }}" />

{% endif %}

This assumes handles are consistent across stores (a reasonable assumption if both stores are managed from the same product data source).

### Using snippets to keep theme.liquid clean (render tag approach)

For multi-store setups with 3+ stores, the hreflang block becomes long. Move it to a snippet:

1. Create a new snippet file: Snippets → hreflang-tags.liquid

2. Paste the hreflang Liquid block into the snippet

3. In theme.liquid, replace the block with:

{% render 'hreflang-tags' %}

This keeps theme.liquid readable and lets you update hreflang logic in one place across all template types.

### SKU-based product mapping vs. URL handle mapping

If your multi-store setup uses different URL handles for the same product (e.g., the UK store uses "running-trainers" while the US store uses "running-shoes"), you cannot use the handle-based approach above. You need a mapping layer.

Options:

- Metafield mapping: Store the equivalent product handle from the other store as a metafield on each product. Reference it in the Liquid snippet.

- Manual override: For small catalogs, hardcode the cross-store URL as a product metafield and use that value in the hreflang tag.

- App-based management: Tools like the GWA Hreflang Manager handle this mapping for you — relevant if your catalogs diverge significantly between stores.

Use the Obsess AI hreflang generator to generate the full hreflang tag set for your specific store configuration — it handles the URL structure and locale code decisions and outputs ready-to-paste Liquid snippets.

---

## Sitemap strategy for international Shopify stores

### How Shopify generates sitemaps per locale

Verify your locale sitemaps exist by navigating to the expected URL paths in your browser. If they return a valid XML sitemap, Shopify is generating them. If they 404, the market may not be fully published.

### Submitting separate locale sitemaps to Google Search Console

This is the step most international merchants skip. Submitting locale-specific sitemaps helps Google crawl your international pages faster and associate them with the correct geo-target.

Steps:

2. In each property, submit the locale sitemap. Search Console → Sitemaps → Add sitemap → Enter the locale sitemap URL.

3. For custom domain markets, add a separate Search Console property for the custom domain.

Google's International Targeting report only works at the Search Console property level — which is another reason separate properties per locale are worth the setup time.

### How to verify sitemap coverage per market

After submitting, return to Search Console → Sitemaps for each property. The "Discovered URLs" count should match roughly the number of products, collections, and pages in that market. If the count is significantly lower than expected, there may be indexing issues with the locale-specific pages.

You can also validate your sitemaps programmatically using the free ecommerce SEO audit — it checks whether locale-specific URLs in your sitemap are indexable and correctly canonicalized.

---

## Validating your hreflang implementation

### Using Screaming Frog to check reciprocal hreflang tags

Screaming Frog (the desktop crawler) has a dedicated hreflang section that is the most reliable way to check reciprocal coverage at scale:

1. Configuration → Spider → Crawl → hreflang — enable hreflang crawling

2. Crawl your primary domain

3. Go to hreflang → All hreflang in the results tab

4. Look for the "Missing Reciprocal" column — any URL flagged here has a broken hreflang relationship

The free version of Screaming Frog crawls up to 500 URLs. For larger stores, you will need the paid version (£259/year) or a similar crawling tool.

Common findings in this audit:

- Pages present in hreflang tags but not crawlable (404, noindex, or blocked by robots.txt)

- Hreflang pointing to non-canonical URLs (URLs with query strings that are not the canonical version)

- Missing reciprocals on recently added products that were not in the theme snippet when it was written

### Google Search Console international targeting report

In Search Console, go to Legacy tools and reports → International Targeting. This report shows:

- Country tab — whether your site is targeting a specific country via Search Console's geo-targeting setting (for ccTLD domains) or hreflang

The Language tab will show "No significant hreflang usage detected" if your implementation is missing or incorrectly structured. When hreflang is working correctly, you will see a count of detected languages and a summary of any errors.

Note: Search Console's International Targeting report uses sampled data, not full coverage. Use Screaming Frog for definitive page-by-page validation.

### Common errors: missing reciprocals, wrong locale codes, x-default pointing at wrong URL

Missing reciprocals: Every hreflang relationship must go both ways. The most common cause is updating one store in a multi-store setup without updating the others. Fix: establish a deployment checklist that includes hreflang snippet verification in all stores whenever theme.liquid is updated.

Wrong locale codes: Using "uk" instead of "en-gb" for British English is a common mistake. The correct IETF BCP 47 codes for frequently targeted markets: