--- canonical: https://amplience.com/developers/docs/release-notes/2024/unpublish-content/ title: Unpublish content description: This release introduces the unpublish content feature, enabling users stop published content from being accessed by their audiences. audience: Business User image: https://cdn.media.amplience.net/i/ampproduct/unpublish-content-1?w=1200&h=630 image_width: 1200 image_height: 630 date_published: 2024-04-22 date_modified: 2024-05-31 --- # 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](#unpublishing-and-delivery-keys). > **Note: Also in this release** > The SEO Assistant extension can now be configured to work with JSON output from the Generative Rich Text Editor. See the [SEO Assistant extension](https://amplience.com/developers/docs/ai-services/seo-assistant/#schema-examples). ## Unpublishing content 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. ![Unpublishing from the content library](https://cdn.media.amplience.net/i/ampproduct/unpublish-content-1?w=1880&fmt=png 'Unpublishing from the content library') A dialog prompts you to confirm the unpublish. Once you confirm, the content is unpublished and its [publish status](https://amplience.com/developers/docs/user-guides/produce-content/publish/#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. ![Unpublished content in the content library](https://cdn.media.amplience.net/i/ampproduct/unpublish-content-2?w=1880&fmt=png 'Unpublished content in the content library') ### Unpublishing linked content 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](https://amplience.com/developers/docs/apis/content-delivery/content-delivery-overview/#unpublishing-linked-content) for more information. ### Unpublishing and a hierarchy node 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](https://amplience.com/developers/docs/dev-tools/content-modeling/hierarchies/managing-hierarchies/#unpublishing-and-removing-the-node) for more details. ## Unpublishing and delivery keys Unpublishing makes it easier to [remove or update a delivery key when an item is published](https://amplience.com/developers/docs/user-guides/produce-content/create/#updating-a-delivery-key). 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](https://amplience.com/developers/docs/dev-tools/guides-tutorials/delivery-keys/#unpublishing-and-delivery-keys) for more information. ## Unpublishing and the Content Delivery API 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](https://amplience.com/developers/docs/apis/content-delivery/content-delivery-overview/), a 404 response and `CONTENT_NOT_FOUND` error will be returned. The [GraphQL Content Delivery API](https://amplience.com/developers/docs/apis/content-delivery-graphql/overview/) will return `null` when querying unpublished content. Unpublishing a content item also removes it from the results of [Filter API](https://amplience.com/developers/docs/apis/content-delivery/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 API Although you can only unpublish a single item at a time from the Dynamic Content Management API using the [Unpublish](https://amplience.com/developers/docs/apis/content-management-reference/content-items/#unpublish-content-item) endpoint, you can use the API to perform common tasks such as unpublishing all archived content. See the [Content Management API overview](https://amplience.com/developers/docs/apis/content-management/content-management-overview#unpublishing-all-archived-content-items) page for an example. ## Related pages [Unpublishing content](https://amplience.com/developers/docs/user-guides/produce-content/publish/#unpublishing-content) [Updating delivery keys](https://amplience.com/developers/docs/user-guides/produce-content/create/#updating-a-delivery-key) [Developer guide: Unpublishing and delivery keys](https://amplience.com/developers/docs/dev-tools/guides-tutorials/delivery-keys/#unpublishing-and-delivery-keys)