Does Your Website Need a Developer or Just a Few Fixes?

Someone is going to tell you that you need a new website. That someone usually sells new websites.

Sometimes they're right. Often the actual problem is four small things, none of which requires a rebuild, and a full redesign would carry every one of them across to the new site.

Here's how to tell the difference before you spend anything.

Start with the symptom, not the solution

"My website needs work" isn't diagnosable. These are:

• Nobody can find it in search
• People find it but don't get in touch
• It looks dated next to competitors
• It's slow
• You can't update it yourself
• It breaks on phones
• It can't do something your business now needs

Each of those has a different answer, and two of them frequently need no developer at all.

Things you can fix yourself, today, for nothing

Before anything else, rule these out. All are common, all are free, and none needs technical skill.

Your contact form is broken. Submit it from a phone, on mobile data, using an address you control. Confirm it arrives and isn't in spam. Broken forms fail silently — nothing tells you, enquiries just stop.

Your phone number isn't tappable on mobile. Tap it. If it doesn't dial, that's one line of code your host's editor can usually handle.

Your content is stale. Old copyright year, a blog that stopped in 2022, "coming soon" pages, staff who left. Visitors read these as *possibly closed*.

You're accidentally blocked from Google. Search `site:yourdomain.com`. If nothing comes back, something is telling search engines to stay away — often a checkbox left on from the build. That's a five-minute fix, not a rebuild, and there's a full walkthrough in why your website doesn't show up on Google.

Nothing on the site mentions price. Adding a starting figure or a range costs nothing and stops people silently assuming you're unaffordable.

If your symptom disappeared, stop here. You've saved yourself a project. The longer version of this list is ten signs your website is losing you customers.

Things a developer fixes without rebuilding

The middle category, and the one most under-used — because it's easier to sell a redesign than a repair.

Speed problems. Oversized images, too much JavaScript, render-blocking scripts, missing image dimensions. Real engineering work, but it's surgery on an existing site rather than replacement. A site failing Google's thresholds — LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1 — can usually be brought inside them without touching the design.

Mobile layout breakage. Text overflowing, buttons too small, horizontal scrolling. Usually CSS fixes, not architecture.

Missing service pages. If you rank for nothing because eight services share one page, the answer is more pages — not a new site.

Adding one capability. A booking form, online payments, a quote calculator. These bolt onto most existing sites.

Accessibility problems. Contrast, keyboard navigation, missing labels. Almost always fixable in place, and increasingly a legal consideration as well as a decency one.

The rule of thumb: if the site's structure is sound and specific things are wrong with it, repair. Repair is cheaper, faster, and preserves the search history the site has already built — which a rebuild can easily throw away.

Things that genuinely need a rebuild

Now the honest other side. Some sites shouldn't be repaired.

You can't change anything without paying someone. If updating a phone number needs a developer, the cost isn't the website — it's every small change for the next five years.

It's built on something no longer maintained. An abandoned page builder, an unsupported framework, a platform whose owner vanished. Patching this is money spent on a foundation that will fail anyway.

It has security problems that can't be patched. Outdated software with known vulnerabilities. This is urgent, not aesthetic.

Fixing the speed means rewriting it. Some sites are slow because of one heavy image. Others are slow because they load a twelve-megabyte page builder to display three paragraphs. The second isn't fixable in place.

Your business changed. You sell different things to different people in different places than when the site was built. Restructuring past that is often more work than starting again.

Every fix breaks something else. The clearest signal there is. If repairs keep producing new bugs, the foundation is gone.

The test that settles it

When you're still unsure, one question decides: is the structure sound, with specific things wrong with it? Or is the structure itself the problem?

Specific things wrong → fix them. Structure is the problem → rebuild.

A useful proxy: write down every problem, then get a quote for fixing them all. If that's a meaningful fraction of a new site, rebuild. If it's a small fraction, fix. Any developer worth hiring will tell you which side you're on, including when the answer costs them the larger job.

What to ask a developer — and what should worry you

When you get an assessment, these answers tell you a lot.

Good signs

• They ask what problem you're trying to solve before proposing anything
• They tell you which items you could fix yourself for free
• They can explain why a rebuild is necessary in terms of your business, not the technology
• They ask about your traffic and current rankings before suggesting anything that changes URLs

Worrying signs

• "Rebuild" arrives before any diagnosis
• The reasoning is that the technology is old, with no explanation of what that costs you
• No mention of preserving your existing search rankings
• A quote before anyone has looked at what's actually wrong

That last one matters more than it sounds. A rebuild that changes your page addresses without redirects can erase years of accumulated search visibility overnight. It's recoverable, but only if someone plans for it — and the plan needs to exist before the build, not after the traffic drops.

The short version

Most websites people describe as "needing to be redone" need three of the free items and one afternoon of developer time. Find out which you are before anyone quotes you for a project.

Frequently asked questions

Do I need a new website or just fixes?

Ask whether the structure is sound with specific things wrong with it, or whether the structure itself is the problem. Specific faults — slow images, broken mobile layout, missing service pages — are repairs. A platform you can't update, can't secure, or that breaks every time it's touched is a rebuild. Get a quote for fixing everything on your list; if it's a small fraction of a new site, repair.

How do I know if my website needs to be rebuilt?

Four signals make a rebuild the honest answer: you can't change anything without paying someone, the platform is no longer maintained, there are security holes that can't be patched, or every fix breaks something else. Age alone is not one of them — "the technology is old" is only a reason if someone can say what it costs you.

Will a new website hurt my Google rankings?

It can, badly, if page addresses change without redirects — years of accumulated visibility can go overnight. It's recoverable, but only if the redirect plan exists before the build rather than after the traffic drops. Ask any developer quoting a rebuild how they'll preserve your existing URLs; a good answer is specific, and no answer at all is a warning.

What website problems can I fix myself for free?

Five of them: test your contact form actually delivers, make your phone number tappable on mobile, update stale content and copyright years, check you aren't blocking search engines with a leftover noindex, and put a starting price somewhere on the site. None needs technical skill and together they resolve a surprising share of "my website needs redoing".

Where to start

Work down the free list first. If your symptom survives all five, you have a real diagnosis to hand a developer — and a much better conversation than "my website needs work".

If the symptom you arrived with was speed, the seven usual causes will narrow it further before you talk to anyone. And if the answer here turns out to be yes, you do need someone, how to hire a web developer is the next step — mostly a matter of judging the conversation rather than the code.

If you'd like that assessment for nothing, book a free 30-minute call. If your site needs four small fixes rather than a project, I'd rather tell you that than sell you a rebuild — and you can see what I do build on the services page.