Shopify International SEO — hreflang, Markets and multi-language setup

When international SEO becomes necessary

Most Shopify stores start with a single market and discover the need for international SEO when one of three things happens: organic traffic data in Google Search Console shows significant impressions from countries that aren’t the store’s primary market; a decision is made to launch Shopify Markets for a new region; or the store starts seeing the wrong regional version ranking in target markets.

The clearest signal that international SEO is overdue is rank leakage — your US store’s pages ranking in the UK instead of or ahead of a UK-specific version you’ve created. This typically happens because both versions share nearly identical content, hreflang is missing or misconfigured, and Google chooses the URL with more authority rather than the more regionally appropriate one.

A second common trigger is currency confusion. Shopify Markets can display localised prices, but if the SEO configuration isn’t correct, Google may index the converted-price version alongside the localised version, creating duplicate page issues and confusing price schema in rich results.

The practical rule: if more than 10% of your organic traffic comes from markets outside your primary country, or if you’ve activated Shopify Markets for any additional region, international SEO configuration is not optional.

URL structure options: subfolders, subdomains, or separate domains

The three URL structure options for Shopify international SEO each have meaningful tradeoffs.

Shopify Markets natively supports subfolders and subdomains. Separate domain setups require more complex configuration and are only recommended when the international market genuinely justifies the operational cost.

For most stores, the answer is simple: use subfolders. Configure Shopify Markets to create /en-gb/, /de/, /fr/ subfolders rather than subdomains. This keeps all domain authority on a single domain, consolidates backlink value, and gives Google a clear site architecture signal.

Step-by-step Shopify Markets setup for SEO

The order of configuration matters. Setting up markets in the wrong sequence creates URLs you then have to change, which requires redirects.

Step 1: Plan your URL structure first. Decide on subfolder codes before activating any market. Use ISO 639-1 language codes combined with ISO 3166-1 country codes where needed: en-gb for British English, de for German, fr for French, en-au for Australian English.

Step 2: In Shopify Admin, go to Settings > Markets. Create the new market, assign the target countries, and set the primary language for that market.

Step 3: Configure the domain/subfolder. In the market settings, enable the localised subfolder option. Shopify will generate the subfolder URL structure automatically based on the market’s primary language.

Step 4: Activate Shopify Translate & Adapt (or a third-party translation app such as Langify or Weglot). Publish translated content for the new market. Do not publish a market with untranslated content — a German market with English content creates near-duplicate pages that Google will canonicalise to the English version.

Step 5: Verify sitemap inclusion. After activating a market, view /sitemap.xml. Each market version of pages should be present. If market URLs are missing from the sitemap, Google cannot discover them efficiently.

Step 6: Verify hreflang output. View the page source of the homepage in each market version. Search for hreflang. All market versions plus x-default should appear.

Working hreflang code example: US default, UK, and Germany

For a store with a US default version, a UK English version, and a German version, the complete hreflang set on every page looks like this:

<link rel="alternate" hreflang="x-default" href="https://store.com/products/example" />
<link rel="alternate" hreflang="en" href="https://store.com/products/example" />
<link rel="alternate" hreflang="en-GB" href="https://store.com/en-gb/products/example" />
<link rel="alternate" hreflang="de" href="https://store.com/de/products/example" />

This set must appear identically on all four URLs: the default US page, the en-GB page, and the de page. The x-default tag on all pages points to the same fallback URL (the US/default version). The en tag covers English-language searchers not matched by a more specific regional tag.

If Shopify Markets generates these tags automatically, they should match this pattern. If they don’t — particularly if x-default is missing — the tags need to be added manually via the theme’s <head> section or an SEO app that supports hreflang injection.

The 7 most common hreflang errors on Shopify stores

1. Missing x-default tag. The most common error. Fix: add <link rel="alternate" hreflang="x-default" href="[your-primary-URL]" /> to every page. Identify it: search for “hreflang” in page source — if x-default doesn’t appear, it’s missing.

2. Non-reciprocal hreflang pairs. Page A lists Page B as an alternate, but Page B doesn’t list Page A. Google ignores non-reciprocal pairs entirely. Identify it: Screaming Frog’s hreflang report shows non-reciprocal pairs. Fix: ensure every hreflang set appears on every URL in the set.

3. Incorrect locale codes. Common examples: en-UK (wrong — should be en-GB), zh when you need zh-Hans or zh-Hant, pt when you need pt-BR (Brazilian Portuguese) or pt-PT (European). Fix: cross-reference against the IANA language subtag registry.

4. Hreflang on noindex pages. If a page is noindexed, hreflang on that page sends conflicting signals. Google can’t index a noindexed page but is being told it’s a valid alternate. Identify it: cross-reference hreflang URLs against your list of noindexed pages. Fix: ensure all URLs referenced in hreflang sets are indexable.

5. Pointing to redirected URLs. Hreflang URLs that return 301 or 302 responses waste crawl budget and weaken signal attribution. Fix: audit hreflang URLs in Screaming Frog to identify any that return 3xx responses rather than 200.

6. Hreflang only on product pages, missing on collection pages. Markets set up hreflang at the product level but collection pages often lack it, meaning collection-level queries return the wrong market version. Identify it: manually check a collection page in each market. Fix: verify hreflang output on collection pages, not just product pages.

7. Duplicate hreflang for the same locale. Two en-GB tags pointing to different URLs on the same page. This creates contradictory signals. Identify it: view page source and count hreflang tags for each locale — there should be exactly one per locale. Fix: audit page source for duplicate locale codes and remove or consolidate.

How to test hreflang implementation

Manual page source check: Right-click > View Page Source on key pages. Search for hreflang. Count the tags — you should see exactly one tag per market version plus one x-default. Repeat on the corresponding page in each market version to confirm reciprocal tags.

Screaming Frog hreflang audit: Set Screaming Frog to crawl the site and enable the hreflang report (Bulk Export > Hreflang > All Inlinks). This generates a complete audit of: missing x-default, non-reciprocal pairs, incorrect locale codes, and hreflang URLs returning non-200 status codes. Run this audit before launch and after any market configuration changes.

Google Search Console International Targeting report: In GSC, navigate to Legacy Tools and Reports > International Targeting. The Language tab shows detected hreflang usage and flags errors such as missing return tags and missing x-default. Note: this report only shows data after GSC has crawled the hreflang tags and can lag 2-4 weeks after implementation. Don’t rely on it for immediate post-launch validation — use Screaming Frog for that.

Currency localisation and thin content

A common mistake is activating a regional market with localised pricing but leaving English content unchanged. Shopify displays the correct currency, but the page content — product descriptions, collection text, meta titles — remains in English.

From an SEO standpoint, this creates near-duplicate content: two pages with identical text but different URLs and currency display. Google will typically canonicalise to the version with more authority (usually the default market) and stop indexing the regional version.

For markets where the target query language differs from the default (German, French, Spanish, Japanese), content must be translated — not just currency-converted. Machine translation without human review creates thin, unnaturally phrased content that Google’s quality systems increasingly identify and discount.

The minimum viable localisation for SEO purposes: translated product titles, translated product descriptions, translated meta titles and descriptions, and translated collection page text. Supporting content (blog posts, size guides, FAQs) can be prioritised after the core commercial pages are localised.

Google’s documented guidance on international URL structures

Google’s international SEO documentation is explicit on several points worth understanding directly. All three URL structures (subfolders, subdomains, separate domains) are supported — none is inherently preferred from a ranking standpoint. Subfolders are recommended as the simplest to implement and maintain. Hreflang is the primary signal Google uses to determine which version to serve; it carries more weight than geotargeting settings configured in Search Console.

Language targeting (hreflang="de" without a country code) is appropriate when content is translated but not country-specific. Regional targeting (hreflang="de-AT" for Austrian German) is appropriate when content is customised for a specific country.

Google also documents that hreflang is a hint, not a directive. The search engine uses it as one signal among several. A store with correctly configured hreflang but thin or machine-translated regional content will still see poor rankings in regional markets. Hreflang solves the “which version to show” problem; content quality determines whether that version ranks at all. Both must be addressed for international SEO to deliver measurable organic traffic improvements.