Sitemap Hygiene After a Website Rebuild: SEO Checklist

A rebuild changes URLs, templates and often the CMS underneath. The sitemap is where all three either agree or contradict each other. Most post-launch visibility problems we are asked to diagnose are not mysterious algorithm events; they are a sitemap describing one version of the site while the canonicals and redirects describe another.

Keep the sitemap URL stable

Search Engine Journal reported in September 2026 that Google warned against unstable sitemap URLs used as a cache-busting trick — changing the file name or appending a version parameter to force a fresh fetch. The practical guidance is the opposite of that instinct: publish one sitemap URL, keep it at that address permanently, and change the contents of the file rather than its location. A stable URL is what lets a crawler build a history of what you have published.

The post-launch checklist

Align canonicals, redirects and internal links

These four signals have to tell one story. The sitemap lists URL A, page A self-canonicals, no redirect sits between A and anything else, and your navigation and body links point at A. When a redirect chain survives a rebuild — old URL to interim URL to new URL — fix it to a single hop, then confirm the sitemap lists only the destination. Chains are tolerated, not free, and they are the easiest post-launch cleanup to leave half-done.

Sample by template, not by page

A rebuild ships templates. If one template renders a wrong canonical or drops a heading, it does so on every page built from it. So sample: pick two or three URLs per template — home, service, location, article, product, paginated listing — and check status, canonical, title, H1, robots meta and internal links on each. Finding one broken template is worth more than spot-checking fifty pages at random.

Set lastmod honestly or leave it out

A lastmod value is a claim that the page changed meaningfully on that date. Stamping every entry with the build timestamp makes the whole file uninformative, because every page looks equally fresh after every deploy. If your generator cannot supply a real per-page timestamp, omit the element. An absent value costs you nothing; a false one trains crawlers to ignore the signal.

The 30-day monitoring rhythm

1. Day 0. Submit the current sitemap, remove stale submissions, confirm the robots.txt reference.
2. Days 1–7. Check the Pages report daily for new exclusions, redirect notices and canonical mismatches, and fix the template that caused each one.
3. Weeks 2–4. Weekly checks. Watch the discovered-versus- indexed gap close, and inspect individual URLs where it does not.
4. Day 30. Re-run the template sample, then compare impressions and clicks to a matched pre-launch period of equal length.

Reading the reports without over-reading them

Coverage and performance reports lag. Recrawling a large site takes weeks, so a drop in indexed URLs on day three is more likely a processing state than a penalty. Compare like periods, note the launch date on every chart you share, and resist re-fixing something that was already fixed and is simply waiting to be re-crawled.

Sources

• Search Engine Journal, report on Google's warning against unstable sitemap cache-busting, September 2026.
• Google Search Central documentation on sitemaps, canonicalization and site moves with URL changes.
• Google Search Console Help on the Sitemaps and Pages reports.

Crawl data, backlink data, search volume, keyword difficulty and ranking forecasts are not included here because they were not available for this article and are site-specific.

Our SEO audit page explains how we run post-launch technical checks, the SEO services page covers ongoing work after a rebuild, and reporting shows how we track recovery. To have a recent rebuild checked, contact us.