Publish / Unpublish individual pages

I'd like to be able to un-publish individual pages, or at least prevent certain pages from being published.

A few scenarios I need this for:

  • When I begin creating a page, but need to make and publish changes to other pages in the meantime (and don't want my half-finished page/s publishing)
  • Pages I no longer want visible on the site (promotions, replaced content etc)
  • A/B Testing for marketing

Currently I'm preventing the pages being accessible by password protecting, and adding the nofollow/index meta to them, as they still appear on the sitemap.xml, even with password protection.

  • Dylan Johnston
  • Jan 18 2017
  • Shipped
  • Apr 24, 2018

    Admin Response

    Update 04/24/18:

    Hi! As of yesterday, we released the feature "Drafted pages" allowing you to draft static pages preventing it from being published to your live site. Learn more here

    Update 03/12/18:
    Hi Everyone! Though we haven't pushed out the ability to publish/unpublish individual static pages yet, we have added the ability to publish single CMS items. This will allow you to update these CMS pages without having to worry about any WIP changes in your project. Learn more here

  • SONDR® commented
    22 Jun 09:08am

    We still need the ability to publish only one static page. This is creating huge complications in our workflow process.

  • Natalie Russo commented
    22 Aug, 2019 05:03pm

    While it's nice to publish single CMS items, it's more important for me to be able to publish static pages. There have been several times I'm working on a clients redesign project when they have an urgent change somewhere else on the site. For larger sites, it'd also be nice to just publish and test the one page I'm working on instead of waiting for all 80 pages to republish when nothing was changed on them.

  • Matt Allan commented
    3 Mar, 2019 11:04am

    Publishing as draft solves this problem for me! 

  • Will Lownsbrough commented
    29 Jan, 2019 09:20am

    Any update on this one Webflow team? And has anyone got a good workaround for pages? 

  • Albert Lewis, Jr. commented
    19 Jan, 2019 09:59am

    Would LOOOOVE this feature. 

  • Michael Naylor commented
    7 Jan, 2019 01:46am

    Can this item please be unmarked as shipped as it is still impossible to publish/unpublish the changes on an individual page without publishing the entire website. This was the original scope of the wishlist request.

    As it stands if you're halfway working through two pages, and want to only push one to the live server it can't be done without a very messy workaround of copying pages and updating url slugs.

  • Jonatan Saine commented
    26 Sep, 2018 12:28am

    PLEASE! This is a huge need and I can see several ways of using this feature. 

  • Michael Naylor commented
    25 Apr, 2018 02:35am

    Hallelujah!!!!! This one took waaayyyy too long and has been the cause of more problems than you can ever imagine but thanks guys, it’s truly appreciated now it’s here!!! :) the low hanging fruit is always the best!

    Have a great evening,


  • Rob Saville commented
    17 Feb, 2018 10:15pm

    This would be a super handy and useful addition, for many reasons. Would be useful to take any half finished/work-in-progress pages offline, until they are completed. Really does need adding - it’s essential!

  • Dan Dawson commented
    10 Feb, 2018 01:51am

    I could use this today!

  • Craig Hynes commented
    30 Jan, 2018 01:44am

    This would be very helpful especially as Templates based on a Collection can't be password protected yet.

  • Stephanie Bishop commented
    16 Jan, 2018 11:55pm

    This is a strangely basic feature that for some reason is unavailable.... Please implement this!!

  • Rob Tourtelot commented
    10 Jan, 2018 08:50pm

    Desperately needed!

  • Stanislav Pykhtin commented
    30 Nov, 2017 07:26pm


  • Jeff Blanchard commented
    6 Nov, 2017 02:37am

    Wow, really this isn't an available option? CMS 101.

  • Michael Wells commented
    2 Oct, 2017 09:23am

    Very much looking forward to this. I have two use cases where this is currently a problem-

    BACKING UP PARTIALLY-BUILT PAGES - If I purchase a template, often I deploy the live site in stages.  For the first publish, I need to delete a lot of the on-page sections in the template, until the client has worked out if/how we want to use them effectively. To do this I clone the page to back it up, then delete those elements. Now I have two nearly-identical pages in my sitemap which means Google penalizes me for duplicate content and it may even promote my "hidden" backup page as being more content-rich than my intended public page.

    COLLECTION PAGES - About 20% of my collections are "type tables", such as "Event Type." These usually don't make any sense as standalone pages, there would never be a case where I'd want to link to them. Currently webflow doesn't appear to give me the option to suppress these pages? So I end up with a bunch of sitemap entries for pages that aren't usable. 

    I realize many search engines will respect no-index meta tags in the page head, but even Google still includes the page in it's directory (showing the title only). 

  • Casey Schorr commented
    6 Sep, 2017 05:48pm

    We need the ability to selectively withhold publishing a specific page or CMS collection item when publishing our site. The use-case is when a major feature change causes us to need to rewrite pages or CMS entries (help articles, feature pages, etc). The page or collection item we are re-working is already published, so when we go in and edit it, it works fine until someone on the team needs to publish the site (i.e they wrote a new blog post). At this time, our half rewritten help article gets published as well, which is a big problem.

    Because the CMS collection entry is already published, I can't revert to a draft or it takes the article down which doesn't work either. The only workaround is to "duplicate" the CMS entry or page and work on the duplicate in a draft state, but it's risky if you forget to change the URL later, you can break links. Copying content is also not a best-practice.

    What we'd like to be able to do is publish the entire site but withhold the specific collection entries from publish so the changes we're making to them don't go live until we specifically publish those collection entries.

  • Sara Pocius commented
    1 Sep, 2017 08:22pm

    This is an absolute must have. I've built in Wordpress, SquareSpace, Shopify and BigCommerce...they all have a draft state for pages. Now that my Webflow site is published, starting new pages is a huge pain. I do not like having unfinished work out there for someone to stumble upon. This is such a basic feature and hope that you are able to implement it soon. 

  • Eeppi Nieminen commented
    7 Aug, 2017 03:25pm

    Definitely needed when one is working with templates. I don't want to publish all the template pages, but want to keep them to make my work easier if I design the site further or need to add elements later. 

  • Cameron Roe commented
    19 Jul, 2017 11:33pm

    Please implement this!

  • Load older comments
  • and 334 more