How to Find Orphan Pages

Direct answer

An orphan page is a URL that exists on the site but has no (or effectively no) internal links from other pages you crawl. Finding orphans means comparing URL sources: a full crawl of clickable links, sitemap membership, analytics or server logs if you have them, and CMS or feed exports. Pages that appear outside the link graph need a decision—reconnect, consolidate, or retire—not automatic promotion.

Orphans are a discovery and architecture issue. They are not proof that a page is “bad,” and fixing them does not promise rankings. The goal is intentional paths so people and crawlers can reach the same useful content through crawlable links.

Why it matters

Sites accumulate orphans after migrations, campaign landing pages, PDF-to-HTML conversions, and product SKUs that leave the catalog navigation. Without inlinks, those URLs depend on bookmarks, ads, or sitemap hints. Public crawl guidance emphasizes that search systems discover content primarily by following links; sitemaps help but do not replace a coherent structure.

For B2B sites, orphans often hide installation guides, comparison notes, or regional variants that buyers still need. Leaving them disconnected wastes editorial work and confuses audits: the content exists, yet the site structure pretends it does not.

How to check

1. Build a link-graph crawl — Start from the homepage and key hubs. Collect only crawlable HTML links (skip pure script-only navigation if crawlers cannot see it).
2. Collect candidate URL sets — XML sitemaps, CMS export of published URLs, and optional log or analytics landing pages.
3. Diff the sets — Flag URLs present in sitemaps or exports but missing from the link-graph crawl. Those are orphan candidates.
4. Validate live status — Confirm 200 vs redirect vs error. Note canonical targets and noindex. An orphan that 404s is cleanup, not a linking task.
5. Classify by job — Keep (buyer-useful), merge (near-duplicate of a stronger URL), or remove (thin leftover). Record sample URLs for each class.
6. Blueprint links or retirement — For keepers, add contextual links from the category, product, or topic hub that should own the page. Re-audit that the URL appears in a fresh link crawl.

Example

A manufacturer publishes a detailed torque-selection guide during a campaign. The URL stays in the sitemap and still loads, but the campaign hub was unpublished and no product page links to the guide. A crawl from navigation never sees it; only the sitemap lists it.

Diagnosis labels it an SEO Health discovery finding. The blueprint might add a “Related guides” link from two relevant product templates and from the applications hub—or, if a newer handbook superseded it, redirect to that handbook and drop the old URL from the sitemap. Re-audit checks inlink presence and final status codes. No step claims a search ranking change; it restores an intentional path.

Mika: Health vs Growth

Finding and reconnecting orphans is primarily SEO Health: architecture and crawl paths. Writing the missing guide that never existed is SEO Growth. Mika separates these so teams do not treat “add links to leftovers” as the same job as “cover unanswered demand.”