Can Webflow CMS collection page URLs have the same structure as regular website page URLs placed under the same folder?
TL;DR
- CMS collection pages in Webflow use a fixed URL format (/collection-name/item-slug) and can't share paths with static pages.
- Static pages can have custom folder paths, but they can't overlap with CMS collection slugs or contain CMS items within static folders.
Webflow CMS collection page URLs cannot have the exact same structure as regular static website pages under the same folder. CMS collection page URLs are generated automatically and follow specific patterns managed by Webflow.
1. CMS Collection Page URL Structure
- Webflow automatically generates URLs for CMS collection pages using the format:
/collection-name/template-slug - For example, if your collection is called "Blog" and you have a post with the slug "my-first-post", the URL will be:
/blog/my-first-post
2. Static Page URL Structure
- Static pages or folder-based pages have manually defined paths.
For example: - A static page "About Us" under the folder "company" would have the URL: /company/about-us
- These can follow any structure you define, provided they don’t conflict with other page names or folder paths.
3. Limitation on Overlapping Paths
- You cannot create a static folder or page with the same path as a CMS collection.
- For example:
- If you have a CMS collection named Blog, you cannot have a static folder or page also named /blog as it will conflict.
- Webflow will show an error if URL paths conflict between static pages and dynamic CMS pages.
4. No CMS Items Under Static Folders
- There is no native support in Webflow to place CMS-generated pages under a static folder like /services/project-abc if "project-abc" is a CMS item and "services" is a static folder.
- All CMS item URLs must reside under the specific collection slug defined when creating the collection.
5. Workarounds (Limited)
- You could simulate folder-level structure by naming the collection with the desired folder name (e.g., name the collection "Services" so URLs become /services/item-name).
- You can use 301 redirects or custom code with reverse proxying outside Webflow, but these are advanced solutions and not supported natively within Webflow.
Summary
CMS collection page URLs in Webflow follow a fixed structure and cannot share a folder-based structure with static pages. All CMS URLs must live under the slug of the associated collection, and overlapping paths with static pages are not allowed.