BigCommerce Sitemap: Find, Submit, and Optimize It
Where BigCommerce Generates Your Sitemap
BigCommerce automatically generates an XML sitemap for every store. You don't need to install a plugin or configure anything — it's built into the platform. Your sitemap is available at https://yourdomain.com/xmlsitemap.php. This is different from most other platforms, which use /sitemap.xml, so make sure to use the correct path when submitting to Google Search Console.
The xmlsitemap.php endpoint generates a sitemap index that includes child sitemaps for each content type. BigCommerce splits URLs across multiple child sitemap files when your catalog grows large, keeping each file within the 50,000 URL limit.
What BigCommerce Includes and Excludes by Default
BigCommerce's auto-generated sitemap includes: all active product pages, product category pages, brand pages, and web pages (CMS pages created in your store's Pages section). These are the URLs you want Google to discover and rank.
BigCommerce automatically excludes: out-of-stock products (when configured to hide them), hidden categories, draft web pages, and internal/system pages like cart, checkout, and login pages. It also excludes URLs with noindex meta tags. This default behavior is reasonable for most stores, but review your sitemap manually to confirm all your key products and categories appear.
To find your sitemap in the BigCommerce admin: go to Store Setup > Store Profile, and look for the XML Sitemap link in the store's SEO section. Some admin interface versions show it directly in the Storefront settings.
BigCommerce's Automatic Sitemap Refresh Schedule
BigCommerce regenerates your sitemap automatically when products, categories, or pages are added, updated, or removed. You don't need to manually trigger regeneration. However, changes may not appear in the sitemap immediately — there can be a delay of up to a few hours depending on your store's activity level and BigCommerce's platform load.
If you've recently made significant changes (e.g., added 500 new products) and they aren't appearing in your sitemap after several hours, try accessing the sitemap URL directly to force a refresh. If the issue persists, contact BigCommerce support — this can occasionally be a platform-level caching issue.
Common BigCommerce Sitemap Issues and Fixes
Sitemap returns 404: This usually means your store is using a custom domain that isn't fully propagated, or your BigCommerce store is in preview mode. Confirm your domain is properly configured in Store Setup > Store Profile > Domain Name. Also check that your store is not in "Coming Soon" mode, which blocks public access including sitemap access.
Products missing from sitemap: Products that are set to "Not Visible" in their availability settings won't appear in the sitemap. Check individual product visibility under Product > Storefront Details > Availability. Also verify the category the product belongs to is not hidden.
Sitemap URL in GSC shows errors: If Google Search Console reports "Couldn't fetch" errors, your server might be returning a non-200 status code for the sitemap URL. Visit /xmlsitemap.php directly and check the response. If it works in your browser but not in GSC, the issue may be related to Googlebot's User-Agent being blocked by your CDN or WAF rules.
BigCommerce Stencil vs Catalyst (Headless) Sitemap Differences
Traditional BigCommerce stores using Stencil themes use the built-in /xmlsitemap.php endpoint described above. If you're using BigCommerce's headless Catalyst framework (built on Next.js), the sitemap situation changes significantly.
With Catalyst, your frontend is a separate Next.js application. The sitemap must be generated by your Next.js app — typically using Next.js 13+'s app/sitemap.ts file. You'll need to query the BigCommerce GraphQL Storefront API or REST API to fetch your product and category URLs dynamically. The BigCommerce backend's /xmlsitemap.php endpoint will point to your backend domain, not your Catalyst frontend domain — so you cannot simply reuse it. You need to build the sitemap in your Catalyst frontend that reflects the frontend URLs.
Submitting to Google Search Console
In Google Search Console, navigate to Indexing > Sitemaps. Enter xmlsitemap.php in the sitemap URL field (GSC already knows your domain from the property). Click Submit. Monitor the submission status — it should show "Success" within a few minutes, and Google will begin processing the child sitemaps.
Also update your robots.txt file to reference your sitemap. In BigCommerce, you can edit robots.txt under Marketing > SEO > robots.txt. Add the line: Sitemap: https://yourdomain.com/xmlsitemap.php. This helps Bing, DuckDuckGo, and other crawlers discover your sitemap automatically.
BigCommerce Faceted Navigation and Crawl Budget
BigCommerce stores with product filtering (color, size, brand facets) generate thousands of URL variations like /shoes/?color=red&size=10. These are not in your auto-generated sitemap — BigCommerce correctly excludes them — but Googlebot still discovers and crawls them via pagination and category links. This wastes crawl budget on near-duplicate content.
To block faceted URLs: add Disallow: /*? to your robots.txt, or use BigCommerce's URL parameter handling in Google Search Console (add the parameters as "no URLs" parameters under Legacy Tools > URL Parameters). Be careful before blanket-blocking: some filter URLs do have unique, valuable content. Brand pages accessed via facets often have genuine unique content and real search volume — review individual filter combinations before excluding them wholesale.
Also check whether your theme uses URL fragments (#) for filtering. Fragments are never sent to the server — Googlebot doesn't see them — making them SEO-safe. If your theme supports fragment-based filtering (e.g., /shoes/#color=red), those URLs pose no crawl budget risk and no robots.txt changes are needed.
BigCommerce Sitemap and lastmod Dates
BigCommerce's auto-generated sitemap includes <lastmod> dates for products and categories. These reflect the last time the product or category was updated in your admin. If you import products via CSV or API without updating them afterward, their lastmod dates may be stale. Google uses lastmod as a signal — not a guarantee — for recrawl priority. A product last modified three years ago will be deprioritized for recrawl compared to one updated yesterday.
After bulk operations (price updates, inventory changes, CSV imports), verify that lastmod dates in your sitemap updated correctly by checking /xmlsitemap.php directly. Look at the <lastmod> values on recently changed products — if they still show old dates, the update may not have triggered a sitemap refresh.
For large catalogs, products that haven't been touched in 12 or more months and have zero organic traffic are candidates for removal or consolidation. Either 301 redirect them to the most relevant in-stock category page, or consolidate similar products into a single stronger product page. These stale, low-traffic products consume crawl budget without contributing to revenue, and their presence can dilute the overall crawl efficiency of your store.