I'm not the original requestor, but I was looking for a way to do this, too.
There are many reasons why one would want a page to not turn up in search. In our particular case, the user who asked for it has a child page where a user can propose revisions for the parent page – the parent page is locked down to prevent editing, and they don't want to use comments. The revision page is named "Revision original page name", and in quick search it shows up before the actual page for some reason.
Other reasons are similar – search results are for people looking for information and some pages may appear to a search engine to contain information, but may contain nothing useful. One case we have is that we've got "source" pages that exist only to be included in other pages – we would like those pages to be invisible to search so users never find them.
In general, being able to exclude pages means giving your readers a better experience.
FWIW, it seems to me that responses to feature request are often along these lines – Atlassian doesn't see why anyone would want to do that, so you reject it. In general, the answer is that users don't see things the same way you want them to, and increased flexibility (when it doesn't introduce increased complexity) is usually a good thing.
Suggestion
I'm not the original requestor, but I was looking for a way to do this, too.
There are many reasons why one would want a page to not turn up in search. In our particular case, the user who asked for it has a child page where a user can propose revisions for the parent page – the parent page is locked down to prevent editing, and they don't want to use comments. The revision page is named "Revision original page name", and in quick search it shows up before the actual page for some reason.
Other reasons are similar – search results are for people looking for information and some pages may appear to a search engine to contain information, but may contain nothing useful. One case we have is that we've got "source" pages that exist only to be included in other pages – we would like those pages to be invisible to search so users never find them.
In general, being able to exclude pages means giving your readers a better experience.
FWIW, it seems to me that responses to feature request are often along these lines – Atlassian doesn't see why anyone would want to do that, so you reject it. In general, the answer is that users don't see things the same way you want them to, and increased flexibility (when it doesn't introduce increased complexity) is usually a good thing.