CMS Content Changes in Staging Immediately Propagate to Production Domain

Environment Synchronization Behavior

Webflow operates on a proprietary hosting model where the Designer serves as the sole development environment, with separate staging (webflow.io) and production (custom domain) publish targets. The platform lacks native version control for CMS content, relying instead on manual site backups for state recovery.

Observed Propagation

When editors modify CMS entries while viewing the staging domain, those changes appear to apply globally across both staging and production environments without an explicit publish action to the production target. This behavior contradicts the expectation that staging serves as an isolated validation layer.

Constraints

• No local development or Git-based workflow exists to stage content changes independently.
• Exporting the site to external hosting removes Designer-based CMS editing entirely.
• Native CMS migration tooling between project environments is absent.

Given these constraints, the inability to preview CMS changes on staging without affecting production creates a single-point-of-failure for content workflows.

Questions

1. Is the immediate propagation of CMS edits from staging to production the documented default behavior, or does it indicate a misconfigured publish setting?
2. Can CMS content be versioned or branched independently of the site design backup snapshots?
3. What workflow does Webflow recommend for validating CMS changes on staging before they reach the live production domain?