Website Redesign Without Losing SEO: The Migration Checklist

Redesigning a website is exciting. Watching your organic traffic collapse two weeks later is not. It happens more often than it should, and it is almost always preventable.

The problem is not the redesign itself. It is that SEO migration gets treated as an afterthought. The new design is approved, the new code is written, the site goes live, and then someone notices that half the old URLs now return 404 errors. By the time redirects are in place, Google has already deindexed pages and reassigned rankings.

This checklist is the process we follow at ASPIRED Digital for every redesign project. It is ordered chronologically: before, during, and after launch.

Phase 1: Before You Touch the Design

Crawl and Document the Existing Site

Before you change anything, you need a complete picture of what exists. Use Screaming Frog, Sitebulb, or Ahrefs Site Audit to crawl your current site. Export a full list of:

• Every URL (including parameter variations)
• Each page's title tag, meta description, and H1
• Internal links and their anchor text
• Pages that receive organic traffic (pull this from Google Analytics or Search Console)
• Pages with backlinks (pull from Ahrefs or Semrush)
• Canonical tags and their targets

This export becomes your migration reference document. Every URL on this list needs a destination on the new site.

Identify Your High-Value Pages

Not all pages matter equally. Sort your pages by organic traffic and backlink count. The top 20% of pages typically drive 80% or more of your organic value. These pages get extra attention during migration. Any mistake with a high-value URL can cause significant traffic loss.

Build the URL Map

Create a spreadsheet with two columns: old URL and new URL. Every old URL gets one of three treatments:

• Direct match: The same page exists at a new URL. Map it with a 301 redirect.
• Merged content: Two or more old pages are being combined into one new page. All old URLs 301 redirect to the new combined page.
• Removed content: The page is being deleted with no equivalent replacement. 301 redirect to the most relevant parent page or category. Never let a previously indexed URL return a 404 without a redirect.

Be precise with this mapping. A lazy approach (redirecting everything to the homepage) will tank your rankings. Google treats mass homepage redirects as soft 404s.

Phase 2: Build the New Site With SEO Baked In

Preserve Metadata

Every page that performed well in search should carry its metadata to the new site. Copy across:

• Title tags (adjust only if improving them)
• Meta descriptions
• H1 headings
• Structured data / schema markup
• Open Graph and Twitter Card tags

If you are rewriting page content as part of the redesign, keep the same target keywords and search intent. Changing both the URL and the content at the same time makes it harder for Google to recognise the page as a continuation of the old one.

Implement Redirects in the Staging Environment

Do not wait until launch day to set up redirects. Implement them on staging and test them. For each redirect, verify:

• The old URL returns a 301 status code (not 302, not a chain of redirects)
• The destination URL returns a 200 status code
• There are no redirect loops
• There are no redirect chains (A redirects to B which redirects to C). Every redirect should go directly to the final destination.

Check Content Parity

If a page ranked for a keyword on the old site, the new version of that page should still target that keyword. Redesigns often involve content restructuring, and it is easy to accidentally drop sections of text, remove internal links, or change heading structures in ways that weaken topical relevance.

Compare the word count, heading structure, and keyword usage of high-value pages between old and new versions. Significant reductions in content depth can cause ranking drops even when everything else is done correctly.

Maintain Internal Link Structure

Internal links pass authority between pages. If your old site had a blog post linking to a service page, that link needs to exist on the new site too. Crawl the new staging site and compare its internal link graph to the old one. Look for orphaned pages (pages with no internal links pointing to them) that previously had strong internal linking.

Phase 3: Launch Day

Deploy and Verify Immediately

After deploying the new site:

• Crawl the live site with Screaming Frog and check for 404 errors, broken redirects, and missing metadata
• Manually test every redirect in your URL map (at minimum, test all high-value page redirects)
• Submit the new sitemap to Google Search Console
• Use the URL Inspection tool in Search Console to request indexing of your most important pages
• Verify robots.txt is not blocking any pages that should be indexed (staging environments often have a disallow-all robots.txt that gets accidentally deployed to production)

Monitor Search Console Closely

For the first 48 hours after launch, check Search Console's Coverage report and URL Inspection tool frequently. Look for:

• Spikes in "Excluded" or "Error" pages
• New 404 errors
• Pages marked as "Discovered - currently not indexed"
• Drops in valid indexed pages

Phase 4: Post-Launch Monitoring (Weeks 1 to 8)

SEO migration effects are not always immediate. Some ranking changes take weeks to appear.

Week 1: Daily Checks

Monitor organic traffic daily in Analytics. Compare to the same days in previous weeks. A small dip (10-15%) in the first week is normal as Google recrawls and reassesses. A major drop (40%+) indicates a problem with redirects, metadata, or content parity.

Weeks 2 to 4: Keyword Tracking

Track your target keywords and compare positions before and after migration. If specific keywords have dropped, investigate the corresponding pages. Common causes:

• The redirect is not working for that specific URL
• The new page has significantly less content than the old one
• Internal links that previously pointed to that page are missing
• The page's title tag or H1 has changed in a way that weakens keyword targeting

Weeks 4 to 8: Stabilisation

By week four, most rankings should have stabilised or recovered. If they have not, conduct a deeper audit comparing the old and new site's technical SEO signals. Check crawl stats in Search Console to confirm Google is crawling the new site at the same rate as the old one.

Keep your redirects in place permanently. Removing 301 redirects after a few months is a common mistake. As long as external sites link to your old URLs (and they will for years), those redirects need to work.

Common Mistakes That Kill Rankings

• Using 302 (temporary) redirects instead of 301 (permanent). A 302 tells Google the old URL might come back. Google may keep the old URL indexed and ignore the new one.
• Forgetting image URLs. If images change URLs and other sites hotlink or reference your images, those 404s generate crawl errors.
• Changing URL structure without redirects. Moving from /blog/post-title to /articles/post-title without a redirect means Google sees a new page and a deleted page, not a moved page.
• Launching with noindex tags from staging. Check every page's robots meta tag after launch.
• Removing structured data. If your old site had schema markup driving rich results, the new site needs equivalent markup.

Frequently Asked Questions

How long do SEO rankings take to recover after a website redesign?

With proper redirect implementation and content parity, most sites see rankings stabilise within two to four weeks. Some fluctuation in the first week is normal. If you follow this checklist, the recovery period should be minimal. Sites that skip redirect mapping or significantly change content can take three to six months to recover, and some rankings may never return if the damage is severe enough.

Should I change my URL structure during a redesign?

Only if there is a compelling reason. Every URL change requires a redirect, and every redirect carries a small risk. If your current URL structure is functional and clean, keep it. If your URLs are messy (query parameters, random IDs, deeply nested paths), a redesign is a good opportunity to clean them up, but plan your redirects carefully.

Do I need to tell Google about the redesign?

You do not need to formally notify Google, but you should submit your updated sitemap through Search Console and use the URL Inspection tool to request indexing of key pages. Google will discover the changes through crawling. Submitting the sitemap speeds up the process. If you are also changing your domain name (not just redesigning), use Search Console's Change of Address tool.

Can I redesign and migrate to a new CMS at the same time?

You can, but it increases risk. Changing the design, the content, the URL structure, and the underlying technology all at once creates more variables to manage. If possible, migrate the CMS first with the same design and URLs, verify everything is stable, then proceed with the redesign. If budget and timeline do not allow for two phases, be extra rigorous with your URL mapping and testing.