Can Webflow CMS collection page URLs have the same structure as regular website page URLs placed under the same folder?

Webflow CMS collection page URLs cannot exactly mimic regular static page URLs under a folder structure. CMS Collection page URLs are tied to the collection’s slug and always follow a specific pattern.

​

1. How Webflow Collection Page URLs Work

​

• When you create a CMS Collection, Webflow automatically generates a collection page with a URL structure of:  

  yourdomain.com/collection-slug/item-slug

• For example, if your collection is called "Blog Posts" and an entry is titled "My First Post", the URL will be:  

  yourdomain.com/blog/my-first-post

​

2. Static Folders vs. CMS Collection URLs

​

• Static folders allow nesting, like:  

  yourdomain.com/resources/guides/seo-guide

• CMS Collection pages cannot be nested inside static folders.
• You cannot manually assign a folder path to CMS collection items that removes or hides the collection slug.

​

3. Workarounds or Alternatives

​

• Reverse proxy: You could configure a reverse proxy (outside of Webflow) using a service like Cloudflare Workers or Netlify Edge Functions to rewrite URLs, but this requires DevOps-level tweaking and defeats Webflow’s no-code purpose.
• Static pages instead of CMS items: If you need fully custom URLs, consider using static pages with folders, though you lose CMS automation.
• Dynamic landing pages inside collections: You can simulate nesting by changing your collection slug to match your desired folder, such as naming the collection “guides” so URLs become /resources/guides/item.

​

Summary

​

Webflow CMS collection URLs must include the collection slug and cannot share the exact same folder structure as manually-created static pages. For fully custom paths, use static pages or external workarounds.