Orphan page

An orphan page is a page on your site that nothing else links to. Search engines struggle to find it and users never reach it from your menus. You will see low impressions and no clicks until you connect it.

By , founder of Porteur · Updated 13 September 2026 · Markdown

Why orphan pages hurt a small site

With no internal links, a page is hard for crawlers to discover and for users to reach. Link equity does not flow to it, so it will not rank for anything meaningful.

On a small site, every page has to pull its weight. A pricing subpage, a help article, or a blog post with no links wastes crawl budget and splits your focus.

A fixed page has at least one crawlable, followed link from a page that is in your main crawl path, for example from /guides, the homepage, or a relevant article.

How to find orphan pages on a small site

Search Console does not list orphan pages directly. You need to compare what your crawler finds to other URL sources you control.

  1. Assemble all known URLs

    Export URLs from your CMS, your XML sitemaps, and any legacy lists you have. Add important landing pages like /pricing and /guides/getting-started.

  2. Crawl the site

    Run a site crawl starting at the homepage. Let it follow standard links. Save the list of URLs found by internal links.

  3. Compare the lists

    Mark any URL that appears in your CMS or sitemap, but not in the crawl’s internal links list. These are your likely orphans.

  4. Cross check with Search Console

    Open the Page indexing report and URL inspection for a few candidates. If they are indexed but get no internal links, they are orphans. If they are not indexed, decide whether to keep them.

If your crawler lets you import a sitemap or other URL list, use that to flag URLs not discovered by internal links. This speeds up the comparison on larger sites.

What to do with each orphan page

  • Keep and link it: add links from relevant pages, hubs, and navigation. Example: link /guides/getting-started from /guides and from the homepage footer.
  • Merge it: move its content into a stronger page, then 301 redirect the orphan to the new destination.
  • Retire it: if it has no use, add noindex, remove it from sitemaps, or 410 it. Clean the CMS so it is not recreated.
  • Fix discoverability: add breadcrumbs, related links, and a simple /guides or /blog index so new posts are never isolated.

Do not rely on the XML sitemap alone. A sitemap helps discovery, but it does not replace internal links and it does not pass link equity.

After changes, recrawl. Then request indexing for key pages in Search Console. Watch impressions for the fixed URLs over the next 28 days in the Performance report.

Traps and false positives

  • JavaScript-only links: links that need a click handler or do not use an href can be missed. Use normal anchor tags for core paths.
  • Nofollow on internal links: this blocks equity and discovery. Remove nofollow on links you want crawled.
  • Canonicals and duplicates: if an orphan has a canonical to another URL, fix the duplicate first. Then decide to redirect or link.
  • Parameter and tag pages: decide if they should exist. Many should be noindexed or removed rather than linked.
  • Blocked parents: linking from a page blocked in robots.txt does not help discovery. Unblock or link from an indexable page.
  • Legacy content: old staging URLs and import leftovers often surface as orphans. Clean them and remove from sitemaps.

Questions

Check my site, free

Run a free check from your URL to see three findings on your site and rivals in about thirty seconds, then decide which orphan pages to fix first.

  • Free check, no card
  • Read-only, your own accounts
  • Readable by your agent

Read next