The safest way to redesign a website without losing traffic is to record what your current site ranks for, keep or redirect every URL that gets visits or links, carry over the content that works, and test everything on a staging copy before launch. Most traffic drops after a redesign come from missing redirects, deleted content and settings left over from development, not from the new design itself. This website redesign checklist walks through each step, from audit to the weeks after launch.
Key takeaways
- Start with an audit: export your current pages, their traffic, their rankings and the sites that link to them.
- Map every old URL to a new one, and set up permanent (301) redirects for anything that changes.
- Keep the content that brings in visitors and leads; improve it rather than deleting it.
- Test on a staging site, then check that search engines are allowed to index the live site on launch day.
- Watch Search Console and analytics closely for the first four to eight weeks after launch.
Decide whether you need a redesign
A redesign is a big project. Before you commit, be clear about why you need one. Good reasons include a site that is hard to update, slow or broken on phones, built on software that is no longer supported, or no longer accurate about what your business offers.
A weaker reason is "it looks dated" on its own. Sometimes a refresh of fonts, colors, photos and the homepage gets most of the benefit for a fraction of the effort. Run your site through our small business website checklist; if most items pass, targeted fixes may be enough.
Set goals you can measure
Write down what the new site should improve: more quote requests, more bookings, more sales, fewer support calls. Note your current numbers so you can compare after launch. A redesign without a baseline is hard to judge.
Step 1: Audit your current site
This is the most important part of the website redesign checklist, and the step most often skipped.
Export every URL
Get a full list of the pages on your current site. Your sitemap, your CMS and a crawling tool are all good sources. Include blog posts, PDFs, landing pages from old ad campaigns and any pages not in your main menu.
Record traffic and rankings
From your analytics, note which pages get the most visits and which ones lead to contact forms, calls or sales. From Google Search Console, export the queries and pages that bring in search clicks. These are the pages you must protect.
Note your backlinks
Pages that other websites link to carry search value. Search Console shows your top linked pages. If those URLs disappear without a redirect, that value is lost.
Save a copy
Keep a full backup of the old site and a few screenshots of key pages. You will want to refer back to them during the project and possibly after launch.
Step 2: Plan content and structure
Sort pages into keep, improve, merge and remove
| Decision | When to use it | What happens to the URL |
|---|---|---|
| Keep | Page performs well and is accurate | Same URL if possible |
| Improve | Page gets visits but content is thin or outdated | Same URL, updated content |
| Merge | Several pages cover nearly the same topic | Redirect the extras to the main page |
| Remove | No traffic, no links, no business value | Redirect to the closest relevant page, or let it return a 404 if nothing fits |
Be careful with "remove." A page that looks unimportant may be the one that brings in a steady trickle of local searches.
Keep URLs the same where you can
The simplest way to avoid redirect problems is to not change URLs. If your old structure is reasonable, keep it. Change URLs only when there is a clear benefit, such as replacing cryptic page IDs with readable paths.
Plan new pages with search in mind
If you are adding services or locations, give each one its own page with a clear purpose. Our guide to SEO for small business covers how to choose what each page should target.
Step 3: Build the redirect map
A redirect map is a two-column spreadsheet: old URL on the left, new URL on the right. Every old URL from your audit should appear on it.
- Use permanent (301) redirects, not temporary ones.
- Redirect each old page to the most relevant new page, not everything to the homepage.
- Avoid chains, where one redirect leads to another. Point old URLs straight to their final destination.
- Include variations: with and without "www," old PDF links, and any URLs used in printed materials or ads.
- Update internal links on the new site so they point directly to new URLs rather than relying on redirects.
Step 4: Build and test on staging
Build the new site on a private staging address so you can test without affecting the live site. Make sure the staging site is blocked from search engines, and write down how it was blocked so you can undo it at launch.
Pre-launch testing checklist
- Every page from the content plan exists and has final text.
- Each page has a unique title, meta description and one main heading.
- Images are compressed and have descriptive alt text.
- The site works on phones, tablets and laptops, in more than one browser.
- Every form submits, sends to the right inbox and shows a confirmation.
- Phone numbers and email addresses are tappable.
- Analytics and conversion tracking are installed and recording test events.
- Cookie consent works where it is required.
- Structured data, such as your business details, is in place where relevant.
- Pages load quickly on a phone over mobile data.
- Basic accessibility checks pass: contrast, keyboard navigation and form labels.
- Your privacy policy and terms are updated for any new tools or data collection.
Step 5: Launch day checklist
Launch early in the week and early in the day, when someone is available to fix problems. Avoid your busiest season.
- Take a final backup of the old site.
- Deploy the new site and point your domain to it.
- Remove the staging block so search engines can index the live site. This single setting causes more post-launch traffic losses than almost anything else.
- Check that HTTPS works on every page, with no security warnings.
- Turn on your redirects and test a sample of old URLs, including your top traffic pages.
- Submit the new XML sitemap in Google Search Console.
- Submit a test enquiry through every form.
- Confirm analytics is recording real visits.
- Update your Google Business Profile, social profiles and email signatures if any links changed.
Step 6: Monitor the first weeks after launch
Some movement in rankings after a redesign is normal while Google processes the changes. What you want to catch quickly are real problems.
Week one
Check Search Console for crawl errors and pages that return "not found." Add redirects for any old URLs you missed. Watch form submissions and calls; a sudden drop to zero usually means something is broken, not that demand disappeared.
Weeks two to eight
Compare traffic and conversions against the baseline from your audit. Look at the pages that performed best before the redesign. If one has dropped sharply, check that it was redirected correctly and that its content was not cut too much. Keep the old site backup until you are confident nothing needs to be restored.
Common causes of traffic loss
| Symptom | Likely cause |
|---|---|
| Whole site disappears from search | Staging block left in place |
| Specific pages lose rankings | Missing or wrong redirects, or content cut too far |
| Many "not found" errors | Old URLs missing from the redirect map |
| Traffic steady but leads drop | Broken forms, missing tracking or weaker calls to action |
How Webvinora can help
Redesigns are a large part of our web design service, and our Custom package includes content migration from your old site. Redirect mapping, staging tests and launch-day checks are part of every relaunch we run, and you can see how projects are structured on our process page. If you are planning a redesign, tell us about your current site and we will reply within one business day.