You do not need to be a security expert to keep a WordPress site safe. The WordPress project's own hardening guide comes back to the same few habits again and again: keep software current, control who can log in, and keep backups. This article turns them into a short routine.
Keep everything updated
Updates are the first line of defence. WordPress says you should always run the latest version, and that older versions no longer receive security updates. That applies to WordPress itself, your plugins and your theme.
- Check the Dashboard for update notices at least once a week.
- Automatic updates have been part of WordPress since version 3.7, so the core software can update itself.
- Before a big update, take a backup. Our guide to updating plugins and themes safely shows the order to follow.
Delete what you do not use
Every plugin is code that someone has to keep patched. WordPress advises deleting any plugin you are not using, not just switching it off.
- Install plugins and themes only from the WordPress.org directory or from companies you know.
- Be careful with a plugin that asks for write access to your files, and read what it does first.
- Remove old themes you tried and dropped.
Protect every login
Weak passwords are one of the easiest ways in. WordPress recommends a strong, unique password, and two-step authentication for logins.
- Use a long password that you use nowhere else. A password manager makes this practical.
- Turn on two-step sign-in for every administrator account.
- Do not use
adminas the administrator username. If your account is named that, create a new administrator, move the content across and remove the old one. - Use SFTP instead of plain FTP when your host offers it, so your password is encrypted on the way.
- Give each person their own account, with the lowest role that lets them do their job.
Keep backups you have tested
Backups do not stop an attack, but they turn a disaster into a restore. WordPress says to keep your backups in a trusted place so that you always have a copy from before any compromise. Its backup guide adds that you need both the database and the files, because downloading the files alone does not save your posts, comments and settings.
Our article on why website backups matter covers how often to take them.
What your hosting should do for you
Some protection belongs at the server, not in WordPress. Look for malware scanning, a firewall, isolation between accounts and automatic backups. On Server Salad plans, these are part of the package: cPGuard malware protection, a web application firewall, CloudLinux account isolation, daily JetBackup backups kept for 30 days, and two-factor sign-in for cPanel. The full list is in what is included with every plan.
Server tools help, but they do not replace the habits above. An outdated plugin is still outdated on the best server.
A five-minute monthly routine
- Update WordPress, plugins and the theme.
- Delete one thing you do not use.
- Check the list of users and remove people who have left.
- Confirm that last night's backup exists.
- Look at your site as a visitor would, including the padlock. See what SSL is if the padlock is missing.
FAQ
Do I need a security plugin?
Not always. WordPress suggests a firewall, either as a plugin, as a service in front of the site or at the server, as one extra layer. If your host already provides a firewall and malware scanning, a second plugin may add little. Updates, strong logins and backups matter more.
Is a small site really a target?
Yes. Attacks are usually automated and look for old software, not for particular businesses. Size does not protect you.
What if my site has already been hacked?
Work through what to do first if your website is hacked, then come back to this routine so it does not happen again.
