umbrella Multi Storefront & SEO

Shopify multi-domain SEO

Why every Shopify domain serves the same sitemap

You added a second domain, fetched /sitemap.xml on both, and counted the same products twice. That is Shopify working as documented. Most guides that describe it are describing a different feature.

Measured on a live Basic-plan store with three non-redirecting domains and 313 products on . Shopify documentation quoted as of .

Check your own store first

Two commands, one per domain. Run them before reading anything below — the answer on your own store is more useful than any description of it.

curl -s https://your-first-brand.com/sitemap.xml | grep -c "<loc>"
curl -s https://your-second-brand.com/sitemap.xml | grep -c "<loc>"

If the two numbers match, both domains are advertising the same catalogue. On the store we measured, three domains each returned the same count — 313 products — and the pattern is the default, not a misconfiguration.

What does Shopify’s documentation actually say?

Two sentences, on two different pages, and the gap between them is where a multi-brand merchant lives.

On sitemaps, Shopify says per-domain sitemaps exist for one specific case: “If your store is on the Basic plan or higher, then you have sitemaps for every additional domain you’re using for international domains.” The same page then gives its guidance for everyone else: “If you have multiple domains and aren’t using them for international targeting, then make sure all domains redirect to your primary domain.” (Shopify Help — finding your sitemap)

On alias domains — domains that serve the storefront without redirecting — Shopify says: “When using alias domains, it’s recommended that the content of the storefront differs from that of the primary domain. Search engines might rank search results lower if multiple domains display the same content.” (Shopify Help — alias domains)

Read those together. Shopify supports non-redirecting alias domains, states that their content should differ from the primary, and provides no mechanism to make the sitemap or the canonical tag differ. The alias-domain page does not mention sitemaps or canonical tags at all. A merchant running several brands on one store is in the gap between those two sentences.

Why do so many guides say each domain gets its own sitemap?

Because for international domains, they do. Shopify Markets assigns a domain to a market, and a market-attached domain gets its own sitemap covering the catalogue as localised for that market.

Guides written about that feature get quoted in answers about a different one. Several currently-ranking pages state flatly that any additional Shopify domain generates its own sitemap. That is true of market domains and misleading everywhere else — and the distinction matters, because it decides whether you have a problem to solve.

The test is what the domain is for. A domain attached to a market for a country or language is the documented case and behaves as those guides describe. A second domain carrying a second brand, in the same country and the same language, is not a market — and it is the arrangement most multi-brand merchants actually have.

What “the same sitemap” precisely means

Worth being exact, because the imprecise version is what makes the guides above sound plausible.

The files are not byte-identical. Fetch /sitemap.xml on each domain and each one lists <loc> URLs on its own hostname. In that narrow sense every domain does have its own sitemap.

What is identical is the contents. Every domain lists your whole catalogue. On the store we measured, three domains published 313 products each — the same 313 — with only the hostname differing. So each brand submits every other brand’s products under its own name, and the sitemap that is supposedly “its own” describes a catalogue that mostly is not.

That is the difference between a sitemap that exists per domain and a sitemap that is about that domain.

Is this a duplicate content penalty?

No, and it is worth saying plainly because a good deal of writing on this subject implies otherwise.

On a default Shopify store, every page served on a non-redirecting secondary domain carries a <link rel="canonical"> naming the equivalent URL on your primary domain. A canonical tag is an instruction about which URL owns a piece of content. So the store is not sending a confused signal — it is sending a clear one, and that instruction credits the primary domain for everything.

The consequence is not a penalty. It is that your secondary brand domains instruct search engines to credit a different domain for every page they serve. What any given search engine does with that instruction is its own decision, and no software controls it.

We do not promise a search outcome, here or anywhere. Umbrella changes what your files say. Search engines decide what to do about it. Our terms commit to that in the place it is binding.

What has to change

Three files, and they only work as a set. Changing the canonical without suppressing the default sitemaps sends two contradicting instructions instead of one.

  • The sitemap — one per domain, listing only the URLs that belong to that brand, hosted where it can be served per-domain.
  • The canonical tag — naming the domain of the brand that owns the page, rather than the primary domain for everything.
  • The robots.txt — disallowing Shopify’s default sitemap on every domain, primary included, and pointing each domain’s Sitemap: directive at its own.

Shopify’s sitemap.xml is generated and cannot be filtered or edited, which is why the third file is not optional: the only way to stop the whole-catalogue sitemap being read is to stop pointing crawlers at it. Umbrella does all three, and the four ways to run several brands on Shopify covers what it costs against the alternatives.

Where to go next