Discussion
  • International SEO
  • Shopify SEO
  • Site Architecture

Shopify Markets with subfolders: which hreflang, currency or duplication issues hit you, and did you override Shopify’s defaults?

Published 1 reply

Discussion starter: an international SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    On most stores, the hreflang tags Shopify generates are not the problem, and I would not replace them. The issues that actually cause trouble with Markets on subfolders sit around the tags: same-language markets that are near-identical apart from currency, prices that disagree between the page, the structured data and Merchant Center, and hreflang being emitted for versions that are not really localised or available.

    So the useful overrides are usually about scope and content, not the tag engine. Decide which countries deserve their own subfolder, make those versions genuinely different where it matters to buyers, and fix the theme or app markup that gets currency wrong. Turning off automatic hreflang is a last resort for stores with a mapping Shopify cannot express and a developer who will maintain the replacement.

    What Shopify does by default, and where that stops

    Shopify’s help page on international SEO for markets describes the defaults clearly:

    • Hreflang tags “are generated automatically based on your market and language configuration”, using a language code plus an optional region code.
    • An x-default tag points to the primary domain.
    • Each market version gets a self-referencing canonical, with hreflang connecting the versions.
    • Sitemaps include the market URLs, with hreflang annotations on each URL.
    • “Automatic redirection applies to customers, but search engine crawlers are excluded”, so crawlers get the URL they request.
    • You can turn off automatic hreflang if you manage tags yourself, but Shopify warns this “can negatively affect your store’s SEO”.

    That covers the mechanics most custom builds get wrong: return links, self-canonicals and crawler-safe redirects. What it does not do is make your market versions different from each other, check what your theme or apps put into structured data, or know whether your French subfolder is 30% translated. Those gaps are where the real issues come from.

    Why hreflang does not remove same-language duplication

    Shopify’s page frames hreflang as telling search engines the versions are “related but distinct pages for different audiences, not duplicate content”. That is true as far as routing goes. Google’s long-standing international guidance is more nuanced: same-language pages for different countries are generally acceptable, and hreflang helps Google show the right URL to the right searcher, but Google can still group near-identical pages and choose one as canonical.

    Think of hreflang as the address labels on identical parcels. The labels tell the courier which copy goes to which country, but they do not make the parcels different. Google may keep one copy in its main index and still deliver the right label to each country. Technically, Google clusters pages it considers duplicates, picks one canonical for the cluster, and can then use hreflang to swap the displayed URL for the searcher’s locale.

    That is why stores with /en-au/, /en-nz/, /en-gb/ and /en-us/ often see market URLs under “Duplicate, Google chose different canonical than user” in Search Console. This is not automatically harmful. It becomes harmful when the swap does not happen and New Zealand searchers land on Australian pages with the wrong currency, shipping promise and returns information.

    Watch for this:

    Search Console generally reports performance against the Google-selected canonical. If Google folds /en-nz/ into /en-au/, the NZ market can look almost invisible in Search Console even when NZ users are landing on NZ URLs. Check analytics landing pages by country before concluding the market is failing.

    The three issues that come up most

    1. Same-language markets that differ only by currency

    Hypothetical example:

    An Australian homewares store runs AU English at the root and adds /en-nz/, /en-gb/ and /en-us/. Product copy, collections and reviews are identical across all four. Only the price and currency change. Google indexes the root versions, most /en-nz/ product URLs show as duplicates with the root chosen as canonical, and the UK versions index patchily. UK sessions from organic search split between /en-gb/ and the AU root, and the AU-root sessions convert poorly because the price is in AUD and the delivery message is Australian.

    There are two honest fixes. The first is to make the versions differ in ways buyers care about: spelling for US English, sizing conventions, delivery times, duty and tax messaging, returns terms, local reviews and payment options. Shopify’s own page recommends adapting content per market rather than stopping at word-for-word translation. The second is to stop creating subfolders for markets you will not localise. Selling to New Zealand from the Australian URL set is a legitimate choice if NZ is small, at the cost of NZ searchers seeing AUD pricing.

    2. Currency and price consistency

    The visible price, the Product structured data and the Merchant Center feed have to agree for each market. The common failures:

    • Theme or app JSON-LD in the wrong currency. A theme that hard-codes priceCurrency, or an SEO app that injects markup using the shop’s base currency, produces GBP visible prices with AUD markup on /en-gb/. Fix the markup rather than removing it: every Offer needs a price for merchant listing eligibility.
    • Tax display. Merchant Center expects GST-inclusive prices in Australia and VAT-inclusive prices in the UK. A market that shows ex-tax prices creates mismatches.
    • Converted prices that move. If market prices are converted automatically, the page price can shift with exchange rates or rounding rules while the feed lags. Fixed market prices, where your setup supports them, are more stable for Shopping.
    • Third-party geolocation apps. Shopify excludes crawlers from its own redirection. A separate app that redirects or overlays by IP may not, and Googlebot crawls mostly from US addresses.

    3. Hreflang pointing at versions that are not real

    Shopify generates hreflang from configuration, not from quality. If you publish French with half the product catalogue still in English, the French hreflang points at pages that are mostly English, which invites Google to treat them as duplicates. If you restrict products by market, crawl the alternates for excluded products and confirm they do not return 404s or redirects. And if a theme or app also outputs hreflang, you can end up with two sets, sometimes conflicting. That double-output scenario is the main reason Shopify offers the switch-off.

    Which defaults I would keep and which I would override

    Default Usual decision When to change it Main risk of changing it
    Automatic hreflang Keep You must exclude unlocalised languages or unavailable products, or combine Shopify with versions on another platform You now own return links, x-default and every future theme or market change
    Self-canonicals on market URLs Keep Almost never. Canonicalising market pages to the primary version conflicts with hreflang. Market URLs drop out of the index, and hreflang signals get ignored
    x-default to the primary domain Keep Only if the primary market is a poor fallback for unmatched visitors Changing the primary market affects far more than SEO
    Crawler exclusion from redirects Keep Never for crawlers. For customers, a banner with a country selector is kinder than a forced redirect. Forced redirects frustrate travellers and VPN users
    A subfolder for every market Override the scope Create subfolders only where price, shipping or content will differ Unlocalised markets lose local currency in results
    Theme and app structured data Always audit Whenever the currency or tax treatment is wrong in any market Low, if tested per market

    Also leave market subfolders out of robots.txt.liquid disallow rules. Blocking a subfolder stops Google from seeing its hreflang and canonical tags, so the cluster breaks in ways that are hard to diagnose.

    How I would diagnose an existing setup

    1. View source on one product in two markets. Count the hreflang sets, confirm each version self-canonicalises, and check the JSON-LD price and currency against the visible price.
    2. Run URL Inspection on market URLs. Compare the user-declared and Google-selected canonical, and check the rendered HTML shows the market’s currency.
    3. Add URL-prefix properties for each subfolder in Search Console so each market reports separately. Country targeting no longer exists in Search Console, so these properties are for reporting only.
    4. Check landing-page fit in analytics. For organic sessions from each country, what share land on that country’s subfolder? A low share means the hreflang swap is not happening.
    5. Review Merchant Center diagnostics by country for price and currency mismatches.
    6. Crawl the hreflang set with a crawler that reports non-200 alternates and missing return links.
    What you see Likely meaning Action
    Market URLs clustered, and local users still land on local URLs Google is clustering and swapping as designed Usually nothing. Report on analytics, not Search Console alone.
    Market URLs clustered, and local users land on another market The swap is failing, often because the versions are too similar Adapt content, or drop the subfolder if the market is small
    Merchant Center price mismatches in one country Markup, tax display or conversion timing Fix structured data and tax settings, then consider fixed prices
    Two sets of hreflang tags App or theme duplication Remove the extra set before touching Shopify’s defaults

    A test worth running before restructuring markets

    If a same-language market is underperforming, adapt its top 50 products first (local spelling, delivery, returns, reviews, tax messaging) and leave the rest unchanged. Over 8 to 12 weeks, track the share of URLs where Google selects the market URL as canonical, and the share of that country’s organic sessions landing on its own subfolder, against the unchanged products. If both improve, localisation is the fix. If nothing moves, the market probably does not justify its own subfolder yet.

    If this were my store, I would treat Shopify’s hreflang as infrastructure and spend the effort where Shopify cannot help: fewer, better-differentiated markets, correct prices in every currency, and reporting that follows users to the URL they actually landed on.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.