A sitemap containing old addresses often points to a generator that was not fully updated. When a product has moved, list its intended current version. The old address can retain its redirect without also being presented as a separate content page in the sitemap.
Take three real examples from the file: a recently moved product, an unchanged article and a removed page. Inspect each response and its final destination. If the sample reveals an error, inspect all entries of that content type.
A small inspection record
This fictional dataset separates observations from decisions:
| Listed address | Response | Action to assess |
|---|---|---|
/old/lamp/ | 301 to /products/lamp/ | Inspect the current destination for inclusion |
/insights/care/ | 200, self-referencing canonical | Retain if publication is intended |
/products/discontinued/ | 404 | Remove from the generator |
A 200 status alone does not make a URL suitable. An empty error view or intentionally excluded page does not belong merely because the server reports success.
Correct the generator
Change the query selecting published addresses. A manually cleaned XML export often becomes outdated again during the next automatic run. Check for disabled products, incomplete language versions and accidental parameter URLs.
After the next normal export, compare its count and sample with the previous version. Submit the current sitemap in Search Console and compare submitted and discovered addresses. Use the redirect checker for individual chains.