Content Health for Confluence
This is Step 1 of the app — small, free, and read-only. There is no dedicated support team yet, but every question gets a real answer from the person who built it.
Get help
Bug reports, feature requests, and general questions. This is the fastest way to reach us and the one we check first.
github.com/amotavasseli/content-health-confluence/issuesIf you'd rather not use GitHub, or your issue involves account or billing details you don't want in a public tracker, email us.
amotavasseli@gmail.comFAQ
No. Content Health requests read-only permissions and nothing else — it cannot edit, archive, move, or delete a page, not as a policy we promise to keep, but because the permissions to do so were never requested. You can verify this yourself on the listing's permissions tab before installing. It reports what it found and stops there; every fix stays yours to make.
Cost. Every scan is bounded so the free report can stay free, and the 300 pages selected are your most recently updated ones — the pages people are actually reading and editing right now, not a random or alphabetical slice of your site. If your site is larger than 300 pages, the oldest, least-recently-touched pages are the ones left out.
The duplicate and contradiction checks are the two findings that require sending page text to an AI model for comparison, and that step costs real money per scan. It's protected by a kill switch that defaults to off. When it's off, you still get the five zero-cost checks — stale, orphaned, empty, broken-link, and ownerless pages — just not the two AI-assisted ones. Turning it on is a deliberate choice we make, not something that happens automatically.
A cheap, structural pass narrows your whole site down to a small number of page pairs that look similar. Only those pre-filtered pairs — not your whole site — are sent to Claude via Atlassian's own Forge LLMs API for a closer read, entirely inside Atlassian's infrastructure. Nothing is sent to a third-party server. For the full policy, see our privacy policy.
Content Health runs on a scheduled interval configured by the app, plus you can trigger a manual rescan at any time from the dashboard. Either way, unchanged pages are skipped automatically, so a rescan only does new work on what actually moved.
No. Install it, open the Content Health page from your Confluence sidebar, and the first scan starts. There's nothing to set up and no credentials to enter — it's free while the app is in early access.
Permissions, restated
This is the single most important thing to know before you install: Content Health has no write scopes at all. It cannot edit, archive, move, or delete a page. Everything it does is read, analyze, and report.
Known limitations
No real page-view counts. The 300-page cap ranks by most-recently-updated, not by how many people actually view a page, because real view counts require an API scope this app does not request.
Broken-link findings can't always tell why a link is broken. A link that points at a genuinely deleted page and a link that points at a page just outside the 300-page cap both surface as "broken link." On a large site scanned under the free-tier cap, a small number of these may be false positives.
No external error monitoring yet. If a scan fails, that failure is recorded in your report and shown on the admin page — but nothing proactively alerts us. If a scan looks stuck or wrong, please tell us via GitHub Issues.