This post contains affiliate links. If you buy something through one of them, Veravix may earn a commission at no extra cost to you.
A plugin update goes through on a Tuesday morning, the checkout page quietly stops working, and the first you hear of it is an email from a customer. A staging site exists to move that mistake somewhere nobody can see it. I read the staging documentation of five hosting companies on 14 November 2026, from the Netherlands, to see which plans include the tool and which leave you to build it yourself. The answer is less uniform than the marketing pages suggest.
A copy of your site that only you can reach
A staging site is a full copy of your WordPress site, files and database, placed at a private address such as a subdomain, where you can update plugins, change themes or test a new PHP version without touching the live site. When the change works, you push it to the live site. When it breaks, you delete the copy and nothing happened. Bluehost’s own guide splits the ways to get one into three: a host-built tool that clones the site and gives you a deploy button, a staging plugin, or a manual copy to a subdomain or local machine. The rest of this post follows that split, because which method you get depends on your plan.
Which plans include a staging tool
These are the pages I read, in the order a shopper might meet them. Plan names and limits change, so use this as a map and confirm on the host’s page before you pay.
| Host | Staging tool | What the host’s own page says |
|---|---|---|
| Hostinger | Built in, from the Business plan up | Its support article says you can create and manage staging from the dashboard if you have a Business web hosting plan or higher. The documentation adds that entry-level plans see an upgrade prompt, that creating the copy can take up to 15 minutes, and that WordPress Multisite is not supported. |
| SiteGround | Built in, not on StartUp | Its plan-comparison table shows “WordPress staging” as a dash on StartUp and a tick on the three plans to its right. The same page describes GrowBig as adding on-demand backups and staging on top of StartUp. |
| Bluehost | Built in on its managed WordPress plans | Its Managed WordPress comparison lists “WordPress Staging Site” as Yes on all three plans in the standard table. Its staging guide still warns that host-based staging is only available on plans that include it. |
| DreamHost shared, VPS and dedicated | Manual | Its knowledge base says that on these plans you create the copy yourself on a dreamhosters.com subdomain. |
| DreamHost DreamPress | Built in | The same article says DreamPress, its managed WordPress plan, includes staging. |
The pattern is that the cheapest shared plan is where staging usually stops. Hostinger’s WordPress hosting page lists three plans (Premium, an unlimited-websites plan above it, and Cloud Startup), and the support article puts the staging tool at Business and above, so the Premium plan is the one that leaves you without it. SiteGround draws the same line one step above StartUp. If you plan to run a store or a site with several plugins, count that gap into the price of the plan you choose, because a single bad update on a live shop costs more than the difference.
What to do when your plan has no staging tool
You have two options, and both cost you some effort.
- A staging plugin. WP Staging is listed in the WordPress.org plugin directory and creates the copy from your dashboard. Bluehost’s guide warns that free versions of staging plugins often limit or leave out the push-to-live step, so test the whole round trip on something unimportant first.
- A manual copy. Copy the files and the database to a subdomain and update the site URL in the copy. DreamHost’s article stresses this step, because a WordPress database stores the full address of the site inside it. Bluehost lists the typical misses: URL replacements, file permissions and search engines indexing the copy.
The manual route is the one where you most need a backup before you start. If you do not yet have a restore you trust, how to restore a WordPress backup is worth reading first.
What a staging copy does not protect
A staging site is a snapshot, and the live site keeps moving while you test. That has one consequence that no host page spelled out in the text I read, so this is my own reasoning from how WordPress stores things: orders, comments and form entries that arrive on the live site after the copy was made exist only in the live database. If you push a staging database over the live one, those newer records can be overwritten. On a blog this rarely matters. On a store it can, so for a shop prefer pushing only files, or choose a quiet hour and take a backup of the live site first.
Staging is also not a performance test, since the copy usually shares the server with the live site, and it does not cover everything a change touches, such as email sending or payment gateways pointed at live accounts. Check those settings on the copy before you click anything that sends or charges.
Three jobs where a staging copy earns its keep
- A PHP upgrade. Raise the version on the copy and click through the pages that use the most plugins. Checking which PHP version your WordPress site runs shows how to find the current one first.
- A theme or page-builder change. Layout problems show up on a copy long before a visitor sees them.
- A plugin update after a long gap. One plugin three major versions behind is the update most likely to break something, so it is the one to run on the copy first.
Whichever route you end up with, tick “Discourage search engines from indexing this site” under Settings, then Reading, on the copy, and after every push open the same screen on the live site and make sure the box is cleared, so a “do not index” flag never travels into your real site. Staging only pays for itself if the habit sticks, so the cheapest plan that includes the tool is usually a better buy than the cheapest plan plus a plugin you have to maintain.
Checked for accuracy and updated on 14 November 2026.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.