Skip to content
Godwin LawsonBUILDING WITH PURPOSE

Web Development

Website Redesign or Small Improvements: Which Does Your Business Actually Need?

Website Redesign or Small Improvements: Which Does Your Business Actually Need?

Choose small improvements when the website’s structure and technical foundation still support the business and the problems are limited. Consider a redesign when several connected issues make it difficult to serve users, manage content or deliver the functions the organisation needs.

The decision should follow an assessment of the current website and the intended result. An old visual style is a reason to review the site, but it does not automatically justify rebuilding everything.

For a business owner, a useful proposal explains what needs to change, why that level of work is appropriate and what useful parts of the existing site will be preserved.

Start with tasks, rather than a preferred solution

Write down what a customer or staff member needs to do and where the difficulty occurs. “Prospects cannot find the relevant service” gives the review a different direction from “the enquiry form no longer reaches our inbox”.

Then identify the evidence: an observed usability problem, a confirmed technical fault, an outdated offer or an operational requirement the site cannot meet.

Keep preferences in the discussion too, but distinguish them from faults. Management may want a stronger visual identity while the most urgent customer problem is an incorrect contact route.

When focused improvements may be enough

A small project can be appropriate when a problem has a clear boundary and the rest of the website remains useful.

  • Correcting contact details and checking enquiry delivery.
  • Updating a service description or replacing outdated information.
  • Repairing a specific mobile layout problem.
  • Improving a confusing navigation label.
  • Replacing oversized or unsuitable media.
  • Adding a relevant project example to an existing page.

These are examples of possible scopes, not diagnoses. A seemingly small symptom can have a wider cause, so allow for investigation before committing to a fixed repair.

My website care and technical support services are a suitable starting point for an existing site that needs assessment or targeted work.

When a larger improvement project may fit

Some websites need more than isolated fixes without needing a complete rebuild. A content and navigation project may reorganise service information, improve key page templates and connect useful project evidence.

Another project might preserve the platform while addressing performance, publishing tools and several important visitor journeys. The work should have a coherent purpose and testable outcomes.

This middle option is useful when the foundation remains suitable but a sequence of unrelated small edits would produce an inconsistent result.

When a redesign deserves serious consideration

A redesign can make sense when the site no longer reflects the organisation, its structure blocks important tasks or the current implementation cannot reasonably support agreed requirements.

For example, a company that has added several service lines may need a different information structure. A public information site being turned into a private operational system may require a separate application project rather than only new page styling.

Ask the provider to explain which limitations cannot be resolved sensibly within the existing setup. A recommendation to rebuild should include the delivery, migration and ongoing support implications.

Question Focused improvements Wider redesign or rebuild
How connected are the problems? Limited to identifiable pages or functions Spread across the structure, templates or workflows
Does the foundation fit? It can still support the agreed purpose Important requirements need a different approach
What needs review? The affected task and nearby dependencies The complete information and user journey
What must be protected? Working functions and existing content Those items plus a deliberate migration and launch plan

A practical distinction using a service website

My services overview connects different types of work with relevant enquiry routes. Correcting one contact label would be a focused change. Reorganising how every service is presented would be a broader information project.

Similarly, my BIUC project presents several specialist capabilities. A proposal for that type of website should assess whether a new requirement affects one destination or the overall structure. This is a planning distinction, not a report of a specific repair or redesign result.

Compare total work and disruption

Ask for a practical comparison where both approaches are credible. Consider discovery, content preparation, implementation, testing, staff time, launch and later maintenance.

A low initial repair quote may be poor value if it leaves several important dependencies unresolved. A large redesign may also be unnecessary when a bounded change solves the actual problem.

Assess what the business will need to provide. A rebuild can require revised copy, photographs, decisions, approvals and migration work. Those commitments should be visible in the plan.

Preserve useful content and web addresses

Identify existing pages, downloads, accounts and functions people rely on. Review available search and usage records before removing destinations or changing URLs.

Where a URL must change, plan an appropriate destination and redirect where required. Google Search Central‘s site-move guidance describes mapping addresses, testing and monitoring when URLs change.

Do not assume a more modern appearance automatically preserves search visibility or improves enquiries. Those questions require their own evidence and follow-up.

Use a phased decision where uncertainty remains

  1. Assess the current site and document the main problems.
  2. Resolve urgent faults that block an important task.
  3. Agree the requirements and compare credible options.
  4. Define a focused first phase with acceptance checks.
  5. Review the result before adding further work.

A phased approach should still fit a coherent plan. Avoid repeated changes that conflict with the direction already agreed or create unnecessary rework.

The right scope is the one that addresses the actual requirement while accounting for the useful work and dependencies already in place.

What should the proposal explain?

A useful proposal identifies the observed problem, recommended scope, deliverables, content responsibilities, testing, timing and support. It also states what is excluded and how additional requests are handled.

For a redesign, include the migration and transition plan. For targeted work, define which pages or functions are affected and which nearby tasks will be checked afterwards.

Ask how completion will be demonstrated. An enquiry repair should include an authorised receipt test. A navigation change should be reviewed through an actual visitor task. A visual redesign needs functional review as well as design approval.

Choose the next step using evidence

If the problem is not yet clear, begin with a review rather than a premature commitment to a full build. My consultation, content development and website design and development services cover different needs.

Explore my selected projects for relevant context and bring the specific user task or business problem to the first conversation.

Frequently asked questions

Does an old website always need replacing?

No. Assess its current suitability, maintainability and user experience before deciding.

Can a redesign keep the same domain?

Often, yes. A domain change is a separate decision with additional implications.

Can small improvements increase enquiries?

They may remove obstacles, but results depend on audience, offer and the wider business process. Define what will be measured.

Technical reference checked 3 November 2026: Google Search Central, site moves with URL changes. Copyable reference: developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes.

Discuss your website or digital project

Send me your current website, the problem you want to solve and the people you need to serve. We can review the requirement and agree a practical scope, timing and quotation.

  1. WhatsApp: Start a conversation on WhatsApp.
  2. Contact page: Send a project enquiry.
  3. Email: [email protected].
  4. Phone: +234 703 799 7791.

Based in Uyo, Akwa Ibom State, Nigeria. Remote working arrangements can be discussed.

Lawson Godwin Hezekiah

About Lawson Godwin Hezekiah

Technology entrepreneur, website developer and founder of Mita School and Techmita. I work with businesses, educational institutions, government organisations and NGOs.

Read my story ↗

Keep exploring

Let us work together

Put the ideas into practice.

If your website or digital strategy needs attention, let us discuss a useful next step.