How to Create Nested CMS Folder Structures in Webflow

In professional web development, platform constraints often dictate content architecture, forcing developers to compromise on URL hierarchy. Specifically, Webflow’s native environment restricts users from nesting a template page inside a folder that shares a base path with an existing CMS collection (for instance, creating a /blog folder when a /blog CMS collection already exists). This poses a distinct architectural obstacle for developers who want to create a strict, logical hierarchy for their editorial content, such as grouping blog categories directly under the primary blog path rather than having them exist as separate, disconnected entities.

This video provides immense core value by revealing a precise platform workaround—a "glitch"—that empowers developers to bypass this technical limitation. By executing a specific sequence of UI interactions within the Webflow designer, viewers will learn how to unlock a hidden structural capability. Ultimately, the viewer will achieve the ability to nest their editorial taxonomy cleanly within their primary editorial space (e.g., routing a category to website.com/blog/categories/animation), bending the platform's architecture to serve a more intentional, unified content strategy.

Beyond the technical execution of this workaround, the viewer will achieve a modernized understanding of content strategy, specifically regarding Search Engine Optimization (SEO) and Answer Engine Optimization (AEO). The tutorial elevates the lesson from a simple "hack" to a masterclass in content architecture, teaching viewers that modern discoverability relies on clarity, structure, and intent rather than outdated keyword stuffing. By the end of the video, viewers will understand that while a perfected URL structure aids human navigation and logical order, it is the overall coherence of the content and internal linking that ultimately drives success in modern search systems.

• Bypassing Native Path Restrictions: Webflow typically prevents two structures from sharing the same base path, but developers can bypass this by triggering a specific "unsaved changes" sequence in the Designer UI, which forces the platform to accept the overlapping folder slug.
• Establishing Intentional Hierarchy: Utilizing this technique allows developers to nest category pages directly under their parent editorial folder (e.g., /blog/categories/), resulting in a cleaner, more cohesive URL architecture that clearly communicates the relationship between content types.
• Adhering to a Strict Order of Operations: To successfully execute this structural adjustment, developers must follow a precise sequence: first create, populate, and publish the CMS collections, then create the parent folder, and finally set the parent folder for the collection.
• Shifting from Traditional SEO to Content Architecture (AEO): Modern optimization is no longer about keyword-stuffed URLs; it requires optimizing for systems that understand content context through architecture, clarity, and structural intent.
• Prioritizing Coherence Over Perfection: While a highly organized URL structure helps users navigate and helps developers map their content, search engines ultimately understand context through text, headings, and internal relationships—making overall content coherence the primary goal for discoverability.

• 01:29 - Create a CMS collection named "blog posts" and configure its collection URL to "blog".
• 02:21 - Create a secondary CMS collection named "categories" and assign it a dedicated collection URL.
• 03:32 - Create a static page named "blog" and assign it the slug "blog" to list the CMS collection items.
• 04:48 - Access the general settings of the categories template page and set the "parent folder" property to nest the page inside a specific folder (demonstrated initially with a temporary folder).
• 06:44 - Trigger the structural glitch by clicking on a different CMS template page in the panel, selecting "exit without saving" on the first pop-up, and then clicking "save changes" on the hidden secondary pop-up.
• 07:55 - Access the categories template page settings again, update the parent folder to the newly forced "blog" folder, and hit save and publish.
• 09:18 - Execute the mandatory order of operations: first create and populate both CMS collections, publish the items, create the parent folder (e.g., "blog"), and finally assign the parent folder to the categories collection.

Webflow CMS Folder Glitch: Advanced URL Structuring Guide

This documentation provides a step-by-step workflow to bypass Webflow's native URL path limitations. By following this guide, you can successfully nest a secondary CMS collection (like categories) under a primary CMS collection's base path (like a blog), creating a strictly logical URL hierarchy.

1. Create the Primary CMS Collection (01:29)

• How: Create a new CMS collection named "blog posts" and set its collection URL to "blog".
• Why: This establishes the primary base path (e.g., website.com/blog) where all of your individual editorial posts will live, setting the foundation for your content architecture.

2. Create the Secondary CMS Collection (02:21)

• How: Create a second CMS collection named "categories" and assign it its own collection URL, such as "categories".
• Why: This generates the organizational taxonomy (the categories) that you will ultimately nest inside your primary blog path.

3. Populate and Publish CMS Data (09:18)

• How: Add dummy or real data items to both the "blog posts" and "categories" collections, and ensure you publish these items so their status is set to "published".
• Why: Setting up a nested URL structure requires a strict order of operations. You must populate and publish the collections before creating the overlapping folder; otherwise, the platform may not behave as expected.

4. Attempt to Create the Overlapping Parent Folder (05:23)

• How: Navigate to the Pages panel and attempt to create a new static folder called "blog" with the slug "blog".
• Why: To nest the categories template, you need a parent folder. However, Webflow will immediately throw an error stating "collection with this URL already exists," because the platform natively prevents two structures from sharing the exact same base path.

5. Trigger the Override Glitch (06:44)

• How: While stuck on the error screen, click on any other CMS template page (e.g., "Team Members") in the Pages panel. A pop-up will appear asking to quit without saving; click "exit without saving". A second, hidden pop-up will immediately appear asking if you want to save unsaved changes. Click "save changes".
• Why: This specific UI interaction bypasses Webflow's architectural roadblock. By triggering this secondary pop-up, you force the system to generate the overlapping "blog" folder despite the initial base path conflict.

6. Nest the Template Page (07:55)

• How: Open the settings for your "categories" template page. Locate the "parent folder" property and change it to the newly created "blog" folder. Webflow may show a warning about possible broken links, which you can ignore. Hit save and publish the site.
• Why: This physically moves the categories template under the blog folder. Your taxonomy now officially lives inside your primary editorial space, resulting in a cleaner, highly intentional URL structure (e.g., /blog/categories/animation).

You can bypass Webflow's native path restrictions by creating and publishing your CMS collections first, then creating your desired parent folder. By triggering a specific "unsaved changes" dialog in the Designer UI, you can force the platform to accept the overlapping slug. Finally, assign this newly forced folder as the parent in your category template settings to achieve the nested structure.

This error occurs because Webflow natively prevents a static folder and a CMS collection from sharing the exact same base path. To bypass this restriction, click a different CMS template page to trigger the "exit without saving" prompt, which will reveal a hidden "save changes" pop-up. Saving here forces the folder creation despite the error, allowing you to establish your desired URL hierarchy.

To successfully nest structures without triggering unresolvable platform errors, you must follow a strict sequential setup. First, create your primary and secondary CMS collections, populate them with data, and ensure they are fully published. Only after completing these steps should you create the parent folder and assign it to the secondary collection.

While a clean, nested URL structure helps users navigate, search engines do not actually need category names in the URL to understand context. Modern SEO and AEO systems deduce meaning primarily from on-page text, headings, and internal linking relationships. Optimizing for overall content coherence and structural clarity is far more effective than obsessing over perfect URL architectures.