What is a staging site?

What it means

A staging site is a rehearsal space. It is a copy of your real website that only you and your team can see. You try things there first, and only move them to the real site once they work.

The real, public site is often called “production” or “live.” Staging sits beside it at a private address, often a subdomain like staging.yourbusiness.com, and is hidden from search engines.

How it works

1. Copy. The live site, including its files and content, is copied to the staging area.
2. Change. You update plugins, try a new design, or rebuild a page on the copy.
3. Check. You click through the pages, test forms and checkout, and look at it on a phone.
4. Push. You publish the changes to the live site, or throw the copy away if the experiment failed.

Staging is not the same as a draft. Most builders let you save an unpublished page, which helps with one new page. But a draft is not a full copy, so you cannot use it to test a site-wide design change or a plugin update.

Code-based tools use a related idea called branches. A branch is a separate line of changes to the code. You work on a branch, review it, and then merge it into the main version that runs the live site.

Why it matters when you build a site

Updates can break things. A theme, plugin or code update can clash with something else on your site. Finding out on staging is far better than finding out from a customer.

Redesigns take time. Staging lets you build a new version over weeks without showing half-finished pages.

Teams need review. A client or manager can approve changes before they go public.

One catch: on a store or a site with forms, the live site keeps collecting orders and entries while you work on staging. Pushing a whole staging copy back can overwrite them. Push only the changes you made, or schedule the push for a quiet moment.

How the big builders handle it

• Webflow. Staging is tied to Workspace plans: the free Starter Workspace includes 2 staging sites, Core ($19 a month billed yearly) includes 10, and Growth ($49 a month billed yearly) includes unlimited staging sites. Webflow also announced Releases site branching at its September 2026 conference, as a beta planned for later in 2026.
• Framer. Pro ($30 a month billed yearly) includes a staging environment and branching with previews, according to its pricing page. Basic does not list it.
• WordPress (self-hosted). Staging depends on your host or a plugin. Our advice from building on WordPress every week: test big theme and plugin updates on a staging copy first, and take a fresh backup before every push.
• AI app builders. These use GitHub branches. v0 works on its own branches and opens a pull request to merge changes. Bolt syncs with GitHub, and branches must be merged on GitHub. Lovable offers two-way GitHub sync.
• Squarespace, Wix and Hostinger. A staging feature is not among the plan details we track for these builders. Ask support before you count on one, and use drafts or unpublished pages where available.

Common mistakes

• Letting search engines index staging. Duplicate copies of your site in Google confuse visitors. Block indexing and password-protect the copy.
• Working on an old copy. Refresh staging from the live site before you start, or you will test against outdated content.
• Editing both copies. Changes made on live while you work on staging can be lost when you push.
• Skipping the phone check. Test responsive design on staging, not after launch.
• No backup before the push. If the push goes wrong, you need a way back.

Related terms

• Website migration: staging is where a new site is built before the switch.
• Plugin: plugin updates are the most common reason to use staging on WordPress.
• Uptime: testing first keeps your live site up.

Comparing design tools? See Webflow vs Framer.