The short answer
Most redesigns that disappoint were not badly designed. They were badly prepared. The new site looked better, but the enquiry form stopped delivering, a page that ranked well vanished, or nobody could log in to the domain on launch day.
This checklist is in the order the work should happen. Use it to brief a supplier, or to check the one you already have.
First: do you need a redesign at all?
A full rebuild is the right answer when the structure, platform or brand no longer fits the business. It is the wrong answer when the site is sound and one or two things are blocking enquiries: an unclear headline, a form that asks too much, a slow page.
| Sign | Likely answer |
|---|---|
| The site looks dated and no longer reflects the business | Redesign |
| You cannot edit it, or the platform is unsupported | Redesign |
| The services or audience have changed significantly | Redesign |
| Traffic is healthy but few visitors enquire | Improve first, then decide |
| One or two key pages underperform | Fix those pages |
| Nobody knows whether it works because nothing is tracked | Measure first |
If you are unsure, read why your website is not generating enquiries before committing to a rebuild.
The 15 checks at a glance
| # | Check | Stage | Why it matters |
|---|---|---|---|
| 1 | Agree what the site is for | Before | Design choices need a goal to serve |
| 2 | Audit existing content | Before | Know what to keep, improve or retire |
| 3 | Benchmark current performance | Before | You cannot prove improvement without a baseline |
| 4 | List every existing URL | Before | The basis of the redirect map |
| 5 | Confirm who owns each account | Before | Avoids launch-day lockouts |
| 6 | Agree the page list and structure | During | Stops scope drifting |
| 7 | Write copy before final design | During | Design should fit real words |
| 8 | Build the redirect map | During | Protects rankings and links |
| 9 | Specify forms and where enquiries go | During | The point of the whole site |
| 10 | Set up tracking and consent | During | Measurement from day one |
| 11 | Test on real phones | During | Where most visitors are |
| 12 | Check redirects after launch | After | Catches broken links early |
| 13 | Send a test enquiry through every route | After | A thank-you message is not proof of delivery |
| 14 | Monitor Search Console | After | Shows crawl and indexing problems |
| 15 | Review at 30 days | After | Compare against the baseline |

Before you start
1. Agree what the site is for
Write one sentence: this website exists to produce more of what, from whom? Everything else is judged against it.
2. Audit existing content
Go through every page and mark it keep, improve, merge or retire. Pages that bring in search visitors or enquiries are assets. Do not let them be deleted because they look old.
3. Benchmark current performance
Record monthly visitors, enquiries, top landing pages, the searches you appear for and page speed. Screenshots are fine. This is the baseline you will compare against after launch.
4. List every existing URL
Export the full list from your sitemap, analytics or a crawl. Every address on that list needs a decision: same address, new address with a redirect, or retired.
5. Confirm who owns each account
Domain registrar, DNS, hosting, analytics, Search Console, Google Business Profile, email. Each should be registered to the business, with a login the business controls. Sort this before the project begins, not on launch day.
During the build
6. Agree the page list and structure
A written page list with the purpose of each page keeps the project on budget. Our guide to what a business website should include goes through it page by page.
7. Write copy before final design
Placeholder text hides problems. Real headlines and real service descriptions show whether the layout works.
8. Build the redirect map
A simple two-column sheet: old address, new address. This single document does more to protect your search visibility than anything else. We explain it fully in how to protect SEO during a website redesign.
9. Specify forms and where enquiries go
For every form: which fields, who is notified, where the record is stored and what the customer sees and receives afterwards.
10. Set up tracking and consent
Decide which actions count: form submissions, calls, bookings. Make sure they are measured, and that cookie consent is handled properly.
11. Test on real phones
Not a resized browser window. Open the menu, read a service page, complete the form with your thumbs.
After launch
12. Check redirects
Test a sample of old addresses, especially the pages that brought the most visitors. Each should land on the right new page, not the homepage.
13. Send a test enquiry through every route
Every form, the phone link, the email link, the booking tool. Confirm the message arrived where it should and the customer confirmation was sent.
14. Monitor Search Console
Submit the new sitemap and watch for crawl errors and pages dropping out of the index over the following weeks. Some movement is normal. A cliff is not.
15. Review at 30 days
Compare with the baseline from check 3. Look at enquiries first, then visitors, then rankings. Fix what the data shows.
What to ask your supplier
- Which of these 15 checks are included in your price?
- Who builds the redirect map, and can we see it before launch?
- Who tests the forms, and how will you show us they work?
- Which accounts will be in our name at handover?
- What happens in the 30 days after launch?
More in our full list of questions to ask a web design agency.
Five mistakes that cause most of the trouble
- Starting with how it looks before agreeing what it is for.
- Deleting old pages without checking whether they bring in visitors.
- Leaving content until the end, then rushing it.
- Launching on a Friday afternoon with nobody watching.
- Treating launch as the finish, when the first 30 days are where problems show.
Who should do what
| Task | You | Your supplier |
|---|---|---|
| Goals and priorities | Decide | Challenge and refine |
| Content audit | Know what matters commercially | Check what performs in search |
| Copy and images | Supply or approve | Write, edit or direct |
| Redirect map | Review | Build and test |
| Forms and tracking | Say where enquiries should go | Build, test and prove |
| Accounts | Own them | Set up in your name |
| 30-day review | Attend | Report and fix |
Common questions
How long does a redesign take?
Weeks, not months, for most small and mid-sized sites, provided content and feedback arrive on time. See how long does a website take.
Will we lose rankings?
A short wobble is common. Lasting losses are nearly always caused by missing redirects or removed content, both of which are preventable.
Can we keep our existing content?
Yes, and often you should. Good content can be carried over and improved without starting again.
Can someone check our current site before we decide?
Yes. A free 24-hour audit will tell you whether you need a redesign or a few targeted fixes.
Want this applied to your website?
George or Nicholas will record a personal walkthrough of your site within 24 hours.
Not ready for an audit? See Website redesign.
