An XML sitemap is a structured file that lists every page on a website along with metadata about each page (last modified date, plus change-frequency and priority fields that Google ignores). Search engines use the sitemap to discover content and prioritize crawling. Where a regular sitemap is broader (often referring to navigation maps for users), an XML sitemap is specifically for search engine consumption.

What an XML sitemap does

Aids discovery: tells search engines about pages they might not find through normal crawling, especially pages with few internal links or deep navigation depth.
Provides metadata: last-modified dates help search engines prioritize re-crawling of recently-updated content, and Google uses lastmod where it is consistently and verifiably accurate. Google states that it ignores the changefreq and priority fields outright, so tuning them buys nothing.
Indicates structure: the sitemap reveals the site's content hierarchy and surface area in a single file, useful for large sites.
Supports image and video discovery: extended sitemap formats include image and video metadata that help with media-specific search results.

Why indexation is the number that matters

One commercial fact sits under all of this: a page that is not indexed earns nothing. On a large catalog, a meaningful share of product and collection pages never make it in. The sitemap is a discovery aid, not a guarantee — search engines still decide which pages are worth crawling and keeping, and thin or near-duplicate variant pages are the usual reason a catalog sits half-indexed while the merchant assumes the whole store is live and earning.

So the question worth a leader's time is not whether the sitemap exists. On Shopify it does, automatically. It is what share of the products listed in it are actually indexed, which the Search Console indexing report answers in a few minutes. If that share is low, the fix is product content, consolidating duplicates, and internal linking from pages that already rank. Nothing done to the sitemap file itself will change it.

XML sitemap on Shopify specifically

Shopify generates and maintains an XML sitemap automatically at /sitemap.xml. The auto-generated sitemap includes:

All published products
All published collections
Pages (about, contact, custom pages)
Blog posts and articles

Shopify's auto-generated sitemap is generally adequate. Common considerations:

Newly published content: can take hours to a day to appear in the sitemap. Not instant.
Excluded pages: the sitemap doesn't include unpublished products, archived collections, or pages explicitly excluded via robots.txt.
Large catalogs: sitemaps over 50,000 URLs are split into multiple files with a sitemap index. Shopify handles this automatically.
International stores: Shopify Markets generates locale-specific sitemaps for multi-region stores.

When to consider a custom sitemap

Headless setups where Shopify isn't generating the storefront. The sitemap needs to be generated by the front-end framework or a separate service.
Custom URL structures not covered by Shopify's defaults — landing pages built outside Shopify, application content, etc.
Granular crawl control for very large catalogs where sitemap-segment-level prioritization matters.

Submitting the sitemap

Sitemap URLs should be submitted to Google Search Console and Bing Webmaster Tools. Once submitted, search engines re-fetch the sitemap periodically to discover changes. Submission isn't required for crawling — search engines will find the sitemap if it's referenced from robots.txt — but explicit submission produces faster indexing for new content.

The indexing report that actually answers whether the sitemap is doing its job lives in Search Console, not in the sitemap file itself, and connecting Google Search Console to a Shopify store and reading that data is the step most merchants skip after confirming the sitemap exists.