How to Translate Shopify Store XML Sitemap and Submit It to Google for Each Language
Google cannot rank pages it does not know exist — and if your French or German store pages never appear in your sitemap, Googlebot may never crawl them. Getting shopify multilingual sitemap submission right is one of the highest-leverage technical tasks when expanding internationally, yet it is also one of the most frequently misunderstood, partly because the behaviour differs significantly depending on which Shopify plan and configuration you are running.
This article walks you through exactly what Shopify generates, what it does not, what a compliant multilingual sitemap looks like, and how to submit each language version to Google without wasting crawl budget.
What Shopify Actually Generates — and When
This distinction is critical: Shopify does not generate per-language sitemaps by default on all plans.
Here is what actually happens depending on your setup:
- Shopify Basic (without Markets or Translate & Adapt active): You get a single
sitemap.xmlindex pointing tositemap_products_1.xml,sitemap_collections_1.xml,sitemap_pages_1.xml, andsitemap_articles_1.xml. No language-specific sitemap files are generated. - Shopify with Markets and Translate & Adapt enabled (available from the Basic plan upward, but only once a market with a translated language is published): Shopify generates language-prefixed sitemaps such as
/fr/sitemap.xmland/de/sitemap.xmlfor each active market locale. These files mirror the structure of the root sitemap but serve URLs under the relevant subfolder. - Headless or custom storefronts: Sitemap generation is entirely your responsibility.
Before submitting anything, confirm which situation applies to you. Navigate to yourstore.com/sitemap.xml in a browser. If you see only four standard child sitemaps, your multilingual sitemaps are not yet live — typically because no translated markets have been published.
For a broader understanding of how your URL structure interacts with sitemap logic, How to Translate Shopify Store Sitemap and URL Structure for International SEO covers the structural decisions that precede the submission steps here.
What a Valid Multilingual Sitemap Looks Like
Whether you are relying on Shopify's auto-generated files or supplementing them manually, every URL entry in a multilingual sitemap should include xhtml:link hreflang annotations so Google understands which page serves which language and region.
A fully valid XML sitemap entry — including the required namespace declaration that makes the xhtml prefix resolvable — looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>https://yourstore.com/products/ceramic-mug</loc>
<xhtml:link
rel="alternate"
hreflang="en"
href="https://yourstore.com/products/ceramic-mug"/>
<xhtml:link
rel="alternate"
hreflang="fr"
href="https://yourstore.com/fr/products/ceramic-mug"/>
<xhtml:link
rel="alternate"
hreflang="de"
href="https://yourstore.com/de/products/ceramic-mug"/>
<xhtml:link
rel="alternate"
hreflang="x-default"
href="https://yourstore.com/products/ceramic-mug"/>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
</urlset>
The xmlns:xhtml declaration in the opening <urlset> tag is not optional — omitting it causes validators and some crawlers to reject the hreflang annotations entirely. Every language version must list all alternates, including itself, and every set must include an x-default entry pointing to your fallback page.
For the full hreflang implementation picture, Hreflang on Shopify: The Complete Guide to International SEO Tags explains how sitemap-based hreflang interacts with on-page tags and which approach Google currently prefers.
Shopify Multilingual Sitemap Submission to Google Search Console
Step 1: Verify Each Language Property
Google Search Console treats yourstore.com/fr/ as part of the same Domain Property as yourstore.com if you have verified a Domain Property. If you only have a URL-prefix property for yourstore.com, your /fr/ pages will appear in that property's data but you will not be able to submit the /fr/sitemap.xml directly against a dedicated property.
Recommendation: Verify a Domain Property in Search Console. This covers all subfolders and protocols under one verification, letting you submit and monitor all language sitemaps in one place.
Step 2: Submit Each Sitemap File
In Search Console, go to Sitemaps in the left nav and submit:
https://yourstore.com/sitemap.xml(root index)https://yourstore.com/fr/sitemap.xmlhttps://yourstore.com/de/sitemap.xml- … one entry per active language
Do not assume submitting the root index causes Google to discover the language sitemaps automatically. Submit each one explicitly. Google's documentation confirms that individual submission results in faster processing.
Step 3: Confirm Status and Errors
After 24–72 hours, return to Sitemaps and check that each submitted file shows a Success status and that the number of discovered URLs is roughly what you expect. A "Fetched with warnings" status often indicates namespace errors (see the XML example above) or URLs returning non-200 HTTP responses.
Crawl Budget: The Concern Every Large Store Must Address
If your store has 10,000 SKUs and you operate across five languages, your sitemap ecosystem is generating approximately 50,000 product URLs before you count collections, pages, and articles. This is precisely where Shopify's default setup can create problems.
Key limits to know:
- A single sitemap file must not exceed 50,000 URLs or 50MB uncompressed. If yours does, you must split it using a sitemap index file.
- Shopify's auto-generated sitemaps already paginate (e.g.,
sitemap_products_1.xml,sitemap_products_2.xml) but only within a single locale. Confirm paginated files exist for each language if your product count is high. - Google allocates crawl budget based on site authority and server performance. Submitting 50,000 URLs to a low-authority domain does not mean Google crawls all 50,000 — it means you should use
<priority>and<changefreq>signals deliberately. Set products on sale or recently updated to0.9priority; seasonal content to0.5. - Consider excluding URL parameters and filtered collection URLs from your sitemaps if Shopify generates them, since duplicate parameterised URLs dilute crawl budget without ranking benefit.
For merchants managing this scale of international content, Using Google Search Console to Monitor Your Multilingual Store explains how to interpret crawl stats per language property and identify which URLs are being ignored.
Content Must Be Translated Before Sitemap Submission Counts
Submitting a sitemap URL to Google is worthless if the destination page is still in English with a /fr/ prefix. Google will crawl it, recognise the content as a near-duplicate of your English page, and either ignore it or apply it to the wrong locale. The hreflang signal in your sitemap only helps if the content at the target URL is actually in the target language.
This is why translation completeness — including SEO meta fields like title tags and meta descriptions — must precede sitemap submission. Why Translated Meta Titles and Descriptions Make or Break Multilingual SEO covers exactly why these fields, not just body content, determine whether your language pages rank.
StoreLingo translates your Shopify products, collections, pages, and articles — including SEO meta fields — using AI, and publishes translations directly into Shopify's native multilingual storefront. Translated content activates Shopify's per-language sitemaps automatically, so the URLs you submit to Google actually contain localised content.
Pre-Submission Checklist
Before submitting your multilingual sitemaps, verify each of the following:
- Every language you intend to submit has at least one published market in Shopify Markets with Translate & Adapt active — otherwise no
/fr/sitemap.xmlfile exists to submit - Open each language sitemap URL in a browser and confirm it returns a 200 HTTP status (not a redirect or 404)
- Validate your sitemap XML at sitemaps.org/validate.php — specifically look for the
xmlns:xhtmlnamespace error - Confirm each sitemap file is under 50,000 URLs and under 50MB; if not, create a sitemap index to split it
- Every URL in the sitemap loads a page where the visible content and HTML
langattribute match the language of the sitemap - Each
<url>block includesxhtml:linkalternates for every language version plusx-default - Search Console shows a Domain Property verified (not just URL-prefix) so all subfolder sitemaps are covered
- Submit each language sitemap file explicitly — do not rely on the root index alone
FAQ
Does Shopify automatically create a sitemap for each language I add?
Only if you have Shopify Markets configured with a published locale using Translate & Adapt. Merchants on Shopify Basic who add a language without publishing it through Markets will not see a per-language sitemap file generated at /fr/sitemap.xml or equivalent — the file simply does not exist until the market is live.
Can I submit multilingual sitemaps if I use a subdomain structure instead of subfolders?
Yes, but you must verify each subdomain (e.g., fr.yourstore.com) as a separate URL-prefix property in Search Console, then submit that subdomain's sitemap within its own property. The Domain Property approach only works for subfolders, not subdomains — which is one of several reasons Subfolders vs Subdomains for Multilingual Stores: Which Wins? generally favours subfolders for Shopify merchants.
What if Google Search Console shows fewer URLs discovered than I expect? First, check the sitemap status for errors (namespace issues, HTTP errors, or sitemap size violations). Second, confirm that the missing URLs return 200 status codes and contain fully translated content — Google may suppress near-duplicate pages from its index even if they appear in your sitemap. Third, review your crawl stats in Search Console to see whether Googlebot is visiting those pages at all; if not, a crawl budget issue is likely and splitting your sitemap with explicit priority signals is the next step.
Choose from 47 languages
StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.
Add to Shopify →