Create two records, not one verdict
A sitemap report and a page inspection describe different resources. Start one record for the sitemap URL and another for a representative page. In each record, capture the exact address, the observation time and the tool that produced the result. Do not transfer the status of one resource to the other.
Google explains that sitemaps help discover URLs but do not guarantee crawling or indexing of all listed items. A successful sitemap submission therefore cannot close a page-indexing task. Equally, a sitemap fetch error alone does not establish that every linked page is absent from Google.
Reproduce the sitemap response
Open the submitted address exactly as recorded, without a logged-in administrator session. Save the response status and body. Compare the hostname and path with the intended sitemap. A file you can open under a different address is not evidence about the submitted URL.
If the response is a login page, error template or redirect to an unrelated page, give that evidence to the hosting owner. If it is valid XML now, record that result with a timestamp rather than dismissing the earlier report. A current success and an earlier failure can both be accurate observations.
Assign an owner to each unresolved question
For delivery, ask the technical owner to correlate the reported period with server or security logs where available. The question is whether a request failed and what caused that failure. Do not infer bot blocking merely because the file opens in your browser.
For the sample page, review its individual Search Console inspection independently. If it has its own access, exclusion or canonical issue, create a separate task with that evidence. Avoid asking an editor to rewrite an article to solve a file-delivery issue that belongs to hosting.
Worked example: a stale file address
Illustrative scenario: a team submits /old-sitemap.xml, then moves its generator to /sitemap.xml. The newer address works, while the submitted address no longer serves the intended file. A service page inspected separately remains indexed.
The team records the mismatch, verifies the maintained map and submits the correct address. It does not claim that all pages were removed from search. Its completion evidence concerns the map and submission; the service-page inspection remains a separate observation. This example is a diagnostic pattern, not a verified customer incident.
Give the next reviewer a clean handover
Use an incident table with these fields: resource type, URL, observed status, observed time, evidence link, responsible owner and next action. Put the sitemap and sample page on different rows. When a report changes, add the new observation instead of overwriting the old evidence.
Close the delivery task when the intended file is served and the relevant submission outcome is recorded. Track page discovery and indexing separately. Keep useful internal navigation in place: Google also discovers pages through links, so the sitemap should complement a navigable website rather than be its only route to important content.