November 5, 2026 · 8 min read

Shopify Markets Hreflang Duplicates: Diagnosing and Fixing Duplicate Content Across Currencies and Domains

Shopify Markets auto-generates hreflang tags, but currency-only markets, SEO app conflicts, and untranslated content still cause duplicate indexing.

Shopify Markets Hreflang Duplicates: Diagnosing and Fixing Duplicate Content Across Currencies and Domains

Shopify Markets auto-generates hreflang tags through content_for_header for every market that has its own subfolder, subdomain, or domain. The duplicate-content problems merchants hit are almost never caused by a missing feature; they are caused by a gap between what Markets can generate automatically and what the store's configuration actually delivers. Know the three failure modes (currency-only markets with no URL, conflicting tags from SEO apps, and untranslated content that makes Google ignore the signal) and you can resolve every GSC report cleanly.

Key takeaways

  • Markets injects hreflang only when a market has a distinct URL (subfolder, subdomain, or ccTLD). A currency-only market produces no hreflang at all.
  • The "Duplicate, Google chose different canonical than user" GSC error almost always means content is identical across URLs, not that hreflang itself is broken.
  • SEO apps and translation apps (Weglot, SEO Manager, Plug In SEO) frequently emit their own hreflang on top of Shopify's auto-output, creating conflicting annotation sets.
  • Canonical tags and hreflang must agree. A canonical pointing to a different-language version causes Google to ignore hreflang entirely.
  • Subfolders are the right default for most stores. Switching URL structure after launch costs 4 to 8 weeks of re-crawl time.

How Shopify Markets actually outputs hreflang

Shopify injects <link rel="alternate" hreflang="..."> tags via the content_for_header Liquid object, which every theme renders inside the <head> of layout/theme.liquid. You do not write those tags manually. The platform uses BCP 47 locale identifiers: a country-specific market like Canada/English produces en-CA, a broader language-only market produces en. It also appends an x-default tag, but only when you have a primary market configured in Markets settings.

What this means in practice:

  • If content_for_header is missing from layout/theme.liquid (common in heavily customized legacy themes), no hreflang is ever output.
  • If you have installed an SEO app that rewrites the <head> block, it may silently strip or duplicate Shopify's injected tags.
  • Subdomains (gb.yourstore.com) and ccTLDs (yourstore.co.uk) require each alternate tag to use a fully qualified absolute URL spanning separate origins. Each origin must also be verified as a property in Google Search Console, or GSC cannot confirm the cross-origin alternates.

The currency-only market trap

This is the most common and least obvious failure mode. Shopify lets you create a market that changes currency and local pricing while keeping visitors on exactly the same URLs as your primary market. That is commercially useful but it is an SEO dead end: no distinct URL means no hreflang is generated, and search engines never learn that market exists as a separate entity.

One real-world pattern I see repeatedly on stores with 500+ SKUs: a merchant adds an AUD market for Australia, leaves the domain structure on "same as primary," and then wonders why Australian organic traffic stays priced in USD and why GSC shows zero coverage for /en-au/. The answer is that there is no /en-au/. The fix is to assign a subfolder or subdomain to that market inside Settings > Markets > [Market name] > Domains.

Rule: A currency-only market (no distinct URL assigned) produces no hreflang output and no indexable page. It is invisible to search engines.

Diagnosing the GSC error: "Duplicate, Google chose different canonical than user"

This error is the most common symptom merchants report. A developer ran this audit on a store in October 2026 and found around 400 URLs flagged under this status. The pattern was consistent: a market subfolder existed (say /en-us/) but the product descriptions, meta titles, and collection copy were word-for-word identical to the primary market. Google looked at both URLs, decided the content was the same, picked the primary URL as canonical, and filed the market version as a redundant duplicate.

Hreflang itself was technically present and valid. That does not matter when the content signals override it. Google evaluates visible content, not just tags. Translating navigation and meta descriptions while leaving the main product body unchanged still leaves a duplicate page.

Diagnostic checklist

  1. Open GSC > Indexing > Pages > filter by "Duplicate, Google chose different canonical."
  2. Export the URL list. Group by template type: product, collection, page.
  3. For each URL, run a view-source diff against the primary-market equivalent. Count how many characters of the <body> differ.
  4. Check the <head> of one affected URL for duplicate hreflang clusters (two sets of <link rel="alternate"> with different href values for the same locale).
  5. Check that the market URL's <link rel="canonical"> self-references, not the primary-market URL.

If step 3 shows near-zero body diff: the problem is content, not tags. If step 4 shows two clusters: the problem is app conflict. If step 5 shows canonical pointing elsewhere: the problem is canonical misconfiguration.

URL structure comparison

StructureExampleHreflang auto-generated by MarketsGSC properties neededTrade-off
Subfoldersstore.com/en-gb/Yes, fully automatic1 (root domain)Easiest to manage; all authority on one domain
Subdomainsgb.store.comYes, but cross-origin alternates must use absolute URLs1 per subdomainClear separation; crawl budget split
ccTLDsstore.co.ukPartial; each domain is a separate origin1 per domainStrongest geo-signal; highest maintenance overhead
Currency-only (no URL)store.com (unchanged)NoneN/AZero SEO visibility for the market

Subfolders are the recommended default. They consolidate domain authority, require a single GSC property, and are the structure Shopify's automatic generation handles most reliably. Switching structure after launch requires 301 redirects, sitemap updates, and resubmission to GSC, with a re-crawl window of roughly 4 to 8 weeks.

App conflict: when two sources output hreflang simultaneously

This is the second most common failure mode in stores that have been running for more than a year. Apps like SEO Manager, Plug In SEO, and Weglot each have their own hreflang generation logic. When you enable Shopify Markets auto-generation and leave the app's hreflang output enabled, every page ends up with two full sets of <link rel="alternate"> clusters. The two sets often disagree on locale codes or point to different URL shapes.

Google has been explicit that duplicate hreflang annotations are harmful to international rankings. The fix is binary: pick one source and disable the other.

  • Shopify auto-generation is on (default): Go into the app settings and disable its hreflang output. For Weglot specifically, you must explicitly disable Shopify's automatic hreflang tags under Online Store > Preferences > Social sharing and SEO to avoid double-output, because Weglot generates its own cluster from its translated URL structure.
  • Custom Liquid is the source: Turn off automatic tags at Online Store > Preferences, then build your own tags dynamically from the localization object (see snippet below). Never hardcode locale strings or handles, because a resource handle can differ per language.
{% comment %} Manual hreflang - only use when auto-generation is OFF {% endcomment %}
{% if localization.available_languages.size > 1 or localization.available_countries.size > 1 %}
  {% for language in localization.available_languages %}
    <link rel="alternate"
      hreflang="{{ language.iso_code }}"
      href="{{ request.origin }}{{ request.path }}">
  {% endfor %}
  <link rel="alternate" hreflang="x-default"
    href="{{ shop.url }}{{ request.path }}">
{% endif %}

This is a simplified starting point. For multi-language markets you need to combine locale.iso_code with country.iso_code to produce the correct en-CA / en-GB format. The localization object is a global Liquid object available on every template, so this snippet in theme.liquid covers every page type automatically.

The x-default gap

Shopify adds x-default only when a primary market is explicitly configured. If you removed the primary market designation or migrated markets without resetting it, every page on the store is missing x-default. This is easy to miss because the other hreflang tags render fine. Check it with a simple view-source on the homepage: search for x-default and confirm it points to your root domain, not to a subfolder.

After any Markets configuration change (adding a market, removing a language, changing domain assignment) resubmit sitemap.xml in GSC and monitor the Coverage report. Shopify's sitemap includes all market URLs when Markets is active, but the re-crawl after a configuration change is not instant.

Content localization: the layer hreflang cannot replace

Hreflang signals intent; it does not override Google's content evaluation. If your en-US and en-AU product pages differ only in the currency symbol and a URL prefix, Google will collapse them into one canonical and ignore the hreflang. The hreflang annotation is a hint, not a directive.

Practical localization beyond currency that makes the content genuinely distinct:

  • Shipping lead times and carrier names ("arrives in 2 business days via Royal Mail" vs "ships in 3 days via USPS")
  • Duty and import-fee disclosure copy (especially post-UCP-08 changes in 2026)
  • Sizing conventions (UK 10 vs US 8 vs EU 38 for clothing)
  • Regional return and refund policy wording
  • Market-specific pricing callouts and promotional copy

Shopify stores translations via the Translate & Adapt API. The API stores a translated value for every content field (product title, description, meta title, meta description, image alt text) alongside the original, without duplicating the product record. The hreflang tag for a market URL is correct only when that URL's content has actually been localized through the API. Products with untranslated content may not get correct hreflang output from Markets.

Verification steps after any fix

  • View-source on a product page in each market subfolder. Confirm one <link rel="alternate"> cluster exists (not two), that every market is represented including x-default, and that every URL in the cluster is absolute and returns a 200 (not a redirect).
  • Hreflang reciprocity. Every alternate URL must itself list all the other alternates. A missing back-reference invalidates the entire cluster. Tools like hreflangchecker.com crawl across all alternates and flag broken reciprocity.
  • GSC URL Inspection on one URL per market template. Confirm the page is indexable and that Google's "Detected" canonical matches the <link rel="canonical"> you declared.
  • Sitemap audit. Confirm that sitemap.xml lists URLs for every active market. If a market URL is missing from the sitemap, resubmit after the Markets configuration is saved.
  • Screaming Frog with all market subdomains in crawl scope. Export the hreflang report and filter for missing x-default, non-reciprocal pairs, and alternates that resolve to a redirect.

For a worked example of debugging a 10,000-SKU catalog across five markets, see the case studies section of this site. The diagnosis sequence there applies directly to any store where the GSC duplicate count is in the hundreds.

The GSC International Targeting report was deprecated in 2023, so do not rely on it. The Coverage and Indexing reports, combined with direct URL Inspection, are now the right diagnostic tools for hreflang issues on Shopify.

Teams without in-house Shopify developers can bring this to Lintel, my Shopify engineering studio, for Shopify performance and technical SEO.

Frequently asked questions

Does Shopify Markets generate hreflang tags automatically?

Yes, for markets that have a distinct URL (subfolder, subdomain, or domain) assigned in Markets settings. Shopify injects the tags via the content_for_header object in layout/theme.liquid. A market configured only to change currency, with no distinct URL, produces no hreflang output at all.

Why does Google Search Console show 'Duplicate, Google chose different canonical than user' for my market URLs?

Almost always because the content on the market URL is identical to the primary market URL. Hreflang is a hint, not a directive; when Google finds no meaningful content difference between two URLs, it picks one canonical and ignores the other. Localizing product descriptions, meta titles, and regional details like shipping and sizing resolves this.

How do I stop my SEO app and Shopify Markets from both outputting hreflang?

Pick one source and fully disable the other. If you rely on Shopify's automatic generation, turn off hreflang output in your SEO or translation app's settings. If you rely on a custom Liquid snippet or an app, turn off automatic tags at Online Store > Preferences > Social sharing and SEO. Never run both simultaneously.

Seven years of Shopify, on one page.

Roles, projects, stack and certifications are on the resume.

Resume Download PDF LinkedIn