Back to Home
Wearepresta
  • Services
  • Work
  • Case Studies
  • How We Price
  • About
  • Giving Back
  • Blog
  • Contact

Hire Us

[email protected]

General

[email protected]

Phone

+381 64 17 12 935

Location

Dobračina 30b, Belgrade, Serbia

We Are Presta

Follow for updates

Linkedin @presta-product-agency
Shopify
| 3 August 2026

Shopify Sitemap XML Submission: The Complete 2026 Guide

Shopify Sitemap XML Submission: The Complete 2026 Guide

If Google cannot find your product pages, they do not exist as far as organic traffic is concerned. A clean Shopify sitemap XML submission is the single cheapest indexing lever most merchants ignore, and getting it wrong quietly costs stores 15 to 40 percent of their potential organic reach in the first six months after launch. This guide walks you through the entire process, from locating your sitemap to confirming Google has crawled it, the same sequence our team runs on every store we ship.

TL;DR

  • Sitemap location: Every Shopify store auto-generates a sitemap at yourstore.com/sitemap.xml, an index file that links to sub-sitemaps for products, collections, pages, and blogs. You do not create it manually, you validate and submit it.
  • Submission target: The primary action is submitting that sitemap URL to Google Search Console and Bing Webmaster Tools, which typically accelerates full-catalog indexing from 4 to 8 weeks down to 7 to 14 days.
  • Ongoing hygiene: Submission is not one-and-done. You need to control what enters the sitemap with noindex tags, canonical rules, and robots.txt edits, or you will feed Google thousands of thin, duplicate, or filtered URLs that dilute your rankings.

Step 1: Confirm Your Shopify Sitemap Exists and Understand Its Structure

Before you submit anything, you need to know exactly what you are submitting. This is the step most tutorials skip, and it is why so many merchants submit a sitemap, see errors weeks later, and have no idea why.

Shopify generates your XML sitemap automatically. You do not build it, install an app for it, or write a line of code. The moment your store goes live, Shopify publishes a sitemap index at a fixed, predictable URL. Your job in this step is to find it, open it, and read it like a map of everything Google is about to crawl.

Where is the sitemap located in Shopify?

Your master sitemap lives at a single, non-negotiable address:

`https://yourstore.com/sitemap.xml`

Replace yourstore.com with your actual domain. If you are still on the myshopify.com subdomain, it will resolve there too, but you always want to submit the sitemap on your primary custom domain, not the myshopify.com version, to avoid canonical confusion.

That top-level file is not a flat list of every URL. It is a sitemap index, a table of contents that points to a set of child sitemaps. When you open it in a browser, you will see something structured like this:

Child sitemapWhat it containsTypical URL pattern
ProductsEvery active product page/sitemap_products_1.xml
CollectionsEvery collection page/sitemap_collections_1.xml
PagesStatic pages (About, Contact, policies)/sitemap_pages_1.xml
BlogsBlog posts and article pages/sitemap_blogs_1.xml

Shopify paginates these child files. If you have more than roughly 5,000 products, you will see sitemap_products_1.xml, sitemap_products_2.xml, and so on. This matters because at scale, indexing problems tend to cluster inside a single paginated child file, and knowing they exist saves you hours of debugging later.

What does a healthy sitemap entry look like?

Each entry inside a child sitemap includes the page URL, a last-modified timestamp, and often an image reference for product photos. That last-modified value is what tells Google a page changed and deserves a re-crawl. When we scope SEO for clients, one of the first health signals we check is whether those timestamps update correctly after a product edit, because a frozen timestamp is a sign of a caching or theme issue that will slow re-indexing.

Pro Tip: Open your product child sitemap and count the entries, then compare that number to your active product count in the Shopify admin. If your admin says 1,200 active products but the sitemap lists 940, you have a discovery gap. Something (a sales-channel setting, a draft status, or a bulk publish that never finished) is hiding 260 pages from Google before you have even submitted anything.

Checklist for confirming your sitemap:

  • Root file: Confirm yourstore.com/sitemap.xml loads without a 404 or a login wall.
  • Custom domain: Verify the sitemap resolves on your primary domain, not just the myshopify.com subdomain.
  • Child files: Open each child sitemap and confirm products, collections, pages, and blogs are all present.
  • Count match: Compare product entries in the sitemap against active products in your admin.
  • Timestamps: Confirm last-modified dates reflect recent edits, not a single frozen date.

Checkpoint: You can open yourstore.com/sitemap.xml in a browser, see all four child sitemaps, and your product count roughly matches your active catalog before moving on.

Step 2: Clean Up What the Sitemap Is Allowed to Include

Here is the hard truth that separates a professional Shopify sitemap XML submission from a hobbyist one: submitting a messy sitemap is worse than not submitting at all. If you hand Google 8,000 URLs and 3,000 of them are thin, duplicate, or filtered variations, you are actively teaching the algorithm that your site is low quality.

Shopify’s default behavior creates a lot of URL noise. Collection filters generate parameter URLs, tag pages multiply, and duplicate product URLs appear under both /products/ and /collections/x/products/ paths. Before you submit, you want to control what belongs in the index.

Which pages should never be indexed?

Not everything Shopify generates deserves a spot in Google’s index. The following almost always hurt more than they help:

Page typeIndex it?Reason
Core product pagesYesPrimary revenue and search targets
Main collection pagesYesHigh-intent category traffic
Filtered/faceted URLs (?filter=)NoDuplicate, thin, infinite crawl paths
Internal search resultsNoThin, low-value, self-generated
Cart, checkout, accountNoNo search intent, Shopify blocks these by default
Tag pagesUsually noDuplicate content overlap with collections
Paginated collection pagesSituationalCan consume crawl budget on large catalogs

Shopify handles some of this automatically. Cart, checkout, and account pages are already blocked. But faceted filter URLs and tag pages are where large catalogs bleed crawl budget. When we scope this for clients running catalogs above 2,000 SKUs, controlling these paths is often worth a 20 to 30 percent improvement in the ratio of indexed-to-crawled pages within two months.

How do you control indexing in Shopify?

You have three primary levers, and they do different jobs:

  1. Theme-level noindex tags: You can edit theme.liquid to add a conditional noindex meta tag to specific template types, such as search results or tag pages. This keeps them out of Google without touching the sitemap directly.
  2. robots.txt.liquid: Since 2021, Shopify lets you edit robots.txt via a robots.txt.liquid template. You can disallow crawling of filter parameters and internal search paths. Be surgical here, a broad disallow rule can accidentally block your entire store, which we have seen happen during rushed launches.
  3. Canonical tags: Shopify sets canonical URLs on duplicate product paths automatically, pointing /collections/x/products/y back to the clean /products/y URL. Confirm this is intact in your theme, because a custom theme edit can break it.

Pro Tip: Do not try to remove URLs from the Shopify sitemap by hand. You cannot, it is auto-generated. The correct pattern is to use noindex and robots rules to signal quality, then let Shopify’s sitemap continue listing canonical pages. Fighting the sitemap directly is a losing battle, controlling the signals around it is the winning one.

Checklist for sitemap cleanup:

  • Faceted URLs: Confirm filter and sort parameter URLs are disallowed or noindexed.
  • Search pages: Add a noindex to internal search result templates.
  • Canonicals: Verify duplicate product paths canonicalize to the clean /products/ URL.
  • Robots edit: Review robots.txt.liquid changes twice before publishing to avoid over-blocking.
  • Tag pages: Decide deliberately whether tag pages add value or duplicate your collections.

Checkpoint: A crawl of your site (using Screaming Frog or Ahrefs Site Audit) shows the same clean URLs in your sitemap that you actually want ranking, with filter noise excluded before you submit.

Step 3: Set Up Google Search Console for Your Store

You cannot submit a sitemap to Google without a verified property in Google Search Console. This is the account that will show you crawl status, indexing coverage, and the search queries driving traffic. Skipping proper setup here is why so many merchants submit a sitemap and then fly blind for months.

How do you verify your Shopify domain?

Google Search Console offers two property types, and the choice matters:

Property typeCoverageSetup difficultyRecommendation
Domain propertyAll subdomains and protocolsRequires DNS recordBest choice, most complete data
URL prefix propertySingle exact URL/protocolMeta tag or HTML fileFaster, but fragments your data

We almost always recommend the Domain property because it captures every version of your site in one place. To verify it, Google gives you a TXT record that you add to your domain’s DNS settings. If your domain is registered through Shopify, you can add the record inside Settings, Domains. If it is external (GoDaddy, Namecheap, Cloudflare), you add it in that provider’s DNS panel. Verification usually propagates within an hour, though DNS can take up to 48 hours.

If DNS access is a blocker, the URL prefix property with the HTML meta tag method is a valid fallback. Shopify supports adding the verification meta tag through Settings, or you can drop it into theme.liquid.

What should you configure immediately after verification?

Once verified, do not stop at the celebration. Configure these before you submit:

  • Confirm the preferred domain matches your canonical (www vs non-www, https).
  • Check that no accidental removals or manual actions exist under the Security and Manual Actions reports.
  • Link Search Console to Google Analytics 4 so query data flows into your reporting.

At Presta, we treat Search Console verification as a launch-blocking task, not a nice-to-have. On the Cosmetica Labs engagement, where we built their state-of-the-art Shopify store with ERP integration and drove an 80 percent revenue increase, clean search infrastructure from day one was part of why organic performance compounded instead of stalling. You cannot optimize what you cannot measure, and Search Console is the measurement layer.

Checklist for Search Console setup:

  • Property type: Choose Domain property unless DNS access is impossible.
  • Verification: Add the TXT record and confirm verification completes.
  • Canonical domain: Confirm the property matches your live https canonical domain.
  • Manual actions: Check the Manual Actions report shows no penalties.
  • GA4 link: Connect Search Console to Analytics for unified reporting.

Checkpoint: Your Search Console property shows a green verified status and begins populating impression data within 48 to 72 hours before you proceed to submission.

Step 4: Submit Your Shopify Sitemap to Google Search Console

This is the core action of the entire guide, and it is genuinely simple once the prep work is done. The complexity was never in the submission, it was in everything you already handled in Steps 1 through 3.

How to submit Shopify sitemap to Google Search Console

Follow this exact sequence:

  1. Open Google Search Console and select your verified property.
  2. In the left menu, click Sitemaps under the Indexing section.
  3. In the Add a new sitemap field, enter only the path: `sitemap.xml`. Search Console already knows your domain, so you do not paste the full URL, just the relative path.
  4. Click Submit.
  5. Wait. Google will show a Success status once it reads the sitemap index, usually within minutes, though full processing of child sitemaps takes hours to days.

You only submit the root sitemap.xml. You do not need to submit each child sitemap individually. The sitemap index tells Google about all of them automatically, and submitting the children separately just clutters your report.

How to create and submit a Shopify sitemap the right way

To be clear, since this is one of the most common questions we get: you do not create a Shopify sitemap. Shopify creates it for you the moment your store is live. The phrase create and submit really means validate what Shopify built, clean the signals around it, then submit the root URL to Google and Bing. If a tutorial tells you to install a sitemap-generator app for a standard Shopify store, be skeptical, you are usually adding a redundant tool that can conflict with Shopify’s native file.

Submitting a sitemap is not the goal, it is the invitation; the real work is making sure every URL inside it earns the crawl it receives.

Pro Tip: After a successful submission, use the URL Inspection tool on three or four of your most important product pages and click Request Indexing on each. This nudges Google to prioritize your money pages instead of waiting for it to work through the sitemap in its own order. It does not guarantee ranking, but on new stores it can pull first indexing forward by 5 to 10 days for those specific URLs.

Checklist for submission:

  • Root only: Submit sitemap.xml, not the individual child files.
  • Relative path: Enter only the path, not the full domain URL.
  • Success status: Confirm Search Console returns a Success read status.
  • Priority pages: Request indexing manually on your top 3 to 5 revenue pages.
  • Record the date: Note your submission date so you can track indexing velocity against it.

Checkpoint: Search Console shows your sitemap with a Success status and a discovered-URLs count that roughly matches your expected page total.

Step 5: Submit to Bing Webmaster Tools and Other Engines

Google gets the attention, but leaving Bing on the table is a mistake, especially heading into 2026 where Bing powers a growing share of AI-assisted search and ChatGPT’s web results. For some product categories, Bing and its downstream AI surfaces drive 8 to 15 percent of organic traffic, and it is nearly free traffic once you have done the Google work.

How do you submit to Bing?

Bing Webmaster Tools has made this trivial. You have two paths:

MethodEffortBest for
Import from Google Search Console2 minutesFastest, one-click transfer of verification and sitemap
Manual verification and submission10 minutesWhen you want a fully independent property

The import option is our default recommendation. Bing lets you sign in with your Google account and import your already-verified Search Console properties, including the submitted sitemap, in a single flow. It is the highest-leverage two minutes in this entire guide.

If you serve international markets, consider Yandex Webmaster (for stores selling into Eastern Europe and Central Asia) using the same sitemap.xml path. The submission mechanics are identical to Google’s.

Checklist for multi-engine submission:

  • Bing import: Use the Google Search Console import to onboard Bing in under 5 minutes.
  • Bing sitemap: Confirm sitemap.xml appears and processes in Bing Webmaster Tools.
  • IndexNow: Enable IndexNow if available, so content changes ping Bing instantly.
  • Regional engines: Add Yandex only if you sell into relevant markets.
  • Consistency: Ensure the same canonical domain is used across every engine.

Checkpoint: Bing Webmaster Tools lists your sitemap as submitted and begins reporting discovered URLs within 72 hours.

Ready to Turn Indexing Into Revenue? Let’s Build It Right

Technical SEO like sitemap submission is the floor, not the ceiling. The stores that compound organic growth pair clean indexing with fast themes, structured data, and a catalog architected for both shoppers and crawlers. Our Startup Studio team frequently builds and launches Shopify stores where SEO infrastructure is engineered in from the first commit, not bolted on after traffic stalls, and the difference shows up as revenue, not just rankings. If you want a store that indexes cleanly and converts the traffic it earns, hire Presta’s Startup Studio to launch and scale your Shopify store or talk to our team directly about a technical SEO audit.

Step 6: Monitor Indexing and Fix Coverage Errors

Submission starts a process, it does not finish one. Over the next few weeks, Google works through your sitemap and reports back on what it indexed, what it skipped, and why. This step is where the real optimization happens, and it is the step most merchants abandon.

Where do you monitor indexing status?

Two reports in Search Console tell you everything:

  1. The Sitemaps report shows submitted URLs versus discovered URLs and flags any parsing errors in the file itself.
  2. The Pages report (formerly Coverage) breaks your URLs into Indexed and Not Indexed buckets, with specific reasons for each exclusion.

The Not Indexed reasons are where you spend your time. Here is how we triage the most common ones:

Search Console statusWhat it meansAction
Discovered, currently not indexedGoogle found it but has not crawled it yetOften crawl budget; improve internal linking
Crawled, currently not indexedGoogle crawled but judged it low valueStrengthen content, add unique copy
Duplicate without user-selected canonicalDuplicate content, canonical unclearFix canonical tags
Excluded by noindex tagWorking as intended (if you set it)Confirm it is intentional, not accidental
Not found (404)Broken URL in sitemapFix redirect or remove product
Blocked by robots.txtrobots rule is blocking crawlReview robots.txt.liquid rules

The status that trips up the most Shopify merchants is Crawled, currently not indexed on product pages. This almost always signals thin or duplicated product descriptions. If 200 of your products share manufacturer boilerplate copy, Google sees no reason to index all of them. The fix is unique descriptions on priority products, not resubmitting the sitemap ten times.

How long should indexing take?

For a new store, expect this rough timeline after a clean submission:

  • Days 1 to 3: Sitemap read, homepage and top pages discovered.
  • Days 4 to 14: Bulk of catalog crawled and indexed.
  • Weeks 3 to 6: Long-tail and lower-priority pages settle in.

A well-prepared store often reaches 80 to 90 percent catalog indexing within two weeks. A messy one can sit at 40 percent for months, which is exactly the outcome Steps 1 and 2 exist to prevent. At Presta, we have seen properly scoped stores hit near-complete indexing in under 10 days simply because the sitemap fed Google only pages worth crawling.

Checklist for monitoring:

  • Weekly review: Check the Sitemaps and Pages reports weekly for the first month.
  • Triage exclusions: Map each Not Indexed reason to a specific fix.
  • Thin content: Rewrite boilerplate descriptions on Crawled, not indexed products.
  • Internal links: Add contextual links to Discovered, not indexed pages.
  • Track the ratio: Watch indexed-to-submitted climb toward 90 percent over six weeks.

Checkpoint: Your Pages report shows a rising indexed count each week and a shrinking list of unexplained exclusions.

Step 7: Optimize for Ongoing Sitemap Health and AI Search

By 2026, sitemap hygiene is no longer only about Google’s blue links. AI search engines and answer engines crawl the same sitemaps to build their understanding of your catalog. A clean, well-structured sitemap is now part of how ChatGPT, Perplexity, and Google’s AI Overviews decide whether to cite or recommend your products. This is the AI-SEO layer, and it rewards the same discipline as traditional SEO, only more strictly.

What keeps a sitemap healthy long term?

Sitemaps are living files. Every product you add, archive, or rename changes what Shopify publishes. The maintenance discipline is straightforward but must be consistent:

  1. When you archive or delete products, confirm they drop out of the sitemap and return proper 404 or 410 status codes, not soft 404s.
  2. When you launch seasonal collections, submit nothing extra; Shopify updates the sitemap automatically, but do request indexing on the flagship new pages.
  3. Audit quarterly for orphan pages that exist in the sitemap but have no internal links pointing to them.

For AI search specifically, the sitemap works best when paired with structured data. Product schema (price, availability, reviews, brand) tells answer engines exactly what each sitemap URL represents. A URL in a sitemap without schema is a name without a description, an AI engine can find it but struggles to understand and cite it.

Does structured data belong in this conversation?

Absolutely, and it is where forward-looking Shopify SEO best practices for 2026 converge. The sitemap tells engines what pages exist; structured data tells them what those pages mean. Together they form the discovery-plus-understanding pair that AI-assisted search relies on. Most quality Shopify themes ship with basic product schema, but our team routinely finds gaps in review markup, availability status, and breadcrumb schema that materially affect eligibility for rich results and AI citations.

Introducing the CRAWL framework, our internal shorthand for keeping a Shopify store discoverable and citable:

LetterPrincipleWhat to do
CCleanKeep only canonical, valuable URLs in the sitemap
RRefreshEnsure last-modified timestamps update on edits
AArchitectureMaintain logical internal linking to every page
WWatchMonitor coverage reports weekly, then monthly
LLabelPair every sitemap URL with accurate structured data

Run a store against CRAWL quarterly and you keep both traditional and AI search engines fed with exactly what they need.

Checklist for ongoing health:

  • Removal hygiene: Confirm deleted products return 404/410, not soft 404s.
  • New launches: Request indexing on flagship new collection and product pages.
  • Orphan audit: Find and internally link sitemap URLs with no inbound links.
  • Schema coverage: Verify product, review, and breadcrumb schema on key templates.
  • Quarterly CRAWL: Run the full CRAWL check every 90 days.

Checkpoint: A quarterly crawl shows no orphan pages, no soft 404s, and complete structured data on your priority templates.

Common Mistakes in Shopify Sitemap XML Submission

We audit dozens of Shopify stores a year, and the same errors surface repeatedly. Here are the three that cost the most traffic.

Mistake: Submitting the myshopify.com sitemap instead of the custom domain. Why It Happens: Merchants submit before or right after connecting a custom domain and never update the property. Fix: Verify a Domain property on your live custom domain and submit sitemap.xml there, then use Search Console’s change-of-address tool if you already indexed the myshopify version.

Mistake: Over-aggressive robots.txt edits that block the whole store. Why It Happens: A well-intentioned attempt to block filter URLs uses too broad a disallow pattern in robots.txt.liquid. Fix: Test every robots rule against real URLs before publishing, and confirm your core product and collection paths are still crawlable.

Mistake: Treating submission as a one-time task and ignoring coverage reports. Why It Happens: The submission succeeds, merchants assume the job is done, and they never revisit Search Console. Fix: Schedule a recurring monthly review of the Pages report so indexing regressions get caught within weeks, not quarters.

Measuring Success: 30, 60, and 90 Day KPIs

A sitemap submission is only worth doing if you can prove it moved the needle. Here is the KPI framework we hold ourselves and clients to, mapped to a 30/60/90 day cadence.

TimeframePrimary KPITargetWhy it matters
30 daysIndexed pages ratio70 to 90 percent of submitted URLsConfirms discovery is working
30 daysSitemap read statusSuccess, zero parse errorsConfirms the file itself is valid
60 daysOrganic impressionsSteady week-over-week growthConfirms indexed pages are surfacing
60 daysCoverage exclusionsDeclining and fully explainedConfirms cleanup is holding
90 daysOrganic clicks and sessionsMeasurable lift vs pre-submissionConfirms traffic is converting to visits
90 daysAssisted revenue from organicAttributable growth in GA4Confirms SEO is a revenue channel

The 30-day window is about plumbing: is Google reading and indexing? The 60-day window is about visibility: are those pages showing up for queries? The 90-day window is about business impact: is organic traffic driving sessions and revenue? If you are still stuck at a low indexed ratio at day 30, the problem is upstream in Steps 1 and 2, not in the submission itself.

Checklist for measurement:

  • Baseline first: Record impressions, clicks, and indexed count on submission day.
  • 30-day plumbing: Confirm indexed ratio above 70 percent.
  • 60-day visibility: Track impression growth and shrinking exclusions.
  • 90-day impact: Measure organic sessions and assisted revenue in GA4.
  • Attribute honestly: Separate SEO gains from paid and email so the story is credible.

Advanced Tips for Sitemap and Indexing at Scale

Once the fundamentals are solid, a few advanced moves separate good stores from dominant ones.

Use log file analysis on large catalogs. If you run 10,000-plus SKUs, server log analysis reveals how Googlebot actually spends its crawl budget. We regularly find Google wasting 30 to 50 percent of crawl requests on filter and pagination URLs that should have been blocked, and reallocating that budget to product pages accelerates deep-catalog indexing meaningfully.

Prioritize crawl budget with internal linking. Google follows links, and pages buried five clicks deep get crawled rarely. A flatter architecture where every product is reachable within three clicks from the homepage improves indexing consistency more reliably than any sitemap trick. This is one reason platform choice matters, and it is a recurring theme in our breakdown of why Shopify is more than just a platform for stores planning for the next decade.

Leverage IndexNow for real-time updates. Shopify integrates with IndexNow so that when a product changes, participating engines (Bing and others) get pinged instantly rather than waiting for a re-crawl. On stores with fast-changing inventory, this can cut update latency from days to hours.

Watch for JavaScript rendering gaps. Some custom themes render critical content client-side. If key product information only appears after JavaScript execution, some crawlers may index a thinner version of the page. Confirm your priority content is present in the rendered HTML.

Advanced checklist:

  • Log analysis: Audit server logs on catalogs above 10,000 SKUs.
  • Flat architecture: Keep every product within three clicks of the homepage.
  • IndexNow: Enable instant update pings for fast-moving inventory.
  • Render check: Verify priority content exists in server-rendered HTML.
  • Crawl budget: Reallocate Googlebot attention from filter URLs to product pages.

If you are just getting started, do not overthink it: confirm your sitemap loads, verify a Domain property in Search Console, submit sitemap.xml, and request indexing on your top revenue pages. That covers 80 percent of the value in an afternoon. If instead you are auditing an existing store that already submitted a sitemap months ago, start at the Pages report, triage your Not Indexed reasons, and work backward to fix the signals feeding your sitemap; the submission is almost never the actual problem, the content and canonical hygiene around it usually is. Merchants weighing a bigger platform decision should also review our WooCommerce vs Shopify 2025 comparison and the complete guide to WooCommerce to Shopify benefits, since indexing behavior differs meaningfully between platforms.

Next Steps:

  • Immediate: Open yourstore.com/sitemap.xml, confirm it loads, and submit it in Google Search Console today.
  • This week: Verify Bing via Google import and request indexing on your five best product pages.
  • This month: Schedule a recurring Pages report review and rewrite boilerplate copy on your top-selling products.

Frequently Asked Questions

How to create and submit a Shopify sitemap?

You do not create a Shopify sitemap manually; Shopify generates it automatically the moment your store goes live. It publishes a sitemap index at yourstore.com/sitemap.xml that links to child sitemaps for products, collections, pages, and blogs. Your real task is to validate that this file is complete and accurate, then submit the root URL to search engines.

To submit it, verify your domain in Google Search Console, open the Sitemaps report, enter sitemap.xml in the field, and click Submit. That single action tells Google about all your child sitemaps at once. Repeat the equivalent process in Bing Webmaster Tools, ideally using the one-click Google import.

The one thing to avoid is installing a third-party sitemap generator app for a standard store. Shopify’s native sitemap is well-formed and updates itself, so an extra app usually adds redundancy and occasional conflicts rather than value.

Where is the sitemap located in Shopify?

Your Shopify sitemap is always located at the same predictable path: yourstore.com/sitemap.xml, using your primary custom domain. That top-level file is a sitemap index rather than a flat list, so when you open it you will see links to child sitemaps such as sitemap_products_1.xml and sitemap_collections_1.xml.

If your store has a large catalog, the product sitemap paginates into numbered files (sitemap_products_1.xml, sitemap_products_2.xml, and so on), with Shopify capping each child file at a set number of URLs. This is normal and requires no action from you beyond awareness.

Always reference the sitemap on your live custom domain rather than the myshopify.com subdomain. Submitting the myshopify version is one of the most common mistakes we see, and it fragments your indexing signals across two domains.

How to submit Shopify sitemap to Google Search Console?

First, verify your store as a property in Google Search Console, ideally as a Domain property using a DNS TXT record so all versions of your site are covered. Once verification shows a green status, you are ready to submit.

In the left-hand menu, click Sitemaps under the Indexing section. In the Add a new sitemap field, type only the relative path sitemap.xml, since Search Console already knows your domain, then click Submit. Within minutes you should see a Success read status, and over the following hours and days Google will process the child sitemaps and begin reporting discovered URLs.

After submission, use the URL Inspection tool on your most important product pages and click Request Indexing to prioritize them. Then monitor the Sitemaps and Pages reports weekly for the first month to catch and fix any coverage errors early.

Do I need to resubmit my sitemap every time I add a product?

No. Shopify automatically updates the sitemap file whenever you add, edit, or remove products, and Google periodically re-reads the submitted sitemap on its own schedule. You submit the sitemap once, and the file stays current without further action.

The exception worth making is flagship launches. When you release a major new collection or a hero product you expect to drive significant revenue, it is worth manually requesting indexing on those specific URLs through the URL Inspection tool to pull their first crawl forward by several days.

For fast-moving inventory, enabling IndexNow lets participating engines learn about changes almost instantly, which is more efficient than any manual resubmission workflow.

Why are some of my product pages not being indexed even after submission?

The most common reason on Shopify stores is thin or duplicate content, which shows up in the Pages report as Crawled, currently not indexed. When many products share identical manufacturer boilerplate descriptions, Google sees little reason to index them all. The fix is unique, useful copy on your priority products, not repeated sitemap resubmission.

Other frequent causes include duplicate canonical issues, accidental noindex tags from theme edits, and crawl budget limits on large catalogs where pages sit as Discovered, currently not indexed. Each Not Indexed status in Search Console names a specific reason, so triage them one by one rather than guessing.

If a large percentage of your catalog stays unindexed for more than a few weeks, the problem is almost always upstream in your sitemap hygiene and content quality, the exact issues Steps 1 and 2 of this guide address.

When does it make sense to bring in Presta’s Startup Studio for this?

Honestly, not every store needs an agency for sitemap submission. If you run a few hundred clean products and you are comfortable in Search Console, the steps in this guide will get you a properly indexed store in an afternoon. Do it yourself, keep the money, and revisit the Pages report monthly.

The threshold where it becomes worth bringing us in is when complexity and stakes rise together. Large catalogs above a few thousand SKUs, international or multi-domain setups, custom themes with rendering or canonical issues, or a migration from another platform are all situations where indexing mistakes get expensive fast and are hard to diagnose without experience. If you are seeing a persistently low indexed ratio, unexplained traffic loss, or you simply cannot afford the weeks of trial and error, that is the point where our Startup Studio pays for itself.

The clearest signal is business impact. When organic search is a meaningful revenue channel and a 20 to 40 percent indexing gap translates to real lost sales, the cost of getting it right professionally is small next to the cost of leaving it broken. If that sounds like your situation, our guide on how to evaluate a Shopify migration agency is a good place to understand what quality technical partners actually do.

Does the Shopify sitemap matter for AI search engines in 2026?

Yes, more than ever. AI search engines and answer tools like ChatGPT, Perplexity, and Google’s AI Overviews rely on the same crawl-and-index infrastructure, and your sitemap is how they discover which pages exist on your store. A clean sitemap is now part of the foundation for AI visibility, not just traditional blue-link rankings.

The bigger lever for AI search, though, is pairing sitemap discovery with structured data. Product schema that describes price, availability, brand, and reviews tells answer engines what each sitemap URL actually means, which improves your chances of being cited or recommended. Discovery plus understanding is the pattern that wins in AI-assisted search.

Because of this, we treat sitemap hygiene and structured data as a single workstream in 2026. A URL that engines can find but cannot understand is a wasted opportunity, and closing that gap is one of the highest-return technical SEO investments a store can make right now.

Sources

  • Google Search Central: Build and submit a sitemap
  • Google Search Central: Manage your sitemaps with the Sitemaps report
  • Shopify Help Center: Finding and submitting your sitemap
  • Shopify Help Center: Edit robots.txt.liquid
  • Bing Webmaster Tools: Import from Google Search Console
  • Google Search Central: Introduction to structured data
  • IndexNow official documentation

Related Articles

Native App Integration vs Custom API Builds: A Shopify App Integration Guide for 2026
Shopify
2 August 2026
Native App Integration vs Custom API Builds: A Shopify App Integration Guide for 2026 Read full Story
Shopify Checkout Extensibility vs Checkout.liquid: Which Is Right for You in 2026?
Shopify
3 August 2026
Shopify Checkout Extensibility vs Checkout.liquid: Which Is Right for You in 2026? Read full Story

Need help with this?

Presta has 15+ years of experience helping clients achieve business results.

Contact Us
Would you like free 30min consultation
about your project?

    © 2026 Presta. ALL RIGHTS RESERVED.
    • facebook
    • linkedin
    • instagram