What SEO work needs to happen before a website redesign launches?
Written by
Passionate Designer & Founder
Before a website redesign launches, you need five things in place: a full crawl export of every indexed URL, a redirect map covering every URL that will change, a baseline traffic and ranking report by page, a Core Web Vitals benchmark for the current site, and a confirmed staging environment where all of it can be tested before anything goes live. Miss any one and you are doing damage control after launch instead of prevention before it.
Want a website live fast? You can build one in Framer (View more here).
Start with the crawl. Use Screaming Frog or Sitebulb, set the crawl depth to unlimited, and export every URL returning a 200 status. Cross-reference that against Google Search Console to find which URLs actually receive organic traffic or have indexed impressions. That intersection is your protected asset list. These are the pages you cannot afford to break, redirect incorrectly, or quietly delete because someone decided to clean up the navigation.
Where redirect maps actually fail
The redirect map is where most redesign projects fall apart. The typical workflow I see: design team builds the new IA, dev team builds the site, someone creates a spreadsheet of old-to-new URLs the night before launch, and half of it is wrong or incomplete. The correct workflow is to finalize the IA, build the redirect map as a deliverable before a single page is built in Webflow or any other CMS, and treat it as a living document that gets QA'd on staging at least twice. Every redirect chain longer than one hop needs to be flattened. Chain redirects bleed link equity and slow crawl.
Content is the piece teams consistently underweight. If the current site has 80 pages and the redesign brief calls for 40, someone needs to audit which of those 80 pages rank, attract backlinks, or serve long-tail intent before anything gets cut. Removing a page that drives real pipeline because it looked redundant in a sitemap exercise is a business cost, not a design opinion. I have seen this mistake made on projects with otherwise careful planning.
Core Web Vitals matter more than most teams account for. Benchmark Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint on the current site using PageSpeed Insights, then set explicit targets the new build must hit before launch. A Webflow site loaded with custom interactions and large hero videos will frequently underperform a simpler build on LCP. Get the targets into the design brief, not the post-launch QA doc. That ordering matters more than people think.
On a McKinsey workstream we supported last year, the pre-launch SEO checklist ran to 47 line items across four categories: technical migration, content preservation, structured data, and analytics continuity. Analytics is the piece most teams skip entirely. If your GA4 or Heap events are firing against old page paths, your post-launch conversion data is broken before anyone notices the traffic dip.
The final check before launch is a staging crawl. Set up the full redirect map on staging, crawl the environment, and verify every old URL resolves correctly to the right new destination. This takes two to four hours and catches roughly 80% of the errors that would otherwise surface in Search Console three weeks later. It is not glamorous work, but skipping it is how you end up in an emergency retrospective.
For a structured view of the full pre-launch sequence, the website redesign checklist covers each phase in order. If you want to pressure-test your specific migration plan, book a 20-min intro and we can walk through it. For the full guide, read our website redesign seo overview.
