By Rakibul Hasan, Moonlab
To redesign a website without losing traffic, record what you have now, map every old URL to a new one, set up 301 redirects, keep the content that performs and check analytics and Search Console right after launch. Most traffic losses come from broken URLs and removed pages, not from the new design.
This checklist is for owners and managers who are about to hire a designer or rebuild their own site. It gives a step by step order, with what to ask your developer. A redesign can cause a temporary dip even when done well, and we cannot guarantee how Google will respond, so the aim is to reduce risk.
1. Decide why you are redesigning
Write down the goal: more enquiries, faster mobile pages, a new brand or easier updates. A clear goal helps you decide what to change and what to keep.
If the site already ranks well, change as little of the structure as you can. A redesign is a chance to improve, not to start over.
2. Benchmark the current site
Before anything changes, save your data. You will need it to measure the result.
- Export top pages and queries from Google Search Console.
- Record visits, enquiries and conversions in Google Analytics.
- Crawl the site with a tool to list every URL, title and heading.
- Note rankings for your main search terms.
- Take backups of the old site and database.
- Record page speed scores for key pages.
3. Map every old URL to a new one
Make a spreadsheet with a column for each old URL and a column for its new address. If the address stays the same, great. If it changes, or the page is gone, decide where visitors should land.
Send old pages to the most relevant new page, not the home page. Send removed pages to a close alternative. Keep URL structures as stable as possible, because every change is a risk.
4. Set up 301 redirects
A 301 redirect tells browsers and Google that a page has moved permanently. Implement your URL map as redirects on the server or in your platform. Avoid chains of redirects, where one leads to another.
Test every redirect before launch on a staging copy, and again after launch. Check redirects from the http and www versions as well.
5. Protect your content and on page SEO
Keep titles, headings, text and internal links that bring traffic. If you rewrite, keep the same topics and the same intent. Do not delete pages that get visits or have links from other sites, merge them with care.
Check that images keep alt text, structured data carries over and the canonical tags point to the right place. Make sure the staging site is blocked from search, and that the block is removed at launch.
6. Check analytics, forms and tracking
Install analytics and any ad or conversion tags on the new site before launch. Test forms, phone clicks, booking links and the thank you pages. Check your cookie consent setup, as in moonlab.space/guides/cookie-consent-uk-eu.
Verify the site in Search Console and submit your sitemap after launch.
7. Launch and check straight away
Launch at a quiet time. Right after, crawl the new site, check for errors and test the key journeys on a phone. Watch Search Console for crawl errors and coverage issues over the next weeks.
Expect some fluctuation. If traffic drops sharply, look first for missing redirects, blocked pages or changed titles.
- Check that the robots file allows crawling.
- Check every redirect from your map.
- Check page speed and mobile layout.
- Compare traffic and enquiries with your benchmark weekly for a couple of months.
A worked example and common mistakes
Here is a made-up example. A dental practice in Glasgow has a twelve year old website with about forty pages. Most search visits go to the home page, a page on teeth whitening and a page on emergency appointments. They plan a redesign with a new look and a new platform.
Before starting, they export the top pages from Search Console and crawl the site to list every URL. They discover that the old site uses addresses such as /treatments/whitening.html, while the new platform would use /whitening. In the URL map, each old address is paired with its new one, and the developer sets up a permanent 301 redirect for each. The emergency page keeps its text and heading, because it brings calls, and the whitening page is expanded, not replaced.
On launch day they check the redirects, the sitemap, the tracking on the booking form and that the staging block is off. For the next eight weeks they compare clicks and impressions in Search Console with their benchmark, and fix any 404 errors they find. A small dip in the first weeks is not a cause for panic, but a sharp loss on one page usually points to a missing redirect.
These are the errors that cause the biggest losses.
- Leaving the staging site blocked from search after launch.
- Redirecting every old page to the home page.
- Deleting pages that had links from other sites.
- Changing titles and headings on pages that already rank.
- Forgetting analytics, conversion tracking or cookie consent.
- Launching without a backup of the old site.
- Not watching Search Console for crawl errors afterwards.
How to decide and what to do this week
Before you sign off a redesign, put these questions to the designer or developer. Clear written answers are a good sign.
- Will every old URL with traffic or links redirect to a relevant new page?
- Which pages and text are staying exactly as they are?
- How and when will the staging block be removed?
- Who tests forms, tracking and cookie consent before launch?
- What is the plan if traffic drops after launch?
- Do we have a full backup of the old site and a way to restore it?
How Moonlab can help
We plan redesigns with the redirect map and tracking in place from day one. See moonlab.space/services/web-development, moonlab.space/services/seo and moonlab.space/services/ui-ux-design. For a check of your current site first, see moonlab.space/guides/website-audit-checklist-small-business.
A free 30-minute automation audit at moonlab.space/contact can open the conversation.
