Website redesign: the complete process without losing rankings
A website redesign in seven stages, from audit to the month after launch, with the redirect map, staging checks and monitoring that protect your traffic.
By Sohail Hussain29 October 20267 min read
A website redesign that keeps its rankings follows seven stages: audit the current site, define what the new one must do, design and write the content, build on a staging site, map every old URL to a new one, launch with checks, and watch Search Console closely for a month. Skip the audit or the redirect map and the redesign that was meant to grow the business cuts its traffic in half.
This is the process we use on every website redesign and migration project. It works for a visual refresh on the same platform and for a full move from, say, WordPress to Next.js. The stages are the same; only the build stage changes. One caution from Google's site-move guidance: make big changes one after another, not all at once. If a new design and a new platform must launch together, keep the URLs and the content the same at launch, and change them in a later step once rankings have settled.
Before starting, check that you need a redesign at all. Not every tired site needs rebuilding. If the structure is sound, the platform is fine and the problem is dated visuals and weak copy, a refresh (new design applied to the same pages and platform) costs a third as much and carries far less SEO risk. Redesign vs refresh walks through the decision.
A full redesign is justified when the platform is holding you back (slow, hard to edit, insecure), the site structure no longer matches the business, or the site has to do new things that cannot be bolted on. The nine signs your website needs a redesign is a quick check.
Stage 1: audit what you have
Before anything is designed, record what the current site does for you. This is two or three days of work and it drives every later decision.
- Export every URL from the sitemap and from Search Console's Pages report. Sites usually have two to three times more URLs than anyone remembers.
- Record clicks and impressions per page over the last twelve months. The top 20 pages by clicks are the ones a redesign must protect.
- Note every page that has backlinks from other sites. Those URLs must redirect, whatever else happens.
- Run a crawl for broken links, redirect chains, missing titles and thin pages.
- Measure Core Web Vitals on the five most visited pages so you can show the new site beats them.
- List integrations: forms, CRM, analytics, chat, booking, payment. Each one has to be rebuilt or reconnected.
How to audit your current website covers the tools and the report format.
Stage 2: define what the new site must do
Write a one-page brief. Who the site is for, what a visitor should do on it, what the business needs from it (enquiries, applications, bookings), and which pages exist to earn search traffic. Decide the platform here, not after design: a layout that assumes a custom build will not translate to a theme.
This is the right stage for the hardest question: what to drop. Most sites carry pages nobody visits. Removing them is fine as long as they redirect to the closest live page. What to keep from your old website explains how to decide.
Stage 3: design and write the content together
Design and copy fail when they happen in sequence. A designer working from placeholder text produces layouts the real copy will not fit; a writer working without a layout produces pages that have to be cut in half. Run them in parallel with a shared sitemap and a rough wireframe per page type.
Keep page titles and headings for pages that rank unless you have a reason to change them. A page ranking for "warehouse racking Pune" does not need a cleverer heading. It needs the same heading, better supporting content and a faster load.
Stage 4: build on a staging site
The new site is built at a private address the public cannot see and search engines cannot index. Two things matter here.
The staging site must be blocked from indexing, with a noindex header or password protection, or Google will index two copies of your site and treat the new one as a duplicate. And that block must be removed at launch. We have seen sites launched with a noindex left on; the fix is a one-line change, and the damage is a month of lost indexing. Staging sites explained covers how to review a staging site properly.
Stage 5: build the redirect map
| Old URL situation | Redirect to | Code |
|---|---|---|
| Page kept, URL unchanged | Nothing needed | 200 |
| Page kept, URL changed | Its new URL | 301 |
| Two pages merged | The merged page | 301 |
| Page removed, close equivalent exists | The equivalent page | 301 |
| Page removed, no equivalent | The parent category page, or let it return 404 | 301 or 404 |
| Image and PDF URLs with backlinks | Their new file location | 301 |
Every row in the audit's URL list gets an entry. On a 40-page site this is an afternoon. On a 900-URL site it is the largest single document in the project, and worth every hour, because it is the difference between flat traffic and a cliff.
Three rules. Never redirect everything to the homepage; Google treats that as a soft 404 and the old rankings are lost. Point each redirect at the final destination in one hop, not through an old redirect. And include the old redirects already on the site, because the links that pointed at them still exist.
Our redirect mapping guide includes a spreadsheet template, and the redirect generator turns the finished list into rules for .htaccess, Nginx or next.config.ts. If you are also changing the domain, the domain change checklist adds the extra steps.
Stage 6: launch with a checklist
Launch on a Tuesday or Wednesday morning, when your team is available for the rest of the week. Then, in order:
- Remove the
noindexand any password on the new site. Confirm by fetching the homepage withcurl -Iand reading the headers. - Switch DNS or deploy to the live domain.
- Test fifty redirects from the map by hand, prioritising the top pages and the backlinked URLs.
- Submit the new sitemap in Search Console and request indexing of the homepage and the top ten pages.
- Confirm analytics, forms, chat and any payment flow work on the live domain, not just on staging. Send a test enquiry.
- Check robots.txt is the production version, not the one that blocked staging.
- Run Core Web Vitals on the same five pages you measured in the audit, and record the results.
Keep the old site's hosting alive for at least a month. You will need to check something on it: an image nobody exported, a PDF a customer still links to, or the exact wording of a page that ranked.
Stage 7: watch for a month
The first week after launch decides whether the redesign protected your traffic. The week after a migration is the detailed checklist; in short:
- Search Console's Pages report: watch for "Not found (404)" and "Page with redirect" counts. A rising 404 count is a missing redirect.
- Crawl stats: a spike is normal as Google recrawls everything. It settles within two weeks.
- Clicks by page, compared with the same pages before launch. Compare week to week, not day to day.
- Enquiries. A drop in form submissions with steady traffic is usually a form problem, not an SEO one.
Small drops of 5 to 15 percent in the first two to three weeks are normal while rankings resettle. A drop that persists past week four, or a drop concentrated in a few pages, is a problem to chase: usually a missing redirect, a changed title, or a page that lost content in the move.
Google's own guidance for all of this is the site move with URL changes page in Search Central. It is long, and it is the primary source every migration checklist, including this one, is built on.
If you are moving between platforms rather than redesigning on the same one, the platform-specific guides cover the extra steps: WordPress to Next.js, Wix to WordPress, Squarespace to WordPress and Webflow to WordPress. The general SEO side is in how to migrate a website without losing SEO.
Was this guide useful?