# Staging Environments UK: Test Before You Go Live

Source: https://dijihost.co.uk/staging-environments/
Updated: 2026-11-12

> dijitul sets up staging environments for UK websites, quoted to your site. We create a private copy on a subdomain, password protect it, keep it out of search engines, stop it sending real emails or payments, and push tested changes to live with a restore point first. It works for WordPress through Plesk WP Toolkit and for other platforms.

## Key facts

- Quoted to the site and how often you use staging
- Staging copy on its own subdomain, such as staging.yourdomain.co.uk
- Password protected, with search engine indexing turned off
- WordPress staging through Plesk WP Toolkit Clone and Sync
- Restore point on live before every push
- Outgoing email and live payments disabled on staging
- Works for WordPress, WooCommerce, PHP apps, Laravel and Node.js

## What a staging environment is

A staging site is a private copy of your live website where you test plugin updates, new designs, PHP upgrades or code changes before your customers see them. A development copy is the same idea, used earlier in a project. When the change works on staging, it is pushed to live. When it does not, nothing on the live site has broken. Staging matters most for shops, booking systems and membership sites, where an update that breaks checkout costs real money every hour it is live.

## How we set it up

- **Its own address**, usually staging.yourdomain.co.uk, with its own SSL certificate and database.
- **Password protection** on the whole staging site, so only you and your developers can see it.
- **Noindex**: search engine indexing turned off. Google's documentation says a noindex rule only works if the page is not blocked in robots.txt, because Google must be able to crawl the page to see the rule. Password protection is the stronger safeguard, so we use both.
- **No real emails**: outgoing mail is disabled or caught, so customers do not get test order confirmations or newsletters.
- **Payments in test mode**: Stripe, PayPal and other gateways switched to sandbox keys.
- **Scheduled tasks** reviewed, so staging does not run live jobs such as stock syncs.

## WordPress staging with WP Toolkit

On our Plesk servers, WP Toolkit does much of the work. Plesk's own guide describes it:

- **Clone** the live site. By default WP Toolkit uses a subdomain with the "staging" prefix.
- On the clone, turn off search engine indexing and turn on password protection, as Plesk recommends.
- Make and test your changes.
- **Sync** back to live: files, database or both. For the database you choose "All tables", "Selected tables" or "New tables". The first two can overwrite live data; "New tables" leaves existing live data alone.
- Create a **restore point** before syncing, and use maintenance mode during the sync if the site is busy.

For WooCommerce, pushing the whole database would overwrite orders placed while you were testing, so we push files and only the tables that changed. See [WordPress maintenance](https://dijihost.co.uk/wordpress-maintenance/) for ongoing updates.

## Other platforms

- **PHP apps and older sites**: a copy on a subdomain with its own database. Useful before a PHP version change, see [legacy PHP hosting](https://dijihost.co.uk/legacy-php-hosting/).
- **Laravel, Symfony and Node.js**: a staging branch deployed from Git, with its own .env file and database, then the same release process to live.
- **Next.js and headless setups**: separate staging builds and API endpoints, so content editors can preview safely.

*Sources, checked 11 November 2026: [Plesk WP Toolkit: staging and production](https://www.plesk.com/blog/product-technology/plesk-wp-toolkit-course-part-3-staging-production-video/); [Google: block indexing with noindex](https://developers.google.com/search/docs/crawling-indexing/block-indexing).*

## Pricing

Staging is quoted to fit the site, whether it lives on our £1 a day + VAT plan or on a [managed VPS](https://dijihost.co.uk/managed-vps/). A one-off staging copy before a redesign is a small job; a permanent staging environment with a Git release process is a bigger one. Tell us your platform and how often you release, and we will price it. Every site we host also has daily backups kept for 14 days, see [website backups](https://dijihost.co.uk/website-backups/).

## FAQs

### What is a staging site?

A staging site is a private copy of your live website where you test changes such as plugin updates, redesigns or PHP upgrades before they go live. When the changes work, they are pushed to the live site. dijitul sets up staging copies for UK websites, quoted to the site.

### How do I stop Google indexing my staging site?

Use password protection and a noindex rule together. Google says noindex only works if the page is not blocked by robots.txt, because Google must crawl the page to see it. Password protection stops anyone, including search engines, seeing the site at all.

### Can I push a WordPress staging site to live?

Yes. On Plesk, WP Toolkit syncs files, the database or both from staging to live, with options for all tables, selected tables or new tables only. Create a restore point first. dijitul handles this for WordPress sites it hosts.

### Will pushing staging to live overwrite my WooCommerce orders?

It can, if you push the whole database. Orders placed on the live site while you were testing would be lost. Push files plus only the tables that changed, or use the New tables option, and take a restore point first.

### Does staging send emails to my customers?

It can if nobody turns it off, because a staging copy has the same settings as live. dijitul disables or captures outgoing email on staging, switches payment gateways to test mode and reviews scheduled tasks so the copy cannot affect real customers.

## Pricing and ordering

This is quoted to fit. Request a quote at https://dijihost.co.uk/quote/ or call 01623 650333.
