You archive a page. A few months later, a colleague searches for the topic — and your archived version is one of the first results. They open it, see outdated information, and either waste time figuring out if it's still valid or act on incorrect data.
This is not a hypothetical. Confluence Cloud's standard search does not automatically exclude archived pages. The issue has been raised in the Atlassian Community (tracked as AI-980), and Atlassian's own guidance points users toward advanced search as a manual workaround. The problem is that manual workarounds are applied inconsistently and put the burden on the person searching, not the person archiving.
The root cause is a gap in Confluence's native archiving: archiving a page hides it from the page tree, but does not remove it from the search index by default. That gap is where Better Content Archiving for Confluence comes in.
How Better Content Archiving solves the search clutter problem
Better Content Archiving adds a content status layer on top of Confluence Cloud. Every page and blog post can carry a status — for example Up-to-date, Needs review, Outdated, or Archived. These statuses are stored as CQL fields, which means you can write precise searches that explicitly include or exclude content based on its lifecycle state.
The app's CQL fields are prefixed with arch.*, so they integrate cleanly with Confluence's built-in CQL fields and any other third-party fields without conflict.
Steps: filtering archived pages out of your search
-
Install Better Content Archiving from the Atlassian Marketplace and complete the initial setup by configuring a content status scheme for your spaces.
-
Define your content statuses. A typical scheme includes statuses like Up-to-date, Needs review, Outdated, and Archived. Go to the app's global configuration and set these up before rolling out to users.
-
Mark archived pages with the Archived status. Users can set a status using the Quick Actions menu on any page — no edit permission required. For existing pages that were already archived with Confluence's native archive function, you can bulk-assign statuses using automation schemes.
-
Search with a status filter using CQL. Use the CQL Search app alongside Better Content Archiving to run filtered searches. To find only active content in a space, use:
space = "YourSpace" and not arch.status = "Archived"
To find only explicitly up-to-date content:
space = "YourSpace" and arch.status = "Up-to-date"
- Embed the filtered search as a macro on your team's space homepage using the CQL Query macro from the CQL Search app. This gives every visitor a clean, status-aware list of current pages without needing to know CQL themselves.
A CQL query using Better Content Archiving fields to surface only relevant, non-archived content
Automate status transitions so archived content stays out of search
Manually marking pages as Archived works but doesn't scale. Better Content Archiving's automation schemes let you define rules that run on a schedule — for example, automatically transitioning pages that haven't been viewed in 180 days to Outdated, and pages that have been in Outdated status for 60 days to Archived.
Once pages carry the Archived status, they are excluded from your CQL queries automatically. No manual cleanup required.
You can also configure the app to send email notifications to page owners before a status transition happens, giving them the opportunity to review and update content before it gets archived. This keeps the process transparent and avoids archiving pages that are still actively used.
Use the Status Report to measure how much noise your search has
If you're not sure how much archived or outdated content is currently polluting your search results, the Status Report gives you a breakdown of page counts by status per space. It's a fast way to audit the scope of the problem before and after a cleanup initiative.
The Content Analytics report adds another angle: it shows page views over time, so you can identify pages that are technically "active" but have had zero views in months — prime candidates for review.
Together, these reports make it easy to move from reactive cleanup to a structured, ongoing content governance process where search results stay relevant without anyone needing to think about it.
