Before you start designing
Crawl the current site
Record every URL, title, meta description and heading. Tools like Screaming Frog make this easy.
Export your best pages
From Search Console and Analytics: which pages get traffic, rankings and conversions? These must be protected.
Export your backlinks
Pages with external links pointing at them need redirects, even if they get little traffic.
During the build
Map every old URL to a new one
One to one where possible, otherwise to the closest relevant page. Never redirect everything to the homepage.
Keep what's working
If a page ranks well, keep its content, or improve it carefully. Don't cut text just because the new design looks cleaner without it.
Carry over the SEO basics
Titles, meta descriptions, headings, alt text, internal links and structured data.
Block the staging site
Staging sites should be password-protected or noindexed, and that rule must be removed at launch. Forgetting this is surprisingly common.
Test speed and mobile
A redesign is the best chance you'll get to fix Core Web Vitals.
At launch
Put 301 redirects live
Test a sample of old URLs, especially your top pages and those with backlinks.
Submit the new sitemap
In Google Search Console, and check robots.txt allows crawling.
Check tracking
Analytics, conversion events, call tracking and pixels all firing on the new site.
After launch
Watch Search Console daily for the first two weeks: coverage errors, 404s, drops in impressions. Some fluctuation is normal for a few weeks. A steep, lasting drop usually means redirects or indexing problems, and the sooner they're fixed, the faster you recover.
When a redesign is also a clean-up
Sometimes the right move is fewer pages. When we rebuilt seospidy.com we went from 13,066 pages to about 70 and redirected everything else. That's a bigger decision than a normal redesign. I've written up why we did it.