A website redesign is one of the easiest ways to lose search traffic. Not because the new site is worse, but because the migration drops the signals the old site spent years earning — URLs, redirect maps, internal links, and structured data. SEO equity is fragile, and a redesign that doesn't plan for it can erase months of growth in a single deploy.
Inventory before you touch anything
Before the redesign begins, capture the full picture of what the current site has earned: every indexable URL, the pages that bring in organic traffic, the backlinks pointing in, and the keywords each page ranks for. This inventory is the baseline you'll protect. Without it, you can't know what you've lost when traffic drops after launch.
- Crawl the current site to capture every live URL and its status code.
- Pull the top organic-traffic pages from Search Console or your analytics tool.
- Export the backlink profile so incoming links can be preserved or redirected.
- Record the current structured data and any schema the site uses.
Map old URLs to new ones — every one
The single most common redesign mistake is letting old URLs 404 because nobody mapped them. Every URL that has traffic, backlinks, or history needs a 301 redirect to its closest equivalent on the new site. Build the redirect map before launch, not after traffic drops. A redirect map is a spreadsheet: old URL in one column, new URL in the other, and a status column you fill in after launch.
Preserve on-page SEO elements
Each new page should carry over the SEO elements that helped the old page rank: title tags, meta descriptions, H1 structure, and the body content itself. A redesign is not a content rewrite — if the old page ranked, the content was working. You can refresh and reorganize, but don't throw away the text that earned the ranking.
- Title tags: keep the ranking titles, or change them deliberately with a reason.
- H1s: one per page, matching the old structure where it worked.
- Body content: migrate the ranking pages' text; don't start from scratch.
- Internal links: rebuild the internal linking structure so pages aren't orphaned.
Structured data and sitemaps
Carry over any structured data (LocalBusiness, Article, Product, FAQ) the old site used, and submit a fresh XML sitemap to Search Console the day the new site goes live. The sitemap tells search engines which URLs to crawl; the structured data tells them what each page is. Losing either is a silent ranking hit that shows up weeks later.
Launch and the first two weeks
On launch day, deploy the redirect map, submit the new sitemap, and watch Search Console for crawl errors and indexation changes. Expect a short-term fluctuation in rankings as the new site is re-crawled; a well-executed migration recovers within weeks. A migration with broken redirects or missing content does not recover on its own — the traffic stays gone until you find and fix the gap.
- Deploy redirects: the full 301 map goes live before the old site comes down.
- Submit sitemap: push the new XML sitemap to Search Console immediately.
- Monitor crawl errors: watch for 404s, soft 404s, and dropped indexation daily.
- Compare traffic: compare old vs. new organic sessions after 2 weeks; investigate any page that dropped more than noise.