Glossary
Orphan page
An orphan page is a published page that no other page on the site links to. It can still be reached by anyone who has the URL and it may be listed in the sitemap, but nothing on the site leads to it — so visitors do not find it by browsing and crawlers do not find it by crawling. The usual causes are unglamorous: a page whose navigation entry was removed, a campaign landing page, a section left behind by a redesign.
Why a sitemap entry is not enough
A sitemap is a suggestion about what exists. Internal links are what indicate that a page matters and how it relates to the rest.
A page listed in a sitemap and linked from nowhere is discoverable and carries no signal about its importance.
Internal links also pass context: the anchor text and the surrounding page say what the target is about.
So a sitemap-only page tends to be crawled less often and ranked more weakly than an equivalent page inside the site's structure.
And for human visitors it does not exist at all, which is usually the more expensive half.
How pages become orphans
A navigation entry is removed during a redesign while the page stays published.
A campaign landing page is created for an external audience and never linked internally, which is deliberate and then forgotten.
A category or tag page is generated by a content system and never included in any menu.
Pagination that only links a few pages ahead, leaving everything past that reachable only by editing a URL.
A page linked only from another orphan, which is a cluster rather than a single page and is the shape that hides the most content.
Why a crawl-based finding is not always right
A crawl reaches what it reaches, bounded by budget and by robots directives, so a page linked only from an unreached page looks orphaned.
Links inserted by script after load are absent from the served markup, so a navigation built entirely client-side can make the whole site look orphaned.
That is worth knowing in itself: a crawler reads roughly what the scan read, so if the links are invisible here they are invisible to discovery too.
A page deliberately excluded from navigation is reported as an orphan because it is one, which is correct rather than a false positive.
What to do about one
Decide whether it should exist. A large share of orphans are pages nobody would recreate, and removing them is the right answer.
For the rest, link them from somewhere that makes sense — a parent category, a related section, a relevant article.
Adding a link from an arbitrary page to clear the finding accomplishes nothing: the link has to be one a reader would follow.
Where the page is genuinely for an external audience only, leave it orphaned deliberately and keep it out of the sitemap so the two agree.
How it is observed
Depth, orphan candidates, breadcrumbs and return-to-home paths are measured from the crawl data already collected.
Navigation is compared across the crawled pages, which is what surfaces a menu that loses entries on some templates.
The sitemap is read separately, so a page advertised there and linked nowhere is visible as the contradiction it is.
Findings are relative to the crawl, and the coverage is reported alongside rather than implied.
Frequently asked questions
- Is a page in my sitemap still an orphan?
- Yes. A sitemap says a page exists; internal links say it matters and what it relates to. The two are not substitutes.
- Why is a page I can click to reported as an orphan?
- Usually because the link is inserted by script and is not in the served markup. That is worth knowing — a crawler reads roughly what the scan read.
- Should every page be linked?
- Every page you want found. A landing page for an external campaign can stay unlinked deliberately, and it should then be kept out of the sitemap so the two agree.
Sources
Related
VeriFixScan crawls a site and applies its checks to every page it reaches, keeping the evidence behind each finding. Scanning one website is free.
Scan a website