The playbook
XML Sitemaps: Checklist
Use this XML sitemaps checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect valid sitemap URLs. Check an actual page or query record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Build the sitemap from eligible published records, not every route the application can generate. Exclude draft pages, error responses, and URLs redirecting elsewhere. Use last-modified information only when it reflects meaningful page changes. A sitemap is a discovery aid, not a promise of inclusion.
Before you use the checklist
Name the exact item being checked and its purpose. Gather URL, status, canonical, last material update. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Include intended indexable canonical pages | A dated observation showing how URL was verified | SEO lead |
| Exclude redirects errors and private URLs | A dated observation showing how status was verified | content or development owner |
| Update the file when eligible published content changes | A dated observation showing how canonical was verified | analytics owner |
Check the failure path
- Look specifically for this failure: assuming sitemap submission guarantees indexing.
- Use the sitemap alongside crawlable navigation and quality pages. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check last material update.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Include intended indexable canonical pages,” a meeting about the subject is not the evidence itself. Retain the relevant URL and status, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents provide a machine-readable list of important canonical URLs for discovery deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow valid sitemap URLs using a consistent definition so later reviews can connect execution quality with useful results.
Test representative templates as well as individual URLs. When a problem appears on several pages built from the same component, a template correction may be more useful than a series of one-off edits. Verify the affected pages after the shared change.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now