Has anyone experienced “disappearing content” on localised sites?
I’m not able to replicate the exact steps, however it’s occurred a dozen or more times on one site we are building and it’s very concerning.
It seems to be isolated to situations where we have used component slots. Some, not all, props on components within these slots, will occasionally “loose” their translated copy.
The primary locale does not experience this issue, only the secondary locale.
I raised the issue with Webflow Support, but without steps to replicate they are not able to help.
Abandoning component slots would be a real shame (and a lot of work) but this might be the only option to prevent translated content from randomly vanishing.
Let me know if you have seen anything like this. I can’t believe that this is isolated to just this one site.
Yes, we have experienced a lot of issues with components + slots + variants when mixed with localization.
So much so that we had our entire site built with components, but re-built everything to remove them. Components + localization (especially it seems when you throw variants and/or component slots into the mix) just isn’t ready for primetime yet.
It’s really unfortunate because components make maintaining a site so much easier. Hopefully the Webflow team realizes these great features can’t actually be used in production if they’re going to result in things like that really important CTA button disappearing randomly on random locales, and are working on stabilizing things.
Edit/update: Webflow confirmed they’re aware of issues like this, so I’d definitely recommend not using components much with locales right now (especially if you mix in variants or slots). Anytime you have an issue, submit a support ticket; the more we do that, the more likely they are to make fixing these issues a priority.
Update 19 Feb 2025
I have reached out to Webflow Support again regarding this bug and have some interesting information.
1/ per the previous reply for John, Webflow Support confirm this is a know issues relating to localisation of components nested within a component slot.
2/ Webflow Engineering have not yet fixed the root cause
3/ This issue is limited to Build / Edit mode. Working on content while in Design mode will not result in the data loss you’ve previously experienced, so part of a workaround options are to avoid the use of Build / Edit mode on secondary locales.
Right now we are about to start on another localization project. This one larger than the previous. And the primary local / existing website is already utilising many component slots.
Given the news of item 3, I am tempted to proceed with the localisation without first removing/converting all component slots. This would mean avoiding Build mode on the localised sub-sites and crossing fingers in the hope this issue will be resolved so that at a later date.
I wish we were not in this position. 
On 6 March 2025 Webflow support informed this issue is now resolved!
Our team has now pushed a fix for the the two separate work streams I previously described, and you should now find that you no longer experience data loss on the secondary locale when using Build / Edit mode .
Since then I have been testing on a fairly large website with many components including nested components inside component slots, and using build mode extensively on localised pages, and I am happy to report that so far we have not seen any vanishing content!
Thank you Webflow support for listening and sorting this issue.