By the end of this lesson you’ll be able to nest a CMS collection under an existing collection path in Webflow — turning mysite.com/categories/animation into mysite.com/blog/categories/animation — using a small glitch that Webflow doesn’t officially support. It’s a fun trick, but the real point is structure: putting your content where it logically belongs.
Here’s the setup. You’ve got a blog posts collection at /blog and a categories collection at /categories. It works, but categories aren’t a separate thing — they’re just a way to organize blog posts. So it would read far more clearly if they lived inside the blog: /blog/categories/…. The obvious move is to make a folder called blog and set it as the categories template’s parent. And that’s exactly where Webflow stops you.
A quick honesty note: this is an unofficial glitch, not a documented feature, so Webflow could change it at any time. It works today and is reversible, but treat it as a clever workaround rather than a guarantee.
How it works
The wall is simple: Webflow won’t let a static folder and a CMS collection share the same base path. The moment you try to create a folder with the slug blog while a blog collection already uses /blog, you get “collection with this URL already exists,” and clicking Create does nothing.
The glitch is entirely about where you click next. Normally, when you’ve typed the slug and click the canvas (or another normal page), Webflow shows a “quit without saving” popup and discards your folder. But if instead you click one of the CMS template pages in the pages panel, a different popup appears — and this time, when you choose Exit without saving, a second popup shows up asking whether you want to Save changes. Click Save changes, reopen the pages panel, and the blog folder is there. Webflow still flags an error on it, but the folder exists and works.
From there it’s ordinary: open the categories template settings and change its Parent Folder from wherever it was to the new blog folder. Webflow warns about possible broken links (fine — you’re doing this before publishing, and this is about structure, not redirects). Save and publish, and your category URLs become /blog/categories/… with no 404s.
The catch that makes or breaks it is order. Create both collections, populate them with items, and publish those items first (status: published). Only then create the blog folder and set it as the parent. Do it in the wrong order and the setup can misbehave.
Finally, the why — which matters more than the trick. Nesting categories under /blog is good information architecture: your editorial taxonomy lives inside your editorial space. But don’t do it for SEO keywords. Modern search and AI systems understand context from your text, headings, and internal links — not from category names crammed into the URL. URL structure creates coherence and helps humans navigate; it isn’t what determines discoverability. The goal isn’t a perfect URL, it’s a coherent one.
How to use it
- Build the collections — create
blog posts(URL/blog) andcategories(URL/categories), add items to both, and publish the items. - Start the folder — in the pages panel, create a new folder and give it the slug
blog. You’ll see the “already exists” error — expected. - Trigger the glitch — instead of clicking the canvas, click a CMS template page in the pages panel. In the popup that appears, choose Exit without saving.
- Save the hidden change — when the second popup asks to save changes, click Save changes. Reopen the pages panel and the
blogfolder is there (error flag and all). - Re-parent categories — open the
categoriestemplate settings and set its Parent Folder to theblogfolder. Accept the broken-links warning. - Publish and verify — publish, open the live site, and confirm a category resolves to
/blog/categories/…with no 404.
A hidden level, sure — but the lasting lesson is that good content isn’t just written, it’s organized. Structure for clarity and coherence, and both people and machines understand your site better.