XML Sitemap Verification Checklist: URLs, Responses and Search Console
A submitted sitemap is a discovery aid, not an indexing receipt. Check the sitemap itself and the pages it lists before interpreting a successful submission as proof that all content is visible in search.
Identify the active sitemap generator
Record the public sitemap or sitemap-index URL and the theme, plugin or platform that produces it. If several generators are installed, determine which output is intended to be active rather than submitting every possible address.
Open the public output without administrator privileges. Confirm that it is a sitemap response, not a login screen, error page or ordinary page with a similar name. Check child sitemaps when an index points to separate content lists.
Review the URL population
Select representative URLs from each listed content type. Include a recent page, an older page and a special template. Check that the addresses use the intended public hostname and lead to the expected content.
Google recommends listing the preferred canonical URLs in a sitemap and notes that sitemap submission does not guarantee crawling or indexing. Use the canonical checklist to compare the page declaration with the listed address. Keep staging domains and accidental obsolete copies out of the intended production list.
| Check | Evidence to record | Next decision |
|---|---|---|
| Public output | Sitemap/index URL and accessible response | Correct access or generation faults |
| Coverage | Expected content types and sample recent pages | Investigate omitted intended pages |
| URL quality | Final preferred addresses and page responses | Remove wrong-domain or obsolete entries |
| Metadata | Meaningful modification dates where provided | Avoid arbitrary timestamps |
| Search submission | Property, submitted URL and reported result | Separate fetch success from index status |
Check exclusions deliberately
Confirm that private, removed or intentionally non-indexable content is treated according to the site’s plan. A sitemap should not become an instruction to expose pages that were deliberately restricted.
If a desired page is missing, inspect its publication state, template and generator exclusions. Adding its URL manually may hide a systematic configuration issue. If a listed page returns a 404 or redirects, decide whether the sitemap should instead name the current preferred destination.
Submit and interpret the result
Use the relevant verified Search Console property and submit the actual public sitemap URL. Record the submitted address and the reported fetch or parse outcome. If the tool cannot read it, compare that with a logged-out request and the host’s access evidence.
Then inspect representative URLs separately. A sitemap read successfully, a page crawled and a page indexed are different milestones. Avoid repeatedly resubmitting an unchanged sitemap as a substitute for investigating an access, canonical or content problem.
Keep updates tied to publishing
After publishing a batch of pages, confirm the generator includes the intended new URLs and that they resolve. After deleting or moving pages, verify that obsolete entries are handled. Check the index as well as child lists when troubleshooting coverage.
Close with a dated record of the generator, tested child sitemaps, sample URLs and any unresolved exclusions. Do not invent a universal time by which search engines must discover or index every listed page. Track the observed search result separately from the technical sitemap check.
Investigate an included URL that no longer works
If a hypothetical sitemap lists a URL that redirects or returns 404, inspect its publication status and intended final URL. Correct the content state or generator’s inclusion rule rather than manually editing a generated file that will be overwritten. Recheck the sitemap and the destination together. Keep submission success separate from whether Google later crawls or indexes each eligible page.
Sources and scope
Official documentation checked October 6, 2026: Google: Build and submit a sitemap. This is HRL’s verification checklist, not a report of a completed migration or a guarantee of crawling, indexing or rankings.
Related guides
Check visibility controls · Review moved URLs · Verify migration discovery