Allow identical CMS slugs for Collections nested in Folders

It is currently possible to "nest" Collection Pages in folders so they inherit the folder slug as their initial slug, then the collection, then the page.

Ex: website.com/folder/collection/item


But the problem is that Collections have identical slugs when nested - which doesn't make sense because they are in fact different slugs due to being nested in folders! This is extremely vital for sites that have collections for products that are organized in similar ways.

Ex: We should be able to do:

website.com/grills/categories/gas

website.com/furniture/categories/tables

website.com/fireplace/categories/wood


But the problem is that Webflow will not allow multiple CMS Collections to have the same slug (in this example, /categories) even though they are nested in different folders. This creates problems because all of the "Category" slugs need to have prefixes with the product type (grills, furniture, fireplace) which defeats the point of nesting them.


When doing restricted actions, such as copying CMS-linked content from a Collection Page to Static Page, Webflow gives and error and lets the user know the action cannot be done. It should be the same for this. If the user tries to unnest a collection from a folder (or delete the folder), Webflow will let them know that url slugs will need to be renamed in order to avoid duplicate slugs.


Please consider making this change! It doesn't seem like it would be very hard to do and would be a huge help.

  • Gabe Hilliard
  • Jun 21 2024
  • Marketing Shippr commented
    2 Aug 11:34am

    This is a crucial feature for us to be able to scale with Webflow. We are active in 3 cities and we must localise our content. In the example of Gabe above, the red part would be our cities (london, paris, brussels), which each have their categories (CMS). For instance, I need the local blogs:

    • /brussels/blog

    • /paris/blog

    • /london/blog