WordPress Security Checklist: 12 Steps to Protect Your Site
A simple checklist that prevents most hacks: updates, strong logins, fewer plugins, backups and a few settings.
Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
Most hacked sites were hacked through an old plugin or a weak password. This checklist covers what matters most.
The essentials
- Keep everything updated: WordPress, plugins and themes. Turn on automatic updates for security releases.
- Delete what you do not use: inactive plugins and themes still hold risk.
- Use strong, unique passwords for WordPress, hosting, FTP and email, kept in a password manager.
- Turn on two-factor login for every administrator.
- Do not use "admin" as a username, and give each person their own account with the lowest role they need.
- Keep backups off the server, and test a restore. See our backup guide.
Settings worth adding
- Limit login attempts with a trusted security plugin or your host's firewall.
- Turn off the built-in file editor by adding this to
wp-config.php:
define( 'DISALLOW_FILE_EDIT', true );
- Use https everywhere. See our SSL guide.
- Set safe permissions: folders 755, files 644, and
wp-config.phpstricter (600 or 640 where your host allows).
Watch for trouble
- Install only trusted plugins and themes, from the official directory or the vendor. Never use "nulled" copies of paid plugins, which often carry malware.
- Check Users and Site Health regularly. An unknown administrator is a warning sign. See our hacked-site guide.
A good host with its own firewall and malware scanning adds another layer.
Related guides
- WordPress Login Page Keeps Reloading or Redirecting (Can't Log In)
- How to Stop WordPress Spam Comments
- WordPress Site Health Warnings Explained: What to Fix and What to Ignore
- Locked Out of WordPress Admin: Reset Your Password Without Email
Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.