Cookie consent перестал показываться на сайтах

Hi ​@Michael10, thanks for reaching out and apologies for the delayed reply! 

I’m assuming your referring to the Cookie consent banner for Figma Sites. If so, here are three things to check:

1. Make sure cookie consent is toggled On, a Privacy policy link is set, and you’ve published the site after saving settings.
2. Test in a private or incognito window to avoid cached consent.
3. Check the list of geographic regions to make sure the banner should appear to you as a visitor.

Please let me know if it’s still not working after checking these, and we can continue troubleshooting together. 

​@djv Thanks for the reply.

I’ve now carefully checked everything you mentioned:

• Cookie consent is enabled in the site settings
• A Privacy policy link is set
• The site was re-published after saving the settings
• I tested in both a normal browser and a private/incognito window

Unfortunately, the cookie consent banner still does not appear at all.

To make sure this is not related to my specific project, I created a completely new test site from a template. On that site I added an embedded Google Maps widget and enabled the cookie consent feature.

As far as I understand, embedded services like Google Maps should not load until the visitor accepts cookies. However, both in preview and on the published site, the map loads immediately and the cookie consent banner never appears.

Steps to reproduce:

1. Create a new Figma Site from any template
2. Enable the cookie consent banner in site settings
3. Add an embedded widget (e.g. Google Maps)
4. Publish the site
5. Open the site in a private/incognito window

Result:
The cookie consent banner does not appear and the embedded content loads immediately.

Since I am located in the EU (Germany), displaying a cookie consent banner before loading non-essential cookies is legally required (GDPR). At the moment this makes it impossible to launch the site in a compliant way.

Could you please check if this might be a bug in Figma Sites?

Thanks for the additional context, ​@Michael10! 

I’ve flagged this over to our Sites team to investigate and work towards a fix.