Klem HQ · Product 1 · Built on Atlassian Forge

PageKeeper.

Find, remind, and archive stale Confluence pages. Keep your knowledge base trusted.

PageKeeper runs nightly inside your Confluence Cloud, scoring every page on edit recency, view count, and broken-link density. Owners get a quiet weekly nudge inside Confluence — one footer-comment per owner, never a flood of email. Admins see a per-space health score and bulk-archive what no longer earns its place.

Install on Marketplace See pricing

Atlassian Marketplace listing approval pending. Email goes to early-access list.

PageKeeper admin dashboard after a completed scan, showing per-page list with stale reasons and recommended owners

01 / Why

Confluence rot is real, and expensive

After two or three years, most Confluence instances hold more outdated pages than current ones. Search becomes a coin flip, new hires learn the wrong things, and storage bills climb every quarter.

Trust in search erodes

Engineers stop opening Confluence because half the top hits are two years old. The wiki becomes the place you check after Slack, not before.

New hires learn outdated things

Onboarding pages reference deprecated services, archived processes, and people who left two years ago. Each correction costs an experienced teammate an hour.

Admins know, but have no time

The IT or knowledge manager can see the rot building. Manual cleanup means weeks of meetings to find owners and adjudicate every page. Nobody has that runway.

02 / How

Set it once. Keep your knowledge base clean

PageKeeper installs in 60 seconds, runs nightly inside Atlassian Forge, and lets owners decide. The product makes recommendations — humans keep authority.

01.

Nightly scans across every space

Choose which spaces to monitor. PageKeeper scores every page each night without touching content — only metadata signals like last-edit, views, and labels.

02.

Configurable stale rules

Set thresholds for no-edit, no-view, and low-traffic pages. Use evergreen labels to skip canonical reference pages. Defaults work; everything is tunable.

03.

Right-person reminders

One footer-comment per owner per scan, posted on their first stale page with mentions. Quiet by design — N owners get N comments, not N times M page noise.

04.

Admin health dashboard

A per-space health score, trends over time, and a ranked list of which teams have the most cleanup to do. Built for admins who want one weekly glance.

05.

Bulk archive with audit log

Archive only by default — pages move to a dedicated archive space and can be restored in one click. Every action is logged with who, when, and why.

06.

Runs entirely on Atlassian Forge

No external servers, no shadow data store. Page metadata stays in your tenant. SOC 2 inherited from Atlassian. Auditable from the day you install.

03 / Dashboard

Built for Atlassian admins who want quiet

Open the dashboard once a week. The health score tells you whether the wiki improved or regressed. The per-page list ranks the worst offenders, each with stale-reasons chips and a recommended owner.

Per-space health score with weekly trendline
Ranked per-page list with stale-reason chips
Recommended owner inferred from page history
One-click bulk archive with full audit log

PageKeeper dashboard scoped to the Engineering space, showing per-page health and stale-reason chips

04 / In Context

Lives where your team already works

PageKeeper admin dashboard overview showing health score and top stale pages

A Confluence page with a single PageKeeper footer-comment notifying the owner

PageKeeper runs entirely inside Atlassian Forge. Pages stay in your instance. Owners are reminded inside Confluence with a single footer-comment per owner — quiet by design.

05 / Pricing

Priced so it’s a no-brainer

Pays for itself with the storage savings alone. Billed monthly through Atlassian. Annual billing available at 20% off.

Free

$0 / mo

1–5 users

Nightly scans across every space
Owner reminders in Confluence
Admin health dashboard
Bulk archive with audit log

Install free

Marketplace listing approval pending. Email goes to early-access list.

Your data stays in your instance

PageKeeper is built so that the simplest answer to every security question is the truthful one: nothing leaves Atlassian.

Runs entirely on Atlassian Forge — no external servers, no shadow infrastructure.

Zero data leaves your Confluence instance. PageKeeper reads metadata only — never page bodies.

SOC 2 inherited from Atlassian. Compliant with Atlassian Cloud Fortified requirements.

Open Privacy Policy and Terms of Service — written in plain language, not boilerplate.

07 / FAQ

Common questions

Will PageKeeper delete my pages?

No. By default, archive only — pages move to a dedicated archive space and can be restored. Hard-delete is opt-in per page.

What signals does PageKeeper use to flag a page as stale?

Last-edit time, view count, broken link density, and label exclusions. Configure thresholds in the admin dashboard.

Does PageKeeper read page content?

No. PageKeeper reads page metadata (last-edit, views, labels, owner) — never the page body. The product cannot see your content.

How does PageKeeper notify owners?

A single footer-comment per owner per scan, posted on their first stale page with mentions. Quiet by design — N owners receive N comments, not N times M page noise.

Can I trial PageKeeper before paying?

Yes. Free tier supports up to 5 users with no time limit. Pro tier offers a free trial through Atlassian Marketplace.