Can Webflow CMS collection page URLs have the same structure as regular website page URLs placed under the same folder?
TL;DR
- Webflow requires CMS Collection Pages to follow a fixed
/{collection-slug}/{item-slug}URL format and doesn't allow them to share folders with static pages. - To align URLs, you can match collection slugs to desired folders or use 301 redirects, but true nesting or merging requires custom hosting solutions.
Webflow does not allow CMS Collection Page URLs to share the same folder structure as regular static pages. Collection pages have a fixed URL structure based on the collection’s slug.
1. CMS Collection Page URL Behavior
- CMS Collection Pages are always under their collection slug, e.g.,
yourdomain.com/blog/my-article. - You cannot place CMS Collection Pages in a custom folder like a static page (e.g.,
yourdomain.com/resources/my-article) unless the collection slug itself is “resources”.
2. Static vs. CMS Page URL Structure
- Static Pages can be organized into folders for structure like
yourdomain.com/resources/toolkits/checklist. - CMS Items must follow the format
yourdomain.com/{collection-slug}/{item-slug}. - Webflow does not support nesting CMS URLs within arbitrary folders matching static pages.
3. Available Workarounds
- Match the collection slug to your desired folder name. For example, set the collection slug to “resources” to get URLs like
yourdomain.com/resources/item-name. - Use 301 Redirects to alias alternate URLs to your CMS items, but this doesn’t structurally integrate CMS items into the same folder as static pages.
- For advanced routing, you would need custom hosting or reverse proxy setups outside Webflow, which is not natively supported.
Summary
Webflow CMS Collection Pages must follow a fixed /{collection-slug}/{item-slug} format and cannot be placed alongside static pages in the same folder structure. You can adjust the collection slug or use redirects for better alignment, but full structural merging isn’t possible within native Webflow capabilities.