When collection items in the primary locale, corresponding localised pages are set to ‘staging’ and subsequently end up being published inadvertently (without being translated). This is a major SEO issue.
Similar behaviour occurs when a page in the primary locale is updated.
Is there a way to prevent this behaviour, and for pages in the secondary locales to be set as ‘draft’ instead?
We have a large content team publishing dozens of pages each day, and manually changing the status of pages across multiple secondary locales each time is highly inefficient and leaves room for human error.
Hey Sam - heh heh CarePatron, I use your product and have chatted to Jamie quite a few times.
CMS Pages
In general when you create a CMS item in a localized site, Webflow creates all of the locales. You would manually visit each locale and publish/unpublish CMS items depending on what you need.
However I’ve seen mentions that the API behaves differently- creating a new CMS item might be more granular and create only the base locale- then you create each of the localized variants you want individually through the API as well.
I think I’d lean hard into the API at least for reporting and auditing- if it could determine which pages are in which locales, and then compare that to e.g. a Google Sheet of what you actually want published where, you’d at least have a workable audit process.
You might even be able to build that more easily using the autogenerated sitemap XML as the means of identifying published locales for each page.
Static pages
Jamie mentioned you guys built using Webflow- he didn’t indicate whether you’re running on an Enterprise plan. If you are, static pages now support locale-specific drafting as well on Enterprise plans.