What a WordPress staging site is
A staging site is a private copy of the live WordPress site. You install a plugin, change a theme or raise the PHP version there, and visitors keep using the live site until you decide the change is safe.
It is not a second public website. Search engines should not index it, and it must not share the live site URL or live orders will get confusing fast. Managed copies of this idea sit on managed WordPress hosting when the plan includes one.
Create a staging site in cPanel
- Create a subdomain such as staging.example.com. Confirm it opens its own folder.
- Copy the live WordPress files into that folder, or use Softaculous clone if your cPanel account has Softaculous and its WordPress clone tool. Softaculous is only the copier. You still fix the URL afterwards.
- Copy the database into a new database and user. Point wp-config.php at that new database, not the live one.
- Run a URL replace so the copy does not redirect home. Use the search and replace steps.
- In Settings, then Reading, discourage search engines on the copy.
Replicate the site with a plugin
A staging plugin copies files and the database into a subdirectory or a subdomain from wp-admin. Use it when you do not have cPanel clone tools. After it finishes, open the copy's own login, not the live login.
Read the plugin's note about what it excludes. Cache folders and backup archives should stay behind. If the copy still redirects to the live host, the URL replace did not run. Do that next, before you test anything.
Host-provided staging compared with plugin staging
Host staging is built in the control panel and gives you a separate folder and database you control; plugin staging runs inside wp-admin and copies the site for you. The panel route suits a site with no plugin budget, the plugin route suits an owner without panel access.
| Decision | Host or panel staging | Plugin staging |
|---|---|---|
| Where you start | cPanel, CloudPanel or the host dashboard | Plugins screen in wp-admin |
| What is created | A subdomain folder and a new database you point wp-config.php at | A subdirectory or subdomain, usually with copied tables |
| URL handling | You run the search and replace yourself | The plugin often rewrites the copy's URL |
| Push to live | You copy changed files and keep the live database | Some plugins add a push button; it can overwrite live options and orders |
| Usual failure | The copy still points at the live domain | A push replaces the live database on a shop |
Whichever route you take, the push is the risky half. Test the checkout or the form on the copy, then move only the files and settings that changed, as the push checklist below sets out.
Site URL and home URL on the copy
WordPress has two address fields under Settings, then General. The WordPress address is where the files live. The site address is what visitors are sent to. On a staging copy both must be the staging host. If either still says the live domain, every click returns to production and you may edit the wrong site.
If you cannot log in because of a redirect loop, set both values in wp-config.php with WP_HOME and WP_SITEURL for the staging host, or correct them with WP-CLI on that copy only.
Staging on CloudPanel or a VPS
On CloudPanel, or any VPS panel, create a second site on a staging hostname. Copy the WordPress files and import a database dump into a new database. Point that copy's wp-config.php at the new database, then run the URL replace against the staging host.
Do not point the staging site at the live database. A form test would write into production. Give the staging vhost its own certificate so the browser is not the thing blocking your test.
Push the copy live without losing orders
- Back up the live site first. A push you cannot undo is not a test.
- Copy the changed plugin, theme or PHP files. Do not copy the staging wp-config.php over the live one.
- On a shop, do not overwrite the live orders and customer tables with the staging database. Those rows moved on while you were testing.
- Leave the discourage-search-engines box unchecked on production after the push.
- Delete or password-protect the staging copy when the test is over so it is not a second public site.
Frequently Asked Questions
What is a WordPress staging site?
It is a private copy of the live site used to test a plugin, a theme or a PHP change before visitors see it. It should use its own URL and its own database.
How do I create a staging site?
Make a subdomain or a second site, copy the files and the database, point wp-config.php at the new database, replace the URL, and discourage search engines on the copy.
Can I build staging on shared hosting?
Yes. A subdomain plus a copied database is enough on cPanel. Softaculous can clone WordPress when that installer is on the account. You still have to fix the site URL and home URL.
How do I push staging changes to the live site?
Back up production, copy the changed files, and do not replace the live database on a shop. Orders taken during the test live only in production.
Will staging hurt SEO from duplicate content?
It will if both hosts are public and indexable. Discourage search engines on the copy, and remove the copy when you are done.
Should plugin updates be tested on staging first?
Yes when the site takes orders or the plugin is large. Update staging, click the checkout or the form, then update production.
Is WebJi® an Indian company?
Yes. WebJi® is headquartered in Jaipur, Rajasthan and has operated since 2005. Billing, support and governance all run from India.
Do you provide GST invoices?
Every purchase and renewal gets a GST invoice with our GSTIN, and hosting prices are quoted exclusive of 18% GST. Claim input credit as applicable.