For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dev Portal
DocsAPI ReferenceLearnCommunityChangelog
DocsAPI ReferenceLearnCommunityChangelog
  • Overview
    • Quick Start
    • Sandboxes
    • Tools & SDKs
    • Support
  • Docs
      • Getting Started
        • Overview
          • Sitemap
    • Archive
    • Closed Beta Programs
Dev Portal
LogoLogo
On this page
  • Proxying the sitemap
  • Flexibility and limitations
DocsStorefrontCatalystContent Management

Sitemap

Was this page helpful?
Previous

Setup

Next

B2B Edition

Built with

The /sitemap.xml URL provides the complete BigCommerce sitemap, which includes canonical URLs for all channels associated with Catalyst. These URLs correspond to the permanent URLs used when making requests to the GraphQL Storefront API. The URLs correspond to a specific channel, and when accessed, returns the relevant sitemap for that channel.

For an example, see the sitemap for the demo version of Catalyst https://catalyst-demo.site/sitemap.xml.

Proxying the sitemap

Catalyst acts as an intermediary when handling requests to /sitemap.xml. When a request is made, Catalyst fetches the sitemap index from BigCommerce by making a request to the canonical URL of the channel. Catalyst then returns the XML response, allowing the sitemap to appear as though it’s served directly from Catalyst.

You can find the implementation for the route in the Catalyst Monorepo.

Flexibility and limitations

The sitemaps don’t need to reside on the same domain as the website they represent, providing flexibility in managing your site’s structure.

For your convenience, BigCommerce automatically redirects any requests for the legacy Stencil sitemap /xmlsitemap.php to /sitemap.xml on Catalyst storefronts.

Catalyst’s sitemap solution works seamlessly with BigCommerce-managed URLs (such as products, brands, and categories). However, if your storefront also uses third-party systems that generate content with different URLs, you will need to submit multiple sitemaps to cover the URLs from various sources.