WordPress Login URL: How to Find, Change and Fix Your Login Page
On almost every WordPress site the login page is at yoursite.com/wp-login.php, and yoursite.com/wp-admin takes you there too. Here's how to find it on any setup, whether to change it, and what to do when you can't log in.
In this article
Key takeaways
- The default login page is yoursite.com/wp-login.php; /wp-admin takes you there when you're logged out.
- With pretty permalinks on, WordPress also redirects /login, /admin and /dashboard, unless a page or plugin uses those addresses.
- If WordPress lives in a subfolder, the login page does too: example.com/blog/wp-login.php.
- A plugin such as WPS Hide Login (2,000,000+ installs) can move the login page, but WordPress's security guide says that shouldn't be your only defence.
- WordPress has no built-in two-factor login; add it with a plugin such as Two Factor and turn it on for every administrator.
- Locked out? Use Lost your password?, then WP-CLI, phpMyAdmin or the emergency reset script, all documented by WordPress.
The short answer
Your WordPress login URL is the address of the login screen, wp-login.php, in the folder where WordPress is installed. These all get you there:
| Try this | Where it goes |
|---|---|
| yoursite.com/wp-login.php | The login page |
| yoursite.com/wp-admin | The dashboard, or the login page if you’re logged out |
| yoursite.com/login | Redirects to the login page |
| yoursite.com/admin or /dashboard | Redirects to the dashboard, or to the login page first |
| yoursite.com/blog/wp-login.php | The login page when WordPress is installed in a subfolder (here, /blog) |
The short addresses come from WordPress itself: wp_redirect_admin_locations() sends /admin and /dashboard to wp-admin and /login to wp-login.php. It only steps in when the address would otherwise be a 404 and pretty permalinks are on, so a page called Login, or a plugin that uses /login, wins.
How to find your login page when those don't work
- WordPress in a subfolder: if the site’s files live in /wordpress or /blog, the login page does too, for example example.com/wordpress/wp-login.php.
- Your hosting dashboard: most hosts put a log-in button next to each WordPress site.
- The setup email: hosts and installers usually send the admin address when the site is created.
- A link on the site: some themes show a Log in link in the footer or a Meta widget.
- A custom login address: if a security plugin moved the login page, the new address is in that plugin’s settings. Locked out of it? Removing the plugin’s folder from wp-content/plugins over SFTP switches it off and brings wp-login.php back.
- Multisite: every site in a network has its own /wp-login.php, and the network admin is at /wp-admin/network/.
For developers, wp_login_url() returns the login address (site_url plus wp-login.php) and can add a redirect_to for where to land afterwards.
Should you change your WordPress login URL?
Bots run brute force attacks against wp-login.php on every WordPress site, so moving it cuts the noise in your logs and some of the load. It doesn’t make a weak password safe. WordPress’s guide to brute-force attacks says obscuring the login URL “can reduce noise but should not be your only defense”, and puts these first:
- Strong, unique passwords and a password manager.
- Two-factor authentication for every administrator. WordPress core doesn’t have it, so add it with a plugin such as Two Factor (100,000+ active installs, published by WordPress.org contributors) or through your identity provider.
- Rate-limited logins at your host, firewall or CDN, or with a plugin such as Limit Login Attempts Reloaded (1,000,000+). WordPress notes that limits at the server or CDN cost your site less under heavy attack.
- A CAPTCHA or Cloudflare Turnstile on the login form.
- XML-RPC protected or switched off if nothing on the site uses it.
With those in place, a new login address is a sensible extra.
How to change the login URL with a plugin
WPS Hide Login (2,000,000+ active installs, 4.8 out of 5) is the most installed single-purpose option. It doesn’t rename or change core files: it intercepts requests, and deactivating it puts everything back as it was.
- Install and activate WPS Hide Login from Plugins, Add New. It takes you to its settings.
- Enter your new login address, for example my-team-login, and save. You can change it later in Settings, WPS Hide Login.
- Bookmark the new address: wp-login.php and wp-admin are now inaccessible to visitors who aren’t logged in.
- If you use a page caching plugin other than WP Rocket, add the new address to its never-cache list.
- Test logging out and back in from a private window before you close your current session.
Forgot the new address? WPS Hide Login stores it in the whl_page option in your database, or you can remove the plugin’s folder and log in at wp-login.php. Security suites can do the same job: Kadence Security (700,000+ active installs, formerly Solid Security) lists a Hide Login URL feature. Don’t rename wp-login.php yourself: the next WordPress update puts it back.
Can't log in? Fix the common problems
| What you see | What to do |
|---|---|
| You forgot the password | Click Lost your password? on the login page and enter your username or email. WordPress emails you a link to set a new one. |
| The reset email never arrives | Your site may not be sending email (here’s why). Reset the password with WP-CLI, wp user update 1 –user_pass=…, or in phpMyAdmin by setting user_pass with the MD5 function, as the WordPress documentation shows; WordPress swaps it for a secure hash next time you log in. |
| The login page reloads or loops | Clear the site’s cookies or try a private window, keep wp-login.php and wp-admin out of page caching, and check that WordPress Address and Site Address match the URL you use, with the same https and www. |
| “Cookies are blocked or not supported by your browser” | Allow cookies for the site, clear the browser cache and check the site address settings. A caching or security plugin that strips cookies on the login page can cause it too. |
| A plugin broke the login page | Rename wp-content/plugins (or just that plugin’s folder) over SFTP to switch plugins off, log in, rename it back and reactivate them one at a time. Debug mode shows which one fails. |
| A white screen or a critical error | Follow our guides to the white screen of death and the critical error message. |
| Locked out by a security plugin | Wait for the lockout to end, try from another network, or rename that plugin’s folder. |
| Nothing else works | WordPress’s emergency password reset script resets the administrator password if you know the username. Upload it to the site’s root folder and delete it straight after. |
How to add a login link to your site
If you’d like a visible way in, WordPress has a Login/out block. Add it to your header or footer in the Site Editor; it shows Log in to visitors and Log out to anyone signed in. Its settings can display the login form in place of the link, and send people back to the page they were on after they log in. In a classic theme, add a custom link to /wp-login.php in Appearance, Menus.
A quick login security checklist
| Do this | Where |
|---|---|
| Give every administrator a long, unique password | Users, Profile, Set New Password |
| Turn on two-factor login | A plugin such as Two Factor; each user sets it up under Users, Profile |
| Limit login attempts | Your host’s or CDN’s firewall, or a plugin such as Limit Login Attempts Reloaded |
| Retire the username admin | Create a new administrator, log in with it, then delete the old account and give its content to the new one |
| Use application passwords for integrations | Users, Profile, Application Passwords; you can revoke one without changing your own password |
| Protect or switch off XML-RPC | Your security plugin or server rules, if no app needs it |
| Move the login page (optional) | WPS Hide Login or your security suite |
Where WPOS fits
WPOS is our product, so weigh this section accordingly. When you run many WordPress sites, the WPOS agent works inside wp-admin on each one: it can list who has administrator access, set up the login protection you choose with the plugin you prefer, and read the debug log when a plugin breaks the login page, checking its work in a real browser before it reports done.
“List every administrator account on our client sites, then set up two-factor login and login rate limits on each one.”
You can start free, with no card needed.
Frequently Asked Questions
yoursite.com/wp-login.php. Visiting yoursite.com/wp-admin also takes you there when you're logged out, and with pretty permalinks on, WordPress redirects /login, /admin and /dashboard too, unless a page or plugin already uses those addresses.
Check whether WordPress is in a subfolder (example.com/blog/wp-admin), look for a log-in button next to the site in your hosting dashboard, and check whether a security plugin changed the login address; its settings, or the email you saved when you set it, will have the new one.
Use a maintained plugin such as WPS Hide Login, which lets you set a new login address and makes wp-login.php and wp-admin inaccessible to visitors who aren't logged in, rather than renaming core files. Set up strong passwords and two-factor login first, because hiding the login page shouldn't be your only defence.
Yes, with a maintained plugin, and it cuts the bot traffic hitting wp-login.php. Bookmark the new address and keep a way back in: removing the plugin's folder over SFTP brings back the default login page.
Usually cookies, caching or a mismatched site address. Clear the site's cookies or try a private window, keep the login page and wp-admin out of page caching, and check that the WordPress Address and Site Address in Settings, General match the URL you use, with the same https and www.
Use WP-CLI (wp user update with –user_pass), set a new password in phpMyAdmin with the MD5 function, or use WordPress's emergency password reset script. The WordPress documentation covers all three; delete the emergency script as soon as you're back in.
Not in WordPress itself. Add it with a plugin such as Two Factor, published by WordPress.org contributors, which supports authenticator apps, email codes and backup codes, or through your identity provider, and turn it on for every administrator.
Start free with 15,000 credits.
Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.
Look after every client site from one place.
WPOS puts an AI agent inside wp-admin on the sites you already run, on any host, and it checks its own work. Free for 30 days: 5,000 credits, a live site plus a sandbox, no card.