Should I Fix or Rebuild My Website?
There is a thing you should know about the quotes in your inbox.
The studio that does redesigns has told you to redesign. The consultant who does platform migrations has told you to migrate. Neither of them is lying to you. They have each answered with the tool already in their hand — the redesign studio sees a redesign, the migration specialist sees a migration. That is not dishonesty; it is the shape of the question they were built to answer. The honest answer to “what should I do with my website” has three branches, and the two that pay the person quoting are the two you tend to hear.
So before you spend a penny, run this. It takes ten minutes and it works on any site, including the one you’re staring at right now.
How to Decide: Fix, Rebuild, or Wait
When someone asks me “should I fix this or start again,” they are usually asking the wrong question. The real one is: where is the problem actually living?
A tired website has its trouble in one of three places. It’s in the pages — the words, the structure, the thing a stranger sees in the first three seconds. It’s in the platform — the system the site is built on, which won’t let you fix the pages even when you know what’s wrong. Or it’s in the business — the offer, the customer, the way enquiries are meant to reach you — and the website is the wrong thing to spend on at all yet.
Three places. Three answers. Find which one is true and the decision makes itself.
Fix It When the Problem Is Local
Start here, because this is the answer I reach for most often, and the one that rarely shows up in a quote.
Throwing away a site that already works is the most expensive mistake on the table — every ranking, every backlink, every year Google has spent learning to trust your domain, set on fire to start again from a zero that takes months to climb out of. The full case for keeping what already ranks is here. What that piece doesn’t give you is the test for your site. So here it is — four checks you run yourself, in ten minutes.
Does it rank at all? Type your business name and your town into Google. Showing up — even on page two — means the authority already exists. You’re not building trust from scratch; you’re tuning what’s there.
Is it indexed, with low clicks? If you can open Google Search Console (or ask me to), look for pages with real impressions but few clicks. That gap is a copy-and-snippet fix — a sharper title and meta description — not a structural one. The hard part is already done.
Is real traffic actually arriving? Open your analytics. Genuine visitors landing on the site means the engine runs. The job is converting them, not finding them.
Can you name the failing pages? List the three pages meant to do the most work. Is the failure on those named pages — a weak homepage, a buried service page, a contact form posting to an inbox nobody reads — or is it everywhere at once? If you can point at named pages, the trouble is local.
When all four hold, you don’t need a rebuild. You need someone to fix the pages that are leaking — and a website makeover does exactly that, working within your existing platform, for a fraction of what a rebuild costs.
The clearest version of this: a site getting real traffic and no enquiries. Usually the platform is fine and the first three seconds are broken. That’s a half-day’s work, not a new website.
Rebuild When the Platform Is the Cage
The test for this branch is one question: can I make the fix the first branch demands?
If the answer is “yes, but the platform turns every change into a fight,” you might still patch it. If the answer is “no, the platform simply won’t let me,” you have your answer. The cage is the problem, and you don’t redecorate a cage. The conditions below are what a failed test looks like in the wild.
An old WordPress build nobody can safely touch. Plugins out of date, a theme nobody understands, every change a gamble that something else breaks.
A Wix or locked-down builder that won’t let you control structure or URLs. You can see what needs fixing. The platform simply won’t let you do it.
A custom site nobody can edit any more. The developer who built it is long gone, the code is a mystery, and changing a phone number means hiring someone for a day.
An ageing shop platform you’ve outgrown. The catalogue creaks, the checkout leaks, and every workaround is another layer of tape.
This is where a migration earns its keep — moving to a platform that works with you instead of against you. Wix to Shopify when the builder is holding the structure hostage. WordPress to Shopify when the maintenance has become a part-time job you didn’t apply for. EKM to Shopify when you’ve outgrown the shop you started on. A Shopify migration runs from £1,490 (from WordPress) or £2,795 (from EKM), and a fresh build from £1,499 — real money, and worth every pound when the platform is genuinely the cage. Not when the site merely looks dated. Dated is a finish problem. Caged is a foundation problem. Only the second one justifies the spend.
Neither — Not Yet
Here is the third branch.
Sometimes I look at a business and the right answer is: don’t spend on the website at all. Not yet.
A website turns up the volume on whatever the business already is. Turn up the volume on an unclear offer and you just get louder confusion. A multiplier needs something to multiply, and some businesses haven’t got the inputs yet. When they’re missing, a beautiful new site amplifies nothing, and the owner concludes — wrongly — that websites don’t work for their kind of business.
No clear offer. If a stranger can’t tell what you sell and who you sell it to in one sentence, no website can rescue that. Get the offer sharp first.
No clear customer. “Anyone who needs us” isn’t a customer. The page can’t speak to a person you haven’t named.
A half-empty Google Business Profile. This is free, it’s where local customers actually find you, and it’s sitting neglected. Filling it in will move more enquiries this month than a redesign moves all year.
No way to capture an enquiry. No phone in the header, no working form, no follow-up when someone does get in touch. The leak is at the bucket, not the tap.
When I see those gaps, I say so. You’re not ready to spend money on the website. Fix these first — most of them are free — and come back to me when you have. It loses me the sale today.
I’d rather tell you to wait and be right than tell you to spend and be the reason it didn’t work. So run the three branches on your own site. Is the problem in the pages? Fix them. Is it in the platform? Rebuild on something that doesn’t fight you. Is it in the business? Stop, sort the inputs, come back when the website has something to amplify.
And if you want a straight answer on which branch you’re standing in, send me the URL. I’ll tell you what I’d actually do — fix, rebuild, or wait — even when the answer is the one that doesn’t earn me a thing. Drop the link to tony.cooper@webuildstores.co.uk and I’ll send back an honest read the same week.
Fix when the problem is local. Rebuild when the platform is the cage. Wait when the business isn’t ready. The trick is being honest about which one you’re looking at.
Tony Cooper
Founder
Put My Crackerjack Digital Marketing Skills To Work On Your Next Website Design Project!
Get Started