Old website, new problems: what's quietly gone out of date
· 5 min read
Most small business websites get built once, launched with a bit of excitement, and then left alone. A few photos get swapped, the phone number changes, maybe a new service gets added. Otherwise it just sits there, doing its job.
The trouble is, the world around it doesn’t sit still. The software underneath it gets old. The rules about cookies and personal data change. Expectations about what a business website should show move on. None of this is visible when you look at your homepage, which is exactly why it gets missed.
This is the first of five posts on what changes between an old website and a new one, and which of those changes can turn into legal or data protection problems. It’s written for business owners, not developers, and there’s a short checklist at the end.
What we mean by “old”
Age isn’t really about the launch date. A site built last year can be “old” if nobody has touched it since. A site from 2015 can be in good shape if someone has looked after it properly.
In practice, an old website is one where nobody can answer these questions quickly:
- When was the software behind it last updated?
- What cookies does it set, and does it ask first?
- Where do contact form messages go, and where are they kept?
- Are the company details on it still right?
If those questions get a shrug, the site is old, whatever its age.
The five things that drift
1. The software underneath
Most small business sites run on software that needs regular updates: the website platform, its plugins, and the server language underneath. When updates stop, known holes stay open. And once a version is old enough, it stops getting security fixes at all, so when the next serious flaw is found, there’s nothing to install.
This isn’t just a technical problem. If your site holds customer details and someone breaks in through an old plugin, that’s a personal data breach under UK GDPR. You’re expected to have kept your systems reasonably secure, and “nobody updated it” isn’t a defence.
2. Cookies and tracking
The cookie rules changed this year. Some simple analytics no longer needs consent, but advertising and tracking still does, and the maximum fine for getting it wrong went up dramatically. Old sites often have a banner that doesn’t actually block anything, or tracking code left behind from a marketing campaign years ago. That’s part two.
3. Contact forms and personal data
Every enquiry form collects personal data. On older sites, those messages are often stored in the website’s database for years, emailed to someone who left the business, or sent without proper encryption. There’s also a new legal duty from June 2026 to handle data protection complaints properly. That’s part three.
4. The legal small print
Limited companies have to show certain details on their website, and so does any business that trades online. Old sites often show an office you moved out of, a trading name from before you incorporated, or no company details at all. That’s part four.
5. Accessibility
UK businesses have a legal duty not to shut disabled people out of their services, and that includes websites. Older sites were rarely built with this in mind. Low-contrast text, images with no descriptions and forms you can’t use with a keyboard are all common. We cover the basics in part four too.
Why this matters more than it used to
For years, an out-of-date website was mainly an embarrassment. That has changed for three reasons.
Attacks are automated. Nobody has to pick your business. Automated tools scan the whole internet for known weaknesses, and small business sites are the easy ones.
The rules have teeth. Since the Data (Use and Access) Act came in, the maximum fine for breaking the cookie rules is the same as for UK GDPR: up to £17.5 million or 4% of turnover. Realistically, a small business is far more likely to get a warning than a fine. But the direction of travel is clear.
Your customers notice. Browsers warn people about insecure sites. Bigger customers and insurers ask about your security before they sign. A website that’s obviously neglected says something about how you look after everything else.
Old versus new, at a glance
| A typical old site | A well-looked-after site | |
|---|---|---|
| Software | Not updated in months or years | Updated, or built so there’s little to update |
| Cookies | Banner that doesn’t block anything, or none | Only what’s needed, with a clear choice for the rest |
| Contact form | Messages kept on the website for years | Delivered securely, not stored on the site |
| Company details | Out of date or missing | Correct, in the footer |
| Privacy notice | Generic template from launch | Says what you actually do |
| Accessibility | Never checked | Basics covered |
A five-minute check you can do today
You don’t need to be technical for this.
- Look at the address bar. Does your site show a padlock, or a “Not secure” warning?
- Visit your site in a private browser window. Does a cookie banner appear? Is there a clear button to say no?
- Scroll to the footer. Is your full company name, company number and registered office there, and correct?
- Find your privacy notice. Does it mention your contact form and what happens to the messages?
- Ask whoever looks after your site when the software was last updated. Ask for a date, not “recently”.
If any of those made you wince, the next three posts go through each area in more detail, with what to do about it. The last one in the series looks at why all of this matters to your business, and how to decide whether to fix your current site or start again.
And if you’d rather someone just looked for you, that’s what our website security check is for. Get in touch and we’ll tell you plainly what needs doing and what doesn’t.
This series is general information for UK businesses, not legal advice. If you’re unsure how something applies to you, speak to a solicitor or check the ICO’s guidance for small organisations.