Website Redesign Checklist: What to Fix Before You Rebuild

Many website redesigns begin with a feeling: the site looks old, the layout feels tired, competitors look sharper or the business has changed. Those feelings may be valid, but they are not enough to guide a rebuild. A redesign should start by naming the problems that matter: weak enquiries, confusing service structure, poor mobile experience, slow pages, outdated content, missing proof, poor search visibility, broken forms or a platform the team cannot manage.

When the problems are clear, the redesign becomes easier to judge. A new visual style is only one part of the work. The redesign must also improve the website goal, page structure, copy, proof, speed, SEO foundations, contact paths and measurement. Otherwise the business may spend money and end up with a modern version of the same weakness.

This checklist is designed for businesses that already have a website and are considering a rebuild. If the site is still useful in parts, protect those parts. If the site is weak everywhere, rebuild with a stronger strategy. Either way, start with evidence before jumping into mockups.

Start by asking what the current website is supposed to achieve. Is it meant to generate enquiries, sell products, build trust, recruit staff or support existing customers? Then compare that goal to what actually happens. A website may look outdated but still attract useful enquiries. Another may look fine but produce low-quality leads because the offer, pricing context or qualification path is unclear.

Review recent enquiries. Which services do people ask about? Are they the services the business wants to grow? Do enquiries include enough information to respond well? Do people ask basic questions that the website should already answer? Do visitors contact the wrong department? These clues show whether the problem is design, copy, structure or lead routing.

If the business does not track leads, fix that during the redesign. A new website should launch with analytics, form tracking, phone and WhatsApp click tracking and clear internal follow-up. For many businesses, this is where analytics setup becomes as important as the new design.

A common redesign mistake is deleting old pages without checking whether they still have value. Some pages may receive search traffic, backlinks, referral visits or direct bookmarks. Others may contain proof, FAQs, service explanations or downloads that should be improved rather than removed. Before rebuilding, create a page inventory.

The inventory should list current URLs, page purpose, traffic, search impressions, backlinks where possible, conversion value, content quality and recommended action. Each page can be kept, rewritten, merged, redirected or deleted. This step protects the business from launching a prettier site that loses useful visibility.

For search-sensitive websites, involve technical SEO audit work before launch. Redirects, canonical tags, metadata, headings, internal links, indexing and sitemap updates should be planned, not guessed on launch day.

Many redesigns fail because they improve the look without improving the way services are explained. A website may have grown over time, with new services added wherever space existed. The menu becomes unclear. Important services hide under broad headings. Related offers are not linked. Buyers cannot tell which service fits their problem.

Before redesigning, map the services the business actually wants to sell. Identify the primary services, secondary services, industries, locations and supporting resources. Decide which services deserve their own pages and which should remain as sections. This is the same logic behind a strong service business website structure.

The redesign should make priority services easier to find and understand. If the business has shifted direction, the new site should reflect the current offer, not the old company profile. If a service no longer matters, remove or downgrade it. If a new service is central to growth, give it depth and proof.

A redesign is a good moment to improve website copy because design cannot rescue vague messaging forever. Review whether the current copy explains the business clearly, speaks to real buyer concerns and uses enough proof. If the old site says the business is professional, reliable and experienced but never shows evidence, the new site should fix that.

Gather testimonials, case studies, project photos, client logos, certifications, team profiles, process notes and measurable outcomes. Decide where proof belongs. Homepage proof builds overall confidence. Service-page proof supports specific offers. Case studies show depth. Process sections reduce fear about delivery. Contact pages prove the business is reachable.

This work should happen before final design. If proof arrives late, the design may not have proper space for it. Strong redesigns are content-aware from the start.

Redesigns often stall because nobody owns the content decisions. The website team may be ready to build, but service descriptions, team bios, project photos, testimonials, pricing notes and approval comments arrive slowly from different people. Before production starts, assign one internal owner for content and name the people who must approve sensitive pages.

This owner should not simply forward every opinion. They should protect the project goal, gather useful input and return clear decisions. If sales says a service page needs stronger qualification, that feedback matters. If operations says a process claim is unrealistic, that matters too. But the feedback should arrive early enough to shape the page, not after the final preview.

A content owner also helps the redesign launch cleanly. They can confirm old content to keep, proof to reuse, pages to rewrite, documents to update and staff details to remove. That practical coordination is often the difference between a redesign that launches on time and one that waits for missing information.

A redesign should improve the experience people actually use. For many Kenyan businesses, that means mobile. Review the current site on several phones. Can visitors read the text, open the menu, find services, tap buttons, complete forms and contact the business without friction? If not, mobile issues should be part of the redesign scope, not an afterthought.

Speed should also be measured. Large images, old plugins, poor hosting, bloated themes and unnecessary scripts can slow the current website. A redesign is a chance to improve the technical foundation. If the new site uses the same heavy habits, it may look better but still frustrate users.

Check security, SSL, backups, broken links, forms, image handling, indexing issues and CMS health. If the current WordPress site is difficult to update, decide whether the problem is the platform, the theme, plugins or lack of maintenance. Sometimes speed optimization and maintenance can repair a site. Sometimes a rebuild is cleaner.

Launch week should not be the first time the team thinks about redirects, forms, analytics or DNS. A redesign has more moving parts than a new website because it replaces an existing asset. Old URLs may change. Forms may need new routing. Analytics may need migration. Search Console needs monitoring. Campaign links may need updating.

Build a launch checklist early. It should include redirect mapping, form testing, phone and WhatsApp links, payment or booking flows if used, metadata checks, sitemap submission, robots settings, page speed checks, mobile review and backup. If the website supports important leads, test notifications with the real team members who will respond.

After launch, monitor performance. Search visibility can fluctuate, but avoid preventable damage by watching crawl errors, broken redirects, missing pages, form failures and speed issues. A redesign should have a stabilization period, not a sudden handoff into silence.

• Map old URLs to new URLs before launch.
• Test every form, call link, WhatsApp link and important button.
• Install and verify analytics, Search Console and conversion events.
• Check mobile layouts, page speed, metadata and indexability.
• Monitor the site for errors after launch and fix issues quickly.

Not every old website needs a full rebuild. A repair may be enough if the site has a solid foundation and the main problems are copy, proof, forms, speed or tracking. A redesign is useful when the business needs a better user experience, new structure and stronger visual presentation. A rebuild is necessary when the platform, codebase, content model or technical setup no longer supports the business.

The fastest way to choose is to score the current site against business value. Does it attract the right visitors? Does it explain the offer? Does it earn trust? Does it work on mobile? Does it generate measurable enquiries? Can the team update it? Is it technically healthy? If several answers are no, redesign or rebuild becomes easier to justify.

A good redesign protects what still works and fixes what is holding the website back. Start with the checklist, then let the new design express the stronger strategy underneath.