Skip to main content

Web Builder Studio

Labs / Web

Website redesign checklist

This is a website redesign checklist for a small business owner who is about to rebuild their site and would rather not lose the traffic they already have. Work through it in order: what to record before anyone touches anything, what to protect while the build is happening, what to do on launch day, and what to check in the weeks afterwards.

Most of the redesigns we get called in to rescue were not badly designed. They were badly handed over. The new site looked better than the old one and brought in less work, because something invisible got dropped on the way: a page that was quietly ranking, a set of addresses that changed without redirects, a setting left switched on from the staging site that told search engines to stay away.

None of that is difficult to prevent. It is just easy to forget at the exact moment everyone is busy admiring the new homepage. So print this, or send it to whoever is doing your redesign. It is written to be handed over.

First

Before you start

Four things to settle before a single page gets designed. Skipping them is what turns a tidy project into an expensive one.

01

Know why you are redesigning

"It looks dated" is a reason, but it is not a brief. Write down the one thing the new site has to do better: more enquiries, fewer phone calls asking the same question, easier to update yourself. If nobody can name it, the site will be judged on taste alone, and taste arguments never finish. It is worth being clear about what actually makes a website good before you brief anyone.

02

Record what currently works

Open Google Search Console and your analytics and find out which pages bring in visitors, which search terms bring them, and which pages lead to enquiries. Write the list down somewhere that is not the old website. You cannot protect a page if you do not know it was earning its keep.

03

List your existing URLs

Every address on the current site, exported in full. Your sitemap.xml is the quickest starting point, and a crawler will catch the rest. This list becomes your redirect map later, and it is close to impossible to rebuild once the old site is gone.

04

Agree who owns the domain and hosting

In your name, in an account you can log in to, before work starts. Not your last designer, not an agency that registered it for you years ago. If you cannot get into the registrar, you do not control the site, whatever the invoice says.

Stage one

Before the build starts

  • Export the full list of current URLs and save it off the site.
  • Save the current page titles and meta descriptions for your best performing pages. These are the easiest thing in a redesign to lose and the easiest to keep.
  • Save the copy from those pages too. If a page is working, the words on it are doing part of that work.
  • Note where your site is linked from elsewhere: directories, suppliers, a trade body, an old news mention. Those links point at specific addresses, and only redirects will carry them across.
  • Check where your form submissions currently go. An address that stops working is a silent lost enquiry, and nobody complains about an email they never received.
  • Take a full backup of the existing site, files and database, and keep it somewhere you control.
  • Decide whether the URL structure needs to change at all. If it does not, do not change it. That is the cheapest good decision in the entire project.

Stage two

While the site is being built

  • Keep the staging site out of search with a password, not only with a noindex tag. A password cannot be forgotten on launch day in the way a tag can.
  • Build the redirect map as pages are created, not the night before launch. Every old address should point to the closest matching new one.
  • Do not redirect everything to the homepage. A redirect that ignores what the page was about tends to be treated as a dead end rather than a move, and the value of the old page goes nowhere useful.
  • Carry the page titles across. If a page was found by people searching for a particular service in a particular town, the new title needs to still say so.
  • Keep the pages that were bringing traffic. If you genuinely want to merge two, redirect the old address to the page that replaces it and make sure the replacement covers the same ground.
  • Rebuild the internal links. Links between your own pages are how a search engine works out which of them matter, and a new navigation quietly strands pages that used to be linked from half a dozen places.
  • Bring image filenames and alt text with you rather than starting again.
  • Keep your business name, address and phone number in the same form as your Google Business Profile.
  • Test every form on staging with a real address and confirm something arrives.

Stage three

Launch day

  • Check the search engine visibility setting. In WordPress it is one tick box under Settings, then Reading, and leaving it ticked after launch will remove a site from search results entirely. This single box has cost more rankings than any design decision we have seen.
  • Check robots.txt is not blocking the site, and that the staging password is gone.
  • Put the redirects live and then test them by hand. Take twenty addresses off your old list, including your best pages, and load each one. Each should land on the right page, in one hop, without an error.
  • Load the site logged out and in a private window. Logged in, everything looks fine to you and to nobody else.
  • Check it on a phone before you check it on anything else.
  • Confirm every page loads over https with no mixed content warnings.
  • Submit the new sitemap.xml in Search Console.
  • Confirm analytics and any tracking is firing on the new pages.
  • Keep the old backup. Do not delete the old site the same week.

Afterwards

The first week after launch

The redesign is not finished on launch day. The first week is when you find the things that testing missed, and it is much easier to fix a broken redirect now than after the old pages have dropped out.

  • Watch Search Console for a rise in pages reported as not found. Almost every one of those is a redirect you missed, and the report is effectively a to-do list.
  • Check which pages are being indexed, and whether your important pages are among them.
  • Compare clicks week on week, but do not panic early. Some movement while pages are recrawled is normal. A steady decline that continues for weeks is not, and usually points back at redirects or missing titles.
  • Test the contact forms again, from a different device.
  • Click through the site as a stranger would, starting from the homepage, and try to reach every service you sell.
  • Ask an actual customer to find one specific thing and watch where they hesitate.

If you want to see what a finished build looks like once it has settled, the University Direct project is a reasonable example, and our process sets out how we work through this in practice.

Questions

Common questions

Will a redesign hurt my Google rankings?

It does not have to. Rankings get damaged by specific, avoidable mistakes: changing addresses without redirects, dropping page titles, deleting pages that were bringing visitors, leaving a noindex setting on after launch, and rebuilding the navigation so that pages lose their internal links. Handle those and a redesign is usually neutral at worst.

Do I have to change my URLs?

No, and mostly you should not. Tidier addresses are a weak reason to take on the risk. If the structure has to change, map every old address to its closest new equivalent and put those redirects live at the same moment the new site does.

How long does a redesign take to settle in search?

It varies with how often your site is crawled, which is largely out of your hands. The practical answer is that I would not draw any conclusions in the first fortnight, and I would investigate rather than wait if things are still falling a month later.

What does a redesign cost?

A redesign of an existing site starts at £495, and a bespoke four page build starts at £795. Hosting is £35 a month. There are two of us, in Hayle in Cornwall, and we do not use templates. The services page has the detail, and there is more writing like this in Labs.