Key takeaways
- A website redesign only costs rankings when the SEO work is skipped. Crawl and benchmark first, map every URL to a 301, and monitor after launch.
- Before you rebuild, crawl the live site and benchmark its rankings, traffic and conversions, so you have a full inventory to protect and a baseline to measure against.
- Map every old URL to its new equivalent and redirect it with a permanent 301. A clean one-to-one redirect map is the single most important document in a migration.
- Carry across the content and metadata that earn traffic, keep tracking continuous through the switch, and never ship with the staging site's search-engine block still in place.
- After launch, submit the new sitemap, hold the 301s for at least a year, and judge the move on enquiries over four to eight weeks rather than a ranking check the next morning.
A website redesign loses SEO only when the SEO work is left out of it. A fresh design does not cost you rankings on its own. Sites lose organic traffic during a redesign through avoidable mistakes: changing URLs with nothing pointing the old ones at the new, cutting the content that earned the rankings, or pushing a staging build live with search engines still locked out. Plan the project as three stages, before launch, launch day and after launch, and you give both the rankings and the enquiries they bring the protection they need.
Why redesigns lose rankings, and why they do not have to
Rankings fall when URLs change without redirects, content gets thinner, or technical signals break, not because the design looks different. Google ranks pages, not pixels. When you rebuild, the danger is that the things Google already trusts quietly vanish. A page at a known URL moves to a new address with no redirect behind it. A well-ranked article is trimmed to three lines to suit a cleaner layout. The title tags, headings and structured data that helped a page rank are never carried across. Replatforming and restructuring URLs is where sites lose the most organic traffic, and almost always through mistakes a plan would have caught. Running a technical SEO audit of the current site before you change anything is the cheapest insurance in the whole project.
Before launch: crawl, benchmark and map
Before a single new page goes live, record what you have, so you can protect it and prove what changed. The groundwork here decides whether launch day is calm or a scramble, and it falls into three jobs: capture the current site, map every URL to its new home, and preserve the content and metadata that already rank.
Crawl the current site and benchmark it
Crawl the live site first, then benchmark its performance, so you have a full record to rebuild from and a baseline to measure against. Export every URL the site exposes with a crawler, then capture where it stands today: top organic pages, the keywords each one ranks for, monthly organic traffic, Core Web Vitals, and the pages that generate calls and form fills. Save all of it. This is the inventory of what you are protecting and the yardstick you will hold the new site to in the weeks after launch. Benchmarking performance against Google’s Core Web Vitals thresholds now, while the old site is live, tells you whether the rebuild is faster or slower once it ships.
Map every old URL to a 301
Map every old URL to its matching new URL and redirect it with a permanent 301, so the authority each page has earned moves with it. Build a simple spreadsheet: old URL, new URL, and a note for anything that needs a judgement call. Match like for like, page to closest equivalent page. Google’s site move guidance recommends server-side permanent redirects (301 or 308) and mapping old URLs to their new destinations before the move. Resist the temptation to send everything that has moved to the homepage, because Google treats a mass redirect to an unrelated page as a soft 404, so you lose the signal you were trying to keep. This redirect map is the single most important document in the project, and the heart of the technical SEO work that protects a move.
Preserve the content and metadata that rank
Carry across the content and the metadata that earn traffic, rather than rebuilding pages from scratch. A new look does not have to mean new words. For every page that ranks or converts, keep the body copy that supports it, and carry over the title tag, meta description, H1 and heading structure, image alt text and structured data. Designers working to a tidy template will often shorten copy without realising a thousand words of it was doing the ranking. Agree, in advance, which pages are protected and must keep their depth. If a page is genuinely being retired, that is a redirect decision, not a quiet deletion.
The phased redesign checklist
Run the move against this before, during and after checklist, and the common failure points have nowhere to hide. Each row is a job with a reason attached, so nobody skips it as busywork.
| Stage | Action | Why it matters |
|---|---|---|
| Before | Crawl the current site and export every URL | Captures the full inventory, so nothing is lost in the move |
| Before | Benchmark rankings, traffic, top pages and conversions | Gives a baseline you can measure the new site against |
| Before | Map every old URL to its new equivalent as a 301 | Moves the authority each page earned to its new address |
| Before | Record titles, meta descriptions, headings, alt text and schema | Lets you carry metadata across instead of rebuilding it |
| During | Keep staging blocked from indexing, then remove the block at launch | Prevents a site-wide deindex from a leftover rule |
| During | Publish the redirects server-side as the new site goes live | Sends people and Google straight to the new URLs |
| During | Keep analytics and tags live through the switch | Leaves no blind spot in the data at the moment it matters |
| After | Submit the new XML sitemap in Search Console | Tells Google what to crawl and index first |
| After | Re-crawl the site to confirm redirects resolve in one hop | Catches chains, loops and stray 404s early |
| After | Monitor indexation, rankings and enquiries for several weeks | Surfaces problems while they are still cheap to fix |
Launch day: redirects, indexing and tracking
Launch is the moment the redirects go live, the search engines are let back in, and the tracking keeps running without a gap. Three things have to happen together, and in the right order.
Publish the redirects server-side
Switch the redirects on as the site goes live, using permanent server-side 301s, not temporary ones. Google’s redirects documentation explains that 301 and 308 are permanent and tell Google the new URL should be the canonical one, while 302, 303 and 307 are temporary and leave the old URL in place. For a redesign, permanent is almost always what you want. Test a sample across the whole map the moment they are live, and confirm each old URL lands on its new target in a single hop rather than bouncing through two or three.
Remove the staging block
Remove whatever was keeping the staging site out of Google, because a block left in place will deindex the new site. Most teams build behind a robots.txt Disallow: / or a site-wide noindex. That protection is sensible during the build and a disaster if it ships. Checking it at go-live is a thirty-second job that prevents weeks of lost visibility, and it is one of the most common ways a careful redesign still falls over.
Keep tracking continuous
Keep analytics, tags and conversion tracking running through the switch, so you can see what the new site is doing from minute one. Carry your GA4 setup and event tracking onto the new build, verify the site in Search Console, and confirm that calls, forms and other conversions still fire. Continuous data is what lets you tell a normal post-launch wobble from a real problem, and it protects the thing that actually pays the bills, which is a website that converts.
If your domain is changing too
If the redesign also moves you to a new domain, tell Google with the Change of Address tool, on top of the redirects. When you move from one domain or subdomain to another, Google’s Change of Address tool in Search Console signals that the move is deliberate and helps transfer signals faster. You need both the old and new properties verified under the same account, and the 301s still have to be in place; the tool supports the move, it does not replace the redirects. It does not cover a switch from HTTP to HTTPS, or between www and non-www, which are handled differently.
After launch: monitor, and give it time
After launch, watch the data closely, hold the redirects for the long term, and judge the move over weeks rather than hours. A redesign is not finished when it ships; it is finished when the numbers settle.
Watch Search Console closely
Check Search Console often in the first few weeks, because that is where a migration problem shows up first. Watch the Pages report for indexation, submit and track the new sitemap, and keep an eye on impressions and clicks for your priority URLs. Some movement is normal while Google recrawls and reassigns signals across the new addresses. A steady slide in indexed pages, or old URLs that are not redirecting, is your cue to act fast rather than wait.
Keep the redirects in place
Leave the 301s running for the long term, not just the first busy fortnight. Google advises keeping redirects for at least a year so it can move all the signals across and other sites’ links can catch up, and there is a fair case for keeping them indefinitely. Pulling them early, once traffic looks fine, is a quiet way to undo the protection you built, especially for pages with backlinks pointing at the old URL.
Judge success by leads, not just rankings
Measure the redesign on enquiries and revenue over four to eight weeks, not on a ranking check the morning after launch. Rankings often dip for a week or two as Google reprocesses the site, then recover. The number that matters is whether the new site brings in as many calls and forms as the old one, and ideally more. Give it a few weeks of continuous data before you draw conclusions, and compare against the benchmark you captured before launch.
Planning a redesign? Protect the rankings you have
A redesign should grow your traffic, not reset it. If you are rebuilding and want the rankings and leads to survive the move, our web design team builds fast, search-friendly sites with the redirect mapping and technical SEO handled as part of the project, not bolted on afterwards. Book a free growth review and we will tell you where your current site is strong, what to protect, and what we would do first, or get in touch if you already have a launch date in the diary. Plain answers, no jargon, for businesses in Leicester and across the UK.