Orphan Pages

An orphan page is a page on a site that has no internal links pointing to it from any other page. It exists, it may be in the sitemap, and it may even be indexed, but nothing on the site links to it. Search engines discover most pages by crawling from one link to the next, so a page with no inbound internal links is difficult to discover and easy to overlook.

Orphan pages matter because they sever a page from the site’s internal link structure. Internal linking distributes authority and signals relevance and importance. A page outside that structure receives none of those signals, so even genuinely useful content can fail to rank simply because the rest of the site does not acknowledge it exists.

How do pages become orphaned?

Orphaning is almost always accidental, a by-product of how sites change over time.

Removed navigation or links. A page was linked from a menu or a hub page that was later restructured, and the link was not replaced.

Migrated or redesigned sites. During a site migration, pages are carried over but the internal links between them are not always rebuilt, leaving content stranded.

Landing pages for campaigns. Pages built for paid campaigns or email are often deliberately kept out of the main navigation, then forgotten and never linked from organic content.

Programmatically generated pages. Bulk-created pages (product variants, location pages) are sometimes published without a linking structure connecting them to the rest of the site.

Old content that lost its links. As a site evolves, the articles that once linked to a page are pruned or rewritten, and the inbound links disappear with them.

How do you find orphan pages?

The principle is the same across every method: build a complete list of URLs that exist, then subtract the URLs a link-following crawler can reach. What remains is orphaned.

Run a site crawl. Crawl the site with Screaming Frog, Sitebulb, or a similar tool. Because the crawler discovers pages only by following links, the resulting list is, by definition, every page that is reachable through internal links.

Assemble the full URL inventory. Gather every URL that actually exists from sources independent of internal links: the XML sitemap, the Search Console indexed pages export, the analytics list of pages that received traffic, and the server log files if available. Crawling tools can ingest these sources directly and cross-reference them against the crawl.

Compare the two lists. Any URL that appears in the inventory but not in the crawl is an orphan: it exists and may receive traffic or be indexed, but nothing links to it. Screaming Frog flags these directly when you connect the Search Console and sitemap data sources to a crawl.

Prioritise by value. An orphan still receiving organic impressions or conversions is the most urgent to reconnect, because it is succeeding despite the handicap. An orphan with no traffic and no purpose is a candidate for removal rather than repair.

How do you fix orphan pages?

Reconnecting an orphan worth keeping means giving it a place in the site’s link structure.

Add contextual internal links. The most durable fix is links from the body content of relevant, related pages, using descriptive anchor text. A link from within a topically related article carries far more weight than a link buried in a footer. See internal linking for placement principles and anchor text for wording.

Connect it to a hub. If the page belongs to a topic cluster, link it from the relevant pillar or hub page and from sibling pages in the same cluster, so it sits inside a coherent structure rather than hanging off a single link.

Add it to navigation where appropriate. For pages that warrant it, a place in the main navigation, a category page, or a breadcrumb trail provides a permanent, reliable link.

Request indexing once reconnected. After adding internal links, use the URL Inspection tool in Search Console to prompt a recrawl so Google picks up the new link context sooner.

When should an orphan page be removed instead of fixed?

Not every orphan deserves reconnection. Some pages were orphaned because they no longer serve a purpose, and reconnecting them would only add low-value content back into the site.

noindex pages that should exist for users but not appear in search, such as standalone campaign landing pages.

Redirect pages that are obsolete but have earned backlinks or still receive traffic: a 301 to the most relevant surviving page preserves the equity. This overlaps with content pruning decisions.

Consolidate orphans that are thin and overlap with existing content into the stronger page, then redirect.

The deciding question is whether the page would earn its place in the site if you were building the structure from scratch today. If it would, reconnect it properly. If it would not, remove it cleanly rather than leaving it stranded.