How to approach it
Fetch each child sitemap. Compare URL inventory with intended index status and sample response codes. Remove URLs that redirect, are retired or point canonically elsewhere, using platform controls where available.
Begin with the collection of child sitemaps and identify which platform or app owns each one. Confirm status and expected indexing on a mixed sample of recent, popular and retired URLs. Compare the URL strings exactly before normalising them, since a format mismatch can obscure which host or path the sitemap actually lists.
Worked example
If 60 archived listings still appear in a feed, identify whether an app or native sitemap exposes them, then fix the publishing source.
How to verify the change
When a retired listing disappears from a native sitemap, check redirects and catalogue menus separately. Removing a URL from the sitemap does not change how the old address responds. Keep reports of deliberate exclusions so an editor reviewing the most recent crawl can distinguish a known policy from a publishing error.
For large exports, group findings by template and publishing source. A sample can reveal a systemic sitemap rule worth fixing. Keep high-value exceptions visible because a small count can still represent an important part of the catalogue.