Backups & maintenance · Guide
How to Delete a WordPress Staging Site Safely (Host, Plugin or Manual)

Short answer
Delete a WordPress staging site with the same tool that created it: your host's staging section, your staging plugin's delete option, or, for a manual copy, by removing its folder or subdomain files and its database. Before deleting, push any changes you want to keep to the live site and take a backup.
Key takeaways
- Push any changes you want to keep to the live site first.
- Use the same tool that created the staging site to delete it.
- Manual staging sites need files, database and subdomain removed.
- Double-check you are deleting staging, not the live site.
- Remove leftover DNS records and search listings afterwards.
When should you delete a staging site?
Delete a staging site once you have pushed or copied the changes you need, when it is outdated and might confuse your team, or when it uses storage and resources you want back.
A staging site is a private copy of your site for testing. Our explainer on what a staging site is covers why sites use them.
Old staging copies can become a security risk. They often run outdated plugins and are forgotten until something goes wrong.
If you will need staging again soon, refreshing it from live is often easier than deleting and recreating it.
Is it safe to keep an old staging site?
It can be, if it is password protected and kept updated, but forgotten copies with old plugins and admin accounts give attackers another way in.
If you keep one, include it in your update routine and security scans, just like the live site.
What should you check before deleting?
Confirm all wanted changes are on the live site, take a backup of the staging copy if it holds unique work, and make sure you know exactly which site and database belong to staging.
Compare the staging and live URLs carefully. Many hosts use similar names, such as a staging prefix.
If your host lists several environments, open each one first and confirm which is live by checking the domain in the address bar.
Note any settings or code you tested but have not moved yet.
Screenshots of changed settings pages are a quick way to keep a record before the copy disappears.
Tell your team before deleting. Someone may still be testing there.
Check whether any automated tasks, such as deployment scripts or scheduled syncs, still point at the staging copy. Turn them off before removal.
| Check | Why it matters |
|---|---|
| Changes pushed or copied | Avoid losing work |
| Backup taken | Allows recovery if needed |
| Correct URL and database confirmed | Avoid deleting live data |
| Team informed | Prevents interrupted testing |
How do you delete a host-created staging site?
Log in to your hosting dashboard, open the site's staging or environments section, choose the staging copy and use the delete or remove option, then confirm.
Managed WordPress hosts usually remove files, database and staging URL together.
Wait for the host to confirm the deletion has finished before creating a new staging copy, since some tools run the removal in the background.
Some hosts keep one staging slot per site. Deleting it frees the slot for a fresh copy later.
Look for a separate staging backup list too. Some hosts keep staging backups apart from live backups, and deleting staging may remove those as well.
If you cannot find the option, search the host's help centre for staging, or ask support to remove it.
How do you delete a plugin-created staging site?
Open the staging plugin's screen on the live site, find the staging copy in its list and use the plugin's delete action, which removes the copy's files and database tables.
Plugins such as WP Staging create copies inside your hosting account and manage deletion from the live dashboard.
Read the confirmation screen carefully. It usually lists the folder and tables it will remove.
After deletion, you can deactivate the staging plugin if you no longer need it.
If the plugin's list shows no copies but files remain, check the plugin's documentation for its staging folder name and remove leftovers manually.
How do you delete a manual staging site?
Remove the staging folder or subdomain's files, drop the staging database or its tables, delete the staging database user, and remove the subdomain and any DNS record.
Find the database name in the staging copy's wp-config.php before deleting files. Our guide on finding wp-config.php shows where it is.
Delete the database in your hosting panel's database tool or phpMyAdmin. The phpMyAdmin documentation explains managing databases.
If staging and live share one database with different table prefixes, delete only the tables with the staging prefix.
Export those tables first, then delete them. Sorting tables by name in phpMyAdmin keeps the staging prefix grouped together.
How do you delete it with WP-CLI?
From the staging site's folder, the wp db drop command removes that site's database, after which you delete the folder; double-check the path before running it.
The wp db drop reference warns that it deletes the whole database in wp-config.php.
Run wp option get siteurl first to confirm you are in the staging copy.
Export the database with wp db export before dropping it, so you still have a copy if you notice something missing later.
How do you avoid deleting the live site by mistake?
Check the site URL, folder path and database name three times, take a full live backup first, and never run delete commands from a folder you have not confirmed.
Open the staging site in the browser and make a small visible change. If the change appears on live, stop.
Also compare the admin bar and site title. Many teams add the word staging to the site title on copies for exactly this reason.
Use different admin colour schemes or a staging notice banner. It helps everyone recognise which site they are in.
Never give staging and live the same admin password. Different credentials add one more pause before you act on the wrong site.
Our guide on setting up a staging site includes ways to label copies clearly.
What about search engines and indexing?
Staging sites should never be indexed, but if one was, the deleted URLs will drop out over time, and you can request faster removal in Google Search Console.
Google's help page on the Removals tool explains temporary removal of URLs from results.
Redirect the staging domain to live only if real people used it. Otherwise let it return errors.
For future copies, block indexing from the start with a login or noindex setting.
Password protection at server level is the strongest option, because search engines cannot read pages behind a login at all.
What else should you clean up?
Remove the staging subdomain and DNS records, cancel any separate SSL certificate, delete staging users and API keys, and clear CDN or caching rules that referenced it.
Staging copies sometimes connect to live services, such as payment test accounts or email tools. Revoke those connections.
Remove staging entries from uptime monitors and backup schedules.
Search your password manager for staging logins and archive them, so old credentials are not reused by mistake.
Check your hosting disk usage afterwards to confirm the space was freed.
Large staging copies often include full media folders, so deleting them can free a surprising amount of space on smaller hosting plans.
Can you restore a deleted staging site?
Only from a backup; host-created staging sites are often removed completely, so take a backup first if there is any chance you will need the staging work again.
Some hosts keep their own backups for a short time. Ask support quickly if you deleted the wrong copy.
Downloading a staging backup to your own computer or cloud storage protects you even if the host's copies expire.
Our guide on restoring a backup with UpdraftPlus helps if you backed up with that plugin.
How do you create a fresh staging site later?
Use your host's staging tool or a staging plugin to copy the current live site, so testing starts from up-to-date content, plugins and settings.
Fresh copies avoid surprises caused by old staging data.
Keep only one active staging copy per site unless you have a clear reason for more.
Multiple copies drift apart quickly, and it becomes hard to know which one holds the latest test work.
Set a reminder to delete or refresh staging after big projects finish.
Write the date and purpose of each staging copy in your project notes, so anyone can tell later whether it is still needed.
Frequently asked questions
How do I delete a staging site in WordPress?
Use the same tool that created it: your host's staging section, your staging plugin's delete option, or delete the files and database manually for a hand-made copy.
Will deleting a staging site affect my live site?
No, as long as you delete only the staging files and database. Always confirm the URL, folder and database name before deleting.
Should I back up before deleting staging?
Yes, if staging holds any work not yet on the live site. Take a backup of the staging copy and the live site to be safe.
How do I remove a staging site from Google?
Delete it and let the URLs drop out, or use the Removals tool in Google Search Console for faster temporary removal from search results.
Can I recover a deleted staging site?
Only from a backup. Host-created staging sites are usually removed completely, so ask your host quickly if you deleted one by mistake.
Sources
- WP Staging WordPress.org Plugins
- phpMyAdmin documentation phpMyAdmin
- wp db drop WP-CLI Command Reference
- Removals and SafeSearch reports Tool Search Console Help
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


