Reconcile sitemap URLs with the public catalog
Compare intended catalog destinations with sitemap entries, response states and canonical preferences. Keep missing active pages, stale redirects and intentionally excluded items in distinct rows. The reconciliation helps locate a generation or source-record defect; adding more URLs does not resolve broken destinations or guarantee that search engines index them.
Worked example — illustrative data.
| URL | Catalog/store state | Disposition |
|---|---|---|
| /products/arc/ | Active intended destination; present in sitemap | Check response and internal link |
| /products/clamp/ | Active but absent | Investigate generation/filtering |
| /old/arc.html | Redirects to new product; still listed | Prefer final intended destination |
| /products/retired/ | Removed; still listed | Review catalog and sitemap removal |
| /products/box/?sort=price | Alternative URL | Review canonical/purpose mismatch |
Export the sitemap URL set and the intended catalog destination set with dates. Compare identity, status, canonical preference and internal discoverability for mismatches. Use a controlled sample to verify whether a reported active product is actually available to customers. Keep intentionally excluded pages in an exceptions list so the reconciliation does not create false alarms. Check last-modified values only where the system can supply meaningful update information.
Check both directions of the sitemap comparison
Compare the sitemap against the intended public catalog, then compare the intended public catalog back against the sitemap. The first direction finds retired or redirected URLs that remain listed; the second finds missing active destinations. Keep intentionally unpublished stock outside the required public set. Record the approved final URL for each mismatch instead of treating every inventory item as indexable.
Active inventory may be intentionally unpublished
A product can be active in inventory but intentionally unpublished or unavailable in a particular market. Confirm the destination policy before treating its absence from the sitemap as an error.
Correct the generation or source record that caused the mismatch, then regenerate and recheck. Do not submit a larger sitemap as a substitute for resolving broken pages or missing internal links.
Does a sitemap entry guarantee that Google indexes the product?
No. A sitemap helps discovery and describes intended URLs. Check the actual response, content, crawl rules and canonical signals separately. A valid sitemap entry is one diagnostic input, not confirmation of indexing.
Continue with Guides for stores, software teams and local businesses, Technical SEO services and How to migrate a store without losing its useful URLs.
For how sitemaps assist discovery, see Google sitemap documentation (checked November 2026).