Term · Web & development
Staging environment
A staging environment is a private copy of a website or application, configured as closely as possible to the live ("production") system, where new features, updates and fixes are tested before real users see them.
[ 01 ]
Explained
Why it matters
- Bugs are found by the team, not by customers.
- Clients can review and accept work in progress.
- Updates to platforms and plugins can be tested safely.
- Migrations and launches can be rehearsed.
Good practice
- Same software versions and configuration as production.
- Password-protected or restricted by network, and excluded from search engines.
- Payment providers in test mode; emails to test inboxes; integrations pointed to test systems.
- No unprotected real personal data — use anonymised or test data.
- A visible marker so nobody confuses it with the live site.
Typical environments
- Development — developers' own machines or shared development servers.
- Staging — integrated, production-like testing and client review.
- Production — the live system.
Deployments move the same code through these environments, ideally automatically. See CI/CD and staging and testing before release.
[ 02 ]
FAQ
Frequently asked questions
Can staging be indexed by Google?
If it is public and linked from anywhere, yes. Password protection is the reliable safeguard.
Do small sites need staging?
If they have forms, payments or regular updates, yes. Many hosting providers offer staging copies for common CMSs.