Antonov/Journal/Web design
Security · Small business

Website hacked? What a small business should do first

A calm, step-by-step plan for the first hour after a hack, the clean-up, Google's review and the repair-or-rebuild decision.

20 Nov 20267 min readBy Gabriel Antonov#Website security#WordPress
Cracked glass browser window with a warning sign and a glowing shield sealing the crack

Your site suddenly redirects visitors to a casino, Google shows a warning next to your name, or a customer calls to say your contact page is full of strange links. A hacked website feels like a break-in, and the first instinct is to panic, delete everything or pay the first person who promises a quick fix. In this guide I walk you through what I actually do when a small business sends me a hacked site: the first hour, the clean-up, getting Google to trust you again, and the honest question of whether to repair the old site or replace it.

How to tell your website has been hacked

Hacks on small business sites are rarely dramatic. Most attackers do not want to deface your homepage; they want to quietly use your domain's reputation. That is why the signs are often subtle. Google groups hacked content into three main types in its Search Console help: code injection (hidden scripts, for example redirects to other sites), content injection (spammy text or links added to your existing pages) and URL injection (brand-new spam pages created on your domain).

If two or more of these sound familiar, treat it as a hack until proven otherwise.

Why small business sites get hacked

Nobody picked your bakery or law office personally. Almost all attacks are automated bots scanning millions of sites for one known weakness. On WordPress, that weakness is usually an outdated plugin. According to Patchstack's State of WordPress Security in 2026 report, researchers recorded 11,334 new vulnerabilities in the WordPress ecosystem in 2025, and 91% of them were in plugins, not in WordPress itself.

0new WordPress-ecosystem vulnerabilities found in 2025 (Patchstack)
0of them were in plugins; core WordPress had only 6
0had no fix from the developer when they were made public
0weighted median time to first exploit for heavily exploited flaws

That last number is the uncomfortable one: for the vulnerabilities attackers love most, the first exploitation attempts start within hours, not weeks. A site that was "finished" three years ago and never updated is not neglected in theory; it is an open door in practice. Weak or reused passwords, abandoned themes, "nulled" (pirated) premium plugins and old PHP versions on cheap hosting make the door wider.

The first hour: what to do right away

Do these in order. They limit the damage without destroying the evidence you will need for a proper clean-up.

  1. Don't delete the site or reinstall blindly. You lose the trail that shows how they got in, and the same hole stays open on the new install.
  2. Take a full backup of the infected state (files and database) and label it clearly. It is your evidence and your safety net.
  3. Change every password: hosting/cPanel, FTP/SFTP, database, WordPress admin users, and the email account connected to the site. Use a password manager and make each one unique.
  4. Turn on two-factor authentication wherever it exists, starting with the hosting account and the domain registrar.
  5. Tell your hosting company. Many hosts can show access logs, scan the account and tell you if other sites on it are affected.
  6. Put up a maintenance page if the site is actively redirecting visitors or serving malware. Losing a day of traffic is better than infecting customers.
  7. Open Google Search Console (verify the site if you never did) and check the Security issues report.
Personal data on the site?If your site stores customer data, such as orders, bookings or form submissions, a hack may be a personal data breach. Under Article 33 of the GDPR, the controller has to notify the data protection authority (in Bulgaria, the Commission for Personal Data Protection) within 72 hours of becoming aware of it, unless the breach is unlikely to put people at risk. The EU has proposed changing this deadline as part of the "Digital Omnibus", but as of November 2026 that proposal is still in the legislative process, so 72 hours is what applies. If in doubt, ask a lawyer the same day.
Glass website layers with dark malicious fragments being lifted out into a quarantine cube
A real clean-up removes every injected file, user and database entry, not just the visible symptom.

Cleaning the site properly

A "quick fix" that only removes the visible spam usually comes back within days, because attackers leave backdoors: small hidden files that let them walk back in. A proper clean-up looks like this:

01

Find the entry point

Check access logs, recently modified files and the plugin list for known vulnerable versions. Fixing the symptom without closing the hole is wasted money.

02

Replace, don't patch

Reinstall WordPress core, themes and plugins from official sources rather than editing infected files. Delete anything you don't use, and every pirated plugin.

03

Clean the database

Spam links and redirects often live in posts, options and widgets. Remove unknown admin users and look for injected scripts.

04

Hunt the backdoors

Scan uploads folders for PHP files that shouldn't be there, check .htaccess and cron jobs, and compare files against clean copies.

05

Harden

Update PHP, set correct file permissions, limit login attempts, enable 2FA and set up automatic, off-site backups.

06

Check from outside

Test the site on a phone and in a private window, from search results, and fetch the pages the way Google does.

Getting Google to trust your site again

Once every affected page is clean, you ask Google to check again. In Search Console, open Security issues, click Request a review and describe exactly what you fixed: what was wrong, how you cleaned it and how you closed the hole. Google's own documentation is clear that half a job does not count: fixing only some pages will not earn you a partial return to search results.

How long it takes depends on the type of problem. Google's guide to requesting a review says phishing reviews take about a day, malware reviews a few days, and sites hacked with spam can need up to several weeks. If the site is found clean, browser and search warnings are removed within 72 hours. Don't send the request again while you wait; that can slow things down. Meanwhile, remove spam URLs that were created on your domain (they should return a 404 or 410), resubmit your sitemap and watch the Pages report as the junk drops out of the index.

The goal isn't to make the warning disappear. It's to make sure there's nothing left for Google to warn about.— the rule I follow on every clean-up

Fix the old site or build a new one?

This is the question clients ask me most, and the honest answer is: it depends on what the hack revealed about the site.

Rebuild makes more sense when…

The site runs on a theme or page builder that is no longer supported, relies on pirated plugins, can't be updated without breaking, was hacked more than once, or already looked dated and wasn't bringing enquiries. You'd be paying to rescue something you were going to replace anyway.

Repair makes more sense when…

The site is relatively recent, the design still works for your business, the hole is clear (one outdated plugin, a weak password) and it can be fully updated after the clean-up. A one-off repair plus a care plan is usually the cheaper route.

A clean-up is a small job, but its price depends on how deep the infection goes, so I quote it after looking at the site. If the conclusion is a rebuild, my website design projects start from €890, go live in 2–5 weeks and include three months of free care, which covers exactly the updates and backups that prevent the next hack.

Glass dashboard with checked plugin tiles, a padlock and a backup loop
Prevention is boring on purpose: updates, backups, unique passwords and fewer plugins.

How to stop it happening again

Most hacks I see could have been prevented with routine work that costs far less than a clean-up. Here is the checklist you can go through today:

Not sure whether your site is at risk?

If you can't tell whether your site is up to date, or you've spotted one of the warning signs above, start with something simple: run the free website check. It takes a minute and gives you a first picture of your site's health before you decide anything. If the site turns out to be compromised or simply too old to keep safe, I'm happy to look at it and tell you honestly whether a repair or a new website is the better investment. Working with a designer in Bulgaria? Here's more on how I work with small businesses across the EU.

Work with me

Want a website that actually brings clients?

Custom design, built fast, SEO-ready from day one. Fixed prices, EU-wide, remote.

Start a project →See the workReply within 24 hours
Keep reading

More from the Journal

All articles