The SEO Checklist for a Website Redesign (So You Do Not Lose Your Rankings)

A redesign is the single most dangerous thing you can do to an established website. We are called in to diagnose traffic collapses several times a year, and the cause is almost never the design — it is the migration around it.

Here is the checklist we run before any site we build goes live.

1. Inventory every URL before you touch anything

Crawl the existing site and export every indexable URL, then join that list against Search Console and analytics data so you know which pages actually earn traffic, links and revenue.

You cannot protect what you have not counted. The pages that matter are rarely the ones in the navigation — they are usually old blog posts and long-tail landing pages nobody on the team remembers publishing.

2. Map redirects one to one

Every retired URL needs a 301 to the closest equivalent page. Not to the home page — a mass redirect to the root is treated as a soft 404 and throws away the link equity you spent years earning.

• One old URL to one new URL, matched by topic and intent
• 301 permanent, never 302 temporary, for a migration
• No redirect chains: A goes straight to C, not A to B to C
• Test the full map on staging before launch, not after

3. Carry metadata and content depth across

Titles, meta descriptions, H1s, canonical tags, structured data and image alt text all need to survive the move. So does the content itself.

Trimming a 1,800-word page that ranks well down to 400 words of elegant marketing copy is one of the most common self-inflicted ranking losses we see. If the old page ranks, the old depth is part of why.

4. Check what the crawler actually receives

Modern front-end frameworks make it easy to ship a page whose content only exists after JavaScript executes. Fetch your new templates as Googlebot would and confirm the title, the H1, the body copy and the structured data are present in the initial HTML.

If your stack is fully client-rendered, use server rendering or build-time pre-rendering for anything you want indexed. This matters more every year as AI answer engines, which are far less patient than search crawlers, become a real traffic source.

5. Benchmark Core Web Vitals before and after

Capture your current LCP, INP and CLS from field data, then hold the new build to at least that standard on a mid-range Android device over a throttled connection.

A redesign that looks better and loads slower is a net loss, and you will feel it in conversion rate long before you see it in rankings.

The 48 hours after launch

Resubmit the XML sitemap, watch Search Console coverage for spikes in 404s and redirect errors, crawl the live site to catch anything the staging environment hid, and keep the old analytics property accessible for comparison.

Expect a small dip for one to two weeks as the index catches up. Anything deeper than that, or anything still down after a month, is a problem to diagnose rather than a phase to wait out.