Link Health scans one Confluence Cloud space, on demand, and reports the broken internal links it can check. The results are grouped by the target that died rather than listed row by row: when a retired page is linked from six others, that is one fix, and Link Health names it at the top of the queue with the count beside it.
Every row is a deep link into the editor of the page that carries the broken link.
Last scan · N pages · N broken · N need a look.If Scan now answers Space administrators only, you can view this space but Confluence does not list you as able to administer it. See Troubleshooting.
A single scan covers up to 500 pages. If the space is larger, the header says so and states how many of its pages were checked, rather than presenting a partial result as a complete one. Scan now also continues a scan that Atlassian paused mid-run instead of starting it over.
After a scan that covers a whole space, Link Health offers a Re-scan … once a day switch under the header. It is off until an administrator turns it on, and it is set per space. If the switch answers Space administrators only, see Troubleshooting.
Turning the switch off stops the daily runs for that space immediately. Results already scanned stay where they are.
| Column | What it means |
|---|---|
| Status | Missing page — the link points at a page Link Health could not find, in this space or in the other space the link names. Red rows are counted as broken. Yellow rows are counted under Needs a look: the evidence cannot tell a deleted page from one that is restricted from Link Health and still opens for your readers. Link Health reads the space as itself, not as you. |
| Page | The page that contains the broken link. Click it to open that page's editor. |
| Link | What the link was pointing at. |
| Detail | Extra context when there is any. For a missing page: what Link Health checked, and whether the page may only be restricted from it. |
| On page | How many times the same broken reference appears on that page. |
Above the table, a banner names any target that several pages point at, so the highest-leverage fix is the first thing you read.
Link Health states its own limits on screen, under the scan header, every time. An empty queue is never presented as a clean bill of health.
Nowhere. Link Health runs entirely on Atlassian Forge and declares no external permissions and no remote services, which is why it is eligible for the Runs on Atlassian program. Scan results are held in Atlassian-hosted Forge storage, scoped to your installation and readable only by the app — it is Atlassian's infrastructure, not the publisher's and not a folder inside your site. The publisher operates no servers for this app and receives no page content. The app also stores your Atlassian account ID as the key of one preference: the last space you picked.
Full detail: Privacy Policy.
New scans require an active licence. The app checks it before starting an on-demand scan, and Atlassian skips the daily scheduled run entirely on a site without an active licence. Results that were already scanned stay readable, so an expired licence never hides what you have already seen. If the app reports that it is unlicensed while you believe it is licensed, allow a few minutes for Atlassian's licence state to propagate, then reload the page.
They are administrator-only by design. Ask a Confluence administrator to open them.
Starting a scan and switching the daily re-scan on or off change what every administrator of the space sees, and a scan spends the app's Atlassian request allowance (its Global Pool), which is shared by every installation of the app. So Link Health asks Confluence whether you can administer that space, as you, and goes ahead only on a yes. You can still read the space's results. Ask an administrator of that space to give you space administration.
Link Health asks Confluence, as you, whether you can open the space and, before a scan or a change to the daily re-scan, whether you can administer it. When Confluence does not answer, for example because it is busy or is limiting requests, nothing is shown, started or changed. That is not a refusal: reload the page, or press Scan now again, in a moment.
Zero means no broken internal links that Link Health could check. Read the notes under the header for the rest: external links and attachments are outside the scan, and the notes count the links into other spaces that could not be checked, the page links that could not be confirmed with Confluence in this scan, and the links that point at a page Link Health cannot see (deleted and purged, never created, or restricted from the app). Rows that need a look are counted separately in the header.
A page that was restored or moved after the scan will still appear until the next scan. Run Scan now again — the header will tell you what changed since the last run. If the row stays, the page may be restricted from Link Health: the app reads the space as itself, so a page it is not allowed to see can look missing to it while it opens for you. The row's Detail says when that is possible.
Support page — how to reach us, what to include, and our response commitment.