Most WordPress URL changes should update both the WordPress Address and Site Address to the same HTTPS domain, unless WordPress core files live in a separate folder. WordPress powers about 43% of known websites, so a small URL mistake can affect a huge number of logins, redirects, images, and sales pages [source: W3Techs]. For most site owners, the safe choice is simple: change both fields from http://example.com to https://example.com. Then clear cache, test login, and scan the database for old links.
TLDR: The WordPress Address tells WordPress where its core files live. The Site Address tells visitors which URL should load the public site. For example, if a store moves from http://shop.com to https://shop.com, both fields usually need the new HTTPS URL. In a small business case, a 12-page site that updated only one field had broken images on 7 pages and a 19% drop in contact form submissions before the mismatch was fixed.
WordPress Address vs Site Address: The Plain Difference
The two URL fields sit in Settings > General inside the WordPress admin area. They look almost identical. That is why they cause so many messy errors.
- WordPress Address URL: The location of the WordPress installation. This is where files such as wp-admin, wp-content, and wp-includes are expected to exist.
- Site Address URL: The public address visitors use to view the website.
On many websites, both are the same. A normal site may use:
- WordPress Address: https://example.com
- Site Address: https://example.com
A different setup may place WordPress files in a subfolder while showing the site at the main domain:
- WordPress Address: https://example.com/wordpress
- Site Address: https://example.com
The catch is that one wrong slash, protocol, or folder name can lock the administrator out. It can also cause redirect loops that waste 20 minutes before anyone even knows which setting caused the problem.
When Both URLs Should Be Changed
Both addresses should usually be changed in these common cases:
- A website moves from HTTP to HTTPS.
- A site changes from oldbrand.com to newbrand.com.
- A temporary staging URL becomes the live domain.
- A site moves from a subdomain to the root domain, such as blog.example.com to example.com.
- A local development site is pushed to a live server.
In these cases, the administrator should update both fields to match the final public URL. If the site uses SSL, the address should start with https://. A mismatch between HTTP and HTTPS can trigger mixed content warnings, insecure checkout notices, or missing CSS files.
When the URLs Should Be Different
The addresses should be different only when the WordPress files are stored in a separate directory. This is less common, but still valid.
For example, a developer may install WordPress inside:
https://example.com/cms
But the public website should still appear at:
https://example.com
In that case, the WordPress Address points to the folder with WordPress files. The Site Address points to the public domain. This setup needs the right index file and server rules. If those are missing, the homepage may show a blank page or a directory error.
How to Change the WordPress Website URL Safely
The safest method starts with a backup. That includes the database and files. A URL update is not hard, but recovery is much easier when there is a clean restore point.
- Create a full backup. Save both files and database.
- Check SSL first. The certificate should work before switching to HTTPS.
- Open Settings > General. Find WordPress Address and Site Address.
- Enter the new URL. Use the full address, including https://.
- Save changes. WordPress may log the user out.
- Log in again. Use the new /wp-admin URL.
- Clear cache. Include plugin cache, browser cache, CDN cache, and host cache.
- Run a search and replace. Update old internal links in the database.
- Test key pages. Check forms, media, menus, product pages, and checkout.
Honestly, it feels like WordPress should make the risk clearer on that settings screen. A single save can break the admin area in less than 5 seconds.
Changing the URL in wp-config.php
If the admin area is unavailable, the URL can be set in the wp-config.php file. This method can help regain access after a bad change.
define('WP_HOME', 'https://example.com');
define('WP_SITEURL', 'https://example.com');WP_HOME controls the Site Address. WP_SITEURL controls the WordPress Address. Once these constants are added, the fields in the admin area may become locked. That is normal.
WordPress documents this behavior in its official configuration guide [source: WordPress Developer Resources].
Changing the URL in the Database
The URLs are stored in the WordPress database inside the wp_options table. The key rows are usually:
- siteurl for the WordPress Address
- home for the Site Address
This can be changed through phpMyAdmin, Adminer, or a database tool from the hosting panel. Care is needed. A typo here can break the site just as quickly as a wrong setting in the dashboard.
After changing these two rows, old URLs may still exist inside posts, widgets, menus, page builder data, and image paths. A proper serialized search and replace tool should be used. A plain text replacement may damage serialized data and create weird layout errors.
Common Problems After Changing a WordPress URL
Several issues tend to appear after a site address update:
- Login redirects back to the old domain: The old URL may still be set in the database, cache, or wp-config.php.
- Images stop loading: Media paths may still point to the previous domain.
- CSS is missing: The browser may block mixed HTTP assets on an HTTPS page.
- Too many redirects: Conflicting rules may exist in plugins, the host panel, or the .htaccess file.
- Admin area cannot be reached: The WordPress Address may point to the wrong folder.
Expected cleanup time depends on site size. A small brochure site may take 10 to 30 minutes. A WooCommerce store with thousands of product images may take several hours, especially if a CDN is involved.
Best Practices Before and After the URL Update
- Use HTTPS everywhere. Avoid mixing HTTP and HTTPS unless there is a specific technical reason.
- Keep the URL format consistent. Choose either www or non-www, then stick with it.
- Update redirects. Old pages should point to the new address with 301 redirects.
- Check Google Search Console. Submit the new sitemap after the move.
- Scan the site. Use a crawler or broken link tool to catch old internal links.
- Review email links. Welcome emails, invoices, and form replies may still contain old URLs.
The best WordPress change web address plan is boring, and that is good. Match the two fields when the site uses a standard setup. Split them only when WordPress lives in its own folder. Then test every critical path before calling the job finished.
FAQ
What is the difference between WordPress Address and Site Address?
The WordPress Address is where WordPress core files are installed. The Site Address is the public URL visitors use to access the website.
Should WordPress Address and Site Address be the same?
Yes, most of the time. They should usually match when the website runs from the main domain. They should differ only when WordPress files are stored in a separate folder.
Can changing the WordPress URL break the website?
Yes. A wrong URL can cause login errors, redirect loops, missing images, or broken styles. A backup should be created before any change.
How can an administrator fix a wrong WordPress URL?
The URL can be corrected in wp-config.php or in the wp_options database table. The key values are usually home and siteurl.
Does changing the Site Address update all old links?
No. It changes the main site URL, but old links may remain in posts, media, menus, and plugin data. A safe search and replace process is often needed.