Skip to content

Your website got hacked. Here’s what that actually costs a small business.

The reason small businesses don’t take website security seriously is that the threat is
usually described badly. “Hackers could target your site” invites the obvious response:
why would anyone bother with me?

It’s a fair question with a boring answer. Nobody picked you. Nothing about this is
personal.

Almost every small business compromise is automated. Scripts crawl the web looking for a
specific outdated plugin version, find thousands of sites running it, and exploit all of them.
Your site wasn’t selected; it matched a pattern. That’s actually worse news than being
targeted, because it means obscurity isn’t protection. A twelve-page site for a landscaping
company in Mobile is exactly as findable by a script as a national retailer, and considerably
less likely to be patched.

So rather than talk about threats, let’s talk about the bill. Here’s what a compromise
actually costs a small business, in the order you encounter the costs.

1. Finding out — usually not from yourself

Most owners don’t discover a hack by noticing something wrong. The site looks completely
normal. Injected code is written to be invisible to the logged-in owner and visible to search
engines and new visitors.

You find out when a customer calls to say their browser is warning them about your site.
Or your email to a client bounces because your domain got flagged. Or you search for your own
business and find your listing marked “This site may be hacked.”

That first cost is reputational and it lands before you’ve had a chance to do anything.
Someone who sees a red warning screen with your business name on it doesn’t call to ask about
it. They go to the next result.

2. The cleanup

This is the part people assume is the whole cost, and it’s genuinely the smaller half.

Cleaning a compromised WordPress site properly means finding every injected file — not just
the obvious ones — checking core files against known-good versions, removing backdoors
(there’s rarely only one), finding unauthorised admin accounts, checking scheduled tasks for
anything that reinstalls the payload, and rotating every credential: admin passwords, database
password, hosting, FTP, API keys.

Then you have to work out how they got in, because if you don’t, you’ll be doing
this again in a fortnight. A thorough cleanup is a day or two of skilled work. A cheap one is
an hour, misses the backdoor, and reinfects.

If you have a known-clean backup from before the compromise, this gets dramatically easier
and cheaper. If you don’t, or you have one but can’t say when the compromise started, you’re
rebuilding.

3. Downtime

Sometimes the site has to come down. Sometimes the host takes it down for you, which is
their right and often the correct call if your server is sending spam.

The cost here depends entirely on what your site does. For a brochure site, a day offline
is an embarrassment. For a business where the website is how people book, order or enquire,
every hour is lost revenue you can estimate fairly precisely — and unlike most of this list,
it’s a number you can calculate in advance. Take your monthly revenue that originates online,
divide by thirty. That’s what a day costs. It’s usually enough to make the rest of this
article feel less abstract.

4. Search damage, which is the slow one

This is the cost that outlasts everything else and gets mentioned least.

When a site is flagged as compromised, it can be removed from search results or
de-prioritised. Getting back in isn’t automatic — you clean the site, then request a review,
then wait. Days, sometimes longer.

Meanwhile the hack itself has usually done search-specific damage. Injected spam pages get
indexed under your domain. Your pages get rewritten with links to somewhere else. If this
went undetected for weeks, there are now hundreds of junk URLs attached to your site that
have to be cleaned up and de-indexed individually.

Rankings you spent years earning can take months to recover. For some businesses this is
by far the largest line on the bill, and it arrives long after everyone’s stopped thinking
about the incident.

5. Email deliverability

A common use for a compromised site is sending spam. Your domain sends thousands of
messages, gets reported, and lands on blocklists.

The consequence: your ordinary business email stops arriving. Quotes, invoices, replies to
customers — filtered as spam, by recipients who never see them and never tell you. Getting
off blocklists means delisting requests to multiple providers, each on their own schedule,
some of which will take weeks.

This one is particularly nasty because it’s invisible from your side. Your email looks
sent. It just isn’t read.

6. Data exposure, if you hold any

If your site collects customer information — accounts, orders, form submissions, anything
with names and contact details — a compromise is potentially a data breach, with notification
obligations attached.

If you take payments, this gets considerably more serious. Card data is the single most
valuable thing on most small business sites, which is why e-commerce sites get more attention
from attackers and need more care.

Most small sites don’t reach this tier. The ones that do should know they have, because the
calculus changes completely.

7. The part nobody budgets for

Your time, and the week you spend on this instead of your actual business.

Owners handling a compromise describe the same experience: three or four days where nothing
else gets done, a lot of calls, a lot of waiting, and a persistent background anxiety about
whether it’s really gone. That week has a cost that never appears on any invoice.

What actually prevents almost all of this

The genuinely annoying thing about this entire article is how mundane the prevention is.
The overwhelming majority of small business compromises exploit a vulnerability that was
patched before the attack happened.

  • Apply updates promptly. Core, theme, plugins. Most exploits target
    known, already-fixed holes. This single habit prevents more incidents than everything
    else combined.
  • Remove what you’re not using. A deactivated plugin still sits on your
    server and can still be exploitable. Delete it.
  • Strong, unique admin passwords and two-factor authentication. Brute
    force attempts against /wp-login.php are constant and automated.
  • Least privilege. Not everyone who edits a page needs an administrator
    account.
  • Tested backups, retained for a reasonable window. Long enough to get
    behind a compromise you didn’t spot for three weeks.
  • A web application firewall and malware scanning. Blocks the automated
    traffic before it reaches your application.
  • Monitoring that alerts a human. Hours of exposure instead of weeks is
    most of the difference in cost.

None of that is clever. All of it is a standing commitment, which is the actual reason it
doesn’t happen.

Where hosting comes into it

This is why we treat hosting and
maintenance as one job rather than
two products. Firewall and scanning at the server level, automated backups we’ve actually
restored, a staging environment so updates get tested before they go live, and someone
watching who will notice.

Cheap hosting isn’t cheap because it’s efficient. It’s cheap because the security,
monitoring and backup work is your problem, and you find that out at the worst possible
time.

If you’re not certain what’s protecting your site right now — who patches it, where the
backups are, whether anyone would know within a day — that uncertainty is itself the answer
worth acting on.

Ask us to review your setup →

Newsletter

Signup our newsletter to get updated information, and insight about the technology

Latest article

Get Started

Name(Required)
Interested in:(Required)