A redesign is the most common way a small business destroys its own search traffic. Not a Google update, not a competitor, but a launch day where the new site looks better and the enquiries stop. The good news is that the causes are boring and predictable, which means a website redesign SEO checklist can catch nearly all of them before anyone presses the button.
Why do redesigns lose rankings in the first place?
Think of each ranking page as an account with a balance built up from years of links, mentions and user behaviour. Change the URL without a redirect and the balance is stranded on an address that now returns a 404. Cut the 600 words of copy that explained the service and replace them with a hero image and four words, and the page no longer matches the queries it used to answer. Drop the footer links to the service pages and the crawler discovers them less often.
Most of these mistakes are made by people acting in good faith. The designer wants a cleaner page. The developer wants tidy URLs. The owner wants rid of the old blog. Each decision is reasonable in isolation and expensive in combination.
What should you crawl and record before anyone touches the old site?
A desktop crawler such as Screaming Frog will produce the URL inventory in minutes for a typical small business site. Export it to a spreadsheet and keep it somewhere the whole project team can see. Then add three columns from Search Console: clicks over the past year, impressions, and the top query per page. Sort by clicks. The top twenty rows are your protected pages, and every later decision should be checked against that list.
Record the pages that link to you from other sites too. Backlink tools show which of your URLs external sites point at. Those addresses need redirects even if the page content is being retired, because the link equity lives on the address.
Finally, take a full-page screenshot of every protected page and save the copy as plain text. When someone asks in week six why the boiler servicing page lost half its traffic, you want to be able to show that it used to have 900 words and a pricing table and now has 120 words and a video.
How do you build a URL map that survives the migration?
The rule of closest equivalent matters more than it sounds. Google's site move documentation is explicit that the move takes place on a per-URL basis, so each old page is evaluated on where it now points. An old page about emergency electricians in Leeds should land on the new emergency electrician page, not the electrical services hub. A retired blog post with no real successor can point to the category page that covers the same topic. Bulk redirecting hundreds of dead pages to the homepage tends to be treated as a soft 404, and the equity evaporates.
Include the odd variants. Trailing slashes, uppercase paths, old query-string URLs, PDFs, and image files that other sites embed. These are the addresses that turn up in the 404 report in week two.
Which redirects should you use, and for how long?
Google's guidance on site moves with URL changes says to keep redirects for as long as possible, generally at least one year, so that all signals can be transferred, including recrawling and reassigning links. The same page notes that Googlebot will follow up to 10 redirect hops, but advises redirecting to the final destination directly and keeping any chain short, ideally no more than three hops. In practice a small business should aim for one hop everywhere, because chains accumulate over successive redesigns and each one adds latency and risk.
Where the redirects live depends on the stack. For a WordPress site on a managed host, the host's redirect manager or a small rules file is fine. For a Next.js or similar framework, the redirect map goes in the config file and ships with the code, which means it is version controlled and survives a hosting change. Avoid redirect plugins that store rules in the database only, because they are easy to lose during a platform switch.
Test the map before launch. A crawler in list mode can take the entire old URL column, request each address against the staging site, and report the status code and final destination. Any 404, any 302, and any chain of more than one hop is a bug to fix before go-live.
What content must carry over unchanged?
This is the argument most owners lose, because the old pages look cluttered next to the new mockups. The answer is layout, not deletion. Long-form copy can sit below a clean hero, behind tabs, or in an expandable section that is still in the HTML. What it cannot do is disappear.
Structured data is the other quiet casualty. If the old site marked up its reviews, opening hours, or service area, and the new template drops that markup, rich results vanish. Compare the schema on the old and new versions of each protected page, and check the new site's markup in Google's Rich Results Test before launch. For a local firm the review markup often drives more clicks than any ranking gain, which is why it pairs naturally with a process for responding to Google reviews.
Internal links need the same audit. If the old site had a sidebar linking every service page from every other service page, and the new one relies on a hamburger menu, the crawl depth of those pages just increased. Rebuild the links in the footer or in the body copy.
How do you keep the technical signals intact?
The staging noindex is the classic. Development sites are hidden from search engines for good reason, and the setting is frequently baked into the template or a platform-level toggle. The site goes live, looks perfect, and starts dropping from the index a page at a time. Check the page source of the live homepage within the first hour and look for a noindex directive. Check the robots file too.
The sitemap should be regenerated from the new site and submitted in Search Console once the site is live. Google's site move guidance says the old sitemap can be removed at that point. Do not leave a sitemap listing old URLs that now redirect, and do not submit the new sitemap while the new pages are still blocked.
Canonical tags deserve a specific look on any page that exists in more than one form. Pagination, filtered category pages, and print versions all tend to generate duplicates. The new template should point each variant at its primary version.
Speed is worth a mention here because a new build is the cheapest moment to fix it. A study commissioned by Google and run with Deloitte, published in 2020, analysed 37 European and American brand sites and over 30 million sessions and found that a 0.1 second improvement in load time raised retail conversion rates by 8.4 per cent and travel booking rates by around 10 per cent, with retail customers also spending 9.2 per cent more per order. The ranking effect of speed is modest by comparison. The conversion effect is not, and it applies directly to any UK shop or ecommerce site going through a rebuild.
Should you go live all at once or in stages?
The staged approach appeals because it feels safer, but it doubles the work. Two sites must be kept consistent, cross-linking becomes complicated, and the crawler sees a site that is half old and half new for weeks. Google's site move guidance recommends moving all URLs on the site simultaneously for anything short of a large site, and notes that it can take a few weeks or more for a medium-sized site's new URLs to gradually replace the old ones in results.
Pick a launch window that is quiet for the business. A Tuesday morning is better than a Friday evening, because problems get noticed and fixed while people are working. Avoid the fortnight before a seasonal peak.
What do you check in the first 48 hours after launch?
Run the same list-mode crawl you ran against staging, but against the live domain. Every old URL should return a 301 or 308 to the mapped destination. Then crawl the new site fresh and look for pages returning 404, pages with noindex, and pages missing from the sitemap.
Use the URL Inspection tool in Search Console on the top ten protected pages to request indexing and confirm Google can fetch them as a user would see them. Check that the rendered page includes the body copy and not just a loading state.
Test on a phone, and preferably on a slow mobile connection. Ofcom's Online Nation 2025 report, as reported by ISPreview, found that UK adults spend around four and a half hours a day online outside work, with the large majority of that time spent on a smartphone. A redesign that looks superb on the designer's monitor and hides the phone number behind three taps on a handset has failed the majority of its visitors.
How do you monitor recovery over the following months?
Search Console's comparison view lets you set the pre-launch month against the current one and filter to a single URL. Work down the protected list. A page that has lost half its clicks a month after launch is a page to inspect: check its redirect if the URL changed, compare the live copy against the saved text, and look at whether its internal links survived.
Watch the coverage report for pages Google has marked as not found or as redirects it considers soft 404s. Those are the entries in your URL map that pointed somewhere too loose.
Backlinks deserve a follow-up. For the handful of sites that link to you and matter, an email asking them to update the link to the new address is worth the ten minutes, because a direct link beats a redirected one. It is also worth reading how answer engines and AI search treat your pages after a migration, since those systems re-crawl on their own schedules and can lag traditional search.
When is a redesign worth the risk at all?
The honest trade-off is this. A rebuild that keeps URLs, keeps copy, and improves speed and mobile usability is close to pure upside. A rebuild that changes the platform, the structure and the content all at once is a migration, and migrations cost weeks of fluctuation even when done well. Decide which you are doing before the design brief is written, and put the crawl, the map, and the redirect test in the project plan next to the wireframes rather than after them.
If the rebuild is being done by an agency or freelancer, ask them for the URL map and the redirect test results as deliverables. A team that cannot produce them is not doing the SEO half of the job, and the web build service you choose should treat that half as standard, not as an add-on.
Website Redesign Without Losing Your SEO Rankings — FAQ
How long does it take Google to process a website redesign?
It depends on the size of the site and whether URLs change. Google's own site move documentation says that for medium-sized websites it can take a few weeks or more for the new URLs to gradually replace the old ones in results, and longer for larger sites. The move happens per URL, not all at once, so some pages will switch quickly while others lag. If the design changes but every URL stays identical, there is no move to process and the risk is far lower. Plan for a few weeks of fluctuation either way, keep redirects in place for at least a year as Google recommends, and judge success on a monthly view of clicks and impressions rather than day-to-day movement.
Do I need to keep the same URLs when I redesign my website?
Keeping URLs identical is the single safest choice, because it removes the need for redirects and the signal loss that comes with a migration. That is not always practical. Old sites often have messy paths, date-stamped blog URLs or a page structure that no longer matches the business. If you must change URLs, map every old address to the closest new equivalent, use permanent server-side redirects, and avoid pointing dozens of pages at the homepage. Where an old page has no real replacement, redirecting it to a genuinely related page is fine, but redirecting everything to the homepage tends to be treated as a soft 404.
Should I use 301 or 302 redirects for a site migration?
Use permanent redirects. Google's redirect documentation states that permanent redirects, such as 301 and 308, tell its indexing pipeline that the target should be canonical, and the new URL is what appears in search results. Temporary redirects, such as 302 and 307, keep the source page in results and do not pass the canonical signal. Set redirects at the server level, either in the web server config, a hosting rule, or a framework's redirect file, rather than through JavaScript or a meta refresh. Redirect each old URL directly to its final destination in a single hop rather than through a chain of intermediate addresses.
Will a faster new website improve my rankings?
Speed matters more for conversions than for rankings on a typical UK small business site. A study commissioned by Google with Deloitte, which analysed 37 brand sites and over 30 million sessions, found that a 0.1 second improvement in load time lifted retail conversion rates by 8.4 per cent and travel booking rates by around 10 per cent. Ranking effects from speed are real but modest, and they will not rescue a migration that lost its redirects or its content. Treat speed as a conversion win you bank after the SEO fundamentals are secure, and measure it with field data from real visitors rather than a single lab test.
What is the most common mistake in a website redesign SEO checklist?
Forgetting to remove the noindex tag or the robots block from the staging site when it goes live. Development sites are usually hidden from search engines, and that setting is easy to carry into production. The result is a new site that quietly drops out of the index over the following days while everyone celebrates the launch. The second most common mistake is rewriting or trimming content on pages that ranked well, because the copy that earned the position is treated as clutter by the designer. Check both within the first hour after launch.
