“We are too small for anyone to bother with”
It is the most common thing we hear when website security comes up, and the reasoning behind it is perfectly sound. A modest South African business does not store card numbers. The customer list is not large enough to be worth selling to anybody. There is no obvious prize. If theft were the motive, the argument would hold.
It usually is not the motive. And once you understand what is, being small stops working as a defence, because the thing worth taking is something almost every established business already has.
What is actually being taken
An established business website carries an asset that has nothing to do with what you sell: years of accumulated standing with Google. A domain that has existed for a decade or more, publishes genuine content and has never done anything untoward is treated by search engines as trustworthy. That trust took years to build and cannot be bought. It can, however, be borrowed.
There is a substantial industry built on placing links and pages on websites Google already trusts, on behalf of operations Google would never trust on their own. Online gambling and counterfeit pharmacies are the usual customers. A brand-new domain is worthless for the purpose. An established South African business with a clean fifteen-year record is genuinely valuable.
So, the objective is not to steal from you, and it is certainly not to break anything. It is the opposite. The aim is to occupy the property quietly, leave every visible thing exactly as it was, and make use of the reputation attached to the address. Which is precisely why it so often goes unnoticed.
Why nothing looks wrong
Three reassurances come up whenever we raise this. All three sound right. None of them covers the situation.

“Our security scan came back clean.” Very likely true, and the scan was not wrong. Scanners examine what your website shows the public. A hidden file that does nothing whatsoever until the attacker calls it directly, with the correct instruction, shows the public nothing at all. It simply sits there.

“We have a security plugin.” Worth having, and we recommend them. But a plugin lives inside your website software. A request that goes straight to a file and never loads your website software is not something it is able to see.

“We would notice.” Not necessarily. File dates can be falsified, so any review that sorts by “recently modified” never surfaces them. Copies get left in separate folders so that a partial clean-up always misses one.
The first real sign is rarely a broken website. It is a fall in Google rankings, because Google usually works out what has happened before anybody else does. By then the visibility has been going for a while.
The gap between “fix available” and “too late” is now days
Every so often a flaw is found in WordPress itself, rather than in a plugin or a password. In July this year one such flaw was published together with its fix, and sites that had not yet applied the fix were being attacked over the following weekend. Not months afterwards. Days.
This changes what “we keep everything updated” has to mean in practice. Automatic updates genuinely help and should be switched on. But they typically run when your website next receives traffic, and a quiet weekend can cost you a day. When the exploitation window is forty-eight hours, a day is the whole story.
The implication is unwelcome but straightforward. Somebody has to be watching for security releases, rather than trusting that the machinery will handle it.
What actually helps
None of this needs a large budget. It needs a handful of ordinary things to be true at the same time.
A firewall in front of the website, not only inside it. Anything that runs as part of your website can only see requests that reach your website in the normal way. An external service sees every request to your domain, whichever file it is aimed at.
Someone accountable for applying security updates within days, and a way of knowing if the site has fallen behind. This is the single highest-value item on the list.
Two-factor authentication on every administrator account, without exception. Passwords alone stopped being sufficient some time ago.
Occasional inspection of the actual files on the server, not only automated scans from outside. This is how the things scanners cannot see get found.
Backups stored somewhere other than the website itself. A backup sitting in a folder on the same server is a copy of everything you own, one guessed address away.
Knowing how long your hosting company keeps server logs. When something does go wrong, those logs are how you establish what happened. They are also usually deleted within weeks, so the question is better asked now than later.
The part that is easy to miss
The reason any of this deserves an hour of your attention is not that an attack is likely this month. For most businesses it is not.
It is that the damage, when it does arrive, lands somewhere nobody is watching. Nothing breaks. No customer complains. There is no ransom note and no dramatic moment. Your search visibility quietly declines, and by the time somebody connects the two things, the traffic has been gone for weeks and recovering it takes months rather than days.
A business that has spent years earning its position in search results has more to lose here than it tends to realise, and the loss does not announce itself.
Most of the list above is an afternoon of work. If you would rather have a second pair of eyes on where your website currently stands, our team is happy to take a look and tell you honestly what we find.
About the author
Robert Haupt is the co-founder of Cape Business Online and has more than 20 years’ experience helping businesses generate measurable growth through SEO, Google Ads, Meta advertising and strategic digital marketing. His focus is on ensuring that every marketing decision is supported by meaningful data rather than guesswork.
Connect with him through LinkedIn


