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
  • Reviewed
CMS
  • 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

  • Brian Aberle commented
    10 Jun 01:38am

    I'm not an expert web designer, but a business owner currently using Squarespace. Within Squarespace, I can take a single page, work on a draft for that page and bring it back online without blowing up the entire site. How is that not an option within Webflow still? Do visitors to the site get to watch us do live updates to the site pages while we're working on it? In 2022?

  • Admin
    Webflow Admin commented
    4 Jun 12:27am

    You're correct. This is available for CMS pages/items and not static pages. Reopened the idea.

  • Gareth Reynolds commented
    3 Jun 05:49am
    Shipped—Remove CMS content without publishing your entire site

    This is cool although it doesn't solve the original idea. The above only works for CMS content. The original idea is that it's on a per page level. You can publish one single page without publishing every page. This way you can work on updating multiple pages at the same time and not have to worry about other page updates going live half finished.

  • Admin
    Webflow Admin commented
    2 Jun 09:52pm
  • Studio DNVR commented
    1 Apr 09:15pm

    Regarding publishing individual pages instead of the entire site, this is what the Webflow support told me:

    "...At the moment, you aren't able to publish individual static pages on your Webflow project.

    This feature limitation is known by the team, though I agree that this could be an awesome feature to have in Webflow, I have no timeline to share at the moment as to when this will be possible. My apologies for any inconvenience this may cause..."

  • Gareth Reynolds commented
    21 Mar 06:16pm

    Just to agree with people that say in reality the solution implemented for this particular request doesn't really solve the issue.

    The idea should be that when working on a project with multiple team members on a website with many pages, it should be possible to make changes to many live pages but only publish the updates for pages that are ready. Saving a page as a draft would take an already live page offline.

    By doing the above, this would allow you to make changes to other pages and not worry about them going live/being published before they are ready.

    Not necessarily directly related to this feature and can kind of be solved by using work arounds such as Git but would be good if there was just better version management in general. I feel this would benefit a lot of teams that are more than just one or two members.


  • Ben Schweitzer commented
    17 Mar 11:00pm

    The current implementation of this feature is not a viable solution for most users, especially businesses with teams. If the page I am drafting already exists on the live site, upon publishing, that draft page will disappear from your live site. I am drafting a new version of an existing page--it doesn't mean you remove the old live page.

  • CabbageApps commented
    14 Mar 05:36am

    ADMINS, any update on this?
    This is not shipped!

  • Angel Torres commented
    8 Mar 02:28pm

    Wow, is this really not being tackled yet? How is this marked shipped? - Admins please address.

  • Adamant commented
    28 Feb 05:54pm

    Crazy. Fix this.

  • Ruthy Lichtenstein commented
    9 Feb 06:40pm

    This is basics... ouch :/

  • Luke Andrews commented
    8 Feb 07:18pm

    The inability to publish design changes to a single page (e.g. to fix a bug) while not publishing other pages that are mid-flight (working on major updates) is a real showstopper for our company. It will be one of the key reasons we stop using Webflow.

  • Kelly Van Arsdle commented
    27 Jan 11:32pm

    Ping. This is really necessary. I am shocked this hasn't been implemented yet.

  • Farid Bonawiede commented
    11 Jan 08:08am

    Admin, please remove the "Shipped" tag. This feature is not live!

  • Geoff Baumbach commented
    29 Nov, 2021 08:01pm

    The current implementation of this feature is not a viable solution for most users, especially businesses with teams. If the page I am drafting already exists on the live site, upon publishing, that draft page will disappear from your live site. I am drafting a new version of an existing page--it doesn't mean you remove the old live page.

    Every other CMS system maintains the old live version while you work on the draft page. It should maintain both the live version (Live site) and the new draft version (staging) and replace the live version with the draft once it is out of draft status. And yes, Draft should be pushed to staging so we can actually test the page out on multiple devices and ensure things like iFrame embeds and custom JS/CSS function properly.

    Why we have to request such a CMS feature is beyond me in 2021. I would expect a whole publishing/revision system as good or better than Wordpress (which is free) and yet here we are, requesting features that were givens 6-10 years ago.

  • John McCarley commented
    16 Jul, 2021 02:57am

    How is this not a live feature yet?!?! This is aboslutely standard across the web. I

  • Andrew Gash commented
    30 Mar, 2021 07:07pm

    This request is not "Shipped". Setting a page to "Draft" takes the whole page down on the next publication. So, yes, in theory, the ability to un-publish certain pages is there. But the ability to publish individual pages without having to publish the entire site and all changes...that's not Shipped. That doesn't exist with Webflow yet.


    Now, I imagine that it may have something to do with the fact that webflow is built so much on CSS, and what you do on one page affects all other pages, but still, to mark this request as Shipped is not accurate.

  • Wendy Schorr commented
    6 Mar, 2021 04:24pm

    Webflow really dropped the ball on this request. I am working on my own personal website and there is a problem with one of my forms. I'd LIKE to have the ability to fix the form and publish that one page without having to post live the rest of the site which is in development. It's ridiculous that with all of Webflow's wonderful features and capabilities that it doesn't fulfill this one, very basic need: The ability to publish individual pages.

  • Bethany Ungar commented
    27 Aug, 2020 02:40pm

    Though the "save as draft" feature is nice for pages that haven't gone live at all yet, it would still be very helpful to be able to publish just one page rather than saving it as a draft.

    Take for example this scenario I'm in: I switch out all of the content on my Online Kids Church page weekly. New content needs to be published on Friday, and the original content needs to remain live through Thursday. To get ahead, on Wednesday I switched out all the Kids Church content without publishing the page. This allowed me to get ahead on my work without publishing the new content too early. My plan was to leave the site unpublished with the Kids Church page updates ready to go, and then just hit the Publish button on Friday.

    However, my supervisor just informed me that one of our signup forms on another page needs to come down immediately, because the event is full and we cannot take any more registrations. In order to remove that form (which is on another page), I have to publish the whole site, meaning all of the new content on the Kids Church page would go live too early. If I could publish one page at a time, I could just publish the page with the signup form on it and the Kids Church page would remain untouched, with the original content remaining live as planned. However, instead I now have to restore my site from a backup to get back all the original Kids Church content, I lose other changes I had made to the site between then and now, and I will have to start the whole process over.

  • Kayode Osinusi commented
    11 Aug, 2020 04:03pm

    This feature will be really helpful as it'll allow us to ship product features in increment. Please make this happen @webflow team. Thanks

  • Load older comments
  • +442