Skip to main content
Solved

Figma Sites URL slug roadmap

  • December 18, 2025
  • 5 replies
  • 111 views
Rook Studios

What is the timeline for adding a parent/child page structure to URLs within Figma Sites?

For example:

website.com/city/thursday-nights/concert-series/band-name/

Right now, the product supports one slug deep. Obviously “flat silo” URLs can work, but we need to be able to nest URLs as child pages. What is the roadmap and timeline for rolling out dedicated URL structure?

Best answer by Celine_

Hi everyone, thanks for sharing your feedback!
At the moment, Figma Sites CMS doesn’t support multi-level nested URL structures like website.com/city/thursday-nights/concert-series/band-name/ as ​@Rook Studios mentioned.
While CMS collections allow for dynamic content, they don’t currently enable deeper parent/child URL hierarchies within Sites.

For more advanced content architectures, a dedicated headless CMS such as Payload would be better suited. We don’t have a timeline to share on expanded nested URL support in Sites at this time.

I’ve shared this thread internally to the Figma Sites team for visibility and consideration, appreciate you raising it!

    5 replies

    Rook Studios
    • Rook Studios
    • Author
    • New Participant
    • February 10, 2026

    ​@Celine_ Maybe you would know this? I see you on the Community side a lot. My team and I are really needing to know this as soon as possible—How can you add nested pages within a URL structure on Figma Sites?

    ala this: website.com/city/thursday-nights/concert-series/band-name/ 

    RebeccaMade
    • RebeccaMade
    • New Member
    • February 10, 2026

    I’d be interested in knowing this as well. It’s a crucial feature to many websites. 

    Jackie Martain

    ​@Celine_ Wondering if you have any insight on the above??  We are currently working on a project and it would be great if we could learn how to add the nested pages 😊

    Celine_
    Figmate
    • Celine_
    • Community Support
    • Answer
    • February 13, 2026

    Hi everyone, thanks for sharing your feedback!
    At the moment, Figma Sites CMS doesn’t support multi-level nested URL structures like website.com/city/thursday-nights/concert-series/band-name/ as ​@Rook Studios mentioned.
    While CMS collections allow for dynamic content, they don’t currently enable deeper parent/child URL hierarchies within Sites.

    For more advanced content architectures, a dedicated headless CMS such as Payload would be better suited. We don’t have a timeline to share on expanded nested URL support in Sites at this time.

    I’ve shared this thread internally to the Figma Sites team for visibility and consideration, appreciate you raising it!

      Rook Studios
      • Rook Studios
      • Author
      • New Participant
      • February 18, 2026

      Hi everyone, thanks for sharing your feedback!
      At the moment, Figma Sites CMS doesn’t support multi-level nested URL structures like website.com/city/thursday-nights/concert-series/band-name/ as ​@Rook Studios mentioned.
      While CMS collections allow for dynamic content, they don’t currently enable deeper parent/child URL hierarchies within Sites.

      For more advanced content architectures, a dedicated headless CMS such as Payload would be better suited. We don’t have a timeline to share on expanded nested URL support in Sites at this time.

      I’ve shared this thread internally to the Figma Sites team for visibility and consideration, appreciate you raising it!

      ​@Celine_

       

      @Celine_

      Thank you for the candid update and for advocating for this thread internally.

      As a studio steward at Rook (a small creative design house who’s bottom line are smaller to mid-sized client sites), we have fully leaned into Figma Sites during the beta phase of a specific, pivotal project for us. We are currently in the middle of an intensive migration of a 100+ page WordPress environment into Figma Sites. While we understand the product is in its infancy, the lack of nested URL support is a significant friction point for a project of this scale.

      For studios like ours to move from "testing" to "deployment" of enterprise-level client work, multi-level hierarchies are not just a luxury—they are a requirement for SEO integrity and information architecture. Specifically, we are looking to streamline "house themes" via Figma Libraries that are reusable across diverse client types. Without deep URL support, those architectural patterns break.

      We are eager to move away from legacy stacks like WordPress and keep our entire ecosystem—from design to live hosting—within Figma. However, our ability to finalize this current migration and commit future high-revenue projects to Figma Sites depends on this functionality.

      Given that we are currently mid-migration, any insight into the roadmap for this—even in the short term—is crucial for our project planning. We’d appreciate any further updates the team can share as they consider the needs of studios doing professional, high-volume work on the platform.

      Eagerly awaiting your team's progress, 🙏🏼 ❣️

       

      Alex J. Bell 

      President, Rook Studios

      Terms & ConditionsCookie settingsAccessibility statement