The Website Redesign Checklist We Run Before Any Rebuild

A redesign is one of the few projects that can make a site worse at its job while looking better. New design, same content, and traffic still drops 30% the week after launch — because nobody audited what the old site was doing right before they rebuilt it. Here's what we check first.

1. Export your current URL list before anything changes

Pull every indexed URL from Search Console and your XML sitemap before the rebuild starts. This is the baseline you'll redirect from and measure against afterward. Skipping this step is the single most common cause of a post-launch traffic crash — pages that ranked disappear with no 301 pointing search engines anywhere.

2. Map every old URL to its new equivalent — no exceptions

Every URL from step one needs a destination: a matching new page, a merged parent page, or an explicit decision that it's gone. "We'll figure out redirects at the end" is how sites lose rankings that took years to build. A technical SEO pass on the redirect map, not just the new templates, is what actually protects existing traffic through a rebuild.

3. Audit which pages are actually earning organic traffic

Not every page deserves to survive unchanged. Pull the last 12 months of organic sessions per URL and treat that as a priority list — the pages already earning traffic get the most redirect scrutiny and the most care in how their content carries over. A total site redesign is also the right moment to notice pages that never should have existed as separate URLs in the first place, and consolidate them instead of rebuilding them as-is.

4. Don't let new design regress Core Web Vitals

A more visually ambitious site is often a heavier one — more images, more animation, more client-side JavaScript. If the old site had a fast LCP and the new one doesn't, you've traded a ranking factor for a font choice. Set a performance budget for the new design before development starts, not as a fix-it-later pass; it's a much smaller lift to hit a target during the build than to claw back speed afterward.

5. Keep your structured data and metadata in the new templates

Product schema, article schema, breadcrumbs, Open Graph tags — these often live in the old templates and get dropped when the new design is built from scratch, since they're invisible in a Figma file. Confirm every schema type the old site emitted still exists on the new one before launch, not after a client notices their rich results disappeared.

6. Stage the launch behind a real crawl, not a visual review

A design review checks how pages look. It doesn't catch a broken canonical tag, an accidentally noindexed template, or a redirect loop. Crawl the staging environment with the same tools you'd use to audit a live site, and reconcile the URL count against your original export from step one.

7. Watch Search Console daily for the first two weeks, not the first day

Indexing and re-ranking after a URL structure change takes time — a clean launch day doesn't guarantee a clean week two. Coverage errors, unexpected 404s, and ranking drops for specific queries all tend to surface after the initial crawl wave, which is usually four to ten days out depending on how often the domain gets crawled.

None of this is about slowing a redesign down — it's about not undoing years of earned rankings for the sake of a new look. We ran this exact checklist on a full storefront rebuild that held steady through its next peak sales event instead of losing ground during the transition. If you're planning a rebuild and want the design and the SEO handled by the same team instead of stitched together after the fact, that's exactly the kind of project we take on.