The Website Redesign SEO Migration Checklist That Keeps Your Rankings

A new website should be a step up. Faster, clearer, easier to convert. But the version of a redesign that quietly destroys a business is the one where the site looks beautiful and the phone stops ringing — because the pages that used to rank on Google now return 404s, or redirect to the homepage, or never got mapped at all. A shiny new site that tanks your traffic is one of the most expensive own goals in small business. The rankings you've built over years are an asset, and a redesign puts that asset on the table.

The good news: this is preventable. Search engines do not punish you for redesigning. They get confused when the move is done badly. The whole game is making the transition legible to Google — same content, same value, new clothes. Below is the full website redesign SEO migration checklist we work through on every rebuild, in the order that actually matters.

Why redesigns lose rankings (and why it's avoidable)

When organic traffic falls after a launch, the cause is rarely the new visuals. It's the plumbing. Pages move to new URLs and nobody tells the search engine where they went. Internal links point at addresses that no longer exist. The staging site's "block everything" setting ships to production by accident. Each of these is a known failure mode with a known fix.

One figure is worth holding onto. Analyses of redesign traffic loss consistently attribute the bulk of it — well over three quarters in some accounts — to broken or missing redirects alone. That single discipline, done properly, is the difference between a dip you barely notice and a drop you spend months clawing back.

Set expectations honestly with whoever signs off the project. Even a clean migration often shows a small, temporary wobble while Google recrawls and reassigns signals. Google itself notes that a small-to-medium site "can take a few weeks for most pages to move," and that larger sites take longer (Google Search Central). Knowing that in advance stops a normal two-week recrawl from triggering a panic.

The pre-redesign SEO audit: know exactly what you have

You cannot protect what you haven't measured. Before a single new page is designed, capture the current site in full. This pre-redesign SEO audit is the foundation everything else sits on, and it has to happen while the old site is still live.

• Crawl every URL. Run a tool such as Screaming Frog across the live site and export the complete list of pages, their status codes, internal links and metadata. This is your master inventory.
• Pull the performance data. Export Google Search Console (which queries and pages bring traffic), Google Analytics, and your server logs. You want to know which pages earn the visits and the revenue.
• Identify the pages that pay the rent. Flag your top organic landing pages, anything with valuable backlinks pointing at it, and pages ranking for terms you'd hate to lose. These get protected first and tested hardest.
• Record the metadata. Title tags, meta descriptions, heading structure, canonical tags and structured data. The new site should carry the winners forward, not silently overwrite them.

By the end of this step you have a spreadsheet of every page, its rankings, its links and its value. That spreadsheet is the spine of the whole migration.

Build the 301 redirect map — one page at a time

If there's a single line that decides whether you redesign your website without losing rankings, it's this one. A 301 is a permanent redirect: it tells Google a page has moved for good and passes the majority of that page's earned authority to the new address. A 302 is temporary and does not transfer that value reliably. For a redesign, you use 301 (or its sibling 308) — Google explicitly recommends "HTTP permanent redirects if possible, such as 301 and 308."

The redirect map for a website redesign is a spreadsheet with the old URL in one column, the new URL beside it, the redirect type, and a notes field. Three rules turn that map from a liability into a safety net:

• Map one-to-one, not many-to-one. Every old URL points to its closest equivalent new page. The lazy shortcut — bulk-redirecting everything to the homepage — tells Google the old content simply vanished, and you lose its rankings outright.
• Kill redirect chains. Old URL A should redirect straight to final URL C, never A to B to C. Chains bleed authority and slow the page. Point each original address directly at its final home.
• Account for the long tail. Old blog posts, filtered category pages, PDFs, image URLs — anything in your crawl and server logs that ever earned a visit or a link needs a destination.

Then test every redirect before launch and again immediately after. A map that looks perfect in a spreadsheet but was never verified on the live server is how rankings quietly disappear.

The golden rule: don't change URLs you don't have to

The cleanest way to preserve SEO during a site redesign is to give Google less to relearn. Every URL you keep identical is a page that needs no redirect, carries no risk and recovers no rankings — because it never lost them. If your address structure is sound, keep it. Reserve URL changes for cases where the old structure is genuinely broken or confusing.

This runs against the instinct to "tidy everything up" during a rebuild. Resist it. Even a flawlessly implemented 301 carries a small chance of ranking drift; the surest way to avoid that risk is to not introduce the change at all. When a designer or platform wants to restructure your URLs for neatness, the question to ask is: what do we gain, and is it worth the migration risk on a page that's already ranking? Often the answer is no.

Stage it safely — and don't ship the "block everything" switch

The new site gets built on a staging environment, and that environment must be kept out of Google's index so it doesn't compete with your live pages as duplicate content. Here's the trap that catches even experienced teams.

People reach for robots.txt to hide staging. But robots.txt only asks crawlers not to visit — it is not a reliable way to keep a page out of the index. As Google's documentation makes clear, to actually keep a URL out of search you "password-protect the files on your server, use the noindex meta tag or response header, or remove the page entirely." Worse, if you block staging in robots.txt, Googlebot can't read a noindex tag inside the page — so a single external link can get the staging URL indexed anyway. The professional move is to protect staging with a password or IP allowlist, full stop.

The flip side is the launch-day disaster: a developer adds a site-wide noindex or a blanket robots.txt disallow on staging, and that setting ships to production. The new site goes live invisible to Google. The pre-launch checklist must include a single, deliberate step — remove all indexing blocks before the site is public — verified by a human who opens robots.txt and views source on a live page.

Launch day and the first fortnight

Launch is the start of the migration, not the end. The actions in the first two weeks decide how quickly Google reassigns your authority to the new URLs. Work this SEO website migration guide sequence on the day and immediately after:

• Confirm redirects are live and correct. Spot-check your highest-value pages first, then run the full map. Every old URL should land on its mapped new page with a single 301 hop.
• Lift any indexing blocks. Verify robots.txt is correct and no stray noindex survived from staging.
• Submit the new XML sitemap in Search Console. This hands Google a clean list of the new URLs to crawl. Google's own advice is to submit the new sitemap and let it supersede the old one.
• Use Change of Address if the domain changed. Moving to a new domain (not just HTTP to HTTPS) means using Search Console's Change of Address tool to signal the move formally.
• Check internal links and canonicals. Internal links should point at the new URLs directly, and canonical tags should reference the new addresses — not the old ones a templating system may have carried over.

Then monitor closely. The consensus across migration practitioners is daily checks for the first week or two, easing to weekly through about month three. In Search Console, watch the Index Coverage and Sitemaps reports for crawl errors, and the Performance report for queries that slip. Catch a missed redirect in week one and it's a five-minute fix; catch it in week eight and you've lost rankings that take longer to rebuild than they did to lose.

Keep the redirects — and structure for AI answers while you're here

Two things often forgotten once traffic looks stable. First, leave the redirects in place. Google advises keeping them "for as long as possible, generally at least 1 year," because that's how long it can take for every signal — including links from other sites — to fully transfer. From a user's point of view, keeping them indefinitely costs nothing and only helps.

Second, a redesign is the ideal moment to make your content legible to AI search as well as classic search. As AI Overviews and assistant-style answers increasingly summarise pages rather than send a click, clear structure earns citations: concise direct answers near the top, sensible headings, and FAQ or HowTo structured data where it genuinely fits. You're rebuilding the templates anyway — bake it in now rather than retrofitting later.

None of this is exotic. It's discipline applied in the right order: audit, map, preserve, stage safely, launch deliberately, monitor honestly. Do that, and the redesign does what it was meant to — a better site that keeps every ranking you earned. Skip it, and the prettiest site in your sector becomes the most expensive mistake on your balance sheet.