Webflow does not currently support nested folders or slugs (like forward slashes) in Collection URLs. Each Collection is treated as a top-level folder, which limits custom URL structures such as site.com/blog/category/category-name
.
However, there's a workaround using Static Pages and a single Collection.
1. Use a Single Blog Posts Collection
- Create one Collection called something like Blog Posts.
- Add a Category reference field to this collection. Create a separate Category Collection.
- In the Blog Posts Collection Template, use category data to group or filter posts.
2. Create a Static “blog/category” Folder
- Go to the Pages panel and create a new Folder named blog.
- Inside it, add another Folder called category.
- Inside that second folder, create a Static Page that will serve as a dynamic router using CMS data.
- Example: name it [category-name] for routing like
site.com/blog/category/design
.
3. Use URL Parameters or JavaScript Redirects
- Since Webflow doesn’t allow dynamic parameters on Static Pages, you will need to:
- Use JavaScript on the static category page (
site.com/blog/category
) to detect and redirect to the actual category (e.g., read URL, then show the proper filtered CMS content). - Or use a reverse proxy on a custom domain setup (e.g., via Cloudflare Workers, Netlify, or NGINX) to rewrite your URLs externally.
4. Use a Reverse Proxy for Full Control (Advanced)
- Host your Webflow site on a custom domain.
- Use a service like Cloudflare Workers to rewrite URLs like:
site.com/blog/category/design
→ site.com/blog-category/design
- This allows SEO-friendly nested slugs without changing Webflow’s internal structure.
Summary
Webflow doesn't support slugs with forward slashes in Collection URLs. To achieve site.com/blog/category/category-name
, you’ll need to either simulate the structure using static folders and filtering logic, or implement a reverse proxy solution outside Webflow.