Every WordPress site has a login page, and every login page is being tested by bots right now. They try common usernames and leaked passwords thousands of times a day, hoping one combination works. You can't stop them knocking, but you can make sure the door doesn't open.
Here are seven steps that close the most common gaps, in rough order of impact.
1. Turn on two-factor authentication (2FA)
If you do only one thing from this list, do this. With 2FA, a stolen or guessed password isn't enough: the attacker also needs a one-time code from the user's phone. It shuts down the vast majority of password-based attacks.
Make it required for every Administrator and Editor account at least. Authenticator apps (Google Authenticator, Microsoft Authenticator, 1Password and others) are more reliable than SMS codes. Plugins such as the two-factor login feature in All-in-One Utilities Pro let you enforce it by role, so nobody can quietly skip setup.
2. Limit login attempts
By default WordPress lets anyone try passwords forever. Limiting attempts locks out an IP address after a handful of failures, which turns a brute-force attack from "a matter of time" into "practically impossible". Set a sensible lockout (for example, 5 tries, then 20 minutes) so real users who mistype aren't punished for long.
3. Stop using "admin" (and stop showing usernames)
Bots always try admin first. If your main account still uses it, create a new administrator with a different username, move content across and delete the old one.
WordPress can also leak usernames through author archive URLs like /?author=1. Disabling author pages, or redirecting them, removes half of what an attacker needs to guess.
4. Move or hide the login URL
Changing /wp-login.php to a custom address won't stop a determined attacker, but it removes your site from the endless stream of automated hits on the default URL. That means fewer lockouts, less server load and quieter logs, so the attempts that do appear are worth looking at.
5. Require strong passwords, and expire old ones where it matters
Encourage a password manager for every team member. For sites with many staff accounts (agencies, schools, membership sites), consider password expiry for privileged roles, so a password leaked from another service doesn't stay useful forever.
6. Keep a login activity log
A log of who logged in, when and from where turns "I think something's wrong" into a clear answer. Look for logins at odd hours, from unexpected countries, or from accounts that should be dormant. Login notification emails for admin accounts are a useful early warning.
7. Give temporary access instead of sharing passwords
Developers, designers and support agencies often need access for a few days. Don't send them your own password, and don't create a permanent admin that nobody remembers to delete. Use temporary logins that expire on their own.
Bonus: the basics that support all of the above
- HTTPS everywhere. Logins over plain HTTP send passwords in the clear.
- Updates. A secure login doesn't help if an outdated plugin offers a back door. The official WordPress hardening guide covers the wider picture.
- Backups. If the worst happens, a clean off-site backup is your fastest way back.
Do you need five plugins for this?
You don't. Installing a separate plugin for each step adds weight, settings screens and update chores. Several of these features (limit login attempts, hiding author pages, hardening) are available in the free All-in-One Utilities plugin, and the Pro add-on adds 2FA, custom login URLs, activity logs and temporary access in the same settings screen.
Whatever tools you choose, set aside 30 minutes this week to work through the list. It's one of the highest-return half hours you can spend on your website.
Written by the team at WordTenance, who look after WordPress and WooCommerce sites for small businesses and build the All-in-One Utilities plugins. Visit wordtenance.com.
Publishing details (not part of the article)
| Field | Value |
|---|---|
| Post title (H1) | How to Secure Your WordPress Login Page: 7 Practical Steps |
| URL slug | secure-wordpress-login |
| SEO title | How to Secure Your WordPress Login Page (7 Practical Steps) |
| Meta description | Bots attack WordPress login pages every day. These 7 steps, from two-factor authentication to login limits and activity logs, keep attackers out. |
| Focus keyword | secure WordPress login |
| Category (suggested) | WordPress Security |
| Tags (suggested) | WordPress security, two-factor authentication, login security, brute force |
| Excerpt | Every WordPress login page is being tested by bots right now. These seven steps close the most common gaps, starting with two-factor authentication. |
| Featured image alt text | Padlock over a WordPress login form protected by two-factor authentication |
| Length | about 621 words |
Links to WordTenance (please keep as they are)
| Anchor text | URL |
|---|---|
| two-factor login feature in All-in-One Utilities Pro | https://wordtenance.com/docs/all-in-one-utilities-pro/security/two-factor-authentication/ |
| All-in-One Utilities | https://wordtenance.com/plugins/all-in-one-utilities/ |
Other references (optional)
| Anchor text | URL |
|---|---|
| WordPress hardening guide | https://developer.wordpress.org/advanced-administration/security/hardening/ |
