Hardening WordPress
A step-by-step guide to securing WordPress: lock down wp-config.php, add security headers, protect the login, and keep plugins and accounts in check.
- 4parts
- 18min in total
- Beginner to Intermediatelevel
- Nov 17, 2026last updated
All parts, in order
- Part 1Read
Lock Down wp-config.php: 7 Settings Every WordPress Site Should Have
Seven wp-config.php settings that close common holes in WordPress: no file editor in wp-admin, HTTPS for logins, no visible errors, fresh salts and more. Copy, paste, test.
- Part 2Read
Security Headers That Actually Protect Visitors
Five HTTP headers that tell the browser how to protect your visitors: no MIME sniffing, no clickjacking, less data leaked to other sites, and HTTPS every time. Plus a safe way to start a Content Security Policy.
- Part 3Read
Protect the Login From Bots and Stolen Passwords
Bots try passwords on every WordPress login page, all day. Stop handing them usernames, slow down guessing, close XML-RPC and other side doors, and add a second factor so a stolen password isn't enough.
- Part 4Read
Plugin Updates, User Roles and Sessions
Most hacked sites run an outdated plugin or have an admin account nobody uses any more. Keep plugins patched automatically, give every account only the access it needs, and make logins expire sooner for staff.
Looking for something else?
Browse all posts




