Website Redesign Without Losing SEO: The Migration Checklist

A new website should grow traffic. Too often it does the opposite: organic visits drop by a third after launch and take months to recover, if they recover at all. The cause is almost never the design itself. It is the migration — URLs that change without redirects, content that disappears, and technical signals that get lost in the rebuild.

Use this checklist to protect, and improve, your search visibility through a redesign or replatform.

Before design: build the baseline

• Crawl the current site with a tool such as Screaming Frog or Sitebulb and export every URL, title, description, heading, canonical and status code.
• Pull performance data from Search Console and analytics: pages with clicks, impressions and conversions over the last 12 months.
• Export backlinks to find URLs that other sites link to.
• Record rankings for your priority keywords so you can compare after launch.
• Flag high-value pages — the ones that drive traffic, links or revenue. These deserve the most care.

During design: protect what works

• Plan information architecture from search demand, not just the org chart. Make sure each priority topic has a dedicated page.
• Keep content depth. If an old page ranks because it answers a question thoroughly, the new page needs to answer it at least as well.
• Keep URLs where you can. Changing URLs is fine when it improves structure, but every change carries risk.
• Design for performance. Heavy imagery and scripts can undo SEO gains through poor Core Web Vitals.

Build the redirect map

Create a spreadsheet with every old URL and its new destination. Rules of thumb:

1. Redirect each old URL to the most relevant new page — not to the homepage.
2. Use permanent (301) redirects.
3. Avoid chains: old → new in a single hop.
4. Include URL variations: trailing slashes, uppercase, parameters, old HTTP and www versions.
5. Retire pages deliberately. If content is gone for good with no equivalent, a 410 or a well-designed 404 is more honest than a misleading redirect.

Before launch: technical QA on staging

• Titles, meta descriptions and H1s present and unique on every page.
• Canonical tags pointing to the correct new URLs.
• Structured data validated for organization, services, products, articles and FAQs.
• XML sitemap containing only live, indexable URLs.
• Robots.txt reviewed — and staging blocks removed before launch.
• Internal links pointing directly to new URLs rather than through redirects.
• Analytics, tag manager and conversion tracking installed and tested.
• Page speed and Core Web Vitals checked on mobile.

Launch day

• Deploy redirects at the same moment as the new site.
• Test a sample of old URLs — especially your high-value pages — to confirm they resolve correctly.
• Submit the new sitemap in Search Console.
• Check that forms, checkout and tracking are working in production.

Replatforming adds its own risks

Moving between platforms — for example from WordPress to a headless stack, or from one ecommerce platform to another — introduces risks beyond a redesign:

• URL structures change by default. Ecommerce platforms often impose their own patterns for product and category URLs.
• Rendering changes. JavaScript-heavy frameworks can hide content from crawlers unless pages are server-rendered or pre-rendered.
• Faceted navigation and parameters can explode the number of crawlable URLs if not controlled.
• Structured data and metadata stored in plugins or apps don’t migrate automatically.
• Image URLs change, which matters if image search drives traffic.

Budget time for a technical SEO review of the new platform before build begins, not after.

After launch: monitor closely

• Watch Search Console daily for crawl errors, 404s and indexation changes for two weeks, then weekly.
• Compare rankings and organic landing-page traffic against your baseline.
• Fix missed redirects as soon as they appear in error reports.
• Expect some short-term volatility. Sustained declines after four to six weeks usually point to a specific fixable cause.