How to Create a WordPress Staging Site Before Updating Plugins or Themes Print

  • wordpress, staging, backup, cpanel
  • 0

Test plugin and theme updates on a staging copy of WordPress before changing your live site. Pakish accounts may offer cloning in WordPress Manager by Softaculous; if not, use a password-protected subdomain staging environment.

Back up first

  1. Download files and export the database — follow WordPress backup and restore or cPanel backup download.
  2. Confirm backup date and time before continuing.

Option A: WordPress Manager staging or clone (if available)

  1. Open WordPress Manager by Softaculous in cPanel.
  2. Select your production WordPress installation.
  3. Look for Clone, Staging, or similar tools.
  4. Choose a staging subdomain such as staging.yourdomain.com.
  5. Wait for the clone to finish, then log in to the staging /wp-admin/ URL.

Option B: Manual subdomain staging

  1. In cPanel, open Subdomains and create staging.yourdomain.com.
  2. Copy WordPress files from production to the staging document root.
  3. Duplicate the database in phpMyAdmin and update wp-config.php on staging with the new database name, user, and password.
  4. Run a search-replace on the staging database for the site URL (use a trusted WordPress migration plugin or Softaculous tools when possible).

Protect staging from search engines

  • Enable Search engine visibility discouragement in staging Settings → Reading, or add Disallow: / to staging robots.txt.
  • Password-protect the staging directory in cPanel Directory Privacy when handling sensitive data.

Test updates safely

  1. On staging only, update plugins, themes, and WordPress core one group at a time.
  2. Check key pages, checkout, and forms after each change.
  3. Review Select PHP Version if updates require a newer PHP release.

Deploy to production

  1. Take a fresh production backup immediately before deployment.
  2. Push approved changes from staging to production using your clone tool, migration plugin, or controlled file/database sync.
  3. Never overwrite production blindly — verify database names and paths to avoid deleting live customer data.

If cloning tools are unavailable or staging breaks email on your domain, contact Pakish support with your domain and whether you need a temporary subdomain only for testing.


Was this answer helpful?

« Back

Powered by WHMCompleteSolution