In WordPress, a Site URL that points to one place and a Home URL that points to another can block logins and break pages. The Site URL is the address where WordPress files live, while the Home URL is the address visitors use to reach the front of the site. The two values can differ on purpose, such as when core files sit in a subdirectory. Problems start when the difference is accidental, after a move, a domain change, or an HTTP to HTTPS switch.
Table of Contents
- What Each Address Controls
- Why A Mismatch Blocks Access
- What Makes The Values Drift Apart
- How To Fix Access Safely
What Each Address Controls
The Site URL controls where WordPress looks for the dashboard, login screen, uploads, themes, and plugins. Change it to the wrong domain or folder and admin links point to a place that does not answer. The Home URL controls the address WordPress prints into menus, links, and most front-end content.
Change it alone and visitors request pages from one host while scripts and styles load from another. Keep both values exact, including www or non-www, HTTP or HTTPS, and any subdirectory. Small spelling differences still count as a mismatch to browsers and cookies.
Why A Mismatch Blocks Access
A mismatch breaks access because logins depend on redirects and cookies tied to one domain. WordPress may send you to wp-login.php on one address, set the cookie for another, then bounce you back to login. Mixed addresses also break appearance and behavior.
A page can load its text from the Home URL while its stylesheet, script, and image paths point to an unreachable Site URL, leaving a bare or half-working screen. HTTPS drift causes the same failure. If one setting uses HTTPS and the other uses HTTP, browsers block the insecure files and login cookies fail, so the dashboard never settles.
What Makes The Values Drift Apart
Moves and copies are the most common cause. Cloning a site to a new domain, staging address, or folder often updates one field and leaves the other pointing at the old location. Domain and protocol edits also create drift.
Adding or removing www, changing folders, forcing HTTPS, or placing the site behind a proxy can alter the effective address without updating both settings. Manual edits add risk. Setting the values in Settings, wp-config.php, or the database at different times can leave competing definitions, with one location overriding the screen you see.
How To Fix Access Safely
Confirm which address is correct before you change anything. Check the live domain, HTTPS status, www choice, and whether WordPress core sits in the root or a subdirectory.
After access returns, replace old addresses inside posts, widgets, and media paths. Test uploads, updates, password reset, and logout, because those paths expose a leftover mismatch fast.
- Open the site in a private window and note where login redirects stop.
- Compare the Site URL and Home URL character by character.
- Update the wrong value in Settings, wp-config.php, or the database, then keep one source of truth.
- Clear browser cookies, site cache, and any redirect cache, then test login and several front-end pages.
