Skip to content
Scaleqode

InsightsWebsites

Signs you have outgrown your website

"It looks old" is the reason most rebuilds start and the weakest one. Here are the signals that actually justify the spend.

5 min read

Most rebuilds begin with the same sentence: the site looks dated. It is a real observation and a poor reason on its own, because a new design on the same structure produces a better-looking site that converts exactly as badly as the last one.

These are the signals that actually mean something, roughly in order of how much they cost you.

You cannot change it yourself

The clearest one. If adding a service, updating a price or publishing an announcement means emailing someone and waiting, the site is already frozen. Businesses in this position stop making changes within a year, and a site nobody updates drifts out of date regardless of how it looks.

This is worth fixing even if nothing else is wrong.

What you sell has changed and the site has not

You have dropped a service, added one, or moved upmarket — and the site still describes the business you were two years ago. This is more damaging than dated design, because visitors are evaluating the wrong company.

It is also often fixable without a rebuild. Rewriting what the site says is a fraction of the cost of rebuilding how it looks.

It is slow on a phone

Not "a bit slow". If it takes more than about three seconds on mobile data, a meaningful share of people leave before seeing anything. They do not report this. They are just never counted.

Slowness sometimes needs a rebuild and often does not — oversized images and too many tracking scripts cause most of it, and both are cheap to fix. Get it measured before assuming.

Enquiries arrive from the wrong people

If most enquiries are for work you do not want, at budgets you cannot serve, the site is doing its job for the wrong audience. That is a positioning problem showing up as a traffic problem, and no redesign fixes it. The words have to change first.

A site that brings the wrong people efficiently is working correctly. It has just been aimed badly.

Nobody can tell what you do in ten seconds

Open it on a phone and hand it to someone outside your industry. Ask them, after ten seconds, what you sell and what they would do to hire you.

If they hesitate on either, that is the problem — and it is a rewrite, not a redesign.

Search brings nothing

If the site produces no search traffic after a year, something structural is wrong: pages that cannot be crawled, no page for anything anyone searches, or one page trying to cover five services. One honest page per thing you sell is the fix, and it is content work rather than design work.

It is embarrassing to send

Worth naming, because it is the most common unstated reason. If you avoid sending your own website to a prospect, that costs you every week. It is a legitimate reason to rebuild, as long as you are honest that it is the reason — and as long as you fix what it says at the same time, not only how it looks.

Check before you decide

Most of the signals above can be tested in an afternoon, for free, before anyone quotes you for anything.

Run the home page and your most important service page through Google's PageSpeed Insights, on the mobile tab. Open Search Console and look at which searches the site appears for, and whether any of them are things you actually sell. Then read the last ten enquiries you received and note who they came from and what they asked for.

Those three checks cover speed, search and audience. If all three look fine, the problem is almost certainly not the site, and a rebuild would spend money on the wrong thing.

When the answer is to change nothing

If you can edit the site yourself, it says what you sell today, it loads in a few seconds on a phone and people who find it get in touch, you do not have a problem to solve. Everything on the list above is absent. What is left is a wish for something newer, and that is not worth a project.

We would rather tell you that now than quote for a rebuild you did not need. A useful check before talking to anyone: write down which signal above you actually have, in one line. If you cannot name one, you are probably shopping for a feeling.

If you do rebuild, protect what already works

A rebuild can lose more than it gains, and the loss is quiet. Before anyone designs anything, list the pages that bring visitors today. Search Console shows them in a minute.

Keep those addresses the same. Where a page has to move, the old address needs a permanent redirect to the new one, one by one, not a blanket redirect to the homepage. Keep the text that ranks, even when the layout around it changes. And check that the new site still tells Google it may be indexed, because staging sites are often built with that switched off and launched that way.

A new site that drops the pages people were finding is slower to recover than one that was never rebuilt. Ask whoever quotes how they handle this. If the answer is vague, that is information about the rest of the work too.

What is not a reason

A competitor redesigned. You do not know whether it worked. Most redesigns are not measured.

The design is a few years old. Restraint ages well. Trends age badly. A plain site from 2021 that says the right thing outperforms a fashionable one from last year that does not.

Someone said it should be modern. Ask what they mean, and whether it costs you anything.

How to spend well

Three of the signals above are content problems and one is a technical problem. Only "you cannot change it yourself" is reliably a rebuild.

So: work out which one you actually have before agreeing to a project. A website analyzer will settle the technical half in a minute — what the site runs on, whether it is secure and whether it works on a phone — and if that comes back clean, the problem is the content, not the build. The budget usually goes further than expected once the real problem is named.

  • websites
  • growth
  • rebuilds

Written by

Abhishek Chaubey builds the websites, software and automation Scaleqode delivers, and made ScalePDF, Scaleqode's free PDF editor.

Read next

More on the same problems.

All insights

Start with the problem, not the service.

The first conversation is about understanding what isn’t working. Sometimes the answer is smaller than expected, and occasionally it isn’t software at all.