Website redesign checklist: relaunch without losing SEO

A website redesign keeps your search traffic and your leads safest when you do four things: record how the current site performs before anything changes, list every page and decide what happens to each one, redirect every old address that changes to its closest new page, and check everything again on launch day and for the weeks after. This checklist takes an established business through those steps in order, from the first inventory to 90 days after launch.

Nobody can promise that rankings won’t move. Google itself says visibility may fluctuate for a while during a move. What a careful redesign does is remove the avoidable causes of lost traffic and lost enquiries, which are usually missing redirects, deleted pages that used to rank, and a site left hidden from search after launch.

Key takeaways

  • Record your starting point first. Search Console keeps 16 months of data, so export it before anything changes.
  • List every address on the old site, including PDFs, and decide for each one: keep, improve, merge or remove.
  • Keep page addresses where you can. Where one changes, use a permanent server-side (301) redirect to the closest new page, and keep it for at least a year.
  • Don’t change your domain and your design at the same time. Google advises one change at a time.
  • Test forms, redirects, tracking and accessibility before launch, then watch Search Console and your enquiries for the next few weeks.

Before you start: refresh, redesign or rebuild?

Be clear about what kind of change this is, because it decides how much of this checklist you need.

  • A refresh keeps the same site and addresses: new photos, better words, fixes to speed or layout. Most of the risk below doesn’t apply.
  • A redesign gives the site a new look and structure, usually on the same domain. Some addresses change, so redirects matter.
  • A rebuild or move puts the site on a new system or a new host, and often changes most addresses. Every step below applies.

If you’re still deciding whether you need a redesign at all, our guide to when to redesign your website, and what it costs covers the signs. Then write down two or three goals for the new site, agree who in your business owns the project, and agree a content freeze: a date after which nobody edits the old site, so nothing is lost in the move.

Step 1: record how the current site performs

You can’t tell whether the new site is doing better, or spot a problem early, without a record of where you started. Do this before any work begins.

  • Export Search Console data. Google says “Search Console keeps data for the last 16 months.” Export the Performance report by page and by search query for the longest period available, and save it. Older data drops off, and you can’t get it back later.
  • Note your most linked pages. Search Console’s Links report shows which of your pages other websites link to. Those pages need redirects above all.
  • Export your analytics. Visits by landing page, and the actions that matter: form sends, calls, quote requests, downloads. If your site still only has an old Universal Analytics tag, it hasn’t recorded anything for a while: Google says standard Universal Analytics properties stopped processing data on 1 July 2023. Set up current analytics on the old site now, so you have a few weeks of figures to compare against.
  • Count your enquiries. From your inbox or CRM, count enquiries per month and where they came from, for the last twelve months. This is the number your business will judge the redesign by.
  • Test speed on your top pages. Note the scores and the main problems, so you can check the new site fixes them. Our guide to checking website speed with PageSpeed Insights shows how.
  • Keep a full copy of the old site. A complete backup of files and database, screenshots of the key pages, and access to the old hosting until well after launch.

Step 2: list every page and decide its future

An inventory is a spreadsheet with a row for every address on the old site. Build it from several sources, because each one misses something: the site’s XML sitemap, a crawl of the site, the pages report in Search Console and the landing pages report in your analytics. Include PDFs, downloadable brochures and old campaign pages. These often have links pointing at them that nobody remembers.

For each row, note the page’s visits, its enquiries, whether other sites link to it and what it’s for. Then decide what happens to it.

Decision When to use it What happens to the address
Keep The page works and earns visits or enquiries Same address on the new site
Improve The topic is right but the page is thin, dated or unclear Same address, better content
Merge Two or more pages cover the same thing Redirect each old address to the combined page
Remove Out of date, no visits, no links and no close replacement Let it return “not found”, or redirect it if a genuinely relevant page exists

Be careful with “remove”. A page can look unimportant in a design review and still bring in steady enquiries from Google. Check its figures before you delete it. And keep what the pages that rank are about: you can improve the wording, but cutting a well-performing page to a short paragraph so it fits a new layout is a common way for a redesign to lose traffic.

Google also says it “uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking”, and asks that the mobile site contain the same content as the desktop site. If the new design leaves content out of the phone version, Google may not use that content for indexing and ranking.

Step 3: plan addresses and redirects

Keep addresses where you can

If your services page lives at yourbusiness.co.uk/services/, keep it there. A redesign that keeps every address the same is the simplest move of all. Change an address only when there’s a real reason.

Map every old address that changes

Add a column to your inventory for the new address. Send each old page to the closest matching new page, one to one. Google recommends “server side permanent redirects from the old URLs to the new URLs as you indicated in your mapping”, and warns: “Don’t redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site.” It says this can confuse users and “might be treated as a soft 404 error”, meaning Google treats the redirect as a missing page.

Use permanent redirects

Google says “The 301 and 308 status codes mean that a page has permanently moved to a new location.” A temporary redirect (302 or 307) tells Google the move isn’t permanent, so it isn’t the right tool for a redesign. Ask your developer to set up redirects on the server, not with page scripts.

  • Point every redirect straight to its final address. If the old site already has redirects, update them so a visitor doesn’t bounce through a chain of addresses.
  • Cover the variations: with and without www, http and https, and with and without a trailing slash, as your old site used them.
  • Keep them. Google’s advice is to “keep the redirects for as long as possible, generally at least 1 year”.

Change one thing at a time

Google advises: “Plan your changes to your site one after the other, not everything at the same time.” Its example is to move to a new domain first, then change the layout. If you must change your domain name, do it as a separate step, and use the Change of Address tool in Search Console: Google says that if you’re changing domain names or subdomains, you should submit a Change of Address in Search Console for the old site.

Step 4: build it right

  • Page titles and descriptions. Write a clear, distinct title and description for every page. Carry over the ones that already work. Our guide to getting your website on Google with Search Console also covers checking how your pages appear.
  • One main heading per page, and headings in order, so both people and search engines can follow the structure.
  • Internal links. Update links inside the site to the new addresses. Google says to “change the internal links on the new site from the old URLs to the new URLs.” Make sure every page you keep is linked from somewhere.
  • Structured data. If the old site has structured data, such as business details or breadcrumbs, carry it across.
  • Forms. List every form on the old site, where each one sends enquiries, and who receives them. Rebuild each one on the new site, with the same or better routing.
  • Analytics and cookies. Set up analytics on the new site and record the same actions you measured in step 1. If any tool sets cookies, check the current guidance on consent from the ICO (the UK’s data protection regulator; since 30 September 2026 its legal name is the Information Commission) before launch, and see our guide to privacy policies and cookie banners.
  • Legal pages and details. Company details, privacy notice, cookie information and terms, as they apply to you. Our guide to what your business website must show by law lists the basics.

Accessibility

A redesign is the cheapest time to get accessibility right, because fixing it later means reworking finished pages. GOV.UK says “All UK service providers have a legal obligation to make reasonable adjustments under the Equality Act 2010 or the Disability Discrimination Act 1995 (in Northern Ireland).” WCAG 2.2 level AA is the widely used standard for what an accessible website looks like in practice.

Make it part of the brief and the testing, not an afterthought. Simple checks catch a lot: can you use every page with a keyboard alone, with a visible focus? Does every image that carries meaning have alt text? Is the text contrast high enough? The W3C’s Easy Checks give the minimum as a contrast ratio of at least 4.5:1 for normal-size text, and describe those checks as “quick and easy, rather than definitive”, so they’re a start, not a full audit. Our accessibility guide has more checks you can do yourself.

Step 5: test before launch

Build the new site on a private preview address, and keep it out of search while you work on it, with a password or a “noindex” setting. Then test it as if you were a customer and as if you were Google.

  • Crawl the preview site for broken links, missing or duplicate titles, and any links still pointing at the old addresses.
  • Test every form end to end. Send a real enquiry through each one and check it arrives with the right person, with every field intact.
  • Check tracking. Make sure analytics records visits and the actions that matter.
  • Test on real phones, including an iPhone, and on a laptop. Check that nothing scrolls sideways on a small screen.
  • Run the accessibility checks from step 4 on your main page types.
  • Prepare the redirects so they can go live the moment the new site does, and test a sample if your developer can.
  • Plan the switch. Agree a launch time when people are around to check things, with a way back to the old site if something serious goes wrong. Avoid launching just before a weekend or a holiday.

Step 6: launch day

  • Remove every block on search. Take off the preview password, the “noindex” setting and any “Disallow” rule in robots.txt that kept the preview hidden. A new site that’s still telling Google to stay away is one of the most damaging launch-day mistakes.
  • Check the redirects live. Open your 20 to 50 most important old addresses and make sure each one lands on the right new page, with a permanent redirect.
  • Submit the new sitemap. Google says: “Submit the new sitemap in Search Console. This will help Google learn about the new URLs.”
  • Check the security certificate. Every page should load over https with no warnings.
  • Send a test enquiry through every form on the live site, and check analytics is recording.
  • Note the launch date in your analytics and wherever you keep your figures, so you can compare before and after.

Step 7: the first 90 days

Expect some movement. Google says “the visibility of your content in Search may fluctuate temporarily during the move”, and that “a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer.” A short wobble is normal. A steady fall usually points to something you can fix.

  • First week: check Search Console’s page indexing report and look for “not found” errors on old addresses. Each one is a redirect that’s missing or wrong. Fix them as they appear.
  • Weeks two to six: compare clicks and impressions for your top pages against the export from step 1. If a page that used to rank has dropped, check its redirect, its content and its title first.
  • Every week: count enquiries and compare them with the same weeks last year. This is the measure that matters most to the business.
  • At 90 days: review the goals you set at the start, and plan the next round of improvements to the pages that matter most.

Keep the backup of the old site, and keep the redirects in place for at least a year.

Mistakes that cost traffic and leads

Mistake How to avoid it
Old addresses left without redirects Map every old address in the inventory, then test them on launch day
Everything redirected to the home page Redirect one to one, to the closest matching page
The preview’s “noindex” left on after launch Make removing it the first launch-day check
Deleting or cutting pages that ranked Check each page’s visits and enquiries before you remove it
Changing domain and design at once Do them as separate steps
Forms sending enquiries to nobody Test every form end to end, before and after launch
No figures from before the redesign Export Search Console and analytics data before work starts
Losing access to the old site Keep a full backup and the old hosting until well after launch

The full checklist

Copy this into a document or spreadsheet and tick it off as you go.

Before you start

  • Decide whether this is a refresh, a redesign or a rebuild
  • Write down two or three goals for the new site
  • Name the person who owns the project and makes decisions
  • Agree a content freeze date for the old site
  • Confirm the domain and hosting are in your business’s name

Record your starting point

  • Export Search Console performance data by page and by query
  • Note the pages other websites link to most
  • Export analytics: visits by landing page and key actions
  • Count enquiries per month by source for the last twelve months
  • Test speed on your top pages and note the results
  • Take a full backup and screenshots of key pages

Inventory and redirects

  • List every address, including PDFs and old campaign pages
  • Mark each one keep, improve, merge or remove
  • Keep addresses unchanged wherever you can
  • Map every changed address to its closest new page
  • Use permanent (301 or 308) server-side redirects, with no chains
  • Cover www, https and trailing-slash variations
  • Plan any domain change as a separate step

Build

  • A distinct title and description for every page
  • One main heading per page, headings in order
  • Internal links updated to the new addresses
  • The same main content on phones as on desktop
  • Structured data carried across
  • Every form rebuilt, with enquiries going to the right people
  • Analytics set up, measuring the same actions as before
  • Cookie consent checked against the ICO’s current guidance
  • Legal pages and company details in place
  • Accessibility built in, with WCAG 2.2 AA as the target

Test before launch

  • Preview site hidden from search while you work
  • Crawl for broken links and missing titles
  • Every form tested end to end
  • Tracking tested
  • Checked on real phones, including an iPhone
  • Accessibility checks on each page type
  • Redirects ready to go live
  • Launch time agreed, with a way back

Launch day

  • Preview password, noindex and robots.txt blocks removed
  • Top 20 to 50 old addresses tested
  • New sitemap submitted in Search Console
  • Change of Address submitted, if the domain changed
  • https working on every page
  • A test enquiry sent through every form
  • Launch date noted in analytics

After launch

  • Week one: fix “not found” errors in Search Console
  • Weeks two to six: compare top pages with your starting figures
  • Weekly: compare enquiries with last year
  • Day 90: review against your goals
  • Keep redirects for at least a year

Common questions

Will a website redesign hurt my Google rankings?
It can, if old pages vanish without redirects, if pages that ranked lose their content, or if the new site is left hidden from search. Redirect every changed address, keep what your best pages are about, and expect some temporary movement while Google catches up. Nobody can guarantee rankings either way.

How long does it take for Google to settle after a redesign?
Google says a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer. Keep watching Search Console for at least that long.

Do I need to redirect every old page?
Every old address that has visits, links from other sites or a clear replacement should redirect to its closest new page. A page that’s genuinely gone, with no visits, links or replacement, can return “not found”. Don’t send everything to the home page.

How long should redirects stay in place?
Google’s advice is “for as long as possible, generally at least 1 year”.

Should I change my domain name at the same time?
Only if you have to, and preferably not at the same time. Google advises making changes one after the other, for example moving to a new domain first and changing the layout later.

What does a redesign cost?
Usually about the same as a new site, because most of the work is the same, plus the time to move content and set up redirects. Our guide to what a business website costs in the UK has published ranges, and our guide on how to brief a web design agency helps you get quotes that include the move.

Free help

If you’d like help with a redesign

We’re Hintling Studio, an independent web design studio registered in London. Moving an existing site can be added to any of our packages: content migration for up to 20 pages, including redirects from the old page addresses to the new ones, so old links lead to the right page. Your written quote gives its price, and every other price, before we start. Packages start from £799 for Launch, £1,499 for Business and £2,499 for Shop, with no VAT to add. Hosting and your domain are extra.

See what’s in each package, or tell us about your current site.

Hintling Studio is not connected with Google, the ICO (Information Commission), GOV.UK or the W3C.

Is your website working for you?

A one-page checklist to score your website in about ten minutes. No sign-up and no email needed: just download it.

Preview of the one-page Is your website working for you? checklist

Let’s build yours.

Send us a short brief and we’ll reply with a fixed quote and a timeline. No calls needed unless you want one.