Website Redesign Checklist: 15 Questions to Ask Before You Start

A redesign should not begin with “make it modern.” It should begin with a specific problem: customers cannot find services, the mobile site is difficult to use, enquiry quality is poor, the team cannot update essential information, or the business has changed. Once the problem is clear, design choices become easier to judge.

Start with the reason for the redesign

Write down the top three things the existing website fails to do. Use evidence where possible: customer questions, lost enquiries, slow pages, outdated offers, pages that receive impressions but no clicks, or a sales process that needs more detail. This list becomes the project brief. It prevents a redesign from becoming an expensive visual change with the same old usability problems.

Good redesigns make a business easier to understand, easier to contact, and easier to trust. Attractive design supports those goals; it does not replace them.

15 questions to answer before choosing a design

Business and audience

1. Who is the main visitor? A local customer, B2B buyer, student, guest, distributor, or job candidate may need a different path.
2. What action should that visitor take? Call, request a quote, book, purchase, download a catalogue, or visit a location.
3. Which services or products produce the best enquiries? Give those pages priority rather than treating every page equally.
4. What must a customer know before contacting you? Scope, location, availability, process, price-enquiry rules, or documentation can reduce confusion.

Content and credibility

5. Which existing pages are useful and accurate? Preserve and improve them instead of deleting valuable explanations without a replacement.
6. Which claims can the business prove? Use only approved case studies, certifications, testimonials, and team information.
7. Who owns the text, photos, logo, domain, and hosting access? Establish this before work begins.
8. Who will keep the information current? Name the person responsible for hours, pricing notices, service changes, and campaigns.

Mobile experience and technical scope

9. Can a visitor complete the main task on a phone? Test the call button, menu, forms, reading size, map, and payment or booking route.
10. Will the design avoid horizontal scrolling and tiny tap targets? These are signs that a desktop layout has been squeezed into a mobile screen.
11. Which features are essential? A gallery, booking tool, catalogue, CRM form, multilingual content, or review link may be valuable; a heavy effect may not be.
12. How will enquiry data be handled? Explain where form data goes, who receives it, and which privacy notice applies.

Search, launch, and ownership

13. Which URLs already receive visits or links? Map them before changing page addresses.
14. What will redirect if a URL changes? A relevant permanent redirect helps users and search engines reach the new equivalent page.
15. How will success be measured after launch? Choose useful measures: qualified enquiries, calls, bookings, catalogue requests, or a reduction in support questions.

Protect the value of your existing pages

A redesign can damage organic visibility when useful content disappears or important URLs change without a plan. Before development, export the key pages from analytics or Search Console, list pages with backlinks or enquiries, and identify the closest new destination for every page being retired. Do not redirect everything to the homepage: a visitor who searched for a specific service should land on the most relevant replacement.

Keep page titles, headings, internal links, canonical URLs, and structured data under review during the build. The goal is not to freeze every old phrase forever. It is to retain useful subject coverage while making the page clearer. If a service has changed, update it honestly and explain the new offer rather than keeping obsolete copy simply because it once received traffic.

Launch and post-launch checks

Review the staging site on a real phone and desktop before launch. Check every navigation link, form, email destination, telephone link, image alternative text, legal page, and primary call to action. Confirm that the important content is visible without a login or interaction. A responsive design uses the same URL and core content across devices, which is the approach Google recommends because it is simpler to maintain.

During the first month after launch, review 404 errors, form delivery, speed, search impressions, branded searches, and feedback from people who use the site daily. The most useful improvements often appear after real customers try the new path. Plan a small post-launch improvement window rather than treating the publish date as the end of the project.