Skip to main content

Walkthrough · Beginner · 10 minutes to set up, and hours saved on a regular basis

How to Use a WordPress Staging Site

Test every risky change on a copy the public never sees — a hands-on walkthrough in plain words that names the classic mistake before you reach it.

The short answer

The job: test every risky change on a copy the public never sees. Time to set aside: 10 minutes to set up, and hours saved on a regular basis. Skill needed: beginner.

Below are the precise steps, the classic stumble, and one tip from the support desk. Wherever the platform already does a step for you, the guide says so rather than handing you a machine's chores.

By the Hosting & Domains team · Reviewed 18 August 2026

Beginner

Experience required

5

Stages, start to finish

Free

Support included

Proven

On the platform itself

No technical background needed. This walkthrough was written for first-timers, proven on our own hardware, and honest about which parts are genuinely tricky rather than merely unfamiliar.

First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.

The route, mapped end to end

Set out end to end, the route is: clone it in one click, make sure it is shut away, break it on purpose, promote deliberately and re-clone before each session.

No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.

One caution before you click anything

Pushing a week-old staging database over a live WooCommerce shop. The push does exactly as instructed and takes a week of real orders with it. Shops push code; shops never push data backwards.

Forewarned is genuinely forearmed here. This one mistake accounts for most of the frustration the topic ever causes — and it disappears entirely once somebody points it out.

The habit that keeps this easy for good

Staging doubles as a preview room. Give clients the staging URL for approval, collect the changes they want, then promote precisely what was signed off with nothing extra slipping along.

A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.

Where this platform takes work off you

Some steps in this guide exist only because hosting traditionally forced them on you. Here the SSL issues itself, the copy is taken daily without being asked, and one-click installers remove the manual setup. What is left is the part that was always genuinely yours.

Stopped mid-guide at an awkward hour? That is exactly what round-the-clock support is for — say which step you are on and we take it from there.

A developer at the terminal with real SSH access to the box

The hosting these steps were tested on

Every walkthrough in this library is run on the platform we actually operate — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen rather than gesturing at it from a distance.

A free SSL certificate comes with every plan and reissues itself before the old one lapses — the padlock is never yours to diarise.

  • Every step checked exactly as published
  • The snag named before it arrives
  • The dull steps taken out of your way
  • People reachable at any hour you stall

Why Hosting & Domains

Standard on every plan

Help that keeps your hours, not ours

Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.

The dull parts automated

SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.

The snag, flagged up front

The classic error for this particular task is named before step one, which is how 10 minutes to set up, and hours saved on a regular basis stays 10 minutes to set up, and hours saved on a regular basis.

Every undo written out

Any step that could bite is marked, together with the exact way to wind it back.

Taken from real tickets

These guides came out of the support queue, so every snag flagged is one people genuinely hit.

Honest about how big it is

Test every risky change on a copy the public never sees is a beginner-level job — set aside 10 minutes to set up, and hours saved on a regular basis, with the platform-absorbed steps marked.

Quick Start

Order placed to site online

  1. 1

    Clone it in one click

    One click in the hosting panel copies the files and database to a private staging URL. Our WordPress plans include up to ten of them, so there is no need to be sparing.

  2. 2

    Make sure it is shut away

    Staging should ask for a login or keep search crawlers out, and ideally both. Check it, because an exposed staging copy is duplicate content and a data leak in one package.

  3. 3

    Break it on purpose

    Run the update that worries you, try the redesign, audition plugins one after another. A failure on staging is information. The same failure in production is an incident with witnesses.

  4. 4

    Promote deliberately

    Push selectively, code and design but never order data, or repeat your verified steps by hand on production. Which one is right depends on whether orders keep arriving while you work.

  5. 5

    Re-clone before each session

    A stale clone is testing last month's site, which proves nothing at all. Clone again before any serious work so the rehearsal matches the live conditions it stands in for.

Built In

Fitted to every plan

  • PHP versions set per site from the control panel
  • Upgrades applied in place, with no migration when you change plan
  • cPanel, which is what most of the industry already runs
  • A daily copy, with restores you run yourself from the panel
  • NVMe SSD storage on every tier, not only the dear ones
  • A renewal figure identical to the one you registered at
  • WordPress and 400+ further applications installed in one click
  • Spam and virus screening on every mailbox by default
  • Your existing site brought across by our engineers, at no charge
  • The name's first year included when you order annually

Frequently Asked

The questions that come up most

When does staging earn its keep, and when is it overkill?

Money and trust decide. Checkout, memberships and major versions all go through staging without exception. A typo fix or a new post does not. With staging one included click away, that judgement costs next to nothing.

What about content published live while I am testing?

That is the classic collision. Selective pushes, files only or chosen tables, keep fresh production content from being overwritten. On content-heavy sites, apply the change forward onto production rather than pushing a database back over it.

What does round-the-clock support actually cover?

A reply from a person at any hour, covering the practical jobs: setting up a mailbox, a DNS record, a WordPress fault, a restore. Not 'server is up, closing ticket'. Put a hard question to us before you buy — the answer is a fair sample of what follows.

Will you move my existing site free of charge?

Yes. Open a ticket with the login for your current host and we bring the lot across — files, databases, mailboxes, configuration. You check the copy before DNS moves, and the old site keeps taking traffic right up to the moment the new one serves it, so nobody meets a gap.

Keep reading

Changing hosts? Run through our checklist first.

A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.

What arrives is the checklist, and then the occasional note on keeping a site quick. Leave whenever you like; the privacy policy covers the rest.

Your site has earned better hosting.

Every plan carries the essentials other hosts bill as extras — and support that answers.

View WordPress Hosting plans