XML sitemap for e-commerce: what to include and what not

If you want steadily growing organic traffic, the first step is clean indexing signals. An XML sitemap for e-commerce is not an “SEO trick” – it is a map that helps search engines reliably find and periodically re-crawl your most important pages: products, categories, brands and key informational pages. A properly structured sitemap speeds up the discovery of new products, while lastmod (last modification date) allows crawlers to plan re-crawls more intelligently. It’s important to understand what to include, what to leave out and how to handle technical limits.

What this gives you in practice

A sitemap does not replace internal linking, but it helps: new products are discovered faster and important updates (prices, stock, content changes) are missed less often. You don’t need any “priority” or “changefreq” – an accurate URL and a correct lastmod are enough. If lastmod honestly reflects real changes, crawlers will return faster to the pages you actually update.

What to include in an XML sitemap for e-commerce

Product pages (PDP). Include only indexable canonical URLs – the main address of each product. If you have variants (size/color), keep only the canonical PDP in the sitemap; include variant URLs only if they are canonical themselves and have unique content.

Categories / collections. Only those that should be indexed (not filtered views). Make sure the URL is parameter-free and canonical.

Brand pages (if used). Valuable when they have substantial content and are consistently indexed.

Important CMS pages. Shipping, returns, warranty – trust signals and frequently searched pages.

Images (recommended). Add product images via an Image Sitemap (a separate file or an extension to the same URLs) so search engines can more reliably discover and associate visuals with the PDP. The minimum required field is <image:loc>.

Best practice: keep PDPs and categories in separate sitemaps (e.g., product-sitemap.xml, category-sitemap.xml), and images in image-sitemap.xml or attached to the specific PDP URLs. This makes administration and error tracking easier.

What not to include (and why)

Search, cart, account and checkout URLs. System pages should not be indexed.
Parameter / filter pages (?size=M&color=red). Faceted navigation creates hundreds of duplicates – don’t waste crawl budget.
Pagination (2, 3, 4…) – keep only the first category page in the sitemap; crawlers will understand the rest via internal links.
UTM and other tracking parameters. This is noise – never include them in the sitemap.

Size, structure and limits (for large catalogs)

One XML sitemap can contain up to 50,000 URLs and up to 50 MB (uncompressed). Larger catalogs use a sitemap index – an index file that points to multiple separate sitemaps (by type, language or date). Recommendation: separate fast-changing content (products) from slow-changing content (policies, About). This makes lastmod changes more visible where they happen most.

`lastmod` – how to use it correctly

Don’t update lastmod “just because”. A meaningful change is a content, price, stock or structured data update that is visible to users. If lastmod reflects reality, search engines will re-crawl the pages that actually change more often.

For e-commerce, a frequent “meaningful” change is a price or availability update on a PDP. In that case, updating lastmod is worth it.

Multilingual / multi-country stores: `hreflang`

hreflang helps search engines understand which page versions are intended for different languages or countries. You can implement it in HTML or in the sitemap – consistency is what matters: all versions must reference each other and form complete groups.

WooCommerce and PrestaShop: implementation flow

WooCommerce (WordPress).

Evaluate what wp-sitemap.xml or your SEO plugin generates: are products, categories and images properly separated?
PDP must have a canonical URL; lastmod must reflect real changes (title, price, stock, content).
If you use a separate Image Sitemap, make sure the main PDP image is always included.

PrestaShop.

Clean module-generated lists from search, filter, cart and parameter URLs.
Leave category pagination for internal navigation – include only the first page in the sitemap.
For large catalogs use a sitemap index and split by type/language.

Most common mistakes

An overloaded sitemap (filters, search, UTM) – a sea of duplicates and wasted crawl budget.
Fake lastmod (“always today”) – the signal loses its value.
Ignoring limits (50k URLs / 50 MB) – some URLs are left out.
Image Sitemap without required fields – missing <image:loc>.
Partial hreflang – incomplete groups and missing return links between languages.

Quick audit plan (15 min.)

Are sitemaps split by type (product, category, pages) and, if needed, by language?
Are there no search/filter/UTM/pagination URLs?
Is lastmod updated only after a meaningful change?
Is the PDP hero image included (Image Sitemap)?
Is a sitemap index used and submitted in Search Console?

Conclusion

An XML sitemap for e-commerce should be short and precise: only canonical, indexable pages, a real lastmod, images where they add value, and a clear structure for large catalogs. This setup speeds up the discovery of new products and categories and helps maintain a cleaner index.