Tool

Orphan page checker

By Sunny Patel · Updated 2026-09-20

An orphan page checker crawls a site and flags every page it finds that has zero internal links pointing to it from anywhere else in that same crawl. Paste a URL below and sitemap.digital builds the real link graph as it goes, then lists every page sitting at zero inbound links so you can fix each one directly.

See the orphan pages guide for the full mechanics of how orphans form and why AI crawlers never reach them; this page stays focused on running the check.

Free to start, no signup required.

Why sites accumulate orphan pages

Orphans build up through a handful of recurring events, not usually through a single mistake. A site migration is a common trigger, since a new template or platform can carry a page's content across while dropping the link that used to point at it. Pruning a navigation menu removes another set of links in one pass, orphaning whatever depended on them. Paginated archives quietly orphan older entries once a listing only links to its first page or two, leaving anything past that reachable only through a sitemap. A page added straight to the sitemap file, with no matching link from an actual page, starts life orphaned instead of developing that way over time.

How detection works on this checker

This scan discovers pages one of two ways, not both at once. When your site has a usable sitemap, the crawler reads that page list and checks only those URLs; it does not also follow links looking for pages the sitemap left out, so a page missing from the sitemap will not appear in these results at all. When no usable sitemap exists, the crawler instead follows real links out from the homepage, recording which page links to which as it goes. A page counts as a true orphan here when it returned a 2xx response, is not the page you started the scan from, and has zero inbound links from any other page in that same crawl.

This is an honest limit worth stating plainly: a capped crawl does not report orphan verdicts at all, not a partial or sample-based count. A larger site that hits the free page cap gets no orphan flag anywhere in that scan; a fuller, untruncated crawl is what brings the check back.

How to fix a confirmed orphan

Match the fix to the page instead of adding a link anywhere convenient. Three patterns work well, and one common shortcut works poorly.

1. Link from the page that already owns the topic, such as a category hub or a closely related article, since that page usually sits at a shallow depth and passes real crawl priority down to the orphan.
2. Add the page to a listing or index it logically belongs in, when one exists, so it gets picked up by the same navigation path as its neighbours.
3. Cross-link it from a newer page covering a closely related question, which also gives both pages a reason to sit near each other in the site's structure.

Avoid dumping the fix into a site-wide footer instead. A link buried among dozens of other footer links carries little weight and rarely reflects which page actually owns that topic, so the orphan gets a technical inbound link without a real contextual home.

Which orphans to fix first

Check each flagged page against real traffic and backlink history before deciding what to do with it: that context turns a flat list of thirty or forty rows into a priority order instead of treating every row the same way.

A page still pulling search visits or holding an external backlink from before it lost its internal links is worth relinking immediately. It already has demand and residual authority behind it, and the only thing missing is the path in. A page with neither signal is a genuine judgement call: fold it into a current page covering the same ground, or let it retire with a redirect if a better replacement already exists. A page that still ranks despite being an orphan is running on stale signals a search engine has not yet revisited, so the fix still matters: that ranking can erode once crawling stops confirming the page is still connected to anything.

Batch several fixes into one release where the site allows it, then rerun this checker afterwards. One rescan then confirms every fix at once, instead of treating each page's relinking as its own separate verification step.

Questions about the orphan check