Keep Website Sitemaps Accurate After Changes

SECTION 01

Define which pages belong before choosing a generator

Ask the agency to document inclusion rules: published content, preferred domain, canonical path and the public page types you want eligible for search. Draft previews, private account pages, redirects and deliberately excluded duplicates should not enter merely because a crawler found a link. A content-driven generator is often easier to maintain than a hand-edited list, provided its eligibility rules are correct.

Google's sitemap guidance describes preferred canonical URLs and accurate last-modification information. Its status-code documentation helps explain why a listed URL returning an error is a different problem from a valid page not selected for indexing. The agency should check both the file and the actual destinations. More entries are not automatically better if they describe unavailable or unintended pages.

SECTION 02

Illustrative example: a consultancy publishes a new guide

Imagine a consultancy adding a reviewed implementation guide to its content system. Publication creates the public route, an internal link and a sitemap entry. A later substantive correction updates that guide's modification date. A separate deployment that changes a footer icon does not claim every article was rewritten. These events should follow content records rather than a blanket 'today' value inserted during every build.

The editor subsequently withdraws an obsolete guide and approves a replacement. The old URL's redirect behavior and the sitemap's preferred destination are checked together. The first release can use a simple generated sitemap with a small automated assertion against published records. More complex sitemap grouping is unnecessary until it serves a real reporting or scale need.

SECTION 03

Accept publishing events, not just XML syntax

Test a new page, a draft, a renamed page, a withdrawn page and an unchanged page across two deployments. Confirm absolute URLs, the expected domain, valid responses and the correct preferred destinations. Check that the public sitemap updates when content changes and that caching does not leave a stale version indefinitely. A valid XML file alone does not prove that the listed pages are appropriate.

Handoff should name who reviews sitemap processing errors and who investigates individual page-indexing issues. If Search Console is connected, review its last-read and processing information separately from page status. Repeatedly resubmitting an unchanged sitemap is not a repair for weak content or inaccessible pages. Ask the agency for a short diagnostic sequence so staff investigate the actual mismatch instead of treating submission as a ranking switch.

SECTION 04

Frequently asked questions