Turn on delete after publishing

Last modified: June 4th, 2026

Permissions required

Members of the Owners and Developers Default Permission Groups, or Custom Permission Groups with the site:settings:git:write permission, can change the post-publishing behavior for a Site.

You can configure CloudCannon to delete a branched Site automatically after a successful publish to its Publish Branch. This is useful for single-task branched Sites — for example, drafting a blog post or making a one-off content update — and keeps your Project tidy.

For new branched Sites in a Project — whether you create them manually or CloudCannon creates them automatically from a Pull RequestDelete this site after publishing is turned on or off based on the Delete branched site after publishing option in your Branch Defaults.

These instructions assume you have already connected a Publish Branch to your Site.

To turn on delete after publishing for a Site:

  1. From your Site, click Site Settings in the Site Navigation.
  2. Click Publishing in the Section Navigation.
  3. Under Post-publishing behavior, check the box labeled Delete this site after publishing.
  4. Click Update Publishing Settings.

CloudCannon will save your post-publishing behavior preference for the Site. The next successful publish from this Site will delete it from CloudCannon, whether you publish by clicking the Publish button in CloudCannon or by merging a related Pull Request in your Git Provider.

A screenshot of the Publishing page in Site Settings shows the Post-publishing behavior section with the Delete this site after publishing checkbox.

This setting takes effect on the next successful publish — it does not retroactively delete Sites that have already published.

You can use the same method to turn delete after publishing off. Branched Sites will then remain in CloudCannon after publishing. Sites that have already been deleted by a previous successful publish are not restored.

Related Resources

Open in a new tab