# Updating current website in Dev

**URL:** <https://community.hubspot.com/t/updating-current-website-in-dev/145034>\
**Category:** Tips, Tricks & Best Practices\
**Tags:** enterprise\
**Created:** [January 16, 2026, 3:09pm UTC](https://community.hubspot.com/t/updating-current-website-in-dev/145034 "2026-01-16T15:09:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![LWorthy](https://avatars.discourse-cdn.com/v4/letter/l/e274bd/32.png) [@LWorthy](https://community.hubspot.com/u/LWorthy)\
**Post date:** [January 16, 2026, 3:09pm UTC](https://community.hubspot.com/t/updating-current-website-in-dev/145034/1 "2026-01-16T15:09:11Z")

</div>

We’re in the process of updating key website pages and the homepage, plus the Nav/Footer on our website.

What we’re looking to get help with:

- Rather than updating individual pages to content staging, we want to have a replica of our current site, so we can build new/amend pages and look at the new UX and UI. Then ideally, push the new/amended pages to live. Is this possible? How do we do it?
- We need to change our existing Nav/Footer. But how do we do this, without changing the current live Nav?

Can anyone give any guidance on the best approach to tackle this project please? Thanks

---

<div class="post-metadata">

**Author:** ![CarolinaDeMares](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/carolinademares/32/22707_2.png) [@CarolinaDeMares](https://community.hubspot.com/u/CarolinaDeMares)\
**Post date:** [January 16, 2026, 4:04pm UTC](https://community.hubspot.com/t/updating-current-website-in-dev/145034/2 "2026-01-16T16:04:00Z")

</div>

Hey @LWorthy !

Yes, this is possible in HubSpot, but it needs to be handled in a specific way. HubSpot doesn’t offer a true “full site clone” or staging environment, so the approach is page- and theme based.

- You can clone your existing pages and keep them unpublished or publish them to a staging subdomain to redesign layouts, content, UX and UI safely. Once approved, those pages can be published to live.
- For the nav/footer, if it’s built as a global module or global partial, any change will immediately affect the live site. To avoid this, the best approach is to clone the current theme, create a new version of the header/footer in that theme, and use it only on the cloned or staging pages.
- Build and review the new pages using the cloned theme and updated nav/footer, then switch live pages to the new theme when you’re ready to go live.

The key thing to be aware of is that HubSpot doesn’t allow pushing the entire site live in one click ( rollout is done by publishing pages or reassigning themes), so a bit of planning upfront makes the process much smoother.

If you need a second hand support on this on [ZUID](https://www.zuid.com/) we can help!

[Carolina De Mares](https://www.linkedin.com/in/carolina-de-mares/)

![CarolinaDeMares_1-1769100842581.gif](https://d2qpr2jzcazej7.cloudfront.net/original/2X/5/583e8ccc626c82a6eeebe25bfda6de9f5454b8d0.gif)

**[ZUID.](https://zuid.com/)**  
Goirkekanaaldijk 12  
5046 AT Tilburg  
Nederland

---

<div class="post-metadata">

**Author:** ![tjones](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tjones/32/31042_2.png) [@tjones](https://community.hubspot.com/u/tjones)\
**Post date:** [January 16, 2026, 8:51pm UTC](https://community.hubspot.com/t/updating-current-website-in-dev/145034/3 "2026-01-16T20:51:05Z")

</div>

Hey! I totally get what you’re trying to do.

Yes, this is definitely possible in HubSpot. The best way to approach it is to **clone your current theme or templates** so you’re not making changes to the live site while you’re building.

Here’s how I’d go about it:

**1. Clone your theme or templates**  
This lets you safely update the nav, footer, and page layouts without touching what’s live. You can do this in **Design Tools** by finding your current theme, cloning it into a new folder, and using that for your updates.

**2. Use Content Staging**  
Go to **Website \> Content Staging** and clone the pages you want to update. Then apply your cloned theme so you can build, test, and preview the new UX and UI in a safe space before anything is published.

**3. Update the nav and footer in the cloned theme**  
These are usually global modules, so if you edit the originals, those changes will go live everywhere. By editing the versions in your cloned theme, you can preview and test the updated nav and footer without affecting the current site.

**4. Publish when everything is ready**  
Once the new pages and navigation are good to go, you can either publish them directly from Content Staging or assign the updated templates to your existing live pages.

Hope that helps. Let me know if you need a hend getting it set up.

---

<div class="post-metadata">

**Author:** ![Pankaj-Sharma](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pankaj-sharma/32/11436_2.png) [@Pankaj-Sharma](https://community.hubspot.com/u/Pankaj-Sharma)\
**Post date:** [January 16, 2026, 11:55pm UTC](https://community.hubspot.com/t/updating-current-website-in-dev/145034/4 "2026-01-16T23:55:32Z")

</div>

Hi,  
Yes, this is absolutely possible. The best approach is to clone your existing templates or pages into a staging or sandbox environment and make all UX and UI changes there, then publish once approved. For the navigation and footer, create separate cloned global modules and assign them only to the staging templates so your live site remains unaffected until you are ready to switch.

This allows safe testing without impacting production.  
Pankaj
