Labs / Web
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
Four things to settle before a single page gets designed. Skipping them is what turns a tidy project into an expensive one.
"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.
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.
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.
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
Stage two
Stage three
Afterwards
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.
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
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.
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.
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.
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.