How-to · Beginner · 10 minutes to create, saves hours routinely
How to Use a WordPress Staging Site
Rehearse every risky change on a copy no visitor will ever see — a practical, jargon-free walkthrough with the classic mistake flagged before you make it.
Straight answer first
The job: rehearse every risky change on a copy no visitor will ever see. Time to allow: 10 minutes to create, saves hours routinely. Skill needed: beginner.
Below you get the exact steps, the classic snag, and a tip from the support desk. Where our platform handles a step for you, the guide says so rather than making you do the robot's work.
Written by the Hosting Seller staff · Checked 1 August 2026
Beginner
Difficulty level
Quick
Time to allow
5
Stages
24/7
Help at any hour
You do not need to be technical for this. The walkthrough is written for first-timers, tested on our own platform, and honest about which parts are genuinely fiddly and which are merely unfamiliar.
Rule of the road: read the snag section before you begin rather than after. It is harvested from the tickets of people who did it the other way round.
The route, start to finish
Here is the route in full: clone the site in one click, make sure it's sealed, break it on purpose, push it live deliberately and re-clone before each session.
No stage needs code or a terminal unless the guide says so outright, and where it does, the exact commands are printed. The full step-by-step sits below; the sections around it give the context that makes it stick.
Read this before the first click
Pushing a week-old staging database over a live WooCommerce shop. The push does exactly what it was told and takes a week of real orders with it. Shops push code; shops never push data backwards.
Forewarned really is forearmed here. This one mistake accounts for most of the frustration the subject produces, and it is entirely avoidable once somebody names it.
One habit that makes this easy for good
Staging doubles as a viewing room. Send a client the staging address for sign-off, collect the changes they want, and then push exactly what was approved with nothing extra sneaking through.
It costs a minute now and pays that back every time the job comes round again — which, like most hosting jobs, it certainly will.
How our platform shortens this
Several steps in this guide exist only because hosting historically made you do them. On our plans SSL issues itself, backups run daily without being asked, and one-click installers replace the manual setup entirely. What is left is the part that is genuinely yours.
Stuck halfway through at an odd hour? That is exactly what round-the-clock human support is for — tell us where you are in this guide and we will pick it up from there.
The hosting this guide is written against
Tutorials age badly when they are written against imaginary hosting. These are written against ours: the same panel, the same installer and the same defaults you will meet.
What you pay on day one is what you pay at renewal, so the year-two invoice holds no surprises worth opening early.
- Step by step, tested exactly as printed
- The snag flagged before you reach it
- The dull steps are already automated
- People on hand at any hour if you stall
Why Hosting Seller
On every plan, as standard
Help on the counter
Stuck on step three at midnight? Support answers at any hour, mid-guide included.
Automation where it belongs
SSL, backups and installs run themselves here, so the guide covers only what is genuinely yours to do.
The snag, named early
The classic mistake for this exact job is flagged before step one, so 10 minutes to create, saves hours routinely stays 10 minutes to create, saves hours routinely.
The undo is always named
Where a step could bite, the guide says so and tells you how to put it back again.
Written from real tickets
Our guides come off the support desk, so the snags flagged here are the ones people genuinely hit.
Scoped honestly
Rehearse every risky change on a copy no visitor will ever see is a beginner-level task — this guide budgets 10 minutes to create, saves hours routinely and says which steps the platform absorbs.
First Steps
From choosing to live
- 1
Clone the site in one click
One click in the hosting panel copies the files and the database to a private staging address. Our WordPress plans allow up to ten of these, so there is no need to ration them.
- 2
Make sure it's sealed
Staging should ask for a login or block search engines, ideally both. Check it, because a staging copy sitting open to the world is duplicate content and a data leak wearing the same coat.
- 3
Break it on purpose
Run the update you are nervous about, try the redesign, audition three plugins in a row. A failure on staging is information. The same failure on production is an incident with customers watching.
- 4
Push it live deliberately
Either push selectively — code and design, never order data — or repeat the steps you just verified on production by hand. Which one fits depends on whether the site takes orders while you work.
- 5
Re-clone before each session
A stale staging copy tests against last month's site and tells you nothing useful. Refresh it before any significant work so the rehearsal matches the conditions on opening night.
In the Box
Packed with every plan
- A backup taken daily, with restores you run yourself
- NVMe SSD storage on every shelf, not just the top one
- A 99.9% uptime commitment, watched by monitoring day and night
- A domain free for year one when you order annually
- Spam and virus filtering fitted to every mailbox
- Site migration done for you by our staff, at no charge
- One-click installs for WordPress and 400+ other applications
- Staging copies so changes get tested before they go live
- LiteSpeed caching running at the server, not bolted on by plugin
- SSH, Git and Composer on the plans built for developers
Across the Counter
The questions we get asked most
When does staging actually earn its keep, and when is it fuss?
Money and trust decide it. Anything touching checkout, memberships or a major version gets staged. Fixing a typo or publishing a post does not. When staging is one included click, the cost of that judgement drops to nearly nothing.
What happens to content added to the live site while I work?
That is the conflict everyone hits. Selective pushes — files only, or specific tables — avoid trampling fresh production content. On content-heavy sites, apply the change forward onto production instead of pushing a database backwards over it.
What does round-the-clock support actually stretch to?
People at the counter at every hour, and a scope that takes in the practical work: mailbox setup, DNS records, WordPress trouble, restores. Not 'the server responds, ticket closed'. Ask us something hard before you order — the reply is a fair sample of what you would get afterwards.
Do you shift an existing site across at no charge?
We do. Open a ticket with the login details for your current host and the whole lot comes over: files, databases, mailboxes and configuration. You check the copy before DNS changes hands, and the old site keeps serving customers until the new one takes the traffic, so nobody ever sees a gap.
What if the site outgrows the plan I bought?
You move up in place. Plan changes are made from the client area with no migration and no downtime, and the range runs from small shared accounts through VPS to whole dedicated servers. Growing becomes a line change on your account rather than a hunt for a new host.
Where do the servers actually sit?
Our hosting runs from European datacentres with London at the centre, behind server-level caching that keeps cached pages quick for visitors anywhere. For most sites the build of the platform — NVMe disks, LiteSpeed, sensible numbers of accounts per machine — decides the speed far more than the postcode does.
Who actually runs the company?
Hosting Seller is a trading name of Bohzo Ltd, a company registered in England and Wales — a real business with a public record and terms published under English law. Looking that up is worth doing about any host before you hand over your domain.
Read next
How to Set Up a Cron Job
Put a script on a schedule and trust it to run without you watching — intermediate level, about 15 minutes.
How to Set Custom Error Pages
Turn a dead end into a signposted page that keeps the visit alive — beginner level, about 30 minutes.
Drupal Hosting
Drupal hosting with Composer, Drush and the PHP version set per site.
PHP Hosting
Pick the PHP version site by site, on quick NVMe hardware.
Packing up and moving host? Take our checklist.
A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.
Do the launch properly this time.
Free SSL, a free move in, renewals charged at the order price, and human support around the clock. That is the whole offer.
See the plans