Orphan pages

Precisely: a URL with zero inbound internal links from other crawlable pages. Note what doesn't count. Being in your XML sitemap doesn't save a page — a sitemap is a discovery hint that carries no authority. Being linked only from a nofollowed link, or only from a page that is itself orphaned, leaves a page effectively orphaned too. The test is whether followed internal links from your live link graph actually reach it.

CONNECTED                      ORPHAN
                               (in sitemap, but no links in)
 [Home] -> [Hub] -> [Page]      [Home] -> [Hub] -> [Page]
              \                              sitemap.xml
               -> [Page B]                     |
                                            [Orphan]   <- nothing
 inbound links: discovery                   links here
 + authority both arrive       inbound links: none ->
                               only the crawl baseline

Internal links do two jobs — discovery and authority — and an orphan misses both, which cascades through three stages:

• chevron_rightCrawling — with no links pointing in, Googlebot has no path to the page during a normal graph walk. It may find it via the sitemap, but recrawls are infrequent, so content changes are noticed late.
• chevron_rightIndexing — pages that look unimportant (no internal links, rarely crawled) are more likely to be left out of the index or dropped from it, especially on large sites where crawl budget is rationed.
• chevron_rightRanking — even if indexed, the page receives only the tiny authority-flow baseline. With no internal equity and no topical link signals, it can't compete for anything but its own brand terms.

Almost always by accident, through a handful of recurring mechanisms:

• chevron_rightPagination decay — blog posts and products fall off page 1 of a feed as new items push them back, and nothing else links to them once they're past the last paginated page.
• chevron_rightFaceted/filtered access only — products or articles reachable solely through filter combinations that crawlers don't (or are told not to) follow.
• chevron_rightMigrations — URLs change, internal links are updated inconsistently, and pages get stranded behind links that now point at the old address.
• chevron_rightPublishing outside the structure — landing pages, campaign pages, or imported content added without being linked from any existing page.
• chevron_rightRemoved navigation — a menu or hub link gets pruned in a redesign, silently orphaning everything it used to reach.

Detection is a set difference: crawl the site by following links, then compare the reachable set against your full list of known URLs (from the sitemap, CMS export, or server logs). Anything in the known set but not in the crawl-reachable set is a likely orphan.

Recovering an orphan worth keeping means reconnecting it to the link graph properly — and the quality of the reconnection matters as much as its existence.

1. Add contextual, in-body links from topically related pages that are already well-linked — ideally a relevant cluster page or hub, not just the footer. One or two strong, relevant links beat a dozen boilerplate ones.
2. Use descriptive anchor text that tells the engine what the recovered page is about — the page has had no anchor signals at all, so this is high-value.
3. If the page genuinely shouldn't exist, don't reconnect it — redirect it to the most relevant live page, or remove it. Reserve this for thin or obsolete content; reconnect anything valuable.

On big ecommerce and publishing sites, orphans are a systemic, not occasional, problem — and the nuance is that not every disconnected URL is worth saving. A crawl that's smaller than the sitemap will report many 'in sitemap, not crawled' URLs that are really a crawl-budget limit, not site problems. RankForge distinguishes a genuine orphan (reachable by no internal link) from a page the audit simply didn't reach, and caveats the count rather than alarming you with budget artifacts — see the structural SEO pillar for how this fits the wider picture.