robots.txt, static files and redirects

How is this not getting more likes? Give it a thumbs up!

Definitely a useful feature, considering robots.txt is not even being auto generated, so SEO with Google tools get affected.

Hello Figma Product Team,

I’m writing as a long-time Figma user who is actively trying to use Figma not only for design, but as part of a real website publishing and go-to-market workflow.

This feedback is specifically about SEO and Google indexing, not language or localization.

1. Make-generated websites are effectively not indexable by Google

Make is extremely productive and intuitive.
However, from an SEO and discovery standpoint, Make-published sites are fundamentally unusable:

• No reliable server-side rendered HTML

• No control over robots.txt

• No support for sitemap.xml

• No canonical or metadata control

• URLs are not consistently indexable

As a result, Make websites are practically invisible to Google Search, regardless of content quality.

This makes Make unsuitable for:

• Company homepages

• Landing pages

• Marketing sites

• Startup MVPs that rely on organic discovery

2. There is no upgrade path from Make to an SEO-capable solution inside Figma

From a user’s perspective, the expected workflow is:

Design → Make → Publish → Grow → Improve SEO

But today:

• Once a site is built with Make, there is no migration path to Figma Sites

• Users are forced to abandon their work and move outside the Figma ecosystem

This creates a dead end rather than a growth path.

3. Figma Sites does not currently solve core SEO requirements either

Even if migration were possible, Figma Sites still lacks essential SEO infrastructure:

• No proper sitemap generation

• No robots.txt control

• Limited metadata management

• Not designed for search-driven traffic

Sites currently feels closer to a presentation layer than a true publishing platform.

What would significantly improve the situation

From a product standpoint, any one of the following would unlock massive value:

1. Make output that is SEO-capable
   (indexable HTML, sitemap, robots, metadata)

2. A supported migration path:
   Make → Figma Sites

3. Clear positioning and documentation:

   • Is Make intended for real websites or demos only?

   • Is Sites intended to support SEO-driven use cases?

Right now, Figma’s design tools are best-in-class, but the publishing story stops just before the most critical step: being discoverable on the web.

I’m sharing this feedback because I genuinely want to keep my workflow inside Figma.
At the moment, SEO limitations are the single biggest reason forcing me to look elsewhere.

Thank you for taking the time to read this, and I hope it reaches the appropriate product team.