Skip to content
Shopify SEO Organic Cart Studio Journal

Why Is My Shopify Sitemap Not Updating? 9 Checks and Fixes

August 22, 2026 · Mustajab Haider Bukhari

A Shopify sitemap usually updates automatically, but the root /sitemap.xml is only an index that links to child sitemaps for products, collections, pages and blogs. If a URL seems missing, open the relevant child sitemap, confirm the resource is published to the Online Store, and check the correct storefront domain. A technical Shopify SEO diagnosis separates a genuinely missing URL from a cached browser view or a Search Console reporting delay.

Shopify does not provide a manual “regenerate sitemap” button. Do not install an app or repeatedly resubmit the same file until you have verified the public XML, canonical URL, status and domain.

Quick diagnosis: what does “not updating” mean?

What you seeLikely issueFirst check
New product absent from root sitemap textLooking at the index, not child fileOpen the product child sitemap
Product absent from child sitemapPublication, visibility or canonical eligibilityConfirm Online Store availability
XML is current but Search Console says old last readGoogle has not fetched it againInspect live sitemap response
Wrong products appearWrong domain, market or cached responseCheck final URL and storefront domain
Sitemap returns HTML, challenge or errorDomain, proxy, app or platform issueTest signed out and inspect HTTP response
URL is in sitemap but not indexedIndexing issue, not sitemap generationUse URL Inspection

How does Shopify’s sitemap work?

Every Shopify store automatically creates a sitemap at the root of its storefront domain, such as https://example.com/sitemap.xml. The file points to separate sitemap files for products, collections, blogs and pages. Large catalogs can have multiple child files.

Shopify’s official guide says these files are automatically updated when products, collections, images, pages or posts are added. It also explains that international domains can have separate sitemaps. See Shopify’s sitemap documentation.

Check 1: open the correct child sitemap

Open /sitemap.xml in a signed-out browser. Find the row whose location contains sitemap_products, sitemap_collections, sitemap_pages or sitemap_blogs. Open that exact child file and search for the canonical URL or handle.

The root file may look unchanged because it continues to reference the same child files. A new product changes the product child sitemap, not necessarily the visible structure of the root index.

Check 2: confirm Online Store publication

A product can exist in Shopify admin without being published to the Online Store sales channel. Confirm its status is active and that Online Store is included in sales-channel availability. Then open the public URL while signed out.

Also check scheduled publication, draft status, market restrictions and app-controlled visibility. The sitemap should represent public canonical storefront URLs, not every object stored in admin.

Check 3: inspect the final storefront URL

Use the preferred primary domain, not an old myshopify.com address, staging host, previous domain or regional domain that redirects elsewhere. Follow the browser redirect and record the final URL.

Shopify can create sitemaps for international domains. A product available in one market may not behave the same on another. Compare the exact domain submitted in Search Console with the domain whose sitemap you are viewing.

Check 4: rule out browser, CDN or proxy caching

Open the sitemap in a private window, add a harmless query string for testing, or fetch it with an HTTP tool. Compare the response body and date across networks if needed. Do not assume that “view source” and the rendered XML came from the same cached response.

If a reverse proxy, headless storefront or security layer sits in front of Shopify, test both the public domain and Shopify-managed origin behavior. A proxy can cache XML longer than HTML or accidentally return a challenge page to crawlers.

Check 5: distinguish the XML from Search Console’s last read

Search Console does not fetch every sitemap immediately after each catalog change. Its “last read” date reports Google’s processing, not the timestamp when Shopify changed the file. If the public child sitemap contains the URL, the generation step has worked.

Google’s sitemap guidance says sitemaps are hints and warns against submitting the same unchanged file repeatedly. See Google’s crawling troubleshooting documentation. Resubmit once after fixing a real error, then allow time for processing.

Check 6: make sure the URL is eligible for the sitemap

Check whether the page redirects, uses a different canonical, is unpublished or is intentionally hidden from search. A sitemap should contain the preferred indexable URL. Google likewise recommends including URLs you want to see in search and using fully qualified canonical URLs in its sitemap-building guidance.

Do not force a redirected or noncanonical URL into a custom sitemap. Fix the resource’s availability and canonical logic instead.

Check 7: test the product URL separately

A URL can appear in the sitemap and remain unindexed. Open Search Console URL Inspection for the exact canonical URL. Review discovery, crawl permission, page fetch, user-declared canonical, Google-selected canonical and current indexing status.

If the URL is known but excluded, sitemap regeneration is not the fix. Address the stated reason, such as a duplicate canonical, noindex directive, soft 404, redirect or crawled-but-not-indexed decision. This belongs to wider ecommerce SEO, not the sitemap file alone.

Check 8: inspect product images separately

Shopify sitemaps can include primary product images. A product URL may be present while a newly changed image is not yet reflected in the XML or search result. Confirm the image is assigned to the product, publicly accessible and not only attached to an unavailable variant.

Image discovery and image search display are separate from page indexation. Do not diagnose a missing Google image as a missing product URL without checking both.

Check 9: look for a platform incident or malformed response

If the sitemap returns a 5xx error, empty response, login page or malformed XML across clean requests, check Shopify’s service status and contact support with evidence. Provide the store domain, affected child sitemap, example missing URL, timestamps, status code and response body.

A concise evidence package is more useful than “the sitemap is broken.” It lets support separate catalog data, domain routing and XML generation.

What should you not do?

  • Do not create a competing sitemap app before checking Shopify’s native child files.
  • Do not submit every child sitemap repeatedly when the root index already references them.
  • Do not confuse sitemap inclusion with guaranteed indexing.
  • Do not edit sitemap.xml manually; Shopify generates it.
  • Do not submit a redirected domain when the primary storefront domain is available.
  • Do not publish draft products merely to make them appear in XML.

A 15-minute Shopify sitemap test

  1. Copy the exact public canonical URL that seems missing.
  2. Open the primary domain’s /sitemap.xml signed out.
  3. Open the relevant child sitemap and search for the handle.
  4. Confirm active status and Online Store publication.
  5. Open the page publicly and record status and final URL.
  6. Check canonical and robots directives.
  7. Compare with the domain submitted in Search Console.
  8. Inspect the URL separately if it is in XML but not indexed.
  9. Save evidence before changing anything.

Why does Search Console still show an old sitemap date?

Google controls when it fetches the file. Shopify controls when the public XML changes. Those clocks are independent. Use the live XML to verify Shopify and Search Console’s last read and status to verify Google processing.

Google retired its unauthenticated sitemap ping endpoint, so old apps that try to ping it no longer cause a fresh fetch. Google says sitemaps can still be submitted through Search Console or referenced in robots.txt. See its notice about the deprecated sitemap ping endpoint.

How long should a sitemap update take?

Shopify describes sitemap files as automatic, but neither Shopify nor Google guarantees an exact indexing time. First verify whether the URL is present in the live child sitemap. If it is, waiting for Search Console or search results is a crawling and indexing question.

If a public eligible URL remains absent after reasonable propagation time and clean-cache testing, document the evidence and contact Shopify support. Do not provide customers or clients with an invented fixed deadline.

FAQs

Can I manually update Shopify’s sitemap?

No. Shopify generates the native sitemap automatically. You can change the underlying publication and content settings, but you do not directly edit the XML.

Why is my new product not in the Shopify sitemap?

Check the product child sitemap, active status, Online Store publication, public URL, canonical behavior and correct market domain. The root sitemap is only an index.

Does submitting the sitemap guarantee product indexing?

No. A sitemap helps discovery and signals preferred URLs. Google still evaluates access, canonicalization and page value before indexing.

Should I submit all Shopify child sitemaps?

Submitting the root sitemap index is normally sufficient because it references the child files. Separate submissions can help reporting, but they do not force faster indexing.

Why does Search Console show an old last-read date?

Google has not processed the sitemap again yet, or reporting is delayed. Compare the live XML first and resubmit only after correcting a real problem.

Leave a Reply

Your email address will not be published. Required fields are marked *