What orphan pages are and why docs sites get them

An orphan page is a page that exists on the site (it returns 200 and is usually listed in the sitemap) but has no inbound links from any other page. Readers cannot navigate to it; search engines can still find it through the sitemap but treat it as unimportant because nothing points at it. Over a few months it slides out of results, and the knowledge on it is effectively lost.

How docs sites create orphans

• Navigation is edited independently of content. On MkDocs, Mintlify, Fern, VitePress and Nextra the sidebar is a configuration file. Remove an entry and the page keeps building. Docusaurus and Starlight generate sidebars from folders but still let you exclude pages.
• Pages are retired by unlinking, not deleting. A writer removes the links to an outdated guide "for now". The page stays live and indexed, contradicting the current docs.
• Version forks copy pages that were already orphaned, so every new version carries the same dead weight.
• Migrations drop pages from the new navigation. The content was imported, the sidebar was rebuilt by hand, and a dozen pages never made it in.
• Landing pages get restructured. A hub page that linked to twenty how-tos is replaced by a curated six, and fourteen become orphans overnight.

Why they matter

• Readers reach them only from search, land on stale advice and lose trust.
• Search engines demote pages with no internal links, so the page stops ranking for the queries it should own.
• They are usually the pages that contradict the rest of the docs, because nobody sees them during reviews.

How to find them

PathIntact's orphan rule is simple: a page listed in the sitemap that received zero inbound links from other crawled pages, with links inside navigation, sidebars, headers and footers counting as inbound. The docs link checker applies it to a 50-page sample; a monitored site gets the full check on every crawl.

Two complementary checks:

• The sitemap diff shows pages that appeared in the sitemap since the last crawl; new orphans usually show up here first.
• The pages table in the dashboard can be filtered to "in sitemap, no inbound links".

How to fix them

1. Decide whether the page should exist. If it is still correct, link to it from the sidebar or from a related page. One good contextual link is worth more than a sidebar entry buried three levels deep.
2. If it is outdated, redirect it to the page that replaced it (see the redirect rules cheat sheet), and remove it from the sitemap.
3. If nothing replaces it, remove it and return 410 or 404, and drop it from the sitemap. Leaving it in the sitemap while it 404s is a separate error PathIntact reports.
4. Watch for regressions. Orphans reappear every time someone edits navigation. Alerts on newly confirmed orphan pages catch the edit the same day.

Check my docs