Figma Make handles the tags and not the files

You can set a title, a description, a custom domain and a switch that controls whether search engines are welcome. What you cannot do is put a file at the root of the site, and two important files live there.

Claims on this page were last checked against the platform's own documentation on .

See what a crawler gets

Figma Make provides a meta title and meta description for a published file, a setting to enable web search, and custom domain support. Figma-hosted files do not provide access to a public folder or support custom server routes such as robots.txt or sitemap.xml, so neither file can be configured. Indexing can be prevented by adding a robots noindex meta tag to a page.

What you get

The per-page basics are present. You can specify a title for a published functional prototype or web app, which appears in browser tabs, search results and social previews, and there is a meta description setting described as a short summary intended to improve click-through from search results.

From Make settings you can enable web search, configure a custom domain, and upload custom web fonts.

Custom domains are supported, with plan-dependent limits on how many you can connect. Getting onto your own domain is the single most valuable thing available here and it is worth doing before anything else, for the same reason it is everywhere: everything else attaches to that address.

The two files you cannot place

This is the constraint that distinguishes Figma Make from most of the platforms in this section.

Figma-hosted files and prototypes do not provide access to a public folder and do not support custom server routes such as robots.txt or sitemap.xml, so it is not currently possible to configure those files directly.

Both of those live at fixed addresses at the root of a domain, and neither can be created if you cannot put a file there. So a Figma Make site has no sitemap to submit and no robots.txt to read.

The absence of a robots.txt is not a problem in itself, and it is worth saying clearly: a missing robots.txt means nothing is restricted, which is a perfectly safe state and better than a wrong one. The sitemap absence is the one that costs you, because a new site with no incoming links is exactly the case where a sitemap does the most work.

Working without a sitemap

It is a disadvantage rather than a blocker, and there are two things that substantially make up for it.

The first is internal linking. A sitemap solves a discovery problem, and links solve the same problem by a different route. Every page needs to be reachable by following links from your homepage, ideally in two clicks or fewer. On a small site that is entirely achievable and it is what crawlers were designed around.

The second is Search Console. You can verify a domain property and request indexing on individual URLs directly, which for a site of a handful of pages is a perfectly reasonable substitute for submitting a sitemap. It is manual and it works.

What you should not do is conclude that indexing is impossible. It is slower to be discovered without a sitemap and it is not prevented.

The switch to check first

There is a setting that instructs search engine robots not to index the site, implemented by adding a robots noindex meta tag to the header of the site or of individual pages.

That is the correct behaviour to want while a project is in progress, and it is the first thing to verify when a published Figma Make site cannot be found.

The pattern is the same one that appears on Framer and Webflow: a toggle switched off during development for good reasons, and never switched back at launch. The site works, it looks finished, and it carries an instruction telling search engines to stay away.

Check it at the site level and on individual pages, since it can be applied at either.

Where this platform fits

Worth being direct about the shape of the tool rather than only its settings.

Figma Make is exceptionally good at producing something that looks finished quickly, which is genuinely valuable for a landing page, a prototype, or a marketing site with a small number of pages that you want to look considerably better than the alternative.

It is a poorer fit for a content-heavy site whose strategy depends on publishing many pages over time, because that is precisely the case where a sitemap earns its keep and where the per-page metadata work grows.

So a reasonable read is: excellent for a small, beautiful site in front of something, and worth thinking twice about if your plan is thirty guide pages. That is not a criticism of the tool, it is a question of matching it to the job.

What to do on a Figma Make site

In order, and none of it takes long on a site of this size.

  • Connect a custom domain, before anything else attaches to the address.
  • Confirm the noindex setting is off on the site and on every page you want found.
  • Give every page a different title and description, written as answers rather than as labels.
  • Link every page from your homepage or from a page reachable from it, since links are doing the sitemap's job here.
  • Verify the domain in Search Console and request indexing on each page individually.
  • Then check that a shared link produces a card rather than a bare URL, since that is the one remaining tag-level item.

Part of a larger guide

This page is one part of Vibe coding SEO. The other parts:

Questions people ask

Can I add a sitemap or robots.txt to Figma Make?
No. Figma-hosted files and prototypes do not provide access to a public folder and do not support custom server routes such as robots.txt or sitemap.xml, so neither file can be configured. Both live at fixed addresses at the root, which is exactly what you cannot write to.
Does the missing robots.txt hurt me?
No. A missing robots.txt means nothing is restricted, which is a safe state and better than a wrong one. The sitemap absence is the one that costs you, because a new site with no incoming links is the case where a sitemap does the most work.
How do I get indexed without a sitemap?
Two things substitute well. Make every page reachable by following links from your homepage, ideally within two clicks, since links solve the same discovery problem. Then verify a domain property in Search Console and request indexing on each URL directly, which is manual and works on a small site.
Why is my Figma Make site not appearing in search?
Check the noindex setting first. There is a setting that instructs search robots not to index, implemented as a robots noindex meta tag on the site or on individual pages, and it is commonly switched on during development and never switched back at launch.
Can I set a title and description per page?
Yes. You can specify a title for a published file, which appears in browser tabs, search results and social previews, and a meta description described as a short summary intended to improve click-through. Write them as answers rather than as labels.
Is Figma Make a good choice for SEO?
For a small, visually strong site of a handful of pages, it is reasonable once the domain and titles are handled. For a content-heavy plan of thirty guide pages it is a poorer fit, because that is exactly where a sitemap earns its keep and where per-page metadata work multiplies.

Confirm nothing is telling crawlers to stay away

The free crawler view fetches your published site and reports what a crawler receives and what your robots directives say.

See what a crawler gets Have Licheo do it for you