How to find and fix orphan pages

Strictly, an orphan page is a URL with zero inbound internal links. In practice the strict definition is too narrow to be useful, because a page with one link from page nine of a blog archive behaves exactly like an orphan: crawled rarely, starved of authority, invisible in search.

  inbound links   behaves like            worth fixing?
  -------------   ---------------------   -------------
  0               true orphan             yes
  1 (pagination)  functionally orphaned   yes
  1 (footer)      functionally orphaned   yes
  2-3 (nav only)  weakly supported        often
  4+ contextual   genuinely connected     no

So treat the orphan report as the top of a list rather than the whole list. Sorting all pages by inbound link count ascending, and looking at where those links come from, surfaces far more of the actual problem — the difference between a template link and an in-body one is covered in contextual vs navigation links.

Every method is the same subtraction: a list of URLs that exists independently of your internal links, minus the URLs a crawler could reach by following links. A crawl alone can never find an orphan, because the crawler has no path to it.

• chevron_rightFree and fastest — the Orphan Page Checker crawls the site and compares it against your sitemap, no account or install.
• chevron_rightAlready have a licence — finding orphan pages in Screaming Frog covers the Crawl Analysis workflow, which is the step most people miss.
• chevron_rightFree, no tools — finding orphan pages in Search Console walks the export-and-subtract method, and adds impression data you cannot get elsewhere.
• chevron_rightOn WordPress — orphan pages on WordPress covers the platform-specific causes: pagination, attachment pages, page-builder templates.

Orphans are almost never created deliberately, which is why they go unnoticed. Knowing your site's pattern is faster than auditing everything.

• chevron_rightArchive pagination — the biggest single source on any site that publishes regularly. A post is linked from page 1 until newer posts push it to page 2, then page 9. It never technically loses its link; it just drifts out of reach.
• chevron_rightMigrations — URL structures change, redirects are set up, and internal links are left pointing at the old paths or nowhere at all. Orphans arrive in batches here.
• chevron_rightDeep filters and facets — products or listings reachable only by selecting three filters in sequence. Real for a user, invisible to a crawler that will not guess the combination.
• chevron_rightPublishing outside the navigation — campaign pages, one-off landing pages, seasonal content. Published, sitemapped, linked from nothing.
• chevron_rightRemoved nav items — a menu tidy-up that drops one link can orphan an entire section beneath it in a single deploy.
• chevron_rightTemplate changes — a related-posts block or breadcrumb removed during a redesign silently strips inbound links across thousands of pages at once.

Most advice stops at "add internal links" without saying from where, and the source page is what decides whether the fix does anything. Work backwards from the target.

1. Search your own site for the target's main topic. The pages that already discuss it are your candidates — the link will read naturally because the context already exists.
2. Of those, prefer pages with real inbound links themselves. A page nothing points at has little to pass on, however relevant it is.
3. Prefer shallow pages. A source three clicks from the homepage puts your target at four; a source at depth seven leaves it buried.
4. Check how many outbound links the source already has. A page with a dozen links passes far more through each than one with a hundred.
5. Avoid linking every orphan from the same one or two strong pages. You are dividing a fixed amount across more targets each time.

  source A                       source B\n  ---------------------------    ---------------------------\n  8 inbound links                0 inbound links\n  depth 2 from homepage          depth 6 from homepage\n  14 outbound links              90 outbound links\n  topically related              unrelated\n         |                              |\n         v                              v\n  meaningful lift                 nearly nothing\n

This is the judgement a link-count report cannot make for you, because it needs a model of the whole graph — which pages hold authority, and how much each link actually moves. That is what internal authority flow describes.

Working down the export from the top is how a day disappears. Most orphan lists are mostly noise, and some entries are supposed to be unlinked.

Discard these

• chevron_rightPaginated and faceted URLs — usually deliberately unlinked, and linking them makes things worse.
• chevron_rightThank-you, confirmation and other post-conversion pages — they should not be linked or indexed.
• chevron_rightCampaign landing pages built for paid traffic — either leave them unlinked and noindexed, or link them properly, but do not do half of each.
• chevron_rightRedirected or dead URLs still listed in a stale sitemap — fix the sitemap, not the link graph.
• chevron_rightThin or obsolete content — redirect it to the relevant page or remove it. Reconnecting a page that should not exist just spreads authority thinner.

Then rank what is left

Order the survivors by evidence that the page already has value:

1. Orphans with Search Console impressions — the page is already being served despite having no internal support. The cheapest win available.
2. Orphans with external backlinks — they hold authority that is currently trapped and reaching nothing else on your site.
3. Orphans that are commercially important — product, service or conversion pages, whether or not they currently rank.
4. Everything else — genuine content that simply fell out of the structure.

The instinct is to add a link from a hub page listing everything. It is the most common fix and close to the least effective.

A page with eighty outbound links divides what it passes across all eighty. Add your orphan as the eighty-first and it receives a rounding error — the arithmetic behind link equity. Worse, a hub nothing links to has little to pass on in the first place.

1. Pick source pages that hold authority. A link from a page with real inbound links is worth many from pages nothing points at.
2. Pick source pages that are topically relevant. A link from unrelated content passes a weak relevance signal even when the authority is there.
3. Place the link in the body copy, inside a sentence that would exist anyway. Sidebar and footer links pass far less.
4. Write descriptive anchor text — what the target page is about, not "click here" or the bare URL.
5. Add two or three good links rather than a dozen weak ones. Returns diminish quickly.
6. Check the path from the homepage afterwards. A link from a page that is itself six clicks deep leaves the orphan nearly as buried as before.

Step 6 is the one people skip. De-orphaning a page onto the end of a long chain fixes the count and not the problem — see crawl depth explained for why the distance matters as much as the link.

1. Purge any page or CDN cache — stale HTML will happily serve the pre-fix version to crawlers for hours.
2. View source on each source page and confirm the anchor is in the raw HTML, not injected by JavaScript.
3. Re-crawl and confirm the page now reports inbound internal links.
4. Check its click-depth from the homepage, not just the link count.
5. In Search Console, use URL Inspection on the target — the discovery section should eventually show a referring page rather than sitemap-only discovery.
6. Give it a few weeks, then compare impressions for that URL.

Orphans are not a one-off cleanup. Every publishing batch, template change and migration creates more, so the useful measure is whether you are fixing them faster than you create them.

• chevron_rightRe-crawl after migrations and bulk imports — the two events that create orphans in batches.
• chevron_rightRe-crawl after theme or plugin changes; they rewrite internal links silently.
• chevron_rightStop relying on archive pagination for discovery. Build topic hubs that link directly to every page in a cluster, the structure described in content clusters.
• chevron_rightAdd a contextual link to at least one existing page whenever you publish. Cheaper than any audit.
• chevron_rightTrack orphans as a share of total URLs rather than an absolute count — a growing site will always create some.

RankForge does the subtraction on every crawl, ranks the orphans by the authority a link would actually move, and names the source page, anchor text and paragraph — so the output is the instruction rather than the list. How often to audit internal links covers a sensible cadence.

Most orphaning is generated by the CMS rather than decided by anyone, and the mechanism differs enough per platform to be worth naming:

• chevron_rightWordPress — posts that fall off the paginated index, and pages published without being added to a menu.
• chevron_rightShopify — products assigned to no collection, and automated collections whose rules silently stopped matching.
• chevron_rightWebflow — Collection List limits and filters, which orphan CMS items in blocks the moment a list stops rendering them.

On stores, orphaning and depth usually have one shared cause — a product reachable only from a long paginated grid — so the fixes overlap. Reducing crawl depth on WooCommerce covers that side of it.