Internal Links Manager

Guide

Orphan pages: how to find them and what to do with them

An orphan page has no internal links pointing at it. It exists, it may sit in your sitemap, and to anything following links it is invisible. Nearly every site older than a year has them — and almost nobody can name theirs.

What counts as an orphan, and what does not

A page is orphaned when no other page on the same site links to it. That is the only criterion. Three things get confused with it:

  • A noindexed page is not an orphan. You told search engines to ignore it on purpose. That is a decision, not an accident.
  • A 404 is not an orphan. The orphan exists and loads perfectly. That is what makes it easy to miss — nothing is broken.
  • Being in the sitemap does not save it. A sitemap tells a crawler a URL exists. Internal links tell it the URL matters, and roughly how much. The sitemap alone is a weak signal.

One useful refinement: a page reachable only from a paginated archive — page seven of a blog listing — is technically not orphaned, but it is close enough to be treated the same way. Practitioners sometimes call these near-orphans. They receive a ссылка, but from a page that itself sits deep and carries little weight.

How pages end up orphaned

Nobody creates an orphan deliberately. They accumulate through ordinary site maintenance:

  • The archive scrolls away. A post drops off page one of the blog, then page three, and eventually nothing links to it except a paginated listing nobody crawls deeply.
  • A campaign ends. The landing page stays live long after the banner linking to it came down.
  • The navigation gets tidied. A menu item is removed to simplify the header, and every page that hung off it loses its only link.
  • Content is migrated. Pages come across in an import; the links between them do not.
  • A category is restructured. Products or posts move, the old category page is unpublished, and its children are cut loose.

The common thread: the page was linked once, and the link disappeared through a change nobody connected to it.

What it actually costs you

Three separate costs, and the third is the one that stings:

  • Crawling. Search engines allocate finite attention per site. Pages nothing links to get visited rarely, so changes to them are noticed late.
  • Authority. Whatever standing your domain has flows along internal links. A page receiving none inherits none, and competes on its own from a standing start.
  • The work already paid for. Someone researched, wrote and edited that page. It is still good. It simply cannot be found by the mechanism most of your other pages rely on. Orphans are usually the cheapest traffic on a site precisely because the expensive part is already done.

Finding yours, step by step

The method is a subtraction: everything that exists, minus everything a crawler can reach by following links. What remains is orphaned.

  1. Get the list of everything that exists. Your XML sitemap is the easiest source. If you suspect the sitemap itself is incomplete, export the URL list from your CMS instead — a sitemap that omits a page will also hide the orphan.
  2. Crawl the site from the homepage. Screaming Frog and Sitebulb both do this. The crawler follows links only, exactly as a search engine would, and produces the list of everything reachable.
  3. Feed the sitemap into the same crawl. Both tools accept the sitemap as an extra source and will then flag the difference for you directly — in Screaming Frog under Crawl Analysis, as Orphan URLs.
  4. Cross-check against real traffic. Export pages with impressions from Search Console and from your analytics. A page nothing links to but that still receives visits is the most valuable kind of orphan — it is ranking despite the handicap.
  5. Filter out what belongs there. Thank-you pages, checkout steps, campaign landing pages you deliberately keep unlinked. Being unlinked is only a problem when it was not a decision.

Search Console alone will not give you a clean answer. Its Links report shows the most-linked targets, not the unlinked ones — absence from a top-list is not proof of absence. Use it as the traffic cross-check in step four, not as the source of truth in step three.

Link, merge or remove

Do not link everything back reflexively. Each orphan gets one of three verdicts, and the question that decides it is simple: would you publish this page today?

  • Link it — if the answer is yes. Find two or three pages whose subject genuinely leads there and link from inside the text, not from a footer list. One editorial link beats five decorative ones.
  • Merge it — if the answer is “not on its own, but the content is worth keeping”. Fold it into a stronger page on the same topic and redirect the old URL there. This is usually the right call for thin posts that overlap.
  • Remove it — if the answer is no. Delete it and let it return 410, or redirect it if it has any inbound links or lingering traffic. Leaving weak pages live to “not lose anything” is how sites accumulate the ballast that drags the rest down.

Work through them by traffic, highest first. An orphan with impressions is a page already ranking with one hand tied; linking it is the fastest win available on most sites.

Stopping it happening again

Finding orphans is a cleanup. Not producing them is a habit, and it comes down to three things:

  • Link on publication, not later. When a page goes live, decide there and then which two or three existing pages should point at it — and edit them. “I will add links later” is how the backlog starts.
  • Treat structural changes as link changes. Removing a menu item, retiring a category, unpublishing a hub: each one cuts links. Ask what loses its route before you make the change, not after.
  • Re-crawl on a schedule. Quarterly is enough for most sites. It takes twenty minutes and catches the drift before it becomes a project.

The structural point is worth sitting with. Orphans are rarely a content problem — they are a side effect of tidying. Every simplification of a navigation buries something.

Where this plugin fits. Internal Links Manager does not find orphans — that is a crawler's job, and Screaming Frog or Sitebulb do it well. What it does is stop new ones appearing: once a rule points a keyword at a page, every future post mentioning that term links there automatically, including posts written long after. The cleanup stays manual; the drift does not come back. See how the rules work.

The short version. An orphan is a page nothing links to — not broken, just invisible. Find them by crawling from the homepage and subtracting that from your sitemap. Sort by traffic, then decide per page: link it, merge it, or remove it. And link new pages on the day they are published, because that is the only moment anyone reliably remembers to. Related: the complete guide to internal linking and choosing anchor text.