A pre-migration sitemap checklist to preserve important URLs, redirects, canonicals, and indexing signals.
This guide is for teams planning cms moves, redesigns, domain changes, or url-structure migrations.. The goal is simple: use sitemap and crawl data to protect organic traffic during redesigns or platform migrations.
What This Solves
Sitemap and indexing issues usually come from mismatched signals: a URL is submitted but blocked, published but not canonical, discoverable but thin, or technically valid but not useful enough to deserve crawl attention. This page gives you a focused checklist for that exact problem area.
What to Check
- Export the current sitemap and indexed URL set.
- Map important old URLs to new destinations.
- Validate redirects and the new sitemap immediately after launch.
Common Mistakes
- Relying only on the new sitemap.
- Redirecting everything to the homepage.
- Submitting old redirected URLs after launch.
How to Prioritize the Fix
Start with the highest-value pages first: homepage, money pages, product or service pages, category pages, and articles already receiving impressions. Fixing a small set of important URLs usually produces a clearer result than changing thousands of low-value URLs at once.
After each fix, crawl the affected URLs, confirm the live HTTP status, check canonical and robots signals, then resubmit or monitor the relevant sitemap in Search Console. If the issue appears across many pages, fix the template or generator rather than editing individual URLs manually.
Bottom Line
Keep the sitemap focused on crawlable, canonical, useful pages. The more consistently your sitemap, robots rules, internal links, and page templates agree, the easier it is for search engines to process the site.
Next step: understand redirects in sitemap cleanup.