Breadcrumbs

Prevent a Page From Being Published

Use the label scroll-sites-no-publish to exclude a Confluence page from your Scroll site, even when the page belongs to one of your site's content sources.

The page will be excluded from your live site, but the content remains available in Confluence, so you can still use it as a resource, for example as a source for include page or insert excerpt macros, or to back page properties.

Applying the Label

To prevent a page from being published in your Scroll site:

  1. Go to any Confluence page that is part of your Scroll site.

  2. Add the label scroll-sites-no-publish to the page.

With your next site update, the page will no longer be published in your site. If the page had already been published before, it will be taken offline.

Behavior of the Label

If you add this label to one of your Confluence pages, that page and all its child pages will be excluded from publishing in your Scroll site. This means:

  • The page will not appear on the live site.

  • The page will not be reachable via a URL.

  • The page will not be included in the search index or in any representation of the page tree (article navigation, child pages macro, filter by label macro, etc.).

  • Links to the page from other published content will return a 404.

  • If the page was already live before the label was applied, it will be taken offline with the next site update.

The content itself remains in Confluence and can still be referenced from other (published) pages — for example via the include page, insert excerpt or page properties report macros.

When to Use Which Label

Scroll Sites offers different labels to control what happens to a page in your site. Choose the one that matches your goal:

  • scroll-sites-no-publish: Don't publish the page at all (and take it offline if it was previously live).

  • scroll-help-center-exclude-page or scroll-sites-only-url: Still publish the page, but exclude it from navigation and search.
    --> See Exclude Articles From Navigation and Search

For more on controlling what gets published, see → Control Publishing of Changes

Use Cases

Here are some examples of how you might leverage this label:

  • Keep draft or work-in-progress pages in the same Confluence space without exposing them on your site.

  • Maintain "building block" pages that only exist to be included into other pages via the include page or insert excerpt macro.

  • Store backing pages for page properties that you surface through page properties report macros, without publishing the source pages themselves.

  • Quickly take a published page offline without deleting it or moving it out of the page tree.