Unpublish content
Release date: 1st May 2024
This Dynamic Content release introduces unpublishing for content items, allowing you to stop published content from being available to your audience. For example, if content has mistakenly been published to your website, you can use unpublish to remove it.
Once you've unpublished content it can no longer be retrieved using its production URL, using either its ID or delivery key if one exists.
A key benefit of unpublish is that it makes it easier to remove and reuse delivery keys that have been published with content. See Unpublishing and delivery keys.
The SEO Assistant extension can now be configured to work with JSON output from the Generative Rich Text Editor. See the SEO Assistant extension.
Unpublishing contentLink copied!
When you're working in Dynamic Content, you can unpublish content from the content library, the content form, and the archive folder.
Here we are unpublishing a content item from the content library, by choosing "Unpublish" from the item's contextual menu.
A dialog prompts you to confirm the unpublish. Once you confirm, the content is unpublished and its publish status icon is updated to a grey cloud. The content item properties pane is also updated to show that the item has been unpublished.
Unpublishing linked contentLink copied!
Unpublishing the parent item of linked content, such as a carousel, unpublishes the parent item but not the child items. The child items remain published in case they are used in other places. See Unpublishing linked content for more information.
Unpublishing and a hierarchy nodeLink copied!
If you no longer wish a content item to be part of a hierarchy, you can simply unpublish that content item and it will no longer be shown. See Unpublishing and removing a node for more details.
Unpublishing and delivery keysLink copied!
Unpublishing makes it easier to remove or update a delivery key when an item is published. You can unpublish the content item you no longer want to retrieve with the delivery key and then reuse that key. See Unpublishing and reusing delivery keys for more information.
Unpublishing and the Content Delivery APILink copied!
Unpublishing removes a content item from delivery so that it can no longer be retrieved using its published Content Delivery URL, either by ID or Delivery Key. When retrieving an unpublished item with the HTTP Content Delivery API, a 404 response and CONTENT_NOT_FOUND error will be returned. The GraphQL Content Delivery API will return null when querying unpublished content.
Unpublishing a content item also removes it from the results of Filter API queries on published content. This is particularly useful when using hierarchies for modeling a site structure. If you unpublish a hierarchy node, it will no longer be retrieved when you query for published children of its parent.
The Content Management APILink copied!
Although you can only unpublish a single item at a time from the Dynamic Content Management API using the Unpublish endpoint, you can use the API to perform common tasks such as unpublishing all archived content. See the Content Management API overview page for an example.