What Is a Staging Site and Why Use One
A staging site is a copy of your website used for testing changes before pushing them to live production — without affecting real users. Softaculous on AsiaGB includes powerful, easy-to-use staging features that let you:
- Test theme, plugin, or core updates before going live
- Test new features without disrupting real users
- Debug issues in a non-production environment
- Test migrations from another hosting provider
Key Fact: Softaculous on AsiaGB includes Staging and Clone features free with every Hosting plan, so you can test before deploying to live production.
Cloning Your Website with Softaculous
The Clone feature in Softaculous lets you copy your entire website (files + database) to another domain or subdomain with ease.
Steps to Clone a Website
- Access the Softaculous Management Panel
- Find the installation you want to clone (e.g., WordPress)
- Click the "Clone" button (or the copy icon next to the Edit button)
- Select the destination Clone URL, such as:
- Clone to Subdomain:
staging.example.com - Clone to Folder:
example.com/staging
- Clone to Subdomain:
- The system will ask whether to clone both Files and Database or Files only — cloning both is recommended
- Click "Clone" and wait approximately 2–5 minutes depending on your website size
- When complete, Softaculous will show "Cloned Successfully" with the destination URL
Tip: After cloning to your staging URL, add <meta name="robots" content="noindex, nofollow"> to the staging site to prevent Google from indexing it.
Creating a Staging Site on a Subdomain
The recommended approach is to create a staging site on a subdomain, which provides clear separation from your production site.
Steps
- First, create a subdomain in DirectAdmin:
- Go to DirectAdmin > "Subdomain Management"
- Create a subdomain like
staging.yourdomain.com
- In Softaculous, use the Clone feature with the target URL set to your new subdomain
- After cloning, verify the staging site works correctly
- Make changes and test on the staging site
- Once satisfied, push the changes to production (see Push to Live below)
Testing Plugins and Themes on Staging
Before updating or installing plugins/themes on your production site, always test on staging first:
- Install the plugin or theme on your staging site
- Test all website functionality thoroughly
- Check for JavaScript errors, layout breaks, or database errors
- Test across different screen sizes (mobile, tablet, desktop)
- Only after everything works correctly, install on production
Caution: Remember to sync the database between staging and production before pushing, as the production database may have new data not present in staging.
Push to Live — Deploying Changes from Staging to Production
Softaculous includes a "Push to Live" feature that makes it easy to deploy staging changes to your production site.
How to Use Push to Live
- Access the Softaculous Management Panel
- Find the Staging Installation you have finished testing
- Click the "Push to Live" button
- Select the Production Installation you want to update
- Choose what to push:
- Files Only: Push only files (suitable when no database changes were made)
- Database Only: Push only the database
- Files + Database: Push both (caution: this will overwrite the production database)
- Click "Push" and confirm
- Once complete, immediately check your production site to confirm everything works correctly
Critical: Always back up your production site before pushing from staging. If something goes wrong after the push, you will be able to restore it.
Using Clone for Development and Testing
Beyond staging, Softaculous Clone can serve other purposes:
- Create a development environment: Clone to
dev.yourdomain.comfor web developers - Test migrations: Clone first, then test migration scripts on the clone before doing it on production
- Simple snapshots: Clone to a folder to keep a snapshot of your website at a particular point in time
- Client demo sites: Clone production to a subdomain for clients to preview changes
Staging vs Production Comparison
| Aspect | Staging Site | Production Site |
|---|---|---|
| Purpose | Testing and development | Live users |
| Google Index | Must be noindex | Must be indexed |
| Access | Dev team only | General public |
| Changes | Test here first | Only tested changes |
| Backup | Not critical (re-clone as needed) | Must back up always |
Best Practices for a Staging Workflow
- Always clone from the latest production: Do not use an old staging copy. Re-clone from the latest production before each test session.
- Hide staging from search engines: Add noindex/nofollow and consider adding basic auth password protection.
- Match the production environment: Staging and production should use the same PHP version and database version.
- Document changes: Keep notes on what was changed in staging so other team members know what to expect.
- Back up before every push: Always back up production before pushing from staging.
Summary: Softaculous staging workflow on AsiaGB lets you safely test changes before going live. Use Clone to create a staging site, test your changes, then use Push to Live to deploy to production with ease.
Try the Staging Workflow on AsiaGB + Softaculous Today
Softaculous Full Edition is free with every AsiaGB Hosting plan. Full Clone and Staging features included — safely test before deploying to production.
View AsiaGB Hosting Plans