The short answer
A website redesign works when it is run in a fixed order: decide what must change, measure where you are, audit what exists, map every URL, brief whoever builds it, agree the structure, write content alongside design, test like a customer, launch carefully and watch the numbers for 90 days. Skipping the early steps is what makes redesigns fail.
Most redesigns that disappoint were not badly designed. They were started in the middle. Someone commissioned new visuals before deciding what the old site was failing to do, so the new site looked better and performed the same, or worse, because nobody recorded what was working before it was replaced.
The checklist below is the order we would run a redesign in for any business site, whether a studio, a freelancer or your own team does the work. Every step exists to prevent a specific and common failure.
Step 1: Decide what the redesign has to fix
Write down, in one sentence each, the two or three problems the redesign must solve and how you will know they are solved. "Enquiries fell this year while traffic held steady" is a problem. "It looks dated" is a symptom. If you cannot name a real problem, you may need a refresh rather than a full redesign.
Reasons that justify a redesign tend to look like this:
- The site is losing you work. Enquiries or sales are falling while visits hold, or visitors cannot find the service they came for.
- Your team cannot update it. Every small change needs a developer, so the site drifts out of date.
- It fails on phones. Most visits are mobile, and the mobile experience was an afterthought.
- The platform has become a risk. Unsupported themes, abandoned plugins or hosting nobody can access.
- The business has changed. New services, a new market, a merger or a rebrand the old structure cannot express.
Reasons that usually do not: a competitor relaunched, someone senior is bored of the colours, or a design trend arrived. We set out the refresh-versus-rebuild decision and its costs in when a redesign is worth it.
Step 2: Record a baseline before anything changes
Before any design work starts, export the numbers the new site will be judged against: monthly enquiries or sales, conversion rate on key pages, organic traffic by page, top search queries and their average positions, and page speed. Without a baseline, nobody can say afterwards whether the redesign helped or quietly hurt.
Most of this takes an hour. Search Console's Performance report gives queries and pages for the last sixteen months; export it. Your analytics tool gives landing pages and conversions. PageSpeed Insights gives speed for your top templates. Your inbox or CRM gives the real number of enquiries, which matters more than any of the others. Save it all somewhere a tracking change during the project cannot overwrite. If you are unsure what to measure, what to measure instead of traffic covers the short list.
Step 3: Audit the current site and inventory the content
An audit tells you what to keep. List every page with its traffic, the searches it ranks for, the enquiries it produces and whether its content is still accurate. Pages that earn traffic or leads keep their substance and usually their address. Pages nobody visits are candidates to merge, rewrite or remove.
The working document is a spreadsheet with one row per URL and columns for title, purpose, monthly visits, conversions, inbound links, a decision (keep, rewrite, merge or remove) and the person responsible. It is unglamorous and it is the single most useful artefact in a redesign. For a scored, area-by-area version, use our website audit checklist.
Step 4: Export every URL and plan the redirects
Every URL on the old site needs a destination on the new one, decided before launch. Pages that keep their address need nothing. Pages that move need a permanent 301 redirect to their closest equivalent. Pages that are genuinely gone should point to a relevant parent page, not to the homepage by default.
Build the URL list from several sources, because each one misses something: a crawl of the live site, the XML sitemap, the pages report in Search Console, the landing pages in your analytics and any pages other sites link to. Include PDFs and image files that rank or get shared. Lost redirects are the main reason traffic collapses after a relaunch, which we explain in redesigning without losing rankings.
Step 5: Write the brief and choose who will build it
A brief of two to four pages gets you comparable quotes and a better project. It should state the goals from step one, the audiences, the page list, required features and integrations, the content you will supply, the budget range and the deadline. Compare studios, freelancers and in-house options against that brief, not against portfolios alone.
Our website brief template walks through each section. Organisations whose rules require a formal tender can use the website redesign RFP template instead. Whoever you choose, read the agreement for ownership of the domain, code and design files before signing; the clauses that matter are in our web design contract checklist, and the trade-offs between builders are in freelancer vs agency vs in-house.
Step 6: Agree the structure before the visuals
Sign off the sitemap and the content of each key page, in rough wireframe form, before anyone designs colours and type. Structure decides whether visitors find what they need; visuals decide whether they trust what they find. Changing the structure after visual design has started is the most expensive kind of revision in a redesign.
Three decisions belong here. The page list, which our guide to what pages a business website should have can help settle. The main path from arrival to enquiry or purchase, drawn as a short sequence of pages. And the number of unique page templates, because templates, not pages, drive most of the design and build effort.
Step 7: Write content alongside design, not after it
Late copy is the most common cause of a delayed launch. Decide who writes each page at kickoff, draft the important pages while wireframes are being agreed, and design with real words rather than placeholder text. Layouts built around lorem ipsum break the moment real headlines, real prices and real product names arrive.
The homepage and the main service pages deserve the most effort, and the homepage's first screen deserves more than the rest of the site combined; what your homepage should say first covers why. If you have not decided who is writing, who writes the website content sets out the options.
Step 8: Build, then test like a customer
Before launch, someone who did not build the site should try to do what customers do: find a service, understand the price, submit every form, buy something, and read it all on a mid-range phone over mobile data. Developers test that features work. Customers reveal whether the site makes sense. A redesign needs both kinds of testing.
The technical side of testing has a known list: forms deliver to the right inbox, analytics and conversion events fire, pages meet Google's Core Web Vitals thresholds, the site works with a keyboard and has readable contrast, and your team can edit pages in the content management system without help. The complete version is our website launch checklist.
Step 9: Launch week
Launch when the people who built the site are available for the two days that follow, never on a Friday afternoon or before a holiday. On the day, deploy, switch on the redirect map, remove any noindex tag or password left over from staging, submit the new XML sitemap and confirm forms and tracking work on the live domain.
A few preparations make launch day calmer. Lower the DNS time-to-live a day or two in advance if the domain is moving to new hosting, so the switch propagates quickly. Take a full backup of the old site and keep a private copy available for reference. Then tell customers and update every place your website address appears, from your Google Business Profile to your email signature.
Step 10: The 90 days after launch
A redesign is not finished at launch. Check Search Console weekly for the first month for crawl errors and indexing changes, confirm redirects are being used, fix what real visitors stumble on, and compare your baseline measures at 30, 60 and 90 days. Small ranking movements in the first weeks are normal; sustained drops need investigating.
When something does drop, the usual causes are a missed redirect, a page whose content was cut back, a title tag that lost its keyword, or a template that is slower than the one it replaced. Each is fixable once found, which is why the first month of watching matters more than the launch itself.
A realistic redesign project plan
For a typical five-to-eight page business site, plan two to four weeks of preparation before kickoff, six to ten weeks of design and build, and a 90-day watch after launch. A corporate site of ten to twenty pages usually takes ten to fourteen weeks to build. Decisions and content, not development, decide whether those dates hold.
| Phase | What happens | Typical duration, 5 to 8 page site |
|---|---|---|
| Preparation | Goals, baseline, audit, URL export, brief, choosing a builder | 2 to 4 weeks before kickoff |
| Structure | Sitemap, wireframes, content plan, writers assigned | 1 to 2 weeks |
| Visual design | Key templates first, then the remaining pages | 2 to 3 weeks |
| Build and content | Development, content entry, redirects, tracking | 2 to 4 weeks |
| Testing | Customer tasks, devices, forms, speed, accessibility | About 1 week |
| Launch and aftercare | Go-live, monitoring, fixes | Launch week plus 2 weeks |
| Measurement | Compare against the baseline | 30, 60 and 90 days after launch |
The full breakdown by type of site, and the decisions that cause most delays, is in how long it takes to build a website.
The whole checklist on one page
Use this list as the running checklist for the project. Each line is a decision or a check, in the order it should happen, and each one prevents a specific failure: a result nobody can measure, lost rankings, a late launch, a site your team cannot update, or a launch-day surprise with nobody around to fix it.
- Two or three written problems the redesign must solve, each with a measure
- One named decision-maker and one named content owner
- Baseline exported: enquiries, conversion rates, traffic by page, queries, speed
- Content inventory with a keep, rewrite, merge or remove decision per page
- Complete URL list and a redirect map signed off
- Brief written, builders compared, contract checked for ownership
- Sitemap and wireframes approved before visual design
- Writers assigned and copy deadlines set at kickoff
- Designs reviewed with real content, on a phone first
- Forms, emails, analytics and conversion events tested on the live domain
- Speed, accessibility and editing by your own team checked
- Launch day chosen with the builders available afterwards
- Noindex and staging passwords removed, sitemap submitted, redirects live
- Website address updated everywhere it appears
- Search Console checked weekly for the first month
- Results compared with the baseline at 30, 60 and 90 days
Where we fit
studiokalex designs and redesigns business websites. If you are not sure whether your site needs a redesign, a refresh or a short list of fixes, tell us what is going wrong and we will say which, including when the honest answer is that you do not need us.
You can see how we work on our web design page, or get in touch with the problem you want the new site to solve.