How to Secure Your WordPress Website: A Practical Checklist for Beginners (2026)
How to Secure Your WordPress Website: A Practical Checklist for Beginners (2026) WordPress powers a huge share of the web, and that popularity makes it a favourite target for attackers. The good news: most WordPress ha
How to Secure Your WordPress Website: A Practical Checklist for Beginners (2026)
WordPress powers a huge share of the web, and that popularity makes it a favourite target for attackers. The good news: most WordPress hacks do not come from clever zero-day exploits. They come from outdated plugins, weak passwords, and basic settings nobody ever changed.
This checklist covers the practical steps that stop the vast majority of attacks. You can work through it in under an hour, even if you are not technical.
1. Keep everything updated
Outdated WordPress core, themes, and plugins are the number one way sites get hacked.
- Turn on automatic updates for minor WordPress core releases.
- Update plugins and themes as soon as an update appears, and delete the ones you no longer use. An inactive plugin with a known vulnerability is still a risk.
- Before any update, take a backup, so a bad update can be rolled back in minutes.
2. Use a strong password and two-factor authentication
- Use a long, unique password for your WordPress admin account, generated by a password manager. Never reuse a password from another site.
- Enable two-factor authentication (2FA) for every admin account. Even if a password leaks, an attacker still cannot log in without the second factor.
- Create separate accounts for each person who needs access, and give each account only the role it needs. Do not share the main admin login.
3. Limit login attempts
By default, WordPress lets anyone try to log in as many times as they want. Bots exploit this with brute-force attacks.
- Install a login-limiting plugin (or use your host's built-in protection) so that a few failed attempts temporarily lock the IP out.
- Consider changing the default login URL from /wp-admin to something less obvious. It will not stop a determined attacker, but it cuts automated bot traffic dramatically.
4. Make sure your site runs on HTTPS
An SSL certificate encrypts the connection between your visitors and your site. Browsers now warn visitors away from sites without it, and Google treats HTTPS as a ranking signal.
Most good hosts include a free SSL certificate with every plan, and it usually activates automatically. If your site still loads over plain http, fix that before anything else.
5. Pick a security plugin and configure it
A reputable security plugin adds a firewall, malware scanning, and file-change detection in one place. Popular free options cover the basics well.
- Turn on the firewall and brute-force protection.
- Schedule a weekly malware scan.
- Turn on file-change alerts, so you know immediately if a core file is modified without your knowledge.
One well-configured plugin is enough. Running two security plugins at once usually causes conflicts, not extra safety.
6. Back up your site, and test the restore
Backups do not prevent an attack, but they decide how bad one is. A site with a tested backup is back online in an hour. A site without one can lose weeks of work.
- Keep automatic daily backups, stored off your server (not only in your hosting account).
- Keep at least one backup from before any big change.
- Test the restore at least once. A backup you have never restored is a hope, not a plan.
7. Remove what you do not use
Every extra theme and plugin is extra code an attacker can probe.
- Delete unused themes (keep one default theme as a fallback).
- Delete deactivated plugins instead of leaving them installed.
- Delete the 'admin' username if it still exists, and never use it for a new account. Bots always try 'admin' first.
8. Harden the basics
A few small settings make automated attacks much harder:
- Disable XML-RPC if you do not need it (most sites do not). It is a common brute-force vector.
- Disable file editing from the WordPress dashboard, so a compromised admin account cannot directly edit theme and plugin files.
- Set sensible file permissions on the server. Your host or a security plugin can check these for you.
- Use your host's server-level protections: a web application firewall, malware scanning, and account isolation between sites on shared hosting.
9. Monitor and stay alert
- Check your site's uptime and scan results weekly. A site that suddenly redirects visitors or shows strange content has probably been compromised.
- Keep the email address on your admin account current, so update and security alerts actually reach you.
- If your host offers free daily backups and malware scanning, use them. They are part of what you pay for.
The 15-minute version
If you only have a few minutes today, do these four things: update everything, turn on 2FA, install a security plugin, and confirm your backups are running. Those four steps alone block the overwhelming majority of automated attacks.
Security is not a one-time task. It is a short routine: update, back up, check. Set a weekly reminder, and your WordPress site will stay boring for attackers, which is exactly what you want.
Disclosure: I write about web hosting and WordPress for beginners. My work is connected to ZedgeHost (zedgehost.com), a web hosting company in Pakistan offering shared and WordPress hosting from Rs 1,499/year with free SSL, daily backups, and free migration. The advice above applies to WordPress on any host.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.