Skip to main content
Question

Sitemap Not Accessible for my Figma Make Site – Blocking Google Indexing

  • November 4, 2025
  • 4 replies
  • 35 views
Alfa
  • Alfa
  • New Member
  • 2 replies

My website (myhyroxplan.com), built with Figma Make, is not being indexed on Google because the sitemap ( https://myhyroxplan.com/sitemap.xml ) returns a 404 error. In my project, I have both a valid  sitemap.xml  file and a  robots.txt  file placed under the  /public  directory, correctly referencing the sitemap. However, this structure does not expose the sitemap to the public internet at the root URL, so Google Search Console cannot read it.


Please advise how I can serve my  /public/sitemap.xml  file directly at  https://myhyroxplan.com/sitemap.xml  for proper indexing.

Is there a supported method or workaround to enable static file hosting at the root, or is this a current limitation of Figma Make for custom domains?

 

Thank you in advance for your support

4 replies

J
Figmate
  • Junko3
  • Figmate
  • 2624 replies
  • November 6, 2025

Hi ​@Alfa ,

 

I understand you’re looking for a way to include a sitemap.xml and robots.txt file under /public.

 

After checking internally, it seems that this setup won’t work as described, since there isn’t a public directory concept in Make.

You might be able to manage this kind of metadata through the settings — for example, by adding custom code — but we don’t currently have specific instructions to support this approach.

 

Thanks,

Alfa
  • Alfa
  • Author
  • New Member
  • 2 replies
  • November 7, 2025

Hi ​@Junko3 ,

Thank you for your quick reply earlier! I’m following up because I believe my setup might actually meet the requirements you mentioned, but the sitemap is still not being served publicly.

Here’s my situation in more detail:

  • My Figma Make project does include a /public directory, where both sitemap.xml and robots.txt are stored (see attached screenshot of my folder structure).

  • The robots.txt file correctly references the sitemap (Sitemap: https://myhyroxplan.com/sitemap.xml), and both files are valid when opened locally.

  • However, once published, the sitemap URL (https://myhyroxplan.com/sitemap.xml) still returns a 404 error, preventing Google Search Console from indexing my pages.

So it seems like Figma Make is not serving the /public directory contents at the root of the site (e.g. /sitemap.xml, /robots.txt), even though these files are present in the project.

Could you please clarify:

  1. Whether there’s currently any supported way to expose static files from /public at the site root (for example via custom code, headers, or a specific deployment configuration)?

  2. Or if this is indeed a platform limitation at the moment for Figma Make’s hosting layer?

 

On Your fix proposal:

I also noticed in my Make settings that there’s a Custom Code section (for adding code at the start or end of <head> and <body>). see attached
👉 Is this the area you were referring to when suggesting a possible workaround for handling metadata or static files like sitemap.xml and robots.txt?

If so, could you please clarify what kind of custom code could make the sitemap accessible to Google Search Console?
Or alternatively, can you confirm if there’s any current limitation preventing static files from being exposed at the root in Figma Make hosting?

 

This issue is currently blocking my site (https://myhyroxplan.com) from being indexed by Google, so any workaround or clarification would be really appreciated.

 

Thanks so much for your help and for confirming how static file handling works in Figma Make!

ffchris1
  • ffchris1
  • New Member
  • 1 reply
  • November 13, 2025

hello is this issue solved anyhow? I try the tag way but is not possible as it’s part of the server’s functions. I’m facing the same issue 

Alfa
  • Alfa
  • Author
  • New Member
  • 2 replies
  • November 13, 2025

Hello ​@ffchris1 no it’s not, I tried to add redirection to Github for the sitemap without success, it sounds google cannot read my figma public folder. I would love to receive real support from Figma team please

 

Thank you


Terms & ConditionsCookie settingsAccessibility statement