StagBane- Page Health Auditor for Confluence

StagBane helps Confluence admins find pages that have quietly gone out of date- unowned, unreviewed, orphaned, or pointing at deleted pages- and review them before people, and Rovo, keep treating them as reliable.

It does this in two places:

• An admin-only review queue in Confluence settings that ranks every page in your audited spaces by staleness, and tells you exactly why each page is ranked where it is.
• A Rovo agent, the Page Health Auditor, that reads individual pages on request and gives a grounded second opinion on whether their content still holds up- and, on your confirmation, can take the same non-destructive actions the queue offers.

It is built entirely on Atlassian Forge. It has no external servers, makes no external network calls, and collects no telemetry. It never archives or deletes anything.

The problem: knowledge rots silently

Confluence makes it easy to write a page and hard to notice when that page stops being true. An onboarding guide describes a tool you retired last year. Two policy pages give different answers to the same question. A runbook links to three pages that no longer exist. None of this announces itself- the page still loads, still ranks in search, and still reads as authoritative.

This was a manageable risk when a human read the page and brought their own skepticism. It is a larger risk now that Rovo and Confluence search surface those same pages as answers, with none of that skepticism attached. A confidently wrong page is worse than a missing one, because people act on it.

StagBane exists to make that decay visible and reviewable- without guessing, and without ever changing your content on its own.

How StagBane works

1. You choose which spaces to audit. StagBane scans nothing until an admin selects spaces, so personal drafts and archives never flood the queue.
2. A daily scan reads page metadata and internal links. The first scan of a space reads each page once to build a link map; after that, only pages that changed are re-read. Page body text is read to extract links and then discarded- it is never stored.
3. Each page is sorted into a band by explicit rules. Critical, Stale, Watch, or Healthy- decided by an ordered list of rules, not a hidden score. Every page shows the rule that placed it there and every signal that fired.
4. You review and act. From the queue, an admin can mark a page as current, flag it for follow-up, ask its owner to review it, or open the Rovo agent for a content-level read. StagBane labels and requests; people decide.

What you get

A deterministic review queue. Every audited page lands in one of four bands- Critical, Stale, Watch, Healthy- and every row names the exact rule that put it there. There is no opaque "staleness score" to argue with: if you disagree with a band, you can see the single sentence behind it and the signals it was based on.

Banding you can explain to your team. Bands are computed from five plain signals- page age, owner presence, review recency, whether other audited pages link to it, and whether its internal links are broken. The highest-precedence rule that matches sets the band, and every firing signal is listed alongside it, so each page's placement is fully explained and defensible in a meeting.

A grounded Rovo agent. The Page Health Auditor reads a page (or compares two) on request and tells you whether the content still looks accurate- the kind of staleness no timestamp can catch. It cites the specific text behind its judgment, names the page version it read, and, for pages already in the queue, cites the queue's band as context. Its verdicts are never stored, and it never changes your content on its own- but on your explicit confirmation it can take the queue's non-destructive actions (mark current, ask the owner to review, flag for follow-up) for you, and site admins can ask it which pages are stale. See the Rovo agent guide.

Non-destructive actions, always. StagBane never archives, deletes, or rewrites a page. Its actions are limited to adding labels, recording a review date, and posting a single comment that asks a page's owner to review it. Every change to your content is one a human triggered and can undo.

Designed for Atlassian trust

StagBane is built to be easy for a security-conscious admin- or an Atlassian Marketplace reviewer- to say yes to.

See Privacy & data for the full, conservative breakdown.

Who should use this

• Confluence site admins who are responsible for the trustworthiness of a knowledge base- especially one that Rovo or Confluence search now answers from. The review queue is admin-only.
• Knowledge managers and documentation owners who need a defensible, repeatable way to decide which pages to review first, instead of relying on memory or ad-hoc audits.
• Teams adopting Rovo who want to clean up the pages their AI answers will be built on, before those answers go wrong.

Every licensed user benefits indirectly: the Rovo agent is available to anyone in Rovo chat, and it only ever reads pages that user can already see.

Note on pricing. StagBane is a single-tier paid app with the Marketplace's standard 30-day free trial, and works on the Confluence Standard plan. Confirm the current price on the app's Marketplace listing.

Start here

• Quick start- install, audit a space, and find your first stale page in about 15 minutes.
• User guide- install, choose audited spaces, read the queue and its signals and bands, use each action, work with the Rovo agent, and troubleshoot confusing results.
• Rovo agent guide- what the Page Health Auditor reads, the actions it can take on your confirmation, the admin stale-list, and example prompts.
• Privacy & data- exactly what the scanner and agent read, what is and isn't stored, what happens on uninstall, and how restricted pages are handled.
• Changelog- what shipped in this release.