2 min readAn original planning guide. Use the linked primary documentation for platform details and the supported procedure for your environment.
Identify the generated source
Find the system or build step producing the sitemap. Note which content types and environments it includes.
Sample URL behavior
Check that listed URLs resolve as intended and match the preferred public address. Look for redirects, missing pages, and unintended preview hosts.
Review scope and metadata
Ensure private or intentionally excluded content is handled deliberately. Use accurate supported metadata rather than inventing modification dates.
Verify publication and maintenance
Check the public sitemap location and supported submission route. Assign ownership when content models or URL structures change.
Worked scenario
See the plan in practice.
A build copies an old staging hostname into sitemap entries. Verify full URLs, not just the list of page paths.
Review your result
Your acceptance checklist
URLs preferred- Environment correct
- Metadata truthful
Use these checks to identify gaps in your sitemap quality checklist. Assign an owner to any unresolved item before the next dependent step.
The terms behind the task
- XML sitemapA machine-readable file listing URLs a site wants search engines to discover, optionally with supported metadata.
- Canonical URLThe preferred representative URL selected or indicated for a set of duplicate or closely similar pages.
- CrawlingThe discovery and fetching of pages or resources by an automated crawler.
Primary references
For the underlying concepts and current platform details:
