What is an XML sitemap? Discovery hints rather than an index guarantee
Explain sitemap URLs and modification dates and distinguish submission, crawling and indexing during maintenance.
Understand the concept
XML sitemaps list discovery URLs and metadata. They do not guarantee crawling or indexing or enumerate accepted pages. Use valid canonical targets, truthful modification dates and remove withdrawn URLs. Generation or submission does not establish search acceptance; inspect processing and pages.
Protocol fields aid discovery rather than decide rankings
Sitemaps.org defines fields and Google describes discovery limits. Sitemaps do not replace navigation links. lastmod should reflect meaningful changes, not every build date. Duplicate parameter URLs can conflict with canonicals. List public useful pages rather than treating URL counts as sufficient for exposure.
Check syntax and actual destinations in one sitemap
Parse a test sitemap and check canonical destinations, live states and excluded drafts or withdrawals. Verify changed-page lastmod against actual edits and existing child maps. No sitemap or private console was accessed here. Valid XML and reachable pages do not establish indexing; observe it separately.
Synchronize sitemaps and links with page lifecycles
Update maps and links for additions, canonical changes and withdrawals. Builds can check duplicates and missing targets, but meaningful edits need truthful dates. Include live and processing checks. Report file availability, submission and observations separately. Do not refresh all dates or invent URLs for apparent freshness.
Checked sources
These sources support the concepts and methods described here. Examples and test scope are labeled separately; check the version of the tools you use.