Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Explainer

Should You Change the WordPress Login URL?

Short answer

Changing the WordPress login URL hides it from simple bots, but it is not real security on its own. Bots can still find the new address, and a weak password is still guessable. Change the URL only as one extra layer, alongside strong passwords, two-factor authentication and a limit on login attempts, because skipping those means the new URL buys little.

Key takeaways

  • The default WordPress login page is wp-login.php, and every WordPress site shares that address.
  • WordPress calls security through obscurity an unsound primary strategy, though hiding the URL can reduce bot noise.
  • Wordfence blocked 18.2 billion brute-force attacks in the second quarter of 2026.
  • WPS Hide Login changes the login address without renaming core files, and deactivating it restores the old address.
  • WordPress core does not include two-factor authentication, so it must come from a plugin.
  • The default login cookie lasts 2 days, or 14 days when Remember Me is checked.

What is the WordPress login URL?

The default login page is wp-login.php in your site's root, reached at yourdomain.com/wp-login.php.

Visiting /wp-admin/ while logged out redirects you to the same login page automatically (WordPress Developer Resources). The login form accepts a username or an email address, and the password is case-sensitive.

Every WordPress site shares this address, which is why bots know where to knock. Brute-force attacks try username and password combinations again and again until one works, often from botnets that spread the attempts across many addresses (WordPress Developer Resources).

What does changing the login URL actually do?

It moves the login form to a custom address and blocks the default one.

The WPS Hide Login plugin lets you change the login form URL to anything you want. It does not rename core files or add rewrite rules; it simply intercepts page requests (WordPress.org). The wp-admin directory and wp-login.php page become unreachable, so you should bookmark the new address.

Deactivating the plugin brings your site back exactly to its previous state. The registration form, lost-password form, login widget and expired sessions keep working, and the plugin needs WordPress 4.1 or higher (WordPress.org). It holds a 4.8 out of 5 rating from 2,114 reviews and was updated 12 November 2026.

Does changing the login URL make WordPress secure?

No, it only reduces noise from bots that knock on the default address.

WordPress's own hardening guide says security through obscurity is generally an unsound primary strategy. It adds that obscuring information might help in some places, such as renaming the admin account (WordPress Developer Resources).

The brute-force guide puts it plainly: obscuring the login URL can reduce noise but should not be your only defence (WordPress Developer Resources).

The same guide adds that security is risk reduction, not risk elimination. A hidden login URL lowers the number of automated attempts you see, but a bot that finds the new address faces the same password check as before.

How big is the brute-force problem?

Large enough that hiding the login page alone cannot solve it.

Wordfence's quarterly threat report for the second quarter of 2026, published 29 September 2026, recorded 18.2 billion brute-force attacks blocked, up 13.8% from the previous quarter (Wordfence). The same report counted 10.4 billion firewall attacks blocked and 2,073 vulnerabilities published.

Those numbers count attacks across the sites Wordfence protects, not yours alone. Even so, they show why a single hidden URL is a thin shield. Bots scan the whole internet, and a new login address is one more thing to find, not a wall.

What should you do instead of, or with, changing the URL?

Use strong passwords, two-factor authentication and a login-attempt limit as your main defences.

The official brute-force guide recommends strong unique passwords with a password manager, two-factor authentication for all administrator accounts, passkeys, rate limiting at the edge or web server, and a CAPTCHA or Turnstile challenge on the login form (WordPress Developer Resources).

Cloudflare Turnstile runs small background checks with no puzzle for most visitors and needs no Cloudflare proxying (Cloudflare Developers). The guide also advises disabling XML-RPC if you do not need it.

As of 2025, WordPress core does not ship two-factor authentication, so it must come from a plugin or a single sign-on provider (WordPress Developer Resources). Wordfence adds two-factor authentication through any TOTP authenticator app, plus login-page CAPTCHA and passkeys (WordPress.org).

WordPress also allows unlimited login attempts by default. The Limit Login Attempts plugin, trusted by 2 million WordPress websites, limits attempts by IP and username, adds automatic lockouts and built-in two-factor authentication (WordPress.org). Its latest changelog entry shown is version 3.4.5.

How do you change the login URL safely?

Install a login-hiding plugin, pick a simple address, and save it somewhere safe before you log out.

With WPS Hide Login, open Settings > WPS Hide Login after activation and type your new login slug, for example “my-login”. Save the settings, then open the new address in a private browser window and confirm the login form appears there.

Check that the old address is blocked. Open yourdomain.com/wp-login.php and confirm it no longer shows the form. If it still does, clear your cache and check again, since a caching plugin can serve the old page.

Tell every administrator and editor the new address before you change it. Anyone with a bookmark to wp-login.php will lose access until they learn the new URL, and support tickets about a missing login page are the most common complaint after this change.

What are the risks of changing the login URL?

The main risk is locking yourself out of your own site.

If you forget the new address, the WPS Hide Login FAQ says to look for the value of whl_page in the options table of your database, or to remove the wps-hide-login folder from the plugins folder, log in through wp-login.php and reinstall the plugin (WordPress.org).

On multisite, whl_page lives in the sitemeta table.

Some plugins and tools expect the default login address. Limit Login Attempts says it protects custom login pages and works with WPS Hide Login, but not every security plugin makes the same promise (WordPress.org). Check each security plugin you use before you change the URL.

A changed login URL can also break automated workflows that post to wp-login.php, such as some mobile apps or integrations. Application Passwords, introduced in WordPress 5.6, give API access without the login form (WordPress Developer Resources).

What about XML-RPC and other login doors?

Hiding wp-login.php does nothing about xmlrpc.php, which bots also attack.

The brute-force guide calls xmlrpc.php a frequent brute-force target, especially its system.multicall method. If you do not use XML-RPC, disable it; if you do, restrict it with firewall rules and rate-limit it hard (WordPress Developer Resources).

The guide gives an example rate limit of 10 requests per minute for /wp-login.php and /xmlrpc.php, with a burst allowance of 20 (WordPress Developer Resources). A limit like that slows automated guessing even when the attacker knows your login address.

Wordfence also offers XML-RPC options, including disabling it or adding two-factor authentication to it (WordPress.org). Its free firewall rules and malware signatures are delayed by 30 days, while Premium gets real-time updates through the Threat Defense Feed.

Which plugin should you use to hide the login URL?

Pick a plugin that only hides the URL, or use a security plugin that includes the feature.

OptionLogin URL featureRating as of November 2026Notes
WPS Hide LoginDedicated, free4.8/5 (2,114 reviews)Only hides the URL
Kadence SecurityHide Login URL under Advanced Security Tools4.6/5 (3,992 reviews)Also adds 2FA and brute-force protection
WordfenceLogin CAPTCHA and 2FA, no URL hiding5+ million installsBest for attempt limits
Limit Login AttemptsProtects custom login pagesTrusted by 2 million sitesBest for lockouts

Kadence Security, formerly iThemes Security, includes a Hide Login URL tool under its Advanced Security Tools, plus two-factor authentication, password requirements and local and network brute-force protection (WordPress.org). Its network brute-force protection covers nearly one million websites, and its site scanner runs 4 times per day on the Basic plan.

If you only want the URL change, WPS Hide Login is the lighter choice. If you want the URL change plus two-factor authentication and lockouts in one plugin, Kadence Security covers more ground.

How do you recover access if you are locked out?

Use the password reset link, WP-CLI or the database, depending on what still works.

The official login guide says to use the “Lost your password?” link on the login screen, which emails a reset link to the account address (WordPress Developer Resources). With WP-CLI, the guide recommends wp user update USERNAME --prompt=user_pass or wp user reset-password USERNAME --show-password.

If a lockout plugin blocked your IP, the Limit Login Attempts FAQ says to rename the limit-login-attempts-reloaded folder in wp-content/plugins, log in, then rename it back and whitelist your IP (WordPress.org). Opening the site from another IP, phone or VPN also works.

Note the session lengths while you recover. The default auth cookie lasts 2 days, or 14 days when Remember Me is checked (WordPress Developer Resources). A locked-out admin on a remembered session may still be logged in on another device.

Should you change the WordPress login URL?

Yes, if you treat it as a small extra layer on top of real defences.

Change the URL when you want fewer automated knocks on your login page and you are willing to keep the new address safe.

Do not change it as a substitute for a strong password, two-factor authentication or an attempt limit, because none of those problems goes away when the address moves.

If you run a site with several administrators, weigh the support cost. Every new editor needs the custom address, and every forgotten address becomes a ticket. For a single-admin site, the cost is small and the noise reduction is real.

For the full picture, read our guide to setting up the Wordfence firewall.

Also read our guide to adding security headers to WordPress.

If your login page itself misbehaves after the change, see our guide on fixing a login page that keeps refreshing.

Frequently asked questions

Is changing the login URL enough to stop brute-force attacks?

No. Changing the login URL hides the form from bots that only try the default address, but it does not check passwords any better. Use it together with a strong password, two-factor authentication and a limit on login attempts. On its own it only reduces the noise in your logs.

What do I do if I forget my new login URL?

Remove the wps-hide-login folder from wp-content/plugins using FTP or your host's file manager, then log in through the normal wp-login.php address. You can also look up the whl_page value in your database options table to find the custom address. Reinstall the plugin only after you are back in.

Can I undo the login URL change?

Yes. Deactivating WPS Hide Login returns the site exactly to its previous state, and the default login address works again. With Kadence Security, turn off the Hide Login URL setting instead. Either way, test the default address in a private browser window after the change.

Will changing the login URL break my plugins?

Some do. Plugins that post to wp-login.php, some mobile apps and a few integrations expect the default address. Check each security and login plugin you use, and test the new address before telling your team. Application Passwords, added in WordPress 5.6, cover API access without the login form.

Is two-factor authentication better than hiding the login URL?

Two-factor authentication is the stronger step. It asks for a code from your phone as well as your password, so a guessed password alone is not enough. WordPress core does not include it, so add it with Wordfence, Kadence Security or Limit Login Attempts Reloaded, all of which offer it free.

Sources

  1. Logging in to WordPress WordPress Developer Resources
  2. Brute Force Attacks WordPress Developer Resources
  3. Hardening WordPress WordPress Developer Resources
  4. WPS Hide Login WordPress.org
  5. Kadence Security WordPress.org
  6. Wordfence Security WordPress.org
  7. Quarterly WordPress Threat Intelligence Report Q2 2026 Wordfence
  8. Turnstile Cloudflare Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test