Your website still works, but it no longer feels quite right. The photographs are dated. Your services have changed. Updating a simple paragraph takes more effort than it should.
Then you visit a competitor’s website on your phone and wonder whether it is time to start over.
Before deciding, it helps to separate what looks outdated from what is getting in the way of your business. A website may need clearer information and a few targeted repairs. It may also have deeper limitations that make a rebuild worth considering.
The useful starting question is: What do your customers need to do on your website, and how well does it help them do it?
Start with what needs to work better
For a small business, a website might need to explain services, show examples of work, answer common questions or encourage an enquiry. Some businesses also depend on online bookings or sales.
Think about where you are noticing friction. Do customers keep calling to ask questions the website should answer? Is an important service difficult to find? Can you update your hours without asking someone for help?
These are useful observations to bring to a website discussion. They do not, by themselves, mean you need a new site.
Try your website as a customer
Open your website on your phone and choose one service a customer might need. Then:
- Find the information that would help you decide whether the service is suitable.
- Find the next step, such as requesting a quote or making a booking.
- Submit a test enquiry and confirm that it reaches the right inbox.
- Write down anything confusing, missing or difficult.
If possible, ask someone unfamiliar with the website to try the same task without guidance. Notice where they hesitate.
This is a practical starting point, rather than a complete technical or accessibility assessment. It gives you specific problems to investigate instead of a general feeling that the website needs work.
What is the difference between a refresh and a rebuild?
For this discussion, a refresh means improving the existing website while keeping its main structure and platform. That could include updating photographs, rewriting service information, simplifying navigation or improving selected page layouts.
A rebuild involves more substantial changes to the website’s underlying structure, templates or platform. It may be appropriate when the current setup cannot reasonably support what the business needs.
The terms are not always used consistently in proposals. Ask what will actually change, what will be retained and why that approach is being recommended.
When a refresh may be the right approach
Consider a local service business whose contact form works, whose information is mostly accurate and whose website can still be maintained. Its photographs are old, its service descriptions are vague and its navigation needs tidying.
In that situation, a refresh is worth investigating. The work can focus on the identified weaknesses while retaining useful parts of the existing site.
Now imagine the same business needs customers to book appointments and pay deposits online. The decision becomes broader: can the current platform support that process reliably, and what would be involved in adding it?
This is an illustrative example, not a client case study. The point is that the business requirement should shape the scope of the work.
When a rebuild deserves consideration
A rebuild deserves a closer look when problems affect much of the website, essential components are no longer supported or the existing setup cannot reasonably accommodate an important requirement.
Even then, investigate the cause before choosing the solution.
| What you notice | What to investigate |
|---|---|
| Dated photographs or unclear service information | Whether focused content and visual improvements would address the problem |
| Enquiries are not arriving | The form, delivery settings and receiving inbox before deciding on broader changes |
| Layout problems across many pages on phones | Whether shared templates can be repaired or need replacement |
| A new booking or sales requirement | Available integrations, their limitations and the work needed to support them |
| Unsupported components or difficult updates | Maintenance options and the scope of replacing affected components |
A recommendation should explain how the proposed work addresses the findings. “The website is old” does not explain what work is needed or why.
Look beyond appearance
The customer exercise helps identify visible difficulties. Other areas deserve a more detailed review.
Performance. Google’s Core Web Vitals measure aspects of loading, responsiveness and visual stability.[1] They provide useful evidence about the page experience, but they do not tell you whether your service information is persuasive or your enquiry process meets your needs. Use measurements alongside practical checks to decide what needs attention.
Accessibility. Can people navigate with a keyboard? Are text and controls readable? Are form fields clearly labelled? W3C provides preliminary checks that can help reveal some accessibility barriers, while explaining that these checks are not a complete assessment.[2] Automated tools can assist, but human evaluation is also necessary.[3]
Maintainability. Consider who will update the website and how routine changes will be handled. A design should be assessed alongside the practical work of keeping information current and the underlying software maintained.
Plan for existing pages and search visibility
Before removing pages or changing their addresses, identify which existing content should be retained and how old addresses will lead visitors to the right place.
Google’s guidance for site moves with URL changes includes mapping old URLs to their new destinations and implementing redirects. It also explains that rankings may fluctuate temporarily while Google recrawls and reindexes the site.[4] For a permanent URL change, Google recommends a permanent server-side redirect where possible.[5]
That does not mean every visual refresh requires a site migration. It means that if page addresses will change, the proposal should include a plan for them.
Compare the full scope—and your own workload
The headline price is only part of the decision. Ask what the proposed work includes and what you will need to provide.
Will existing content be reused, edited or rewritten? Who supplies photographs? Are redirects, testing and handover included? What hosting, software subscriptions and ongoing support will be needed afterwards?
Your time belongs in the calculation too. Gathering images, checking service descriptions, reviewing layouts and approving changes all need a place in the schedule. Agreeing on those responsibilities early gives you a clearer picture of the project.
When comparing quotations, look for a defined scope and clear responsibilities. A lower price may reflect fewer deliverables; a higher price should be supported by an explanation of the additional work.
Ongoing maintenance also needs an owner. For WordPress sites, the official WordPress documentation recommends backing up the database and files before updating.[6] Ask who will handle updates, backups and checks after changes, and what is included in any support arrangement.
Ask how the changeover will be handled
If your business relies on website enquiries, it is reasonable to ask how the work will affect day-to-day operations.
Before work begins, clarify:
- How will the current website remain available while changes are prepared?
- Who controls the domain, hosting and business email, and will any of those services be affected?
- What will be tested before launch, including forms and bookings?
- What is the recovery plan if a change causes a problem?
The answers will depend on the project. Having them agreed in advance helps define what a successful handover should involve.
Can the work be done in stages?
If the website remains usable and maintainable, ask whether improvements can be prioritised. A broken enquiry process may deserve attention before new photography. Clearer service information may be useful while a larger project is being planned.
Staging the work is worth discussing, but so is avoiding duplication. Ask which improvements would carry forward into a future rebuild and which might need to be done again.
Before committing, you should be able to answer three questions:
- What specific problems will this work address?
- Why is the proposed approach suitable for the existing website?
- What will it take to keep the result working and up to date?
Choose the level of change your business needs
You do not need to arrive at a website consultation knowing whether you want a refresh or a rebuild. Start with three things you want the website to do better, along with any difficulties you or your customers have noticed.
That gives the conversation a practical focus: what is worth keeping, what needs attention and where a larger change may be justified.
Let’s talk about your website
Through Website Consulting, Econoweb Designs can help you assess your existing website and consider which improvements deserve priority. The aim is to give you a clearer understanding of your options and the work involved, so you can make an informed decision.
Website Maintenance & Support can help with the ongoing care of your website as your business needs change.
If you are unsure where to begin, let’s talk about your website.
References
- Google, web.dev, Web Vitals.
- W3C Web Accessibility Initiative, Easy Checks — A First Review of Web Accessibility.
- W3C Web Accessibility Initiative, Evaluating Web Accessibility Overview.
- Google Search Central, How to move a site.
- Google Search Central, Redirects and Google Search.
- WordPress Documentation, Updating WordPress.
