We have critical data on some of the Confluence pages. Even though no data is saved by the third party LLMs, we would like to exclude some contents from the index or in other words: hide them from rovo (regardless of search, agent etc.)

+1 This functionality would definitely help us declutter search results and help users find the content they're looking for.

This would be a game-changer for our team! We're currently evaluating competing platforms due to the frustration and confusion this causes for our users.

We have a separate space for our team huddle notes and this content spills over into our search results when trying to use our other KB specific space.

+1 We store customer/meeting notes in personal spaces. We want these pages to be accessible to everyone, but not have them available in the global search. There is not an easy way to exclude these pages. 

Being able to easily exclude all personal spaces and/or all meeting note pages would be great.

Please help us spread the word and share it in social media to get more votes  feel free to retweet our post if you like. https://twitter.com/nmc_info/status/994638611499966464 

I up-voted as well for our team. We're a service firm: when we finish a project, I'd love to "demote" its pages while leaving them available for browsing.

This would be extremely helpful. Our experience is that Confluence becomes a massive pile of pages.. and search results often show tons of older, less-relevant pages.

I'd think to add this option to the Restrictions interface... and that it would behave the same way: a child page would inherit its settings from a parent page.

I imagine pages and spaces should have three states, not two:

1. Active page, as today. In search results, browsable, etc.
2. Less-Active page, still content that you want available, but 'demoted' to a child state when it comes to search. I want these sorts of pages to remain in my browsable hierarchy, but I want them ignored for search purposes.
3. Archived pages, no search, no browse.

I think this feature request really is about improving search results, not about page attributes or states. I'd like search to be much more useful... and by 'demoting' various pages and nested directories of pages, the important stuff can float to the top. That's the theory anyway.

Super useful!

Concurring. We have how-to's that are useful for specific teams that I have to put a disclaimer at the top of to ignore for all but a select few. We also want to keep documents for historical purposes.

Concurring. We have how-to's that are useful for specific teams that I have to put a disclaimer at the top of to ignore for all but a select few. We also want to keep documents for historical purposes.

We store tons of retrospective journals as pages. We need them to be accessible by everyone but in the same time they quite pollute search results page. Those pages shouldn't be indexed. Now we can't protect them properly except that moving them to private space

I'm very surprised that this feature doesn't already exist. 

It would be extremely useful to exclude specific topics from the internal search feature.