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…
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down and move changes live safely.
A WordPress staging site is a private copy of your website where you can try updates, new plugins and design changes without risking the live site. If something breaks on the copy, your visitors never see it. This guide explains the ways to create a staging site, how to lock it down so it does not email customers or appear in search results, and how to move changes to the live site without overwriting new orders or content.
Create a copy of your files and database (with your host’s staging tool, a plugin or by hand), change the site address on the copy, and lock it down: block search engines, protect it with a password, and stop emails and payments. Test the change there, then move it live. On a site that keeps receiving orders, comments or sign-ups, move only the code and settings you changed, not the whole database, or you may overwrite live data.
How this guide was prepared: it is research-based. We used the WordPress and WP-CLI documentation listed under Sources, checked on October 23, 2026. Staging features differ by host, so we describe the steps in general terms and cannot promise they match your hosting panel.
Staging is a copy used to test; it is not a backup and not a development site you build forever. WordPress has a concept of environment types: the function wp_get_environment_type() returns local, development, staging or production, set through the WP_ENVIRONMENT_TYPE constant or environment variable, and it defaults to production. Setting the staging value helps plugins and themes know that this copy is not the real site.

You have three main options: your host’s one-click staging tool (the simplest if your plan has it), a staging or migration plugin, or a manual copy of files and database. Ask your host what is available. A staging copy should live on the same kind of server and PHP version as the live site, or tests may not show real behaviour.
Copy the files and the database to the staging location, and update wp-config.php with the staging database details. Then replace the live address with the staging address in the database. WP-CLI’s wp search-replace does this without corrupting serialised data; run it with --dry-run first to see what would change, and skip the guid column with --skip-columns=guid. Avoid a plain text search and replace in the database, which can break serialised values. Always back up first; see is your WordPress backup really safe.
Run the update or change on the copy and test what matters to your business: forms, logins, search, and for a store the cart and checkout. Our guide to updating WordPress plugins safely has a test routine, and the WooCommerce maintenance checklist covers store flows. Note exactly what you changed so you can repeat it on the live site.
For a simple brochure site, many hosts let you push the whole staging copy to live. For a site that keeps changing, that can overwrite new orders, comments, form entries and users that arrived on the live site while you tested. In that case apply the same updates on the live site during a quiet period, or push only files (themes, plugins, custom code) and settings, not the database. Take a fresh backup of the live site first, and have a way back.
After the change goes live, run the same tests on the live site. Then delete or lock the staging copy so it does not become a forgotten, outdated and possibly insecure second site, and remove any temporary passwords or access you created.
No. A backup lets you restore; staging lets you test. You need both.
Not always, but it is useful for any site where downtime or a broken page costs you business.
Only if you push carelessly or the copy shares live services, such as email or payments, so lock it down first.
Before each round of testing, so it matches live as closely as possible.
Check what your host offers, make a copy, lock it down and test one change. If you would like staging and tested updates handled for you, wpallsolution’s higher WordPress maintenance packages include staging, as shown on the pricing page. We cannot promise outcomes without seeing your setup.
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.
Care plans give agencies steady work after launch. See how white label WordPress maintenance works, what to include and what to agree…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout