Technical SEO Checklist Before a Website Redesign or CMS Migration
Google's own site-move guidance turned into a practical checklist: redirects, canonicals, Search Console, and what to monitor after launch.
A website redesign or CMS migration can lose most of a site's search rankings within weeks if the technical SEO groundwork isn't done before launch — not because Google penalizes redesigns, but because redirects, canonical tags, and sitemaps are easy to get wrong under a launch deadline.
Google's own site-move documentation is direct about the biggest cause of migration traffic loss: changing more than one thing at once. Here's the technical checklist to work through before you launch, based on Google Search Central's current guidance.
Key Takeaways
- Google's core migration guidance is to change one thing at a time — don't combine a domain move, a redesign, and a CMS migration into a single launch if you can avoid it.
- Every old URL needs a server-side 301/308 redirect to its new equivalent, with redirect chains kept short — Google recommends staying under 3–5 hops.
- Search Console needs both the old and new site verified (including www/non-www and HTTP/HTTPS variants), plus a Change of Address submission if the domain itself is changing.
- Redirects should stay active for at least a year after launch — Google explicitly warns against removing them early.
- A small-to-medium site can take a few weeks for most URLs to fully re-index after migration; larger sites take longer. That timeline is normal, not a sign something's broken.
Before You Touch Anything: Build a Full URL Map
Every indexed URL on the current site needs a documented destination on the new one before launch, not figured out reactively afterward. Pull the full list from Search Console's Index Coverage report and your current sitemap, and map each one — including any that are being consolidated, renamed, or removed entirely.
Google's Core Rule: Change One Thing at a Time
Google's site-move documentation is specific about this: combining a domain move with a redesign, content overhaul, or navigation restructure at the same time makes it nearly impossible to diagnose what actually caused a ranking or traffic change afterward. If a redesign, a CMS migration, and a new domain are all on the table, sequencing them separately — even a few weeks apart — makes problems traceable instead of tangled together.
The Technical Checklist
Redirects
- Server-side 301 (or 308) redirects for every old URL to its correct new equivalent — not a blanket redirect to the homepage.
- Keep redirect chains short; Google recommends staying under 3–5 hops from old URL to final destination.
- Plan to keep redirects active for at least one year post-launch, per Google's own guidance — removing them early can strand any traffic and link equity still arriving at old URLs.
Canonical Tags and Indexing Signals
- Every new page needs a correct, self-referencing rel="canonical" tag.
- Remove any noindex directives or robots.txt blocks that were only meant to keep the staging/development site out of search results.
- Update internal links sitewide to point directly to new URLs — relying on redirects for internal links wastes crawl budget and slightly dilutes link equity.
Search Console and Sitemaps
- Verify both the old and new site in Search Console, including www/non-www and HTTP/HTTPS variants.
- If the domain itself is changing, submit a Change of Address request in Search Console (not needed for an HTTP-to-HTTPS-only change).
- Submit the new XML sitemap, and remove the old one only once the migration is confirmed complete.
After Launch: What to Actually Monitor
Watch Search Console's Index Coverage and Sitemaps reports to track how the new URLs get indexed and how the old ones drop out. Server logs are worth checking too — unexpected 404s or 5xx responses on URLs that should be redirecting are the earliest signal something in the URL map was missed.
Why This Matters Specifically for a CMS Migration
A CMS migration adds a layer most redesigns don't have to deal with alone: the new platform's own URL structure, slug conventions, and redirect handling all have to match the plan above exactly, not approximately. See what to expect during a Payload CMS migration for how this checklist fits into an actual project timeline, and WordPress vs. Payload CMS if you're still weighing whether the migration is worth it in the first place.
Frequently Asked Questions
Will a website redesign hurt my SEO rankings?
Not inherently — Google doesn't penalize redesigns. Ranking loss during migrations almost always comes from technical mistakes (missing redirects, wrong canonicals, blocked indexing) rather than the redesign itself.
Should I redesign my site and migrate to a new CMS at the same time?
Google specifically recommends against combining major changes into one launch — it makes it much harder to diagnose what caused any ranking or traffic change afterward. Sequencing them separately is safer even if it takes longer.
How long should redirects stay active after a migration?
At least one year, per Google's own guidance. Removing redirects early can strand traffic and link equity that's still arriving at old URLs.
Do I need to submit a Change of Address in Search Console for every migration?
Only if the domain itself is changing. A CMS migration or redesign on the same domain doesn't need it — but you still need both old and new versions of the site verified in Search Console.
How long does it take for rankings to recover after a migration?
Google states a small-to-medium site can take a few weeks for most pages to re-index; larger sites take longer. A temporary dip during that window is expected, not necessarily a sign of a broken migration.
Sources and Further Reading
Google Search Central — Site Moves With URL Changes
Planning a Redesign or CMS Migration Without Losing Rankings?
A CMS migration review builds the full redirect map, canonical strategy, and Search Console plan before launch — not as damage control after traffic drops.
Written by
Rafael Arceo
Rafael Arceo is a digital marketing and web technology specialist focused on Google Ads conversion tracking, GTM, GA4, SEO, WordPress, Payload CMS, and website conversion setup.
Related Posts
Google's four LCP subparts explained, with the specific fix for each — and why compressing images alone often doesn't move your score.
What actually moves the needle on image-driven page speed — correct sizing, modern formats, and lazy loading — and what doesn't matter as much.
What LocalBusiness structured data actually does in Google Search and Maps, which fields matter most, and when a service business genuinely needs it.
Need Cleaner Tracking or a Better Website Setup?
Send your website URL and I can help identify what needs to be checked, fixed, or improved.