Skip to content

WordPress Security for Tradies: 8 Steps

A hacked site costs you calls. Each step says what it does, what good looks like and where tradies go wrong.

If you buy through an affiliate link on this page, I may earn a commission at no extra cost to you.

The short version

  • Why sites get hacked: 91% of the WordPress holes found in 2025 were in plugins.
  • Use secure hosting: a firewall in front, malware scans and HTTPS everywhere. See step 1
  • Lock down every login: a long passphrase and a second step for every admin. See step 2
  • Limit who can do what: as few admins as you can, and no shared logins. See step 3
  • Keep it all up to date: WordPress, plugins, theme and PHP, every month. See step 4
  • Cover the update gap: shield a known hole until its fix arrives. See step 5
  • Keep backups that work: daily, a copy elsewhere, and one before updates. See step 6
  • Watch for trouble: uptime, malware scans, new holes and expiry dates. See step 7
  • Harden with care: some old tips help little, and some break sites. See step 8
  • Already hacked? What to do first. See what to do
  • Do it yourself: steps 2 and 3, and picking a good host, take little more than your time.
  • Hire me for the rest: Website Care, with hosting, from $120 a month + GST. How it works

Why sites get hacked

As I see it, most hacked sites come down to a weak spot in a plugin or theme, or an admin login someone got into. Fix both and you've dealt with most of the risk.

A weak spot like that is called a vulnerability, or a hole. Patchstack, a WordPress security company, counted 11,334 new ones in 2025, 42% more than the year before. Of those, 91% were in plugins and 9% in themes.

So after the host, which stops a lot of attacks before they reach your site, the steps start with the logins, then spend most of their time on keeping plugins patched and on getting you back if it goes wrong anyway.

Where 2025's holes were

  • Plugins91% of new vulnerabilities
  • Themes9% of new vulnerabilities
  • WordPress itselfJust 6, all low priority
Patchstack's count of new WordPress holes in 2025, from State of WordPress Security in 2026.

The eight steps

Steps 1 to 3 keep people out, 4 and 5 close the holes, 6 and 7 catch what slips through, and 8 deals with what's left.

  1. Use secure hostingStops attacks before they reach you
  2. Lock down every loginKeeps people out of the dashboard
  3. Limit who can do whatLimits what one stolen login can do
  4. Keep it all up to dateCloses the known holes
  5. Cover the update gapShields a hole until its fix arrives
  6. Keep backups that workGets you back if it goes wrong
  7. Watch for troubleTells you first, not a customer
  8. Harden with careCloses the rest without breaking it

Step 1: Use secure hosting

What it does: stops a lot of attacks before they reach your site. A good host puts a firewall in front, scans for malware and gives the site a free certificate, so every page loads on HTTPS, the secure version of a web address. HTTPS runs on SSL, now usually called TLS: it scrambles what passes between the browser and your site so nobody else can read it, and the certificate is the file that proves the site is who it says it is.

Four layers of protection

  1. 1Cloudflare's firewallStops known kinds of attack before they reach the server.
  2. 2The serverRocket.net's own firewall, malware scanning and daily backups.
  3. 3WordPressPatchstack checks the plugins every 6 hours and shields holes it knows about.
  4. 4A copy elsewhereA second daily backup, off the host, made with WP Umbrella, a maintenance service.
How the WordPress sites I host are set up, as of November 2026.

What good looks like

  • A firewall in front of the site that blocks known attacks.
  • Malware scanning on the server, running in the background.
  • A free SSL certificate, so every page loads on HTTPS.
  • Daily backups by the host.
  • Two-step login for the hosting account, not just the site.
  • Your designer moves files securely (SFTP or SSH), never plain FTP.

Where people go wrong

  • Paying extra for an SSL certificate. A good host includes one.
  • Skipping a firewall to save money. Cloudflare's free plan has one.
  • Cheap shared hosting that leaves the security to you.
  • A hosting login with a weak password and no second step.

The four layers above are how I set up the WordPress sites I host, Barnes Family Roof Plumbing's and Ascent Garage Doors' among them: Rocket.net runs one firewall before traffic reaches the server and a second on it, and Patchstack checks their plugins for new holes every 6 hours.

Step 2: Lock down every login

What it does: keeps people out of the one place they can change anything. As I see it, a guessed or stolen admin password is one of the two most common ways someone gets in, and the fixes cost little more than time.

The old adviceToday's advice
Capitals, numbers and symbolsNo forced mix of characters
No real words at allRandom, unrelated words
Eight characters, no second stepAt least 15 characters
Change it every few monthsChange it only if it may be stolen
One strong password for everythingA different one for every account
A code by text messageA passkey or authenticator app
Rows 1 and 4 are from NIST, the US National Institute of Standards and Technology, and the rest from the Australian Cyber Security Centre, November 2026.

What good looks like

  • A passphrase of at least 15 characters for every login.
  • Random words that have nothing to do with each other.
  • A different password for every account you have.
  • A password manager to remember them all for you.
  • A second step for every admin, or a passkey instead.
  • Any username but "admin", as WordPress itself advises.
  • Login attempts limited before they reach WordPress.
  • The same care on your hosting and domain name logins.

Where people go wrong

  • Forcing a mix of capitals, numbers and symbols.
  • Changing passwords every few months for no reason.
  • Codes by text message, the least secure second step.
  • Reusing a password, so one leak opens every door.

WordPress doesn't come with a second login step, so it's added with a plugin or through your host. An authenticator app makes a new one-time code on your phone, and a passkey logs you in without a password at all, which the Australian Cyber Security Centre calls a more secure way to log in. For people guessing at your password, WordPress's own advice is to limit login attempts before they reach your site.

Step 3: Limit who can do what

What it does: limits the damage if any one login is stolen. Every administrator holds a full set of keys to your site, so the fewer admins you have, the fewer ways in there are.

WordPress's five roles

Administrator
Everything on the site
Editor
Publishes and manages everyone's posts
Author
Publishes and manages their own posts
Contributor
Writes posts, but can't publish them
Subscriber
Can only manage their profile

Smith Plumbing's logins

  • The ownerThe one admin who runs the siteAdministratorRight
  • Office managerUpdates job and news pagesEditorRight
  • Web designerTheir own login, removed after the jobAdministratorRight
  • Old apprenticeLeft last year, login still activeAdministratorWrong
The roles as WordPress describes them. Smith Plumbing is a made-up example.

What good looks like

  • As few administrators as the site can get by with.
  • Everyone else on the lowest role that does their job.
  • A login of their own for everyone, never a shared one.
  • Access that runs out for anyone doing a one-off job.
  • Old logins deleted when the people using them move on.
  • "Anyone can register" left off unless the site needs it.

Where people go wrong

  • Sending your admin password to someone by email or text.
  • Making everyone an administrator because it's quicker.
  • A login that's still active for a past worker or designer.
  • Open sign-ups on a site that doesn't need them.

The Australian Cyber Security Centre warns that anything staff do with your login is likely to be put down to you, and says never to share passwords, even with staff. That's one more reason everyone gets their own login.

Step 4: Keep it all up to date

What it does: closes the holes that are already known. Updates to WordPress, plugins and themes often carry security fixes, and only the newest WordPress is officially supported. PHP, the code WordPress runs on, needs updating too: each version stops getting security fixes on a set date.

How long each PHP version gets fixes

  • PHP 8.5Fixes to 31 Dec 2029
  • PHP 8.4Fixes to 31 Dec 2028
  • PHP 8.3Fixes to 31 Dec 2027
  • PHP 8.2Fixes to 31 Dec 2026
  • PHP 8.1No fixes since 31 Dec 2025
Security fixes for PHP, the code WordPress runs on, from php.net, 14 November 2026. The line marks today.

What good looks like

  • Updates on a schedule, not when you remember.
  • A backup taken right before every update you make.
  • The site and its forms checked after each update.
  • PHP, the code WordPress runs on, still getting fixes.
  • PHP 8.3 or newer, the version WordPress itself recommends.
  • Plugins and themes their makers are still updating.
  • Paid licences kept current, so updates keep coming.
  • Plugins you no longer use deleted, not just turned off.

Where people go wrong

  • Switching off WordPress's own security updates.
  • Updating the live site with no backup taken first.
  • A lapsed licence, so a plugin quietly stops updating.
  • A plugin nobody has updated in years, still running.

I've seen some sites go five years or more without a theme or plugin update, mostly because a licence ran out and the updates stopped coming. Some of them were hacked so badly they had to be rebuilt from the ground up.

Step 5: Cover the update gap

What it does: protects a plugin's known hole until the fix arrives, or until your next update. Attackers move fast once a hole goes public, and many holes have no fix at that point yet.

  1. Day 0Holes go public, and 46% of them had no fix at that point.
  2. 5 hoursTypical time to the first attack on the most targeted holes.
  3. 24 hoursAbout half of the high-impact holes have been attacked.
  4. Up to a monthThe next update, if you only update your site once a month.
Patchstack's figures for 2025, from its 2026 report. The monthly update is an illustration.

Free security plugins can lag: Wordfence's free plugin gets new firewall rules 30 days after the paid one. Your other plugins and themes need watching too, even the ones you paid for: in 2025, 76% of the holes reported to Patchstack in paid plugins and themes could be used in real-world attacks on websites.

What good looks like

  • Your plugins checked against new holes every few hours.
  • A virtual patch: a firewall rule for one known hole.
  • A critical hole patched within days, not in a month.
  • The real update made once it's out, with a backup first.

Where people go wrong

  • Waiting for the monthly update when a hole goes public.
  • A free plugin whose new firewall rules arrive late.
  • Thinking a paid plugin is safe just because you paid.
  • Finding out about a hole only when you next log in.

Step 6: Keep backups that work

What it does: gets you back to a working site if an update breaks it or someone gets in. Without a backup, you'd have to fix everything by hand, and that's often a nightmare.

  1. 1Every dayThe host's backupMade automatically, and kept by the host that runs your site.
  2. 2Every dayA second copyKept away from the host, made each day with WP Umbrella.
  3. 3Before every updateA fresh backupMade just before each update, so I can undo it if the update breaks your site.
The three backups in each of my care plans, as of November 2026.

What good looks like

  • Daily backups, taken without anyone having to remember.
  • A second copy kept somewhere away from your hosting.
  • A fresh backup before every update or big change.
  • Backed up often enough to keep new bookings or orders.
  • A restore you've already tried, so you know it works.

Where people go wrong

  • Backups kept only on the same server as the site.
  • Leaving your first restore until the day you need it.
  • Restoring last week's site and losing the bookings since.
  • Restoring a backup that already has the hack in it.

Step 7: Watch for trouble

What it does: tells you something's wrong before your customers do. A hacked page, an expired certificate or a site that's down all cost you calls, and you can't fix what you don't see.

Smith Plumbing's website

  • UptimeIs the site loading?Up
  • Plugin holesChecked every 6 hoursNone open
  • Malware scanThe site's filesClean
  • SSL certificateExpiry dateValid
  • Domain nameRenewal dateNot due
  • PHP errorsCode failing quietlyNone
  • Site healthPHP version, indexingGood
An illustration of the checks I run on every site on a care plan. Smith Plumbing is made up.

What good looks like

  • Uptime checked every few minutes, with an alert to you.
  • Malware scans of the site's files, run on a schedule.
  • Expiry dates watched for the certificate and domain name.
  • Google Search Console set up, so Google can email you problems.
  • A record of who logged in and what they changed.
  • A Google search, now and then, for pages you didn't make.

Where people go wrong

  • Finding out from a customer that your site is down.
  • Treating a malware scan as a lock. It finds a hack after the fact.
  • Alerts that end up in an inbox no one ever reads.
  • Checking only the pages you know. Hacks add new ones.

If you're doing it yourself, UptimeRobot's free plan gives you 50 monitors, each checking one thing, like your home page, every 5 minutes. It's allowed for business use too, so there's no reason to go without.

Step 8: Harden with care

What it does: closes the smaller ways in once the basics are done. It's also where most copy-and-paste advice lives, and some of that helps little, or takes the whole site down.

The tipVerdictWhat it is, and what the source says
Turn off the file editorWorth doingWordPress calls it an extra layer if an admin login is stolen.
Tighten file permissionsWorth doingWordPress: no folder should ever be open for anyone to change.
Change the table prefixHelps a littleThe start of each table name in the site's database. It can block some database attacks.
Hide the login pageHelps a littleWordPress: it cuts the noise, but never as your only defence.
Move wp-config.phpContestedThe file with the database password. Some say moving it carelessly can add holes, and others disagree.
The X-XSS-Protection headerLeave it offAn old header browsers no longer need. OWASP, a web security group, says not to set it.
HSTS preload listNot advisedA browser list of HTTPS-only sites. The list's own site doesn't recommend joining.
From WordPress's Advanced Administration Handbook, OWASP and hstspreload.org, November 2026.

What good looks like

  • Every change tried out on a copy of the site first.
  • The dashboard's file editor turned off.
  • File permissions set the way WordPress advises.
  • Security headers: rules your site gives to browsers.
  • XML-RPC, a common target of login attacks, closed if unused.

Where people go wrong

  • Pasting server code from a guide exactly as it's written.
  • Blocking every IP address but yours, then getting locked out.
  • Old security headers that browsers no longer need.
  • Relying on a hidden login page instead of real locks.

One line the server won't accept in its settings file can take the whole site down with an error. And blocking every IP address but your own can lock you out when yours changes, or when the server sees Cloudflare's address instead of yours.

If your site's been hacked

Take a breath: WordPress's own advice on a hack starts with staying calm.

  1. Write down what you seeWhat looks wrong, when you noticed and what changed lately
  2. Tell your hostOther sites on the server may be affected, and your host can help confirm it
  3. Change every passwordHosting, WordPress, files and database, for every user
  4. Clean it upRemove what was added and close the way they got in, or it comes back
  5. Clear things with GoogleCheck Google Search Console, then ask Google to recheck the site

The Security Issues report in Google Search Console shows what Google found, and Google's recheck can take a few days to a few weeks.

If you'd rather hand the clean-up to me, tell me what you're seeing and when it started. If I don't already look after your site, the clean-up is quoted as one-off work. Then it can go on a care plan, which covers any later clean-up.

WordPress security costs

You can do steps 2 and 3 yourself, and choose a good host, for little more than your time. Cloudflare's firewall comes on every plan, though the free one has fewer rules. Paid security plugins such as MalCare Protect and Wordfence Premium cost US$99 and US$149 a year for one site, as of November 2026.

Steps 4 to 7 never stop, so that's where most owners get help.

My Website Care plan covers hosting, updates, patching, backups and monitoring for you, from $120 a month + GST, or $95 a month + GST if you'd rather keep your own hosting.

Which steps you can do yourself: steps 1 to 4
StepDo it yourself?
1. Use secure hostingA good host, yes. Setting up the firewall takes know-howPartly
2. Lock down every loginA password manager and two-step loginsYes
3. Limit who can do whatSorting out who can log in and do whatYes
4. Keep it all up to dateOne click, but backing up and checking take timePartly
Which steps you can do yourself: steps 5 to 8
StepDo it yourself?
5. Cover the update gapA security service has to watch every pluginUsually not
6. Keep backups that workHost backups, yes. Testing a restore takes know-howPartly
7. Watch for troubleFree uptime alerts, yes. Responding takes timePartly
8. Harden with careOne bad line can take the whole site downUsually not

How to spot good care

Whether you hire me or someone else, these are what I'd look for.

Warning signs, and the good sign to look for instead
A warning signA good sign
Updates with no backup taken firstA backup before every update, and the site checked after
Leaves a known hole open until the next monthly updatePatches a critical hole within days
Asks for your password to get startedAsks for a login of their own
Puts your domain or accounts in their own name, not yoursLeaves your domain and accounts in your own name
Promises your site can't be hackedSays what they do, and what happens if your site is hacked
Sends a report that says "all good"Sends a report of what was updated and fixed each month

How I do it: Website Care plans, for WordPress sites Australia-wide.

Security questions

Is WordPress secure?

WordPress itself is in good shape: Patchstack found just 6 new holes in it in 2025, all low priority, out of 11,334 in all. The risk sits in the plugins and themes you add, and in how well the site is looked after from month to month.

Do I need a security plugin?

Not any one in particular. A firewall in front, checks for new holes and malware scans matter more than which plugin does them. On a care plan, Patchstack checks the plugins for new holes every 6 hours.

How often should I update my site?

Every month, with a backup first, which is what I do for the sites I look after. A critical hole can't wait for the month, though: in 2025, about half of the high-impact holes were attacked within 24 hours of going public. So on those sites, Patchstack checks the plugins every 6 hours and shields a hole it knows about, and I patch a critical hole within days.

Can you guarantee my site won't be hacked?

No, and be wary of anyone who does, because no one can stop every attack. The security on every site I look after makes a hack very unlikely, and if it does happen while you're on a care plan, cleaning it up is part of the plan.

Can you clean up my hacked site?

Yes. Tell me what you're seeing and when it started. If I don't already look after your site, the clean-up is quoted as one-off work, and once it's clean it can go on a care plan. If you're already on one, the clean-up is part of it.

Written by Max Jacobs

I'm a civil engineer turned web designer, based in Geelong, VIC. I've built websites and run marketing since 2015, and I don't hand the work to juniors: the person you email does it.

Want a safer site?

I look after WordPress hosting, updates, backups and security, Australia-wide.

Start your enquiry

Tell me about your site and I'll say which plan suits.