Woot! Woot! Feature added 27-April-2023.
Replace Collection Pages with Collection-Bound Pages
VIDEO WALKTHROUGH-
https://www.youtube.com/watch?v=dTqGQZYvnhA
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"
https://wishlist.webflow.com/ideas/WEBFLOW-I-1212
https://wishlist.webflow.com/ideas/WEBFLOW-I-982
You can Collection-bind the home page, just like any other page
https://wishlist.webflow.com/ideas/WEBFLOW-I-337
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.
DESIGN NOTES
From a design standpoint, I think...
The Collection-level Slug becomes meaningless, as each page already has it's own Slug defined, which makes more sense.
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
.svg){kind=logo}
AND allow us to weave static, editable content components throughout a "collection-bound" static page!
1. New page from template
2. Bind to collection
3. Wire up elements that should pull from collection...AND
4. Continue adding static design/content, and/or components (that content editors can edit
WE NEED THIS URGENTLY!!
Upvoted for the ability to optionally create collection pages (incl. e-commerce collections).
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.)
This would be very helpful!
We really need this.
We need this urgently!
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.
https://discourse.webflow.com/t/placing-a-collection-page-in-a-subdirectory/72047/1 this dates back to 2018. THAT'S 5 YEARS WEBFLOW
Really is a joke that nothing has been actioned on this
Any work around here?
PLEASE do this. This is fundamental to SEO & site structure. What's the update on this?
Any news here?
Deseparely need this for a clean URL structure. This is basic 101 for SEO. Please help!
I want this feature enabled to render my react app on the dynamic route so that I can render content based on the URL
Need this so badly.
Important for SEO so you can have a clean URL structure.