A redesign is not a visual refresh with a new theme. From search’s point of view, it is a controlled migration of equity: URLs, content, internal links, structured data, and performance. Treat it like a migration even when the domain stays the same.
Inventory before you design
List every URL that earns traffic or links. Note titles, H1s, index status, and top landing pages. You cannot protect what you have not measured. This inventory drives the sitemap for the new site — not a blank wireframe deck.
Map URLs like your rankings depend on it
Every important old URL needs a destination. Prefer one-to-one where intent still matches. When pages consolidate, pick a primary and 301 the rest. Never leave soft 404s or “we’ll fix redirects later.”
Use the same discipline as a platform move. Our website migration SEO checklist covers the technical sequence; redesigns need that sequence too.
Content parity, not content amnesia
New copy can be better. It should not delete the entities, FAQs, and proof that already rank. Keep what searchers and Google already associate with you, then improve clarity and conversion.
Staging is for SEO QA, not just design QA
Crawl staging for broken links and missing titles
Validate redirects on a staging host or preview map
Check schema, canonicals, and noindex mistakes before go-live
Compare Core Web Vitals against the old site — regressing speed is an SEO change
Launch week monitoring
Watch Search Console coverage, top landing pages, and server logs for 404 spikes. Fix within days, not months. Ranking dips that last a quarter are usually preventable process failures, not “Google adjusting.”
If the redesign includes a platform change, read how we handle website migration.
For scoped packages, see pricing.
Real migration outcomes live in our work — including St. Louis and Kansas City corporate housing rebuilds.