Publishing Restrictions

Users can restrict the publication of items using publishing restrictions in Content Editor. Publishing restrictions let users specify that a specific item or a version of an item is publishable or unpublishable, either within a specific date range or indefinitely. In this way, users can control which items and pages are available for publishing at any given time.

For example, if a user has set up Sitecore to periodically publish the entire site to make sure it is always up to date, the user can create publishing restrictions on the items that they do not want to publish. This can be done for items that are still in progress or for finished items that should only be published when a certain campaign is rolled out, for example.

Items that are publishable are eligible to be sent to the publishing queue when a page is submitted to the publishing workflow. 

In Content Editor:

1. Click the page in the Content Tree to select it.
2. In the Publish Ribbon Navigation, click Change.
3. In the Publishing Settings dialog box, uncheck Publishable.
4. Click Save.

Users may want to publish an item on a specific future date and have the item appear in chronological order based on assigned date rather than created date. 
For example, an article may be set to publish in January 2027 but is added to the website in September 2026. The content author wants the article to display in the proper order. Placing the article in the 2027 > January folder does not tell Sitecore the proper order to sort for the publishing date. The “Publishable from” date needs to be set. 

1. In Content Editor, navigate to the item you want to prevent from publishing.
2. Click to select the item.
3. In the Navigation Ribbon, click the Publish tab.
4. Click Change.
5. In the Publishing Settings dialog box, click the Item tab. Set the “Publishable from” date range. Click OK.

If a user specifies a date range for when an item or item version is publishable, it does not mean that the item is published on the start date and removed again on the end date. Instead, it means that the item is available for publishing and included when the user submits that item or page to the publishing workflow. 
To make an item appear on the website on the start date and be removed again on the end date, the user must submit the item or page to the publishing workflow on both dates to push the changes live to production via the publishing queue.

Documentation updated: May 29, 2026

Is there an issue with this documentation? Report it here.