“I think I need a new website.”
Whenever a small business owner tells me this, my first question is simple:
What is wrong with the website you already have?
Sometimes the answer is obvious. The site no longer represents the business. Customers struggle to find what they need. The team cannot manage it properly. The structure has become a mess.
Sometimes the website is perfectly usable and the problem is somewhere else.
People cannot find the business.
The contact form is full of spam.
Nobody knows whether the website generates enquiries.
The homepage has too many things competing for attention.
Or the website generates an enquiry and nobody inside the company knows who is supposed to reply.
A small business website redesign can solve important problems. It can also become an expensive way of replacing a website that needed a few specific changes.
I have worked with websites as part of digital marketing for more than 18 years. My approach is to diagnose the problem first, then decide whether the website needs a fix, a refresh, or a rebuild.
Those are three very different jobs.
Fix, refresh or rebuild: what is the difference?
Here is the distinction I use.
| Option | What it means | Typical situation |
|---|---|---|
| Fix | Repair a specific problem | Broken SSL, spam forms, missing tracking, broken contact form |
| Refresh | Improve parts of the existing website while keeping its basic foundation | Weak customer journey, unclear service pages, too many CTAs, missing content |
| Rebuild | Rethink the structure, customer journey, platform or way the website supports the business | Website and business goals no longer match, structure is fundamentally wrong, team cannot manage the system |
The difficult part is working out which category your website falls into.
That decision should happen before anyone starts choosing a new theme, colour palette or homepage layout.
Before a small business website redesign, ask what the website is supposed to do
The first conversation I want to have with a business owner is about the business itself.
What is the website supposed to accomplish?
For one company, the answer may be generating calls.
Another may want quote requests.
A consultant may want qualified enquiries.
A shop may want purchases.
Another business may use its website primarily to establish credibility before a prospect speaks to the sales team.
Once we know the business goal, we can ask a much more useful question:
Is the existing website helping that happen?
This is where small business website redesign conversations often start to change.
A business owner may tell me, “People cannot find us.”
That immediately opens another set of questions. Is this really a website design problem? Has SEO been done? Is the business being promoted? Does the website have useful content? Is Google Search Console installed? What searches already bring people to the site?
Replacing the design does not automatically make a business easier to find.
I have also seen websites that have existed for years with almost no new content. Four or five blog posts were uploaded when the site launched, and nothing meaningful has been published since. A new design will still leave you with the same content problem.
Before spending money on a small business website redesign, find out what you are asking the redesign to fix.
When your website needs a fix
Some website problems are wonderfully boring.
That is good news because boring problems are often easier and cheaper to solve.
Suppose you type your website address and the browser gives you a security warning.
I am immediately going to check the SSL certificate and the HTTPS configuration.
That does not give me a reason to rebuild the website.
The same applies to a contact form producing so much spam that the inbox becomes unusable. I would look at the form setup, spam protection and reCAPTCHA before discussing a new site.
Tracking is another common one.
I have opened websites where Google Analytics or Search Console had never been properly configured. The owner wants to change the website because “it isn’t working,” but we have almost no data showing what people are doing.
In that situation, I would rather install the tracking first and start collecting useful information.
Cookie and privacy setups may also need attention depending on where the business operates, who it serves and what tracking technologies are being used.
These are fixes.
You identify a specific problem and deal with it.
A small business website redesign would be excessive if the main issue is a broken form, missing SSL certificate or absent analytics.
When your website needs a refresh
A refresh goes further.
The technology may be working. The site may load. Forms may submit. Google may already know that the website exists.
The experience between one page and another is where things start falling apart.
Imagine someone lands on one of your useful pages from Google.
They like what they read and want to know more.
They follow a link to your service page.
The service page suddenly becomes vague.
It talks about “solutions,” “quality,” “innovation” and “customer satisfaction,” but the visitor cannot work out whether this is the service they were looking for or what they should do next.
That is the kind of problem I would consider for a refresh.
You may need stronger service pages.
You may need to connect your pillar pages and supporting content properly.
You may need a clearer next step from one part of the site to another.
You may need to remove competing CTAs.
You may simply need to fill in pieces of the customer journey that were never built.
I have had to do this with my own AnksImage website.
At one point, I had far too many variations of essentially the same request: hire me for writing, work with me, contact me, read this, look at that.
The site had accumulated pages and options without enough attention to how somebody was supposed to move through it.
I looked at the analytics and simplified.
I reduced the number of pages I was asking people to navigate. I became much stricter about the action I wanted someone to take.
That work did not require throwing away the entire website.
It required me to understand what the website was supposed to do and remove some of the noise I had created myself.
That is a refresh.
When a small business website really needs a rebuild
There are situations where I will recommend rebuilding.
The first is when I cannot connect the existing website to the business goals in any meaningful way.
If the company needs qualified enquiries, for example, I want the website to make three things clear reasonably quickly:
Who are you?
What do you do?
What should the right visitor do next?
If the structure of the website makes those answers difficult to establish across the site, individual fixes may turn into a long chain of patches.
At that point, rebuilding becomes worth considering.
The customer journey itself is missing
This is one of the biggest reasons I would consider a rebuild.
A beautiful website can have a beautifully designed contact form.
Someone fills it in.
Then what?
Who receives the enquiry?
Who has responsibility for answering it?
How soon?
What happens if that person is unavailable?
Where is the lead recorded?
What happens after the first response?
I look at this because I work on websites as a digital marketing consultant as well as someone who understands website strategy.
For me, the website does not stop working when someone clicks Submit.
That click has to go somewhere.
If the business has never thought about that part of the journey, a website project gives us a chance to build the customer path properly.
The structure no longer reflects the business
Businesses change.
Services disappear.
New services become important.
The target audience changes.
What used to be a side service becomes the main source of revenue.
Sometimes the existing navigation and page structure can handle those changes.
Sometimes they cannot.
If we have to force every new business priority into a structure that belongs to a completely different version of the company, I start considering a rebuild.
The people managing the website cannot comfortably use it
The technology has to work for the people responsible for it.
I have worked on projects where platform decisions created problems for the internal team. One involved moving away from WordPress into a CakePHP-based setup.
The important lesson for me was not about declaring one platform universally better than another.
The issue was practical.
Could the people responsible for routine website work actually manage the system without depending on a developer for every change?
This is one reason I often prefer systems such as WordPress for small-business websites. I know the platform well, and the administrative side can usually be made manageable for non-technical teams.
Your own organisation may have completely different requirements.
The right platform is the one that supports what your website needs to do and what your team can realistically maintain.
A technically impressive system becomes a business problem when ordinary updates become unnecessarily difficult.
“My website looks old” is not enough information
I hear this one a lot.
“The website looks old.”
Okay.
What happens when somebody uses it?
Can they understand the business?
Can they find the service?
Can they use it comfortably on mobile?
Can they contact you?
Is the information correct?
Does the website accurately represent what you sell today?
If those things are working, I would investigate before deciding that visual age alone justifies a small business website redesign.
There are situations where an old appearance starts affecting credibility.
A footer that looks abandoned, old dates, outdated staff information, discontinued services and visibly neglected pages can make a visitor wonder whether the company is still active.
A site can also feel dated because the way people use websites has changed. Navigation that worked reasonably well years ago may be awkward on current mobile devices.
Those are concrete issues we can examine.
“I am tired of looking at it” is different.
And yes, sometimes that still matters.
I have had decision-makers who understood that I could fix the existing website and chose to rebuild anyway.
They were sick of the existing site. They wanted a fresh look. They wanted the website to reflect how they now saw the business.
That is their decision to make.
My job is to make sure they understand what they already have, what should be preserved and what the new website needs to accomplish.
Your small business website redesign can actually destroy things that were already working
This is the part of a small business website redesign that deserves more attention.
I have seen rankings take a plunge after redesign work.
Pages disappear.
URLs change.
Backlinks that used to point somewhere useful lead nowhere.
Content that Google had already indexed gets removed because somebody decides it does not fit the new design.
Internal links are forgotten.
A redesign team can become so focused on what the new website should look like that nobody records what the existing website has already earned.
That is why I want access to Search Console and analytics before major changes whenever possible.
Which pages already receive impressions?
Which pages receive traffic?
What searches are people using?
Which URLs have backlinks?
Which pages lead visitors deeper into the website?
Which actions are already being taken?
You may still decide to remove a page.
At least make that decision knowing what the page was doing.
This is also why a redesign needs a proper URL and redirect plan when page addresses change. A new structure should have a clear relationship with the old one.
A prettier menu is very little consolation if pages that were bringing people to the business suddenly disappear from search.
What I check before recommending a website redesign
My starting point is usually the business goal and the customer journey.
Then I want to understand what evidence we already have.
I look at analytics when they are available.
I check Search Console.
I look at how the homepage explains the business.
I check what happens on mobile.
I follow the navigation as a customer would.
I look at the calls to action.
I test forms.
I look at the service pages.
I check whether there is enough useful content to support the services the business wants to be known for.
I look at whether the site has obvious trust signals.
I want to know whether tracking exists.
Then I follow the enquiry.
Where does it go?
Who receives it?
That final question is important.
A website can generate leads and still disappoint the business because the operational process behind the website is weak.
The design team may have technically completed its job.
The customer still does not receive a reply.
That is why I prefer looking at the whole customer journey rather than treating the website as an isolated piece of technology.
Use this small business website redesign decision checklist
Before you approve a redesign, work through these questions:
- Fix: Is there one identifiable problem such as SSL, spam, tracking, a form, cookie setup or another contained technical issue?
- Refresh: Does the website basically work, while the messaging, service pages, content, CTAs or customer path need improvement?
- Rebuild: Has the website stopped matching the business goals, structure, customer journey or way the team needs to manage it?
- What is the website supposed to achieve for the business?
- Do you have analytics or Search Console data showing what currently works?
- Which pages already receive useful traffic or search visibility?
- What happens after someone submits a form or makes an enquiry?
- Can your internal team manage the website comfortably?
- Are you replacing the website because of evidence, or because everybody is tired of looking at it?
- What existing URLs, content, rankings and links need to be protected if you rebuild?
If you cannot answer those questions yet, I would hold off on choosing the new homepage design.
First find out what you are actually trying to improve.
Fixing the right problem can save you an unnecessary rebuild
A small business website redesign can be the right decision.
I have no problem recommending one when the website has stopped supporting the business.
I am much more cautious when someone wants a redesign because traffic is low, the website is a few years old, the form receives spam or nobody has looked at the analytics.
Those are different problems.
Start with your business goals.
Then look at how a customer currently moves from finding your website to understanding your offer, trusting you, taking an action and receiving a response.
Once you know where that path is failing, the decision becomes much easier.
You may need a fix.
You may need a refresh.
You may genuinely need to rebuild the whole thing.
The important part is knowing why.
If you are reviewing your website yourself, start with my Small Business Website Checklist (2026). It covers the practical things I look for when checking whether a small-business website is ready to turn visits into calls, bookings and enquiries.
If you are already considering a redesign and want someone to diagnose the website before you commit to rebuilding it, my Website Diagnostic is designed for exactly that conversation.
And if paid traffic is already reaching the site but those clicks are not turning into sales or enquiries, read Why Your Ads Get Clicks But No Sales or download Fix My Ads.