How to find orphaned pages in Confluence

A Confluence space rots quietly. Pages get created, linked from somewhere, then that link is removed or the parent page is reorganised — and the page is still there, still searchable, but nothing points to it anymore. That’s an orphaned page: no parent in the tree, no inbound link, not the space homepage. Confluence Cloud does keep a native list of these, buried in Space Settings — but it only covers one space at a time and gives you nothing to fix them with, which is why orphans still pile up.

What Confluence’s native orphan list actually shows

Confluence Cloud tracks this, just not where most people look. Go to Space Settings → Content → Hidden and you’ll find what Atlassian’s own docs describe as the space’s orphaned items — pages with no incoming links that also sit outside the page hierarchy. Three things limit it in practice:

• It’s per space. There’s no instance-wide or cross-space view, so auditing ten spaces means opening the Hidden screen ten times.
• It’s a list, not a tool. There’s no bulk re-link, merge, or archive action attached to it — you still clean up each page one at a time.
• It’s easy to miss. The screen is labelled Hidden, not Orphaned, which is a large part of why “how do I find orphaned pages” keeps coming up in Atlassian’s own community forums.

The same gap exists for broken internal links, only worse: Confluence has no native report for those at all — a link-validator feature request has sat open on Atlassian’s tracker since 2019. You find each broken link when it 404s in front of a reader, the worst possible time.

So the native orphan list is real but narrow, and broken links get no native list whatsoever.

Auditing more than a handful of spaces

Checking the Hidden screen space by space works fine for one or two spaces. Past that, the practical move is to scan every space at once and compute the same thing Confluence’s native list does — plus the broken links it doesn’t track. That’s what Evergreen does: it surfaces orphaned pages (no parent, no inbound link, excluding the homepage) and broken internal links across your spaces in one pass, free for up to three spaces, with no data leaving your tenant.

What that adds over the native list:

• One list across spaces instead of opening Hidden in each one.
• Broken links in the same report — the half of space decay Confluence doesn’t track at all.
• A repeatable audit — run it again after a reorg instead of re-checking by hand.

The takeaway

Confluence Cloud’s own orphan list — Space Settings → Content → Hidden — is real, but it’s per-space, has no bulk fix, and stops at orphans; it says nothing about broken links. If you’re managing more than a couple of spaces, either check Hidden in each one and hunt broken links by hand, or use a content-hygiene tool like Evergreen to compute both across every space in one pass — the same sweep finds stale pages and broken links.