Table of contents
Staging is a full copy of your website (files + database) running at a separate address, hidden from Google and customers, where you test updates, new plugins and design changes before moving them to the live site. Most good hosting providers create staging with one click; without that feature, you can set it up with a plugin or manually. Cost: zero or a few dozen zł a month. Cost of not having it: a store that crashes after an update on Friday at 5:00 p.m.
Thesis: without staging, every update is an experiment on your customers
In July 2026, WordPress forced the 7.0.2 update because of a critical vulnerability. Sites without staging had two options: update blindly or stay exposed. Sites with staging checked the page builder conflict in 15 minutes and updated without risk. If you update on production, you're running a test — except your audience is your customers.
Three ways to set up staging
| Method | Who it's for | Time | Cost |
|---|---|---|---|
| Hosting feature (panel: “Create test copy”) | Anyone with hosting that offers this option — in Poland, most of the better plans | 2–10 minutes | Included in hosting or a few dozen PLN/month |
| Plugin (clones the site to a subdomain or locally) | Hosting without a staging feature | 15–30 minutes | 0–300 PLN/year |
| Manually (copy files + export database + replace URLs) | Unusual configurations, large stores, developers | 1–2 hours | Time |
Our recommendation: the hosting feature. It’s synced with backups, has a “push to production” button and requires no configuration. If your hosting doesn’t have it, that’s a factor when choosing hosting — more important than price.
Step by step (hosting method)
- Create a test copy from your hosting panel. You’ll get an address like
staging.twojadomena.plortwojadomena.pl/staging/. - Secure it: an HTTP password (most panels do this automatically) and
noindex— staging in Google’s index is a duplicate of your entire site. - Disable email sending and integrations that “do things”: payment webhooks, wholesaler sync, newsletter sending. A staging site with an active courier integration can generate real shipping labels.
- Make your changes: updates, a new plugin, rebuilding a section.
- Test using the checklist below.
- Push to production — but carefully (see “The push-to-production trap”).
What to test on staging — checklist
- [ ] Home page, 2 service pages, 1 post — no errors in the browser console
- [ ] Contact form — sends (to a test address)
- [ ] Menu, search, filters
- [ ] Store: add to cart → checkout → test order (gateway in sandbox mode)
- [ ] Admin panel and editor (Elementor / blocks)
- [ ] Mobile version of key sections
- [ ] Speed: compare PageSpeed before and after — a new plugin version can add 200 kB of scripts
- [ ] PHP logs: no new warnings
The full testing procedure after a WordPress 7.x update is in our article on what WordPress 7 changes.
The migration trap: staging → production
This is where staging does more harm than good if you don’t understand it. The “push to production” button copies the entire database from staging — including its state from an hour ago, when you made the copy. If in the meantime, on the live site:
- orders came in through the store,
- someone submitted a form,
- a post was published,
- a user registered
— that data will be overwritten and lost.
Three strategies to avoid this:
| Strategy | When |
|---|---|
| Push only files (theme, plugins), not the database | Updates and code changes — 90% of cases |
| Freeze production during the push (maintenance mode, 10–15 minutes) | Database structure changes, new fields |
| Repeat the changes manually on production after testing | Changes to content and settings — staging is for testing only |
In a store, never overwrite the production database with the staging database. Context: the 3-2-1 backup strategy — staging doesn’t replace backups, it complements them.
Staging and a WooCommerce store — three additional rules
- Payment gateway in test mode — for several versions now, WooCommerce can detect staging and disable payments; check it, don’t assume.
- Mark test orders in a note so that if databases are ever merged, they don’t end up in your accounting.
- Disable integrations (BaseLinker, wholesalers, couriers) on staging — or connect test accounts. We explain how such an integration works in our article on BaseLinker in WooCommerce.
When staging isn't enough
Staging tests changes. It doesn't test load — that's the job of a performance test, which we cover in our Black Friday checklist. Nor does it test how a change will affect conversion — that's what an A/B test on production, with real users, is for.
From our experience
Every site we look after has a staging environment, and no update bigger than a security patch goes to production without being tested on a copy. The most common problem staging catches: a new plugin version conflicting with the page builder, which only shows up in the editor — on the front end everything looks fine.
If your hosting doesn't offer staging or you're not sure how to use it safely, as part of our website maintenance service we set it up and test every change before it goes live.
FAQ — staging and test copies
It shouldn't be. It must have noindex and ideally HTTP password protection. An indexed staging site is a duplicate of your entire website and can drag down the original's rankings — check this once a month by typing into Google site:staging.twojadomena.pl.
Yes — it's a second full copy of your site on the same server. For large stores, it's worth creating one for the duration of testing and deleting it after you push the changes, so it doesn't take up space and resource limits.
Yes, local WordPress tools are free. The difference: a local environment doesn't reflect your server configuration (PHP version, cache, limits), so some problems only show up on the hosting. Staging on the same hosting as your live site is more accurate.
Author: Adrian Kamiński — Websky Studio, Poznań. WordPress website and store maintenance — every change tested on a copy before it goes live.
Your feedback
Was this article helpful?
One click — it helps me choose future topics.

