Allow Collection-Bound Pages Anywhere

Woot! Woot! Feature added 27-April-2023.

Replace Collection Pages with Collection-Bound Pages


Current collection pages have a number of design restrictions-

  • Every CMS collection gets a collection page, even if you don't want it

  • Each CMS collection can only have one collection page, even if you need more than that

  • Collection pages cannot be within folders

  • Collection pages cannot be password-protected

  • The homepage cannot be a collection page

Instead of treating collection pages as a separate thing, and enforcing these rules, it seems cleaner to be able to create a standard "static" page, wherever you like, and the "bind" it to a collection. That would be the definition of a collection-page. In this way, you get to use all of the existing page-design mechanisms, and solve all of the above problems-

You don't need to create collection pages for CMS collections that don't need them, e.g. "Publication Type"

You can Collection-bind the home page, just like any other page

Freedom to organize your pages, both visually in the designer UI, and logically within Folders.

Password-protection, both on the page itself, or on the parent folder.


From a design standpoint, I think...

  1. The Collection-level Slug becomes meaningless, as each page already has it's own Slug defined, which makes more sense.

  2. Collection-bound pages follow the same rules as Folders, for example,

I can have a static page named /mypage
AND I can have EITHER a folder named /mypage OR a collection-bound page named /mypage

I cannot have BOTH a folder named /mypage AND a collection-bound page named /mypage, since the subpaths could conflict. I haven't tested this, however I"m pretty cure it's already the case that you cannot create a folder under the path "/mypage" and a CMS collection with the slug "mypage", for the same reason.

  • Michael Wells
  • Oct 15 2018
  • Reviewed
  • Toni Liebold commented
    15 Apr 08:03am

    Upvoted for the ability to optionally create collection pages (incl. e-commerce collections).

  • Abceleradora commented
    11 Aug, 2023 04:54am

    Feature partially added.

    You can nest within folders, but you cannot naked-serve a collection at the root domain (e.g. Collection "Blog Posts" must be served at */blog/page or deeper instead of just */page.)

  • Lee Mullet commented
    13 Jun, 2023 02:32pm

    This would be very helpful!

  • Random Sounds commented
    24 Mar, 2023 10:53pm

    We really need this.

  • Jean Herelle commented
    24 Feb, 2023 05:24pm

    We need this urgently!

  • Liam Gillespie commented
    31 Jan, 2023 11:09am

    It's really effecting our business and Webflow seem to just be ignoring people on these kinds of SEO related topics, it's not good enough that a company of this size doesn't have the capacity to make fundamental updates like this. this dates back to 2018. THAT'S 5 YEARS WEBFLOW

  • Liam Gillespie commented
    31 Jan, 2023 11:02am

    Really is a joke that nothing has been actioned on this

  • Liam Gillespie commented
    31 Jan, 2023 10:33am

    Any work around here?

  • Jason Roach commented
    20 Jan, 2023 01:52am
    ^ This!!!
  • Hunter Varnum commented
    4 Oct, 2022 04:09pm

    PLEASE do this. This is fundamental to SEO & site structure. What's the update on this?

  • Petr Bílek commented
    12 Jan, 2021 07:21pm

    Any news here?

  • Steven Haynes commented
    28 Dec, 2020 11:19am

    Deseparely need this for a clean URL structure. This is basic 101 for SEO. Please help!

  • Jithu Reddy commented
    6 Nov, 2020 12:21pm

    I want this feature enabled to render my react app on the dynamic route so that I can render content based on the URL

  • Steven Haynes commented
    15 Oct, 2019 02:29pm

    Need this so badly.

  • Markus Smet commented
    12 Mar, 2019 08:03am

    Important for SEO so you can have a clean URL structure. 

  • +104