WordPress Login Redirect Loop: Fix Being Sent Back to wp-login
You type the right password and WordPress sends you back to the login page. The cause is usually cookies, address settings, caching…
Most break-ins start at the login screen. Use this practical checklist for passwords, two-step login, admin accounts, attempt limits and HTTPS.
WordPress login security is about making the page where people log in hard to attack and hard to misuse. Automated bots try common passwords on login pages all day, and a single weak or reused password on an administrator account can undo every other safeguard. The good news is that the main protections are simple and mostly free: strong unique passwords, two-step login, fewer administrator accounts, limits on attempts and HTTPS. This guide goes through them in a practical order and notes what each one does and does not do.
Give every user a long, unique password kept in a password manager, turn on two-step authentication for all administrators, keep the number of administrators small and give everyone else the lowest role that works, limit repeated login attempts at your host, firewall or a plugin, serve the admin over HTTPS and plan a safe recovery. The WordPress hardening guide recommends strong passwords and two-step authentication, limiting the database user’s privileges, disabling file editing in the dashboard and keeping software updated. No measure makes a site unhackable.
How this guide was prepared: it is research-based. We used the WordPress hardening documentation and the WordPress source listed under Sources, checked on October 23, 2026. Features such as two-step login or passkeys depend on your setup or on plugins, so check what yours supports. We do not claim that any measure prevents all attacks, and we are not a cybersecurity firm.
Every WordPress site has a predictable login address, so bots can try stolen or guessed passwords at scale. The usual ways in are weak or reused passwords, accounts that nobody remembers, and too many people with administrator rights. A successful login gives an attacker the same power as the account owner, including installing plugins, so protecting accounts matters more than hiding the login URL. Our article on PHP2Shell and website security covers server-level issues, which are a separate layer.

The WordPress hardening guide advises strong passwords: mixed characters, no names or words tied to you or your site, no short or single-type passwords, and the strength meter when you change one. A password manager makes unique long passwords practical. Never reuse a password from another service, and change any that may have been exposed. Avoid the username “admin”, as the guide also notes.
Two-step authentication asks for a second proof, such as a code from an app or a device-based passkey, in addition to the password, so a stolen password alone is not enough. The hardening guide recommends enabling it. WordPress core does not necessarily include it on every version, so use a trusted plugin or your host’s feature, and check the plugin’s update history. Passkeys follow the W3C Web Authentication standard and replace the password with a device credential; support depends on your plugin. Keep recovery codes safe, and test the login in a private window.
Give each person the lowest role that lets them work: editors do not need administrator rights, and former staff or agencies should have their accounts removed or downgraded when the job ends. WordPress stores roles and capabilities in the database, and an account with the wrong role is a risk; see “You are not allowed to access this page” for how roles work. Review the Users list regularly for accounts you do not recognise. Also review Application Passwords, a core feature since WordPress 5.6 that lets an account give a script or app access, and revoke the ones you do not use.
Bots try many passwords quickly, so limit how often one source can attempt a login. Your host, a firewall or a security plugin can lock a source out after several failures or add a delay. Set limits that do not lock out real staff, and log what is blocked. Also keep WordPress, plugins and themes updated, because outdated software is another way in; see how to update WordPress plugins safely.
The hardening guide recommends requiring an encrypted HTTPS connection for administration, so passwords are not sent in the clear, and using SFTP instead of plain FTP. Make sure the admin and login pages load over HTTPS without warnings; see WordPress mixed content warnings. Plan recovery: where recovery codes are kept, who can reset access, and how you would regain control if an account were compromised. If a login problem blocks you, see WordPress login redirect loop.
It is one of the most effective extra steps for administrator accounts, and the WordPress hardening guide recommends it.
It can reduce noise, but strong credentials and limits matter more.
No. It helps with attempts and monitoring, but passwords, roles and updates are still your responsibility.
Keep recovery codes and know who can reset access before you need it.
Related guide: WordPress Redirecting to Spam Sites: First Steps for a Redirect Hack
Related guide: Stop WordPress Form Spam: Honeypot vs Turnstile vs reCAPTCHA
Work through the five steps for every administrator account. wpallsolution offers WordPress maintenance packages that include login hardening in higher tiers, shown on the pricing page. We are not a cybersecurity firm and cannot promise that a site will never be attacked.
You type the right password and WordPress sends you back to the login page. The cause is usually cookies, address settings, caching…
Old PHP stops getting fixes, but a rushed update can break plugins. Learn to check your version, test compatibility and switch PHP…
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout