Features
An explainable review queue ranks every page you audit into four bands. An advisory Rovo agent answers what no date filter can. Nothing here archives, deletes, or rewrites your content.
See the decay
Find the pages most likely to be wrong before Rovo or search treats them as reliable. A daily incremental scan ranks every page in your audited spaces- the worst pages rise to the top, and healthy pages stay out of the way.
Four bands, one rule, one sentence
Every audited page lands in one of four bands:
Critical Stale Watch Healthy
Bands come from an explicit, ordered rule set- first match wins. There is no numeric score, by design: a composite number is exactly the failure mode this queue exists to avoid. Every row can still state the single rule that placed it there, in one plain sentence.
"Why is this page here?"
R3- This page has no owner, no current review, and is over a year old.
Five signals, never a guess
Every band comes from five deterministic facts: page age, owner presence, review state, whether any other audited page links to it (orphaned), and whether its own links point at pages that no longer exist (broken internal links). All five are measurable facts about page metadata and link relationships- not opinions.
Internal links only. StagBane never checks external URLs, and never checks links into spaces you haven't chosen to audit.
Broken internal links- a report with an export
Filter the queue to every page whose outgoing links point at an audited page that no longer exists, and export the result as CSV. The export respects whatever filters are applied, so this view exports as its own report- the report Confluence Cloud has no native answer for.
Worth a closer look
A shortlist surfaces pages banded Healthy or Watch whose titles suggest hidden risk- a past year in the title, or words like "legacy" or "draft." One click opens the Rovo agent for a content-level read. This is a nomination, not a freshness judgment.
You choose what gets audited
StagBane scans nothing until you select the spaces to audit- personal spaces, drafts, and archive spaces can stay out entirely. The first scan of a space builds a link map; after that, the daily scan is incremental, re-reading a page only when its version changes. Apply the pha-evergreen label to any page that's old on purpose, and it moves to the Excluded view- out of banding until you remove the label.
Run the review loop without the burnout
Ownership rot is the part no date filter fixes by itself. StagBane's actions are built around the failure mode admins actually describe: reviewer rotations that collapse onto one person.
A Confluence admin describing exactly this failure, on r/atlassian:
"We tried a 'page reviewers' rotation thing where ownership moved around the team but it just became one persons job and they burnt out fast. I also looked at Comala approvals and confluence's built-in page expiry reminders, but they still assume someone is around to act on the reminder which is exactly the gap we have."
u/ciggafteregret, r/atlassian
Request a review- owners resolve it from the comment
One click posts a single templated comment that @mentions the page's owner. The owner replies Verified or Stale right in the thread- no queue access needed. Verified marks the page Verified Current and closes the request; Stale records a human verdict that overrides the automatic signals.
A rolling 24-hour Request Budget- default 25, admin-adjustable 1–100- plus one open request per page make notification storms structurally impossible.
Per-space review cadence
The review window is a site-wide setting, but a fast-moving policy space can be reviewed every 90 days while a stable reference space stays at a year. Set an override for one or more spaces at once (same 30–1095-day bounds as the global window); anything without an override follows the global window.
Dismiss a reason
Already considered a flag and accepted it? Dismiss that specific reason and it comes back on its own the moment the facts change- the page is edited, or that reason's specifics shift. A dismissal never changes the underlying band, is never shown to readers, and never touches the badge, the Rovo-readiness view, or the agent. Every dismiss and restore is written to an audit log.
Group by owner, and a weekly digest
Group the queue by owner to see who holds the most stale pages, with an Unassigned bucket for pages nobody owns. A weekly digest rolls the Critical and Stale pages into a "docs we would not trust" view, grouped by owner, with new and resolved counts since last week. In-product only- nothing is emailed, and nothing leaves Atlassian.
Someone on r/atlassian specified that digest before we built it:
"before letting it answer employees, i'd make it produce a weekly 'docs we would not trust' queue: no owner, no reviewed date, conflicting duplicate, too many caveats, referenced system no longer exists, last update older than whatever your team picks."
u/Hairy-Marzipan6740, r/atlassian
Show readers- and Rovo- where you stand
Two views make the corpus's health visible outside the queue: a badge every reader sees, and a coverage view for admins.
The Last Verified badge
Every audited page carries a badge in its byline. When a human has vouched for a page within the review window, readers see a green "Verified <date>" lozenge- and only then. It shows verification recency, not edit recency: a page that's merely Healthy, with no risk signal fired, is never labeled Verified, because nobody vouched for it.
Bands are never shown to readers. A site admin who opens the popover sees the full band, the reasons, and a link back to the queue- the same information the queue already grants admins, disclosed nowhere new.
Rovo-readiness, by space
An admin-only view shows the band distribution for a space, plus a headline "Rovo-trustworthy %"- the Healthy share of monitored pages. It's a coverage figure, always shown with its per-band counts, never a per-page score. The same view is askable directly in Rovo chat; non-admins are refused before any read.
Advisory rovo-ignore marker
Flag pages for AI governance with an advisory marker. StagBane's own agent and badge honor it. Atlassian does not currently ship a native way to exclude a single page from Rovo, so this marker is advisory, not enforcement- native Rovo indexing is unaffected. For hard exclusion, use Confluence's own page permissions to restrict the page.
Ask the question no date filter can
When the deterministic queue isn't enough, the built-in Page Health Auditor Rovo agent is an optional second opinion- on-demand, advisory, and never the thing that changes your content on its own.
Do these two pages contradict each other?
Ask the agent to compare two pages and it reads both, names the specific claims that disagree, and cites the page version it judged. A date filter can tell you a page is old; it cannot tell you two pages disagree. This read is unique to the agent- nothing else in StagBane, or in native Confluence, gives you this answer. The verdict is advisory and chat-ephemeral: never stored, never written back to your content, never a final ruling.
Audit one page, or find what overlaps it
Ask whether a single page still looks accurate, or ask the agent to search for other pages that might overlap or conflict with it- returned as candidates to compare, not verdicts. Asked to work through a longer list, it audits up to five pages per reply, then offers to continue.
Confirm-to-act, nothing more
On your explicit confirmation, the agent can trigger the same non-destructive actions a queue button does- mark a page current or stale, request an owner review, set the needs-review label. It never edits page content, and it never acts without you saying yes.
Admin-only questions, in chat
A site admin can ask "which pages are stale?" and get the queue's ranked list right in chat, or ask for a space's Rovo-readiness view without opening the queue. Non-admins are refused before any read.
If you have to trust one, trust the queue.
Full detail on data handling and the 10 permission scopes: see Trust & Security.
See what StagBane finds in your own spaces.
Ranked, explainable, and non-destructive from the first scan.
Get StagBane on the Atlassian Marketplace