A removed page remains in an old sitemap shard

What to change

The top-level inventory may point to several smaller files, and an old child file can preserve withdrawn routes. Ask the supplier to inspect every referenced part and provide a combined list of unique public destinations. A withdrawal test should remove the article from that complete list. Also check obsolete deployed files so someone following an older inventory reference does not continue to receive misleading publication information.

A worked example

Illustrative example

Illustrative test: Withdraw a sample guide and inspect both current and previously used shards. Ask for the combined route list so the practice can verify the withdrawal without inspecting individual files.

How to check the result

No referenced sitemap file advertises the withdrawn route.

A mistake to avoid

Reviewing only the sitemap index misses the URLs inside its children.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordOpen every child sitemap referenced by the index.Check each listed route against the approved public inventory.Remove obsolete shards through the generator's normal cleanup process.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.