Skip to main content
Question

Static files in public/ folder not served at root URL after publish

  • June 1, 2026
  • 1 reply
  • 12 views
Mayank PlanAVenture

Hi Figma Make Support,

I'm having an issue where files placed in the public/ folder (robots.txt, sitemap.xml, manifest.json) are not being served at their root URLs (e.g. https://www.planaventure.ai/robots.txt) after publishing.

What I've tried:

  • Confirmed files are in the public/ folder in the Figma Make editor
  • Published multiple times
  • Added a custom Rollup plugin (generateBundle) in vite.config.ts to explicitly emit the files — still not working

Evidence:

  • https://www.planaventure.ai/robots.txt returns plain text "Not Found" (HTTP 404)
  • The Last-Modified header on this 404 response is Wed, 14 Jan 2026 and has not changed despite multiple publishes — confirming the file is never being deployed
  • The main index.html deploys correctly with today's date, so publishing itself is working

Question

Does Figma Make's deployment pipeline support serving static files from the public/ folder at root paths? If so, is there a specific configuration required?

Thanks
Mayank

1 reply

Jaycee Lewis
Figmate

Hi ​@Mayank PlanAVenture 👋 Thanks for the detailed writeup, the headers make this easier to diagnose.

This is a current platform limitation, not something a config will fix. Per the Make FAQ: “Figma Make optimizes published files automatically but doesn't currently offer specific customizability for SEO optimization.” A teammate of mine confirmed the specifics in a related thread — “no access to a public folder or custom server routes like robots.txt/sitemap.xml”

A few options, roughly in order of effort:

  • Custom Code (partial) — Figma Make settings let you inject snippets into the head or body of your published app. Useful for metadata and analytics tags, but it won't give you a root-served `robots.txt` — so it's more of a stopgap
  • Edge proxy (full workaround, dev path) — Since your domain points at Figma Make via DNS, you can front it with a an edge proxy: intercept requests for `/robots.txt` and `/sitemap.xml`, return them directly from the Worker, and pass everything else through to Figma. That gets you genuinely root-served static files today without waiting on the platform (spotted it here from a community member)
  • +1 the feature request — If you'd rather have native support, there's an open request tracking exactly this (robots.txt, static files, redirects)

Hope that helps! — Jaycee

Terms & ConditionsAccessibility statement