Description:

We would love to request the ability for Webflow CMS collections to dynamically nest inside other CMS collections to allow for more flexible URL structures and dynamic content relationships.

Problem:

Currently, Webflow only allows one CMS collection per dynamic template page, which restricts building dynamic URL structures that involve multiple relational layers. For example, it is not possible to create a dynamic page structure like:

/[collection-A]/[collection-B-item-slug]

where Collection A and Collection B are separate collections (e.g., Service Types and Locations).

This limitation forces users to either:

• Create large, combined collections manually (which is not scalable), or

• Build static pages for what should otherwise be dynamic, scalable, SEO-friendly content.

Requested Solution:

Allow CMS pages to support dynamic URL nesting by:

• Enabling a “parent” CMS collection (e.g., Service Type) to contain a “child” CMS collection (e.g., Locations), and dynamically generate pages like:

/service-type/location

• Allowing multi-collection references in URL structure settings.

Benefits:

• More scalable and automated site structures for service businesses, real estate, tourism, franchises, multi-location companies, etc.

• Better SEO URL hierarchy (service-first/location-next or vice-versa).

• Reduced need for manual workarounds and static page creation.

Real-World Example:

A franchise business offering “Gym Cleaning” services across multiple cities would ideally want dynamic pages like:

/cleaning-service/gym-cleaning/auckland

/cleaning-service/gym-cleaning/christchurch

but built dynamically based on two related CMS collections (Service Types and Locations).

Thank you for considering this! It would be a major upgrade for serious CMS users and agencies.