Does your website need a rebuild, or a precise repair?
An awkward page does not automatically justify replacing a whole website. A rebuild becomes more reasonable when the structure or platform prevents the business from making the changes it needs to maintain.
Name the problem you can observe.
Examples: the service is hard to understand, the contact route fails, the team cannot edit opening hours, or important pages are inaccessible on a phone. Start with the actual difficulty rather than “the site feels old”.
Use the website enquiry checklist to separate a content problem, a broken action and a visual concern. Each can call for a different amount of work.
Check whether a focused repair can hold.
A repair is a strong candidate when the useful structure is already there, the team can maintain it and the problem is limited. You may need one clearer service page, a simpler navigation label or a working form.
The Eightfold Creative case is a useful example: I gave Brent a prioritised plan for clearer pages and an enquiry path; he made the changes. The case identifies what was verified live. Traffic, enquiry and revenue effects were not measured.
Look for the reasons to rebuild.
A rebuild may be justified when the information is organized around an offer the business no longer has, repeated fixes conflict with one another, or the team cannot make necessary changes safely.
- Content is mostly useful
- Plan to retain and improve it, even if the platform changes.
- Structure hides the real offer
- Map the customer’s decisions before designing page layouts.
- Editing is unreliable
- Inspect access, workflow and platform limits; training may be enough.
- Several core paths are broken
- Compare a coordinated repair with a rebuild using the same requirements.
Protect the parts that already work.
Inventory the current public URLs, useful search entry pages, forms, domain settings and accounts. Decide which addresses stay, which redirect and what can be retired. Preserve the content or history the business still needs.
Before changing the site, keep a recoverable copy and write down how each important customer journey works. After the change, repeat those journeys and check that useful old addresses still lead to the right place.
Compare complete options.
Ask for the repair and rebuild options to include content, migration, testing, access and upkeep. A low build price can be misleading if the team must recreate all the content or reconnect important tools afterwards.
Choose the option that addresses the observed problem and can be maintained. Retest the same customer journey after the change so the decision is assessed by working behaviour as well as appearance.
