Clarify what is actually broken

A website can feel old for many reasons: the design is dated, the content is vague, the service structure is confusing, the website is slow, forms are unreliable or analytics is missing. These problems need different fixes. A rebuild should name the real weakness before production starts.

Trust problem
Content problem
Technical problem
Conversion problem

Protect useful search and proof assets

Old websites sometimes contain pages, links, case evidence or search visibility that should not be deleted casually. Before rebuilding, review which URLs attract traffic, which pages support enquiries, which proof can be reused and which outdated content should be redirected or rewritten.

Make the service structure sharper

Most redesigns underperform when the new website still explains services in a generic way. The rebuild should make it easier for buyers to understand what you do, who it is for, what makes the work credible, how pricing is shaped and what the next step looks like.

Add tracking before judging performance

A rebuild should not launch blind. Forms, phone clicks, WhatsApp clicks, quote requests and important campaign sources should be measurable. Without tracking, it becomes difficult to know whether the new design improved the business or only improved appearance.

Plan ownership after launch

The website should be easy enough to maintain, secure enough to trust and structured enough to improve. If the team cannot update content, add proof or review lead sources after launch, the rebuild will slowly become another old website.

Decision filter

Repair, redesign or rebuild?

A rebuild should be chosen because the business needs it, not because the current website feels old. Use this filter before committing budget.

Option	Best for	Watch out for
Targeted repair	The website has a few weak areas but the structure, platform and content still work reasonably well.	Small fixes will not solve a deeper trust, SEO or architecture problem.
Structured redesign	The business needs clearer services, better proof, stronger mobile UX and a cleaner conversion path.	Redesign should include redirects, content review and analytics checks, not only new visuals.
Full rebuild	The current platform, content model, performance or workflow cannot support the business anymore.	Needs more planning, migration care and ownership decisions before work begins.

Founder checklist

Questions Kelvin would ask before approving a rebuild

These questions keep the project grounded in business value instead of drifting into surface-level redesign conversations.

What problem is the rebuild meant to fix?

Name the business problem before naming the design style.

Which pages already earn traffic, trust or enquiries?

Protect useful URLs, proof and search signals before replacing the site.

What should the buyer understand faster?

Rebuild service structure, proof placement and calls to action around real buyer questions.

How will we know the rebuild worked?

Track forms, calls, WhatsApp taps, quote requests and lead source from launch.

For a quick first read, use the Website Redesign Readiness Score before requesting a scoped quote.

Practical questions

Frequently asked questions

When is a website redesign better than small fixes?

A redesign is better when the problems are connected: weak structure, dated design, poor mobile experience, unclear services, missing proof and unreliable conversion paths. Small fixes are enough only when the foundation is mostly healthy and the issues are isolated.

What should be reviewed before deleting old pages?

Review traffic, backlinks, Search Console performance, enquiries, internal links and content relevance. Some old pages should be improved or redirected rather than deleted, especially if they still support search visibility or buyer decisions.

Should analytics be added before or after a redesign?

Analytics should be considered before launch and checked immediately after launch. Forms, calls, WhatsApp taps and quote requests should be tracked so the business can compare performance and identify what needs improvement.

How does founder involvement improve a website rebuild?

Founder-led planning helps connect the website to business consequences: what the site must explain, which buyers it must serve, how the structure supports SEO, what proof is needed and how leads will be measured after launch.

What is the first step before rebuilding?

Start with a review of the current website, business goals, service structure, content gaps, technical issues and conversion path. That review decides whether the right next move is repair, redesign or a deeper rebuild.

Continue planning

Founder Notes: What to Fix Before Rebuilding a Website