Orphan Pages, Explained (and How to Find Them)

An orphan page is a page that exists on your site, and may even still be indexed, but has no internal links pointing to it from anywhere else on the site. The only way to reach it is a direct URL, an old bookmark, a sitemap entry, or a leftover external link. It's one of the more common technical issues on sites that have grown or changed over several years, and one of the least visible — nothing looks broken, because the page itself loads fine. It's just cut off from the rest of the site.

Why orphan pages happen

• Site redesigns and navigation overhauls — a new menu structure gets built, and pages that weren't explicitly carried over into the new navigation simply stop being linked, even though the pages themselves were never deleted.
• Campaign and promotional landing pages — built for a specific ad campaign or seasonal push, often deliberately not linked from the main site so visitors only reach them through the campaign itself. Once the campaign ends, the page frequently stays live and indexed with no link ever added.
• Blog posts that rotated out of a "recent posts" widget — if a post was only ever linked from a homepage module that surfaces the newest content, it becomes an orphan the moment newer posts replace it there, unless something else links to it.
• Pages superseded by a newer version — a service page rebuilt or rewritten, with the old version left live at its original URL but no longer linked from anywhere, instead of being redirected or removed.
• Platform or CMS migrations — content that carried over during a migration but didn't get re-added to the new navigation or internal linking structure.

Why they're worth fixing

An orphan page isn't neutral — it actively costs you in a few specific ways. It gets a weaker importance signal from Google, since internal linking is one of the clearest signals of which pages on your site actually matter; a page nothing links to reads as low-priority almost by definition. It gets crawled less frequently over time, which means any updates you make to it are picked up more slowly, if at all. And any content investment that went into building the page — research, writing, photos — sits unused, since almost no visitor stumbles onto a page with zero paths leading to it.

How to find every orphan page on your site

Finding orphan pages requires comparing multiple lists of "pages that exist" against one list of "pages that are actually linked," since no single source gives you the full picture on its own.

• Crawl your site with internal link counts — a tool like Screaming Frog, crawled in standard mode, reports the number of internal links pointing to each page it finds by following links. Anything with zero inbound internal links found during that crawl is a candidate.
• Compare against your XML sitemap — the sitemap represents every URL you consider indexable. Cross-reference it against the crawler's linked-page list; any URL that appears in the sitemap but wasn't reached by following links from the crawl is very likely an orphan.
• Cross-check against Google Search Console and analytics — the Pages report in Search Console shows what Google has indexed, and analytics shows what's actually getting traffic. A page indexed and receiving occasional traffic but absent from your internal link crawl confirms it's an orphan that's surviving on external links, direct visits, or a sitemap entry alone.
• Some crawler tools support a dedicated "list mode" or orphan-page comparison feature that automates this cross-referencing directly, pulling from the sitemap, Search Console, and analytics data together in one report.

Fixing what you find

Once you have the list, each page needs a decision, not a blanket action.

• Still valuable, still accurate — give it a real home: a navigation link, a footer link, or contextual links from genuinely related pages. See the internal linking strategy guide for how to do this without cramming links in artificially.
• Outdated but the topic is still relevant — update the content and then link it in properly, rather than leaving stale content live and disconnected.
• Superseded by a better page — redirect it to the current version with a 301, consolidating whatever signal it retained.
• No longer relevant at all — remove it properly (a genuine 404 or 410 status) rather than leaving a low-value page sitting in the index. See the content pruning guide for how to decide what's worth cutting.

Preventing new orphans going forward

The most durable fix is building link-checking into how you publish, not just how you audit. Every new page should be linked from at least one relevant place — navigation, a hub page, or contextually from related content — before or immediately after it goes live. See the website structure guide for how to plan navigation and internal linking so pages don't quietly fall through the cracks as your site grows, and the XML sitemaps guide for how sitemaps fit into discovery — useful, but never a substitute for real internal links.