A redesign changes more than the way a site looks. It changes the map search engines use to understand what still exists, what moved, and what deserves attention.
That map is often the sitemap. When it is wrong after a redesign, the site can look clean to visitors while search engines keep finding stale or missing URLs.
What usually goes wrong
The first problem is old URLs that remain in the sitemap after pages are removed. Search engines keep receiving invitations to crawl pages that now return 404s or redirect somewhere vague.
The second problem is missing new pages. A redesigned service page can launch perfectly and still stay out of the sitemap because the route was added outside the generator's expected pattern.
The third problem is mixed host or protocol signals. Some sitemap URLs use www, others do not. Some have trailing slashes, others do not. Individually these look minor. Together they tell crawlers the site has no single source of truth.
Check sitemap entries against live responses
After a redesign, crawl every URL listed in the sitemap. Each one should return the expected status, canonical tag, and final destination. A sitemap full of redirects is not automatically a disaster, but it is often a sign the generator is publishing old knowledge.
Then check the reverse direction: important live pages should appear in the sitemap unless there is a deliberate reason to exclude them.
That second pass matters because missing URLs do not create loud errors. They simply become harder for crawlers to discover and revisit.
Watch the first two weeks
The redesign risk is highest immediately after launch, but the proof window continues. Search Console may start reporting new indexing issues days later, after Google processes the changed map.
Monitor sitemap fetch status, indexed page counts, not-found URLs, redirect patterns, and canonical mismatches. The goal is not to panic at every neutral Search Console row. The goal is to catch structural mistakes before they become the new normal.
Keep the old map for comparison
Before launch, export or save the old sitemap. After launch, compare it to the new one.
Some removed URLs should be gone. Some should redirect to replacements. Some may reveal pages that were accidentally dropped from the redesign plan. Without the old map, teams rely on memory, and memory is a poor migration tool.
Put sitemap checks in the release habit
Sitemap monitoring should not be a once-a-year SEO chore. Any time a site changes platform, route structure, canonical host, service pages, or blog system, the sitemap deserves a proof pass.
Site Clinic treats this as part of website operations because sitemaps are not content. They are infrastructure for discoverability.
If you are comparing monitoring tools, ask whether they only ping the homepage or whether they can tell you when structural SEO files drift. Our comparison page shows why uptime alone is not enough after a redesign.