A website redesign checklist should help you decide whether a new site is ready for customers. New colours and cleaner layouts are only part of that decision. Your business also needs its useful content, enquiries, search visibility and day-to-day editing to survive the change.
This guide is for UK business owners commissioning a redesign, whether an agency or an internal team is doing the work. Use it at the briefing stage and again before release. The example checks below are suggested working practices, not a promise of rankings, enquiries or a particular project duration.
1. Agree what the redesign needs to improve
Write down the problem in terms a customer would recognise. Perhaps visitors cannot tell which service suits them, your mobile enquiry form is awkward, or the team cannot update opening hours without help. Choose one main problem and a small number of supporting improvements. That gives design reviews something firmer than personal taste.
For each problem, record the existing behaviour and the change you want to see. A hypothetical consultancy might find that people request quotes without knowing its service area. Its redesign brief could ask for that information earlier in the journey and a clearer enquiry form. Whether enquiry quality improves would still need measuring afterwards.
Separate essentials from later improvements. Changing the website, brand, domain, booking system and customer database together creates a much larger project than refreshing the pages. Ask the team to show which changes depend on others and which can be delivered separately. Our web design overview provides a starting point for discussing the visual and functional work.
2. Make an inventory before removing anything
Create a list of the pages and features you already have. Include pages that are missing from the main menu: old landing pages, downloads, news articles and help pages may still be used. Add contact forms, booking tools, member areas and any connection that sends information to another system.
Beside each item, give it an owner and a proposed decision: keep, improve, combine or remove. Someone who understands the service should approve content changes. The developer should not have to guess whether an old product specification or eligibility condition is still important.
- Save a dated copy of important page content and existing page addresses.
- Record recent enquiry totals and the pages customers used, where reliable data is available.
- Note gaps in measurement instead of treating missing data as zero activity.
- List domain, hosting and software account owners without putting passwords in the project sheet.
- Agree who is responsible for backups, restoration testing and access after handover.
Use comparable periods when looking back at results. A busy seasonal month and a quiet launch week are not a fair before-and-after comparison. Also record business changes, such as a new service or reduced opening hours, that could affect the figures independently of the redesign.
3. Approve real content before polishing the layout
Ask to see a service page populated with your actual words, images and customer questions. Placeholder text hides practical problems: a long service name may break a menu, a qualification may need explanation, and a short headline may leave the offer unclear.
Each important page needs a clear purpose and a useful next step. For a service business, that might be checking suitability and requesting a conversation. A visitor should understand who the service is for, what they can ask about and what happens after they make contact. Avoid adding reviews, certifications or results that nobody can substantiate.
Have the person who will maintain the site try routine editing on the test version. Ask them to change a paragraph, replace an image and preview the result on a phone. If those tasks require specialist help, clarify the support arrangement before accepting the build. Include content ownership and training in the written scope; our guide to choosing a web design agency covers the wider supplier decision.
4. Give changed page addresses a checked destination
Changing a page’s appearance does not automatically mean its address needs changing. For addresses that do change, ask for a written map connecting the old page with its relevant replacement.
Google’s site-move guidance explains URL mapping, redirects and monitoring. It advises against sending unrelated old pages to the homepage and recommends keeping redirects for at least a year. The new sitemap and internal links should use the intended new addresses. Temporary search fluctuations can occur; a migration plan cannot guarantee unchanged rankings.
Have the developer check that each mapped old address actually reaches the intended live page. Include important links used in emails, printed materials or saved customer bookmarks. If a page has no relevant replacement, agree how its removal should be handled rather than inventing a misleading destination.

5. Test the customer journey, including the reply
Choose a few realistic tasks and write down the starting point and expected finish. For example: arrive on a service page, check the service area, find a suitable contact option and send a clearly labelled test enquiry. Check the confirmation message and the destination inbox. A message on screen does not tell you whether the team received the enquiry.
Repeat important tasks on a real phone and a desktop browser. Check error messages as well as the successful route: an empty required field, an incorrectly formatted email address and a return to the previous step. Use invented test details, avoid real customer information and arrange test submissions with whoever receives them.
Review integrations with their owners. A booking request might appear on the website but fail to arrive in the team’s calendar. A form might send an email but omit a field the sales team needs. For payment journeys, use the provider’s supported test arrangements and agree any production verification separately.
6. Check accessibility and performance early
Accessibility should be considered while the templates are being built. W3C’s Easy Checks offers a first review covering areas such as page titles, headings, contrast, keyboard focus, zoom and form labels. Try using the main journey without a mouse, and check whether enlarged text remains usable. W3C explicitly notes that these checks are not a comprehensive accessibility assessment. Passing a quick checklist is not proof that every barrier has been removed.
For performance, ask the developer to explain which templates were tested and under what conditions. Google’s Web Vitals guidance focuses on loading, responsiveness and visual stability. Real-user measurements and a controlled test answer different questions; a single favourable test score should not be presented as everyone’s experience.
Prioritise problems that obstruct customer tasks. A menu that cannot be reached by keyboard, an unreadable error message or a large visual shift during form entry deserves a clear owner and fix. Keep the remaining improvement list visible so that acceptance does not silently become abandonment.

7. Turn your website redesign checklist into a sign-off sheet
Before choosing the release moment, agree who can approve it and who can pause it. The table below is an example to adapt with your team. Replace the role names with actual people, attach the test evidence and give every unresolved item a decision.
| Check | Suggested owner | Evidence to keep |
|---|---|---|
| Content describes current services accurately | Business owner | Approved page list and outstanding corrections |
| Changed addresses reach relevant pages | Developer | Tested old-to-new address map |
| Enquiries reach the right recipient | Customer service lead | Labelled test received with required details |
| Search settings are appropriate for launch | SEO lead or developer | Live indexing and sitemap checks |
| Essential tasks work across devices | Tester and business owner | Task results, devices and remaining defects |
| A recovery plan is available | Hosting or development lead | Backup, recovery procedure and named contact |
Decide in advance what would delay release. A spelling correction on a minor page is different from a contact form that loses messages. If the site accepts orders or bookings, recovery planning must also account for records created after launch; replacing a database with an older copy could lose them. Ask the responsible specialist to document a safe approach.
8. Set the first review dates before launch
Arrange an immediate live check and a later review once the site has accumulated useful activity. Confirm who watches for failed enquiries, missing pages and customer complaints, and how urgent problems are reported. Keep the original baseline alongside the new results.
Review enquiry quality as well as totals. If visitors now understand your service better, fewer unsuitable enquiries might be useful; fewer suitable enquiries would require investigation. Avoid declaring success or failure from a tiny sample. Record what changed and what remains uncertain before choosing the next improvement.
If you are preparing a redesign brief, review Alchemist Media’s website service and current scope, then discuss your existing site and priorities. Bring the page inventory, important customer tasks and any fixed deadlines. Ask which migration, testing and aftercare responsibilities are included in the proposed work.
Frequently asked questions
Do I need a complete redesign to fix a few weak pages?
Not always. First identify whether the problem is content, navigation, performance or an underlying system limitation. A focused improvement may be sufficient. Ask for the reason a full rebuild is necessary and what existing work can be retained.
Should every page get a new address?
No. Review addresses separately from visual design. Keeping useful addresses can reduce migration work. Where changes are justified, ask the developer to document the destinations and test them as part of the release.
When is a redesigned website finished?
For project acceptance, use the agreed scope and evidence of completed checks. For ongoing operation, the website still needs maintenance and review. Clarify the difference between fixing a delivery defect, routine support and paying for a new feature.
Sources
Technical references checked on 20 November 2026: Google Search Central’s site-move guidance, W3C’s introductory accessibility checks and Google’s Web Vitals documentation, linked in the relevant sections above. The project worksheet and suggested ownership roles are editorial examples to adapt to your business.
Recent Comments