How Wix Generates Sitemap.xml for Stores
Wix automatically generates a sitemap.xml for every site, including stores, and hosts it at yourdomain.com/sitemap.xml. Unlike self-hosted platforms, store owners cannot upload a custom sitemap file — Wix owns the generation process entirely. The sitemap updates dynamically as products, collections, blog posts, and static pages are added or removed.
For Wix Stores specifically, the generated sitemap includes product pages, product gallery pages (collections), and any static pages built in the Wix Editor. The file is submitted to Google Search Console automatically when you connect Search Console through Wix's SEO Settings panel. This hands-off approach suits smaller catalogs but creates friction for stores with complex URL structures or large SKU counts.
What Wix Includes — and Excludes — From the Sitemap
Wix includes in its sitemap: published product pages, collection (category) pages, standard static pages marked as indexable, and blog posts if a blog is active. Pages marked as 'Hidden from search engines' in the SEO panel are excluded, as are password-protected pages and pages set to noindex via the page's SEO settings tab.
Wix does not include filter or faceted navigation URLs in the sitemap. When a visitor applies filters (size, color, price range) on a collection page, those filtered URLs are generated client-side and never appear in the sitemap. This is actually correct behavior — including faceted URLs would create duplicate content — but it means filtered collection URLs will not receive direct crawl priority from Google.
Wix also excludes dynamic pages created through Wix Velo (formerly Corvid) dataset-driven routing unless you explicitly configure those pages as indexable and the CMS collection backing them is set to 'Visible to everyone.' For stores using Velo to build custom product landing pages or lookup tools, this exclusion is a common crawl gap.
Wix's Sitemap Index Structure and Large Catalogs
Wix uses a sitemap index file rather than a single flat sitemap once a site grows beyond a modest page count. The sitemap index at /sitemap.xml references child sitemaps segmented by page type — typically one for store pages, one for static pages, and one for blog pages. Each child sitemap follows the standard XML format with loc, lastmod, and changefreq elements.
For stores with more than a few hundred products, this segmented structure helps Google allocate crawl budget efficiently. However, Wix does not expose controls to customize priority values or changefreq settings on a per-page or per-collection basis. Every product page receives the same default priority, which limits fine-grained crawl signaling available on platforms like Shopify or WooCommerce where developers can modify sitemap templates directly.
Wix SEO Panel and Sitemap Controls
The primary control surface for sitemap behavior in Wix is the SEO Settings panel, accessed under Settings → SEO. From here, store operators can exclude specific pages from indexing (which removes them from the sitemap), connect Google Search Console for automatic sitemap submission, and review which pages are currently marked as hidden. Wix's SEO Wiz tool provides guided recommendations but does not surface sitemap-specific diagnostics.
At the individual page level, every Wix page has an SEO tab in the editor where 'Hide this page from search results' toggles noindex and sitemap exclusion simultaneously. For product pages, this setting is accessible from the product editor inside the Wix Stores dashboard under each product's SEO section. Bulk management of indexation status across hundreds of products is not available natively — changes must be made product by product, which is a significant operational constraint for large catalogs.
Third-Party Apps and Workarounds for Sitemap Gaps
The Wix App Market contains SEO-focused apps — including SEOmatic and Wix's own SEO tools — that extend sitemap visibility and provide crawl diagnostics. SEOmatic, for example, generates supplemental sitemaps for structured data and provides a dashboard showing which pages are indexed versus excluded. These apps work alongside Wix's native sitemap rather than replacing it, so they address reporting and auditing more than they fix core generation limits.
For Velo-powered stores needing dynamic page inclusion in the sitemap, the recommended workaround is using the Wix Velo sitemap API, which allows developers to write custom sitemap generation logic via a sitemap.js file in the site's backend. This file can return dynamic routes from CMS collections directly into the sitemap index. This requires developer access and familiarity with Wix Velo's backend modules, placing it outside the reach of non-technical store operators without a developer on staff.
Stores that need full control over sitemap structure — custom priority, dynamic hreflang entries for multilingual catalogs, or XML news sitemaps for content-heavy stores — hit the ceiling of what Wix supports natively. In those cases, the practical path is either engaging a Wix Velo developer to build a custom backend sitemap, or evaluating whether platform constraints justify a migration to a more configurable ecommerce platform.
Actionable Steps to Audit and Improve Your Wix Store Sitemap
Start by fetching yourdomain.com/sitemap.xml directly in a browser and counting the child sitemaps in the index. Then open Google Search Console, go to Sitemaps, confirm the sitemap is submitted, and check the 'Discovered URLs' count against your actual product count in Wix Stores. A large gap between discovered URLs and live products points to pages set to hidden, products in draft status, or a Velo dynamic routing gap.
Next, audit individual products where ranking matters most: open each product in the Wix Stores dashboard, click the SEO tab, and confirm 'Hide this page from search results' is unchecked. For collections, do the same in the Wix Editor for each collection page. Finally, if the store uses Wix Multilingual, verify that translated product pages appear in the sitemap index — Wix generates separate child sitemaps per language, and misconfigured language settings can silently exclude translated pages from submission.