Best Practices for XML Sitemaps with Large Ecommerce Catalogs

Large ecommerce catalogs can get messy fast. New products, filters, expired items, redirects, and duplicate URLs can turn an XML sitemap into a noisy file instead of a useful crawl guide.

For large stores, a sitemap should include only the URLs you want search engines to find and index. That usually means canonical product pages, key categories, approved collections, and important content pages.

At Cartiful, we often see sitemap issues hiding bigger ecommerce SEO problems: redirected URLs, non-canonical pages, faceted URLs, and false lastmod updates. A clean sitemap helps reduce crawl waste and makes large catalogs easier to monitor.

Quick Answer

For large ecommerce catalogs, the best XML sitemap setup includes only canonical, index-worthy, fetchable URLs. 

Split large sitemap files by page type or section, use a sitemap index, keep lastmod accurate, remove redirects and non-indexable pages, and monitor sitemap performance in Search Console. Do not rely on Google’s old ping endpoint because it has been deprecated and now returns 404

What XML Sitemaps Do for Large Ecommerce Sites

An XML sitemap helps search engines find important URLs on your store. This is especially useful for large ecommerce sites where product pages, categories, media files, and supporting content can be hard to find through navigation alone.

But a sitemap does not replace internal links. 

Search engines still use your site structure, navigation, product links, category hierarchy, and crawlable anchors to understand which pages matter most.

Think of your sitemap as a clean discovery list, not a replacement for good architecture.

For large stores, XML sitemaps help with:

• Product URL discovery
• Category and collection discovery
• Faster awareness of important page updates
• Easier Search Console monitoring
• Better audit workflows by page type or section

They work best when they match the real canonical structure of the store.

What Should Be Included in an Ecommerce Sitemap?

Your sitemap should include pages that are index-worthy, canonical, and useful for organic search.

Most large ecommerce sitemaps should include:

• Canonical product pages
• Main category pages
• Important subcategory pages
• Approved collection or brand pages
• Buying guides and commercial content
• Localized URLs, when hreflang is properly handled
• Image data only when image discovery matters

It should usually exclude:

• Redirected URLs
• Noindex URLs
• Blocked URLs
• Non-canonical product variants
• Sort and filter parameter URLs
• Internal search result pages
• Empty category pages
• Expired products with no search value
• Duplicate paths to the same product

A simple rule: if you would not want that URL indexed, it should not be in your XML sitemap.

Why Canonical-Only Sitemaps Are the Safest Default

Large ecommerce stores often create multiple URLs for the same page. This can happen through filters, tracking parameters, product variants, sort orders, collections, or alternate category paths.

For example, the same product may be accessible through:

• A main product URL
• A category-based product URL
• A filtered collection URL
• A tracking parameter URL
• A color or size variant URL

Only the preferred canonical version should be included in the sitemap.

If your sitemap includes non-canonical URLs, it sends a mixed signal. Your canonical tag says one page is preferred, but your sitemap asks search engines to crawl another version. That creates noise.

A clean sitemap should support your canonical strategy, not compete with it.

Why lastmod Matters More Than priority and changefreq

For ecommerce sites, lastmod is the sitemap field worth getting right. 

Google says it may use lastmod when the value is consistently and verifiably accurate, and that it should reflect the last significant update to the page. Google also says it ignores priority and changefreq.

That means your team should not waste time assigning priority scores to every page. Focus on making lastmod trustworthy.

Good reasons to update lastmod include:

• Product description changes
• Major price or offer updates
• Structured data changes
• Important content updates
• Meaningful internal link changes
• Stock or availability changes that affect the page

Bad reasons to update lastmod include:

• Sitemap regeneration with no page change
• Footer copyright updates
• Tracking script changes
• Minor template edits that do not affect main content
• Updating every URL to make the sitemap look fresh

Bing has also warned against using sitemap generation time as the page modification date. In its 2023 analysis, Bing said 84% of known XML sitemaps included lastmod, but only 79% had correct values.

The point is simple: do not make every URL look updated every day. That can weaken trust in your sitemap data.

lastmod Done Right vs Done Wrong

For large catalogs, lastmod should reflect real page-level change, not system activity.

How to Split Sitemaps for Large Ecommerce Catalogs

Google’s technical limits are clear: one sitemap can contain up to 50,000 URLs or 50 MB uncompressed. If your store exceeds either limit, split the sitemap into multiple files and use a sitemap index. Google also notes that multiple sitemaps can help track search performance by individual sitemap in Search Console.

For large ecommerce stores, sitemap segmentation should not be random. Split sitemaps in a way that helps both search engines and your team.

Common sitemap splits include:

• Product sitemaps
• Category sitemaps
• Blog or guide sitemaps
• Brand or collection sitemaps
• New arrival sitemaps
• Region or language sitemaps
• High-priority catalog sitemaps
• Archive or low-update sitemaps

A store with 150,000 products might use:

• /sitemap-products-1.xml
• /sitemap-products-2.xml
• /sitemap-products-3.xml
• /sitemap-categories.xml
• /sitemap-guides.xml
• /sitemap-images.xml

Then all child sitemaps can sit inside one sitemap index.

Simple Sitemap Index Example

<?xml version=”1.0″ encoding=”UTF-8″?>

<sitemapindex xmlns=”http://www.sitemaps.org/schemas/sitemap/0.9″>

  <sitemap>

    <loc>https://www.example.com/sitemaps/products-1.xml</loc>

    <lastmod>2026-04-10</lastmod>

  </sitemap>

  <sitemap>

    <loc>https://www.example.com/sitemaps/categories.xml</loc>

    <lastmod>2026-04-09</lastmod>

  </sitemap>

  <sitemap>

    <loc>https://www.example.com/sitemaps/guides.xml</loc>

    <lastmod>2026-04-07</lastmod>

  </sitemap>

</sitemapindex>

Simple Child Sitemap Example

<?xml version=”1.0″ encoding=”UTF-8″?>

<urlset xmlns=”http://www.sitemaps.org/schemas/sitemap/0.9″>

  <url>

    <loc>https://www.example.com/products/womens-waterproof-hiking-jacket</loc>

    <lastmod>2026-04-08</lastmod>

  </url>

  <url>

    <loc>https://www.example.com/products/mens-trail-running-shoes</loc>

    <lastmod>2026-04-10</lastmod>

  </url>

</urlset>

The Best Sitemap Structure Is the One You Can Monitor

A sitemap split by page type or business section is easier to debug than one large file.

If product URLs are indexing well but category pages are not, segmented sitemaps help you find the issue faster. If one product section drops after a migration, a separate sitemap can make that easier to spot in Search Console.

This is where XML sitemap work becomes practical. The goal is not just to submit URLs. The goal is to know which parts of your catalog search engines are reading, ignoring, or struggling to process.

Screaming Frog’s sitemap audit guidance follows the same idea: XML sitemaps should be up to date, error-free, and include indexable canonical URLs. Its audit workflow can also compare sitemap URLs against crawl data to find orphan URLs, missing URLs, and non-indexable pages.

Automation Matters More Than Manual Sitemap Updates

Manual sitemap maintenance does not work for large catalogs. Product pages change, categories shift, items go out of stock, and redirects get added. Your sitemap logic should update automatically based on clear rules.

A solid automation setup usually handles:

• adding new canonical URLs automatically
• removing redirected, deleted, or blocked URLs
• updating lastmod only for meaningful changes
• rebuilding child sitemaps without rewriting the whole system
• validating output on a schedule
• publishing a stable sitemap index URL (Google for Developers)

The key warning: automation should not rewrite every lastmod value every time the sitemap is generated. That creates false freshness.

Submission and Discovery: What Still Works

For most ecommerce sites, the practical setup is simple:

• Add the sitemap index to robots.txt
• Submit the sitemap index in Search Console
• Use the Search Console API only when programmatic submission is needed
• Stop using Google’s old sitemap ping endpoint

Google has completed the deprecation of the sitemap ping endpoint. Requests to the old endpoint now return 404, and Google says sitemap submission should happen through Search Console, the API, or robots.txt.

For large stores, the main value of Search Console submission is not just discovery. It is monitoring. You can see whether Google processed the sitemap and whether any errors appeared.

Should Large Catalogs Use Image Sitemaps?

Sometimes, yes.

Image sitemaps can help when product images are important for search and are not easy to discover through normal crawling. This can happen on image-heavy stores, JavaScript-heavy product galleries, or catalogs where image search matters.

Image sitemap data is most useful when:

• Product images load through JavaScript
• Important images are missing from indexed product results
• Product visuals drive search demand
• The store has many unique product images
• Image search can support revenue

For many ecommerce stores, a clean product sitemap is enough. For visual categories such as fashion, furniture, rugs, beauty, decor, or accessories, image sitemap support may be worth testing.

XML Sitemaps and Feeds Can Work Together

XML sitemaps are best for the full set of important URLs. RSS or Atom feeds are better for recent additions and recently updated content.

For fast-moving ecommerce sites, a practical setup can be:

• XML sitemap for the full product and category catalog
• RSS or Atom feed for recent updates
• Separate monitoring for new or frequently updated sections

This is not needed for every store. But if a store publishes new products, guides, or seasonal collections often, feeds can support faster discovery of recent updates.

What to Monitor After Launch

Submitting a sitemap is not the final step. After launch, ecommerce teams should monitor how search engines process the sitemap and whether important pages are being indexed.

Track:

• Submitted URLs vs indexed URLs
• Sitemap fetch status
• Processing errors
• Non-canonical URLs in the sitemap
• Redirected URLs in the sitemap
• Noindex URLs in the sitemap
• Orphan URLs found only in the sitemap
• Important canonical URLs missing from the sitemap
• Sections with heavy “Discovered – currently not indexed”
• Crawl changes after migrations or catalog imports

This is also where internal linking matters. If an important product page only exists in the sitemap but has no strong internal links, it may be technically listed but still weak in the site structure.

For better results, connect sitemap cleanup with a technical SEO audit, internal linking review, and crawl budget analysis.

Practical Checklist for Large-Catalog XML Sitemaps

Build

• Include only canonical URLs.
• Keep each sitemap under 50,000 URLs and 50 MB uncompressed.
• Use a sitemap index for multi-file setups.
• Split sitemaps by page type, section, language, or update speed.
• Use absolute URLs only.

Clean Up

• Remove redirected URLs.
• Remove blocked URLs.
• Remove noindex URLs.
• Remove duplicate parameter URLs.
• Remove broken or empty pages.
• Remove expired products that should not rank.
• Remove faceted URLs that are not approved landing pages.

Freshness

• Use lastmod where you can keep it accurate.
• Update lastmod only for meaningful changes.
• Do not refresh every timestamp during routine sitemap generation.
• Ignore priority and changefreq for Google.
• Keep sitemap generation tied to real product and content changes.

Submit

• Add the sitemap index to robots.txt.
• Submit the sitemap index in Search Console.
• Use the Search Console API only if needed.
• Do not use Google’s deprecated ping endpoint.

Monitor

• Review fetch and processing status.
• Compare submitted vs indexed URLs by sitemap section.
• Audit orphan URLs.
• Check for non-indexable sitemap entries.
• Recheck after migrations, platform changes, catalog imports, or template updates.

Common XML Sitemap Mistakes on Large Ecommerce Sites

The same issues show up often:

• Adding every generated URL to the sitemap
• Including non-canonical product URLs
• Leaving redirected URLs in the sitemap
• Setting every lastmod value to today
• Spending time on priority and changefreq
• Splitting sitemaps without a reporting reason
• Including filtered URLs that should not rank
• Keeping discontinued products in the sitemap too long
• Treating sitemap submission as a one-time task
• Forgetting to compare sitemap URLs with internal crawl data

A sitemap should make your store easier to crawl and monitor. If it is full of duplicates, redirects, and stale URLs, it does the opposite.

Frequently Asked Questions

1. How many URLs can one XML sitemap contain?

One XML sitemap can contain up to 50,000 URLs and can be up to 50 MB uncompressed. If your ecommerce store exceeds either limit, split the URLs into multiple sitemap files and use a sitemap index.

2. Should large ecommerce catalogs use one sitemap or many?

Large catalogs should usually use multiple sitemap files under one sitemap index. This helps meet technical limits and makes it easier to monitor products, categories, content, and other sections separately.

3. What is the best way to split ecommerce sitemaps?

The best split is the one that helps reporting and maintenance. Common options include product sitemaps, category sitemaps, guide sitemaps, brand sitemaps, language sitemaps, and update-frequency sitemaps.

4. Should XML sitemaps include only canonical URLs?

Yes. As a default rule, include only canonical URLs that you want search engines to consider for indexing. Avoid duplicates, filtered URLs, redirects, and product URLs that canonicalize somewhere else.

5. Does Google still use priority and changefreq?

No. Google says it ignores priority and changefreq. For Google, accurate canonical URLs and trustworthy lastmod values are more useful than those older optional fields.

6. How should lastmod be handled on product pages?

Use lastmod only when it reflects a meaningful page update. Product copy changes, offer changes, structured data updates, important stock changes, or major internal link changes may justify a new date. Routine sitemap regeneration does not.

7. Should out-of-stock products stay in the sitemap?

They can stay if the page remains canonical, indexable, useful, and worth showing in search. If the product is permanently discontinued with no value or replacement, it should usually be removed, redirected to a close alternative, or handled according to your discontinued product strategy.

8. Can image data be added to product sitemaps?

Yes. Image sitemap data can help with image discovery, especially for visual catalogs or JavaScript-heavy product galleries. It is most useful when product images matter for search visibility.

Final takeaway

The best XML sitemap for a large ecommerce catalog is not the biggest one. It is the cleanest and easiest to trust.

Keep only canonical, index-worthy URLs. Split large sitemap files in a way that helps monitoring. Use accurate lastmod values. Remove redirects, noindex pages, and filtered junk. Then compare sitemap data with crawl and indexation data regularly.

For store owners, sitemap cleanup is not just a technical SEO task. It helps search engines focus on the pages that matter: key categories, priority products, strong collections, and useful buying content. 

Cartiful can help connect that cleanup with better site structure, stronger landing pages, paid traffic performance, and ecommerce growth.