Most redesigns fail on search for one reason: nobody wrote down what the old site was doing for the business. The new design looks better, launches on a Friday, and by the following month enquiries are down. The pages that brought in visitors were renamed, merged or deleted, and Google had no way to follow them.
This checklist is for the person who owns the site, whether you are doing the work or briefing someone else. It is in order: before you design, while you build, at launch and after.
Before you design anything
Start by recording what the current site does. Without a record you cannot tell later what you lost.
List every page on the current site. A free crawling tool or your sitemap will give you the full list of addresses. Put them in a spreadsheet.
Find the pages that bring visitors. In Google Search Console, open the performance report and export the pages that get clicks. Do the same in your analytics tool. These are the pages you must not damage.
Find the pages other sites link to. Links from other websites are hard to earn again. Mark any page with outside links as protected, even if it looks dated.
Note the words that already work. For each protected page, copy its title, its main heading and the first paragraph. If a page ranks, part of the reason is the way it is written. Rewrite carefully, not from scratch.
Take a baseline. Write down your monthly visits, clicks from Google and enquiries for the last three months. You will compare against this after launch.
Decide what happens to every page
Go down the spreadsheet and give each address one of four outcomes:
Keep. The page stays, at the same address, with its content improved.
Merge. Two weak pages on the same topic become one stronger page. The old addresses redirect to the new one.
Move. The page stays but gets a new address. The old address redirects to the new one.
Remove. The page has no value. Redirect it to the closest related page, and let it return a "gone" message only if nothing is related.
Keeping addresses the same wherever you can is the cheapest protection you have. Every address you change is a chance for something to go wrong.
Build it on a private copy
Your developer should build the new site on a private test address, not on your live domain.
Keep the test copy out of Google. Search engines should not index it, and you do not want two versions of your site competing. A password is the safest way to do this.
Then remember to switch it off. The most common launch mistake is leaving the "do not index" setting on after the site goes live. Put it on the launch checklist as its own line.
Carry over the basics. Each important page needs a page title, a meta description, one main heading, sensible subheadings, descriptions on images and working internal links. A new design often loses these without anyone noticing.
Check the technical files. The sitemap should list the new addresses. The robots file should not block the pages you want found.
Test on phones. Google mostly judges your site by its mobile version, so test there first.
Test speed. A prettier site that loads slowly can lose ground. Run the new pages through Google's free PageSpeed Insights tool before launch.
Plan the redirects
A redirect tells browsers and search engines that a page has moved. Without one, anyone following an old link or search result lands on an error page, and the page's history with Google is lost.
Use permanent redirects, called 301 redirects, for pages that have moved for good.
Redirect each old address to the single most relevant new page. Sending everything to the homepage is a lazy shortcut that search engines tend to treat as an error, and visitors hate it.
Test every redirect on the list before launch, not after. One agency guide on redesign costs makes the point that missing redirects can throw away the strength a page has built up, and that fixing the damage later costs more than doing the mapping up front (LOW/CODE Agency). That source sells redesigns, so weigh it accordingly, but the advice is standard.
Launch day checks
Confirm the "do not index" setting is off.
Open ten of your most important old addresses and check that each lands on the right new page.
Check that the sitemap loads and lists the new addresses.
Submit the new sitemap in Google Search Console.
Make sure your analytics and any tracking are installed on the new site.
Test the contact form, the phone number and the WhatsApp link yourself.
Look for obvious broken pages on mobile.
If your web address itself is changing, for example from one domain to another, there is an extra step in Search Console to tell Google about the move. Ask your developer to handle it.
After launch
Search results take time to settle, so do not panic over a few days of movement. Do check on a schedule.
Week one: open the Search Console page report and the errors list. Fix any addresses showing "not found".
Weeks two to six: compare clicks and visits with your baseline once a week. A small dip while Google re-reads the site is normal. A steep drop on specific pages means something broke on those pages.
Keep the old redirects. Leave them in place for at least a year. Removing them early undoes the work.
Common mistakes
Deleting old blog posts because they look dated.
Changing every address because the new design "needs a cleaner structure".
Launching without testing the redirects.
Forgetting that the contact form and tracking need to be rebuilt too.
Judging success on how the site looks, not on enquiries.
Common questions
Will a redesign hurt my Google ranking?
It can, and it does not have to. Most losses come from avoidable mistakes: changed addresses with no redirects, lost page titles, a site left set to "do not index", or a slower build. A careful migration usually settles within weeks.
Should I change my domain name during a redesign?
Only if you have a strong reason. A new domain starts without the history of the old one, even with redirects. If you do have to move, make it a separate, planned step.
How long should I keep redirects?
At least a year. If an old address still has outside links pointing to it, keep its redirect for as long as the links exist.
Can I redesign in stages instead of all at once?
Yes. Changing a few pages at a time carries less risk and makes it easier to see what caused any drop. It takes longer, and it can leave the site looking uneven in the meantime.
Work with Crelivio
If you want help with this, start with a free one hour consultation. We will talk through your situation and tell you what makes sense. Book a free consultation, ask for a quote, or read about our web development service.
