Common problem

Your website feels outdated

Here is the honest version. Outdated normally means looks dated, and looking dated is the least important thing on the list. The risks that actually cost you are unsupported software, no HTTPS, unusable on phones, and nobody knowing the login.

Separate two questions that always get asked as one: what is broken, and what looks dated. Broken means unsupported software with known holes, no HTTPS, a layout unusable on a phone, wrong information on the page, or nobody holding the login. Dated means you have seen newer sites.

Fix broken. Think carefully about dated. A plain, plain looking site that loads fast, works on a phone, and tells the truth about your business will out-earn a beautiful rebuild that nobody has a reason to visit.

And genuinely: sometimes the answer is leave it alone. If it is safe, usable and accurate, an old site that brings in work is not a problem waiting to happen. It is an asset you have already paid for.

What actually matters, ranked

In order of how much each one costs you if it is true. Notice how far down appearance sits.

1. Nobody knows who controls it

Top of the list and rarely the reason anyone calls. If you cannot log in to the domain registrar, the host, or the content management system, you do not own your site in any practical sense. Domains lapse and get bought by someone else. Hosts suspend accounts on unpaid cards nobody has seen in years. Sort this out before you discuss colours.

2. Unsupported software with known holes

An old content management system, an abandoned theme, plugins whose authors stopped shipping updates. Once a vulnerability is public and no patch is coming, the hole stays open permanently. Automated scanners find these without anyone targeting you specifically. This is a real, ongoing liability rather than an aesthetic one.

3. No HTTPS

If your address bar says Not Secure, every visitor sees that warning before they see your business. Certificates are not exotic or expensive any more, and there is no good reason to be without one. What that warning actually means is covered under website security problems.

4. Unusable on a phone

Most people looking for a local business are on a phone. If they have to pinch and zoom to read your hours, or your menu is a PDF, or the tap targets are too small to hit, you are losing the enquiry regardless of how the desktop version looks. This is the single most common genuine fault on an old site.

5. The information on it is wrong

Old prices, a phone number nobody answers, a member of staff who left years ago, hours from before you changed them. This is the cheapest thing on the whole list to fix and it does direct damage every day it stays up.

6. Nobody can update it without a developer

If changing your hours means emailing someone and waiting three days, the site will drift out of date permanently, because that friction always wins. That is a structural problem, and it is what maintenance or a better editing setup is for.

7. It is slow

Old sites accumulate weight. Worth measuring rather than assuming: see slow business website before concluding that age is the cause.

8. It looks dated

Last, deliberately. It does affect whether people trust you, and that is real. It is just not the emergency it gets sold as, and it is frequently the only item on the list that anyone mentions.

One related detail worth checking while you are here, because older sites predate it entirely: paste your homepage into a message and see what appears. If it shares as a blank grey box, the page is missing its preview tags. That is a small fix with a visible payoff every time someone recommends you: see missing link preview image.

How to check your own site honestly

  1. Open it on your phone as a stranger would

    Private window, no shortcuts. Can you find the phone number, the hours and what you sell in under ten seconds without zooming? That is the test most old sites fail.

  2. Look at the address bar

    Padlock or Not Secure. If it says Not Secure, that is the first fix and it is not a big job.

  3. Read every word on the site out loud

    Slowly. You will find a member of staff who left, hours that changed, a service you stopped offering. Owners almost never do this and it always turns something up.

  4. Work out what it is built on

    A content management system, a website builder, or plain HTML files? Then find out whether the version and plugins are still supported. Plain HTML that has not changed in years is far safer than a stale content management system.

  5. Establish who holds the keys

    The domain registrar, the hosting account, the content management system, the DNS. Write down who has each. If any answer is a person nobody has spoken to in three years, that is your first project.

  6. Check whether it is actually working

    Look at Search Console and your analytics. A site that brings in enquiries every week is doing its job, whatever you think of the header.

  7. Only now, ask how it looks

    With the real risks separated out, decide whether appearance is a problem you want to spend on. It is a legitimate reason. It is just a choice, not an emergency.

Refresh or rebuild

Both are legitimate. The mistake is buying the expensive one because the cheap one was never offered.

A refresh is usually enough when

  • The structure and pages basically work
  • It is on supported, updatable software
  • It is on HTTPS and nothing is broken
  • The mobile layout is fixable rather than absent
  • The problem is photos, copy, colour and type
  • You still control the accounts and can edit it

A rebuild is warranted when

  • It runs on software that is no longer supported
  • There is no mobile layout worth saving
  • It has been hacked, or is patched together beyond repair
  • Nobody can change anything without breaking something
  • The business it describes no longer exists
  • Every small change costs more than it should

When the answer is leave it alone

  • It loads fast and works on a phone. Plain and functional beats fashionable and slow, every time, for a business that needs the phone to ring.
  • It is on HTTPS with nothing unsupported running. No open holes means no urgency, whatever the design year.
  • Everything on it is true. Accurate hours, a phone number that gets answered, services you actually offer. That is most of what visitors came for.
  • It brings in enquiries. If the numbers say it works, redesigning it is a risk, not an upgrade. Rebuilds lose rankings and conversions surprisingly often.
  • You control the accounts and can edit the content. Ownership and editability are worth more than a modern header.
  • The money would do more elsewhere. If the site works and nobody finds it, a rebuild does not fix that. Read not showing on Google first.

When to bring in help

The checks above are yours to make and they cost nothing. Bring someone in when:

  • You cannot work out what the site runs on, or whether it is still supported. That is IT consulting more than design.
  • The logins are lost and you need control of the domain and hosting recovered before anything else happens.
  • You have decided to rebuild and want the rankings and content you already earned carried across. See website redesign.
  • A refresh is the right call and you want it done without touching the structure that already works. That is web design at a smaller scale.
  • The pattern is that it goes stale every year. The fix is maintenance, not another rebuild.

Who this is for

  • Owners who suspect the site is a liability but cannot say why
  • Businesses on software nobody has updated in years
  • Anyone who has been quoted for a full rebuild and wants a second opinion on whether it is necessary
  • Sites nobody can edit because the person who built it is long gone

When this is not the right fit

  • Anyone who wants a rebuild because a competitor has one. That is not a reason, and we will say so before taking the work.
  • Sites that are safe, fast, accurate and bringing in work. Leave it alone. Spend the money on being found.
  • Businesses whose real problem is that nobody visits. A newer site does not create demand by itself.

What SolvenceHQ can help with

We start by separating what is broken from what is dated, because those need different answers and get sold as one thing. If your site is fine and only looks old, we will tell you that even though it is the smaller job.

  • An honest verdict: refresh, rebuild, or leave it alone
  • Work out what the site runs on and whether it is still supported
  • Recover control of the domain, hosting and content management accounts
  • HTTPS, security and mobile usability fixed without a rebuild where possible
  • Redesign that keeps the URLs, content and rankings you already have
  • Ongoing maintenance so it never gets this far again

Common questions

How do I know if my site is actually outdated or just not to my taste?

Separate the two questions deliberately, because they get answered together and should not be. Ask what is broken: is it usable on a phone, is it on HTTPS, is the software still supported, does anyone have the login, is the information on it true? Then ask what looks dated. Broken is urgent. Dated is a judgement call, and owners are much harsher on their own site than customers are.

If everything in the first list is fine and only the second bothers you, you have a design preference, not a problem. That is still a legitimate reason to spend money, but it should be an informed choice rather than a scare.

Should I refresh or rebuild?

Refresh when the structure works and the surface is tired: new photos, better copy, updated colours and type, fixed mobile layout. Rebuild when the foundation is the problem: unsupported software, no mobile layout worth saving, or nobody can safely change anything. Rebuilding a site whose only real fault is dated photography is an expensive way to solve a cheap problem.

If you do rebuild, protect what you already earned. That is the whole point of a redesign done properly rather than starting from nothing.

Will a rebuild hurt my Google rankings?

It can, and this is where rebuilds go wrong most often. Change every URL with no redirects and you throw away whatever the old site had earned. The mitigation is not complicated: map the old URLs to the new ones, redirect them permanently, keep the content that was working, and watch Search Console closely for weeks afterwards. It just has to be planned before launch rather than discovered after.

Is an old site a security risk?

It depends entirely on what it is made of. A plain HTML site from years ago has almost no attack surface and can sit there indefinitely. An old content management system with unsupported plugins and no updates is a genuine liability, because known holes stay open. The age of the design tells you nothing; what runs underneath tells you everything. See website security problems to work out which one you have.

Nobody knows who has our website login. Is that a problem?

Yes, and it is more urgent than how the site looks. If you cannot get into the host, the domain registrar, or the content management system, you do not control your own site. Domains expire, hosts lapse, and previous developers move on. Establishing who holds what, and getting it back into your name, is the first job on that site, before any design conversation.

Get a Quote

Refresh, rebuild, or leave it alone?

Send us the URL and we will give you a straight answer on which one you need, including when the answer is that the site is fine.