Home/HighLevel/Features/Sites/How to create a WordPress staging environment in HighLevel

Funnels, Websites and Forms

How to create a WordPress staging environment in HighLevel

In short

A WordPress staging environment in HighLevel is a duplicate of your live site that lives on a separate URL. It lets you test plugins, themes, content changes, and settings without affecting the production site. When satisfied, you can push all staging changes to the live site with a single action.

AreaSites · Wordpress
Used forMarketing agency, Ecommerce boutique, Consulting firm
Setup steps9 steps in 1 task
Last updatedNovember 16, 2026

01Who this is for

  • Digital agencies that manage many client WordPress sites, can test updates safely before going live.
  • Solo entrepreneurs maintaining their own WordPress site, can experiment with design changes without risking downtime.
  • In house marketing teams, can collaborate on new content or features in isolation from the public site.

02Staging environment access, explained

The staging feature creates a full copy of a WordPress site, including files, database, and configuration, on a separate server location. The copy appears at its own URL and provides its own admin login, so any modifications stay isolated until you decide to publish.

Staging lives under the Sites > WordPress section of a subaccount. From there you can toggle between the live and staging views using a selector in the top right header. Publishing pushes every change from the staging copy to the live site and cannot be undone. The process usually completes within a few minutes.

Only certain functions are available in each environment. Plugins, themes, users, debugging tools, and server settings are present in both live and staging. Domain management, production analytics, and subscription cancellation exist only on the live site, while a dedicated staging URL and isolated user messaging are exclusive to staging.

03How businesses use staging environment access

  • Marketing agency. The agency creates a staging copy of a client’s WordPress site, installs a new theme, and runs functional tests. After confirming the design works, the agency clicks Publish to copy the changes to the client’s live site.
  • Ecommerce boutique. The boutique adds a payment plugin in the staging environment and verifies checkout flow without exposing shoppers to potential errors. Once the transaction process is verified, the boutique publishes the update.
  • Consulting firm. The firm uses the staging URL to let multiple team members edit content simultaneously. After reviewing the drafts, the firm uses the Publish action to move the finalized pages to the live website.

04The numbers and rules that matter

  • Available in Both Live & Staging: Plugins, Themes, Users, WordPress Debugging, Server Settings (phpMyAdmin, PHP version), WordPress Management (Autoupdates, SEO indexing).
  • Available in Live Only: Domain Management, Production Analytics, Cancel Subscription.
  • Available in Staging Only: Dedicated staging URL and admin access, Disabled areas clearly marked as staging only, Users added in an isolated environment with messaging during publish.
  • Publish completes within the next 2 to 5 minutes.

05Before you start

  • WordPress Hosting subscription must be active for the location or subaccount.

06How to set up and use staging environment access in HighLevel

Set up and use a staging environment for a WordPress site

  1. Log into the appropriate subaccount.
  2. Navigate to Sites > WordPress.
  3. Select Manage Website for the target site.
  4. Click the + Create Environment button.
  5. Allow time for the system to prepare the staging copy.
  6. View the new staging URL and admin credentials displayed.
  7. Use the Live | Staging toggle in the header to change views.
  8. When ready, click Publish to move staging changes to the live site.
  9. If needed, press Delete to remove the current staging environment.

07What it looks like in HighLevel

08Settings that matter

  • Plugins. Controls which plugins are installed and active in both live and staging sites.
  • Themes. Manages the theme files and activation status across both environments.
  • Users. Defines user accounts and permissions for live and staging, with isolated users in staging.
  • WordPress Debugging. Enables debugging tools that function in both live and staging copies.
  • Server Settings (phpMyAdmin, PHP version). Sets database access and PHP configuration for both environments.
  • WordPress Management (Auto, updates, SEO indexing). Controls automatic updates and SEO indexing behavior in live and staging.
  • Domain Management. Handles domain assignments and DNS only on the live site.
  • Production Analytics. Collects analytics data solely for the live environment.
  • Cancel Subscription. Allows subscription cancellation only from the live view.
  • Dedicated staging URL and admin access. Provides a unique URL and admin login for the isolated staging copy.
  • Disabled areas clearly marked as staging, only. Shows messages for features that cannot be used in staging.
  • Users added in an isolated environment with messaging during publish. Creates separate user accounts in staging and informs when they are moved to live.

09Things to know before you rely on it

  • Publishing from staging to live cannot be undone.
  • Creating a staging environment may take an indeterminate amount of time.
  • The publish process typically completes within two to five minutes.
  • Changes made directly on the live site do not appear in the staging copy.
  • Domain management, production analytics, and subscription cancellation are unavailable in staging.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

I find staging environment access convenient for testing changes before publishing live.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about staging environment access.

Do changes made in the staging environment affect the live site?

No. Edits in staging stay separate until you use the Publish action.

What happens when I publish from staging to live?

All modifications from staging are transferred to the live site and the action cannot be reversed.

Why are some options disabled while I’m in staging?

Those options belong to live only features; a message prompts you to switch back to live to use them.

How long does it take to create a staging environment?

The preparation period can vary and may take some time.

Can I delete and rebuild my staging environment?

Yes. Use the Delete button to remove the current staging copy and then create a new one.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.