The playbook
XML Sitemaps: Template and Field Guide
This XML sitemaps template turns a broad task into a record another person can use. It captures URL, status, canonical, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| URL | Record the URL associated with this page or query record. Use a stable reference so later updates can be matched. |
| status | Record the status associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| canonical | Record the canonical associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| last material update | Record the last material update associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with URL. Use the same reference throughout the record so notes are not attached to the wrong item. Then include intended indexable canonical pages. This establishes the information required before the worksheet becomes a request for action.
Next, exclude redirects errors and private URLs. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as assuming sitemap submission guarantees indexing, rather than a broad instruction to “improve performance.”
Finally, update the file when eligible published content changes. Put use the sitemap alongside crawlable navigation and quality pages in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Assuming sitemap submission guarantees indexing |
| Action | Use the sitemap alongside crawlable navigation and quality pages |
| First check | Include intended indexable canonical pages |
| Follow-up check | Update the file when eligible published content changes |
| Outcome to define | valid sitemap URLs |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If status changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep valid sitemap URLs connected to the item so the team can later assess whether the action was useful.
Search results and indexing decisions are not controlled by the publisher. Record what your team changed and what was observed afterward. Avoid turning a correlation between a release and a traffic change into a claim of proven causation.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now