{"id":20384,"date":"2026-11-02T12:22:21","date_gmt":"2026-11-02T11:22:21","guid":{"rendered":"https:\/\/stage.surver.nl\/kennisbank\/wordpress-staging-omgeving\/"},"modified":"2026-11-03T14:51:08","modified_gmt":"2026-11-03T13:51:08","slug":"wordpress-staging-environment","status":"publish","type":"kennisbank","link":"https:\/\/stage.surver.nl\/en\/kennisbank\/wordpress-staging-omgeving\/","title":{"rendered":"WordPress Staging Environment: What It Is and How to Use It"},"content":{"rendered":"
\"WordPress<\/figure>\n\n\n\n

A major update for WooCommerce or your page builder is coming up, and you\u2019re hesitant to click the button because you don\u2019t know what will still work afterward. A staging environment is a separate copy of your WordPress website where you can test updates, new plugins, and changes before deploying them to your live site. This prevents any errors from being immediately visible to visitors and customers. I\u2019ll explain when you need one, how to set one up, and how to deploy changes to your live site without losing any orders.<\/p>\n\n\n\n

What is a staging environment?<\/h2>\n\n\n\n

A staging environment, also known as a staging site, is a copy of both the files and the database of your live site, isolated on a subdomain or in a subfolder. In this context, your live site is referred to as the production environment. I always think of staging as the dress rehearsal for a performance. Everything goes just like on opening night, except there\u2019s no audience in the theater. If an update breaks the copy, no one will notice, and you\u2019ll have plenty of time to figure out why. Staging is part of good hosting, just like backups and monitoring. Read more What is managed WordPress hosting?<\/a>.<\/p>\n\n\n\n

Staging is often confused with other types of copies, even though each serves a different purpose.<\/p>\n\n\n\n

Form<\/th>What It Is<\/th>What is it for?<\/th>For whom<\/th><\/tr><\/thead>
Staging environment<\/td>Protected copy on the same hosting service<\/td>Testing Updates and Changes<\/td>Every site administrator<\/td><\/tr>
Local development environment<\/td>A copy on your own computer<\/td>Building and Programming<\/td>Developers<\/td><\/tr>
Clone<\/td>A separate copy of your installation<\/td>Basis for staging or a second site<\/td>Site Administrators<\/td><\/tr>
Backup<\/td>File and Database Snapshot<\/td>Rolling Back After an Error<\/td>Everyone<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

A backup does not replace staging. A backup allows you to recover data after the fact, while staging prevents things from going wrong.<\/p>\n\n\n\n

When should you test something on the staging environment first?<\/h2>\n\n\n\n

You should test on the staging environment whenever you make a change that could affect how your site works\u2014not just when you make changes to the content. Examples include a major WordPress update, a new version of WooCommerce, a resource-intensive new plugin, or a theme change. Also, a higher PHP version<\/a>, custom code changes, and, of course, a redesign should be done on a copy first. Editing a text or publishing a blog post doesn't have to go through staging. That's just content, and you can publish it directly to the live site.<\/p>\n\n\n\n

If I could give you just one piece of advice, it would be this: Always test WooCommerce and page builder updates on staging first. These are the updates where I see the most broken checkouts and misaligned pages, precisely because they make deep changes to your site. A small plugin that just adds a widget is fine to update right away if you\u2019ve just made a backup. You can read about how to set up your entire update routine in Updating WordPress Safely<\/a>. Testing on the staging environment is also a standard part of good WordPress maintenance<\/a>, even if you outsource it.<\/p>\n\n\n\n

How to Set Up a Staging Environment<\/h2>\n\n\n\n

You can create a staging environment through your hosting control panel, using a plugin, or manually. Keep in mind that each copy uses additional storage space. Be sure to delete it when you're done; otherwise, after a few months, you'll have a forgotten site with outdated plugins on your account.<\/p>\n\n\n\n

Through your hosting control panel<\/h3>\n\n\n\n

This is the method I recommend to everyone. You don't need any additional plugins, and the copy runs on exactly the same server settings as your live site.<\/p>\n\n\n\n

    \n
  1. Clone your WordPress installation to a subdomain or subfolder using the cloning feature in your hosting control panel or installer, such as Installatron.<\/li>\n\n
  2. Lock the copy and log in to it.<\/li>\n\n
  3. Make the update or change.<\/li>\n\n
  4. Test the site as a visitor would, including on your phone.<\/li>\n\n
  5. Deploy the change to production, as described in the following section.<\/li>\n<\/ol>\n\n\n\n

    Using a plugin<\/h3>\n\n\n\n

    WP Staging is the best-known plugin. The free version clones your site to a subfolder, but pushing to the live site is only available in WP Staging Pro. The downside is that the copy runs within the same installation and the same account. If your hosting provider supports it, I therefore prefer to go with the first option.<\/p>\n\n\n\n

    Manual<\/h3>\n\n\n\n

    To do this manually, create a subdomain, copy the files and the database, and then adjust wp-config.php<\/code> and specify the site URL to restrict access. That's a job for developers. If you don't have any on staff, our webmaster service<\/a> take care of it for you. The technical steps are largely the same as Moving a WordPress Website<\/a>.<\/p>\n\n\n\n

    From staging to production without data loss<\/h2>\n\n\n\n

    With a full push, the staging database overwrites the one on your live site, and everything that has been added to the live site since the clone was created will be lost. This applies to orders, newsletter subscriptions, form submissions, and comments, as well as the user list. For a live e-commerce site, this is the biggest risk of staging, and it\u2019s almost never mentioned. My advice, therefore, is to never blindly restore the entire database. Only push the files, transfer only the database tables that you\u2019ve actually modified, or simply reapply the change to the live site now that you know it works. For online stores, the step-by-step approach is outlined in How to Update WooCommerce Without Breaking Your Checkout<\/a>.<\/p>\n\n\n\n

    Always make a backup of your live site yourself first, because when you restore an older backup, the current state isn't automatically preserved. Then I go through this checklist.<\/p>\n\n\n\n

      \n
    1. Create a full backup and learn how to Restore a backup<\/a> performs.<\/li>\n\n
    2. Deploy the change outside of peak hours.<\/li>\n\n
    3. Place a test order right away and test your forms.<\/li>\n\n
    4. Clear the cache and test the site again, both on your desktop and on your phone.<\/li>\n<\/ol>\n\n\n\n

      If you don't want to do this yourself for your online store, then WooCommerce maintenance<\/a> Take the hassle out of testing and updating.<\/p>\n\n\n\n

      Keep your staging environment isolated<\/h2>\n\n\n\n

      A staging environment must be invisible to Google and must not reach real customers. Without proper isolation, Google will see the same site twice, and the copy will compete with your live site. Therefore, set the following under Settings > Reading<\/strong> the check mark next to Search engines discourage indexing this site<\/strong> (noindex), or protect the copy with a password or IP restriction. The mistake I see most often is that this setting gets carried over to the live site. Then your actual site slowly disappears from Google, and no one realizes why. Some plugins recognize a staging environment by the constant WP_ENVIRONMENT_TYPE<\/code> in wp-config.php<\/code> and then put themselves in a safe position.<\/p>\n\n\n\n

      When it comes to an online store, security measures go beyond Google. Your test data includes real customers and orders, so set the payment provider to test mode and make sure transactional emails aren\u2019t sent to real customers. Nothing is more confusing than a customer receiving an order confirmation for a test order.<\/p>\n\n\n\n

      What we handle as standard at Surver is the cloning feature itself. On all shared hosting plans, you can create a staging environment by cloning your installation in Installatron, and on Surver Cloud, we\u2019ll set it up for you. You can restore backups of your live site on shared hosting free of charge using JetBackup 5 in cPanel. If you want to restore a backup to a copy, please contact our support team. You can read more about the plans on our Managed WordPress Hosting<\/a>. If something did go wrong during the live stream, read about what to do in the event of a Site Down After an Update<\/a>.<\/p>\n\n\n\n

      Frequently Asked Questions<\/h2>\n\n\n\n

      Does a staging environment cost extra?<\/strong><\/p>\n\n\n\n

      With many hosting providers, you can clone your site using the tools that come with your plan. At Surver, Installatron\u2014which lets you clone your site\u2014is included in all shared hosting plans. The WP Staging plugin lets you clone your site for free, but you\u2019ll need WP Staging Pro to push it to production.<\/p>\n\n\n\n

      Is WP Staging safe?<\/strong><\/p>\n\n\n\n

      WP Staging is a widely used plugin from the official WordPress repository. The main risk lies in a copy that remains publicly accessible. So make sure to restrict access to the copy and delete both the plugin and the copy once you're done testing.<\/p>\n\n\n\n

      Does a staging environment affect my SEO?<\/strong><\/p>\n\n\n\n

      Only if Google indexes the copy. If you block it with \"noindex\" or a password, staging will have no effect on your rankings. After each deployment, make sure the \"noindex\" setting hasn't carried over to your live site.<\/p>","protected":false},"excerpt":{"rendered":"

      Er staat een grote update klaar voor WooCommerce of je pagebuilder, en je durft niet op de knop te drukken omdat je niet weet wat er daarna nog werkt. Een staging-omgeving is een afgeschermde kopie van je WordPress-website waarop je updates, nieuwe plugins en wijzigingen test voordat je ze live zet. Zo voorkom je dat […]<\/p>\n","protected":false},"author":2,"featured_media":20518,"template":"","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}}},"kennisbank_categorieen":[52],"class_list":["post-20384","kennisbank","type-kennisbank","status-publish","has-post-thumbnail","hentry","kennisbank_categorieen-hosting"],"acf":[],"_links":{"self":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank\/20384","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank"}],"about":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/types\/kennisbank"}],"author":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/users\/2"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media\/20518"}],"wp:attachment":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media?parent=20384"}],"wp:term":[{"taxonomy":"kennisbank_categorieen","embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank_categorieen?post=20384"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}