imbahub
Menu +
US
Talk to us
IMBAHUB / Knowledge & guides

Check that unpublishing reaches the sitemap actually being served.

A deleted CMS record can survive in an older sitemap. Compare versions rather than searching source code alone. Use a marked test page and an agreed access outcome: a sitemap does not independently determine whether a page can be opened or indexed.

Locate the version difference
  1. Source correct?

    Check the intended status and URL.

  2. Artifact correct?

    Compare the generator's actual selection.

  3. Delivery correct?

    Inspect the sitemap response from the environment.

Acceptance includes a control page that must remain listed.

The stale row has gone, but all other pages are missing too. Pass?

No. Selection must exclude the correct record while retaining the intended positive controls.

Record the baseline and the page decision

Record test page identity, language, URL and publishing version. Identify the sitemap and any child file containing the address. Distinguish removing the entry from the intended page response after unpublishing.

A fictional retired course sheet might have a relevant replacement or none at all. Decide that before the test. Do not invent a broad redirect merely to make a check pass, and do not put private information on the test page.

Follow the source change through build and delivery

Unpublish in a safe environment and identify the job expected to update the sitemap. Compare source status, generated file and actual XML response. A correct file on a developer's disk does not establish what the traffic-serving environment uses.

If the list is split, check the affected child sitemap and index. An old child file can still be linked or served. Record available version or timing evidence without changing content lastmod simply to label a build.

StateCheckExpected evidence
Published test pageSource and delivered listCorrect approved URL appears
Unpublished recordNew selection after the jobAddress absent under the decision
Failed buildWhich version still serves?Version and failure visible to the owner
Old child fileIndex and actual XML responseNo active stale entry overlooked
RepublishingNew status and any new URLOnly the currently intended address returns

Isolate why an address remains

If source status is correct but the build file is wrong, inspect selection rules and the source read by the job. If the build file is right but delivery is old, inspect the deployment artifact, host and cache layer. Change one established cause at a time.

Include a positive control: another intended page must stay listed. Empty XML is not an accepted fix for one stale row. Verify the page response and relevant internal links separately, without exposing protected content to crawlers.

Test republishing and state the limits

Republish the marked page under the test plan. If its address changed, only the currently intended URL should return; the old address follows its own migration decision. Review language groups if equivalents are affected.

Record source, job, artifact, actual XML, page response, remaining drift and owner. An address disappearing from the sitemap does not prove that a search engine has removed it from its index. Monitor search status separately when authorized evidence is available.

Sources and further reading

Questions, answered

Does sitemap removal remove a page from Google?

Not by itself. Other routes may make the URL known; access and indexing directives need separate decisions.

Must lastmod change when the sitemap is rebuilt?

No. A page modification date is different from the file generation time.

IMBAHUB

Let’s plan your website

Choose a marked test page and trace its removal through to the delivered XML response.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.