Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    AI-109Define the input source for Atlassian Intelligence to refer from
  2. Suggestion
    AI-585Filter searches by Space Category
  3. Suggestion
    AI-1046Rovo connector for Salesforce
  4. Suggestion
    AI-1150AI-generated Jira issue summaries in Confluence only provide outputs in English
  5. Suggestion
    AI-1077Include indexing progress on the logs
  6. Suggestion
    AI-1078Add Rovo logs to Organisation Audit Logs
  7. Suggestion
    AI-1007Suggestion to provide a way to restrict Ask AI to search only content within the Confluence Cloud instance
  8. Suggestion
    AI-167Enable User Default Filter in Confluence Search
  9. Suggestion
    AI-188Custom content should be visible in quick search
  10. Suggestion
    AI-1143Search fails to find pages with text due to tokenization. 
  11. Suggestion
    AI-1144Confluence search does not display partial search results
  12. Suggestion
    AI-1145Searching for a URL doesn't show results containing the URL
  13. Suggestion
    AI-1146Provide Better Search and Export in Confluence for Legal Discovery
  14. Suggestion
    AI-1142Support being able to search the page with the image having certain words via Atlassian Intelligence.
  15. Suggestion
    AI-792Allow searching for content contributed or created by disabled user
  16. Suggestion
    AI-1139Connector for Zapier
  17. Suggestion
    AI-1137Support multiple team connection in Miro
  18. Suggestion
    AI-1050Ability to build custom connectors for Rovo
  19. Suggestion
    AI-70Audit log for AI changes on Confluence
  20. Suggestion
    AI-180CQL to be used in Basic search
  21. Suggestion
    AI-181Search Administrative Functions with Quick Search
  22. Suggestion
    AI-349Italian language is not available in Indexing language list
  23. Suggestion
    AI-538Confluence Search: Wildcards at the beginning of a word do not work
  24. Suggestion
    AI-618Search terms should be highlighted in pages
  25. Suggestion
    AI-633Include the 'Expand macro' title in searchable content
  26. Suggestion
    AI-795Restore the ability to search for Site Spaces (exclude Personal Spaces)
  27. Suggestion
    AI-897Provide ability for additional attachment types in Advanced Search
  28. Suggestion
    AI-1022Rovo/Atlassian AI requires the ability to search within archived Jira issues.
  29. Suggestion
    AI-1024Query Confluence whiteboards and Confluence databases
  30. Suggestion
    AI-1027Allow Atlassian Intelligence to completely translate all selected text
  31. Suggestion
    AI-1062Get 'Atlassian Rovo' app for Slack approved by Slack
  32. Suggestion
    AI-1069Rovo connector for Miro
  33. Suggestion
    AI-4Ability to customize slash command list
  34. Suggestion
    AI-157Add labels to autocomplete / quicknav in search box
  35. Suggestion
    AI-323 Norwegian language is not available in Indexing Language list
  36. Suggestion
    AI-347Enable Spanish Indexing Language in General Configuration
  37. Suggestion
    AI-576Improve SQL Query for Attachment Indexing On Large Instance
  38. Suggestion
    AI-580Search results page could provide an option to export the results to an external file
  39. Suggestion
    AI-584Improve Advanced Search in Confluence UI with CQL
  40. Suggestion
    AI-587Allow Confluence Search to be accurate for page titles
  41. Suggestion
    AI-611Allow search feature to ignore accent
  42. Suggestion
    AI-621Exclude specific pages from search index without restricting access
  43. Suggestion
    AI-737Ability to Search for Labels with Quick Search
  44. Suggestion
    AI-764Ability to search by user mentions in comments on labeled pages
  45. Suggestion
    AI-829Number of the Threads for Indexing Should be Increased
  46. Suggestion
    AI-898Ability to Search for Content added with User Profile macro
  47. Suggestion
    AI-917JSM only users encounter XP-Search Aggregator errors on Recently updated and Contributors macros
  48. Suggestion
    AI-1009Enhance Search results ranking to prioritize recent content for Anonymous Users
  49. Suggestion
    AI-124Bring smart search to the live search macro
  50. Suggestion
    AI-161Re-introduce Search Favouring Label by Default and Label Browser
Refresh results
<< Previous 1 2 3 4 5Next >>
92 of 299
Uploaded image for project: 'Atlassian Intelligence'
  1. Atlassian Intelligence
  2. AI-621

Exclude specific pages from search index without restricting access

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Search - Core (DO NOT USE)
      • affects-server
      • cc-findability
      • index
      • search
      • search-result
      • solved-by-ai-rovo
    • 5
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      Feature request opened in behalf of our customer Normand(CSP-121033):

      We would like tho remove a page from the search index only without restricting the user access to it.

      Users would be able to browse/navigate directly into the page, however if they try to search for the page in Confluence search it would return not results for that page.

        is duplicated by

        Suggestion - CONFCLOUD-35817 Exclude specific spaces from search index

        • Gathering Interest
        is related to

        Suggestion - AI-795 Restore the ability to search for Site Spaces (exclude Personal Spaces)

        • Gathering Interest

        Suggestion - CONFSERVER-33161 Exclude specific pages from search index without restricting access

        • Not Being Considered
        mentioned in

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        Page Loading...

        (3 mentioned in)

              • All
              • Comments
              • Work Log
              • History
              • Activity

              Dave Lines added a comment - 21/Feb/2025 2:09 PM

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

              Dave Lines added a comment - 21/Feb/2025 2:09 PM +1 This functionality would definitely help us declutter search results and help users find the content they're looking for.

              michael_mcnees@sweetwater.com added a comment - 06/Nov/2019 9:35 PM

              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.

              michael_mcnees@sweetwater.com added a comment - 06/Nov/2019 9:35 PM 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.

              RaeRo added a comment - 06/May/2019 4:01 PM

              +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.

              RaeRo added a comment - 06/May/2019 4:01 PM +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.

              Danielle Borges added a comment - 10/May/2018 6:05 PM

              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 

              Danielle Borges added a comment - 10/May/2018 6:05 PM 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  

              Scott Love added a comment - 10/May/2018 4:56 PM - edited

              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!

              Scott Love added a comment - 10/May/2018 4:56 PM - edited 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: Active page, as today. In search results, browsable, etc. 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. 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!

              JR McLaughlin added a comment - 30/Mar/2018 7:31 PM

              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.

              JR McLaughlin added a comment - 30/Mar/2018 7:31 PM 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.

              JR McLaughlin added a comment - 30/Mar/2018 7:31 PM

              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.

              JR McLaughlin added a comment - 30/Mar/2018 7:31 PM 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.

              Ivan Styazhkin added a comment - 18/Oct/2017 5:03 PM

              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

              Ivan Styazhkin added a comment - 18/Oct/2017 5:03 PM 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

              George Alpizar added a comment - 31/Mar/2017 2:03 PM

              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. 

               

               

              George Alpizar added a comment - 31/Mar/2017 2:03 PM 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.     

              Joel Beach added a comment - 28/Mar/2017 3:46 PM

              Please add this feature. It doesn't seem like it would be that hard to flag something as either available or unavailable for search results.

              Joel Beach added a comment - 28/Mar/2017 3:46 PM Please add this feature. It doesn't seem like it would be that hard to flag something as either available or unavailable for search results.

                Unassigned Unassigned
                dluvison Deividi Luvison (Inactive)
                Votes:
                221 Vote for this issue
                Watchers:
                101 Start watching this issue

                  Created:
                  03/Apr/2014 1:15 PM
                  Updated:
                  18/Apr/2025 4:01 AM
                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian