You find orphan pages on WordPress by comparing what is linked against what exists. Crawl the site to see which pages are reachable by following internal links, then compare that set against your full list of URLs from the sitemap and Search Console. The pages that exist, and sometimes even rank, but have no internal links pointing to them are your orphans. Finding them before a redesign matters because a redesign typically rebuilds the pages you can navigate to, and the orphans, by definition, are the ones you cannot navigate to, so they get dropped silently, including any that quietly earn traffic. WPBuildAI crawls the site and lists the orphan pages so you decide, before the rebuild, which to relink, keep, or retire.

Orphans cost more than they used to, because a page that is rarely crawled is a page that cannot be quoted: Seer Interactive found pages cited in an AI Overview at roughly 2.1 percent click-through against 0.9 percent uncited, and citation depends on the crawler reaching the page in the first place.

What an orphan page is

An orphan page is a page with no internal links pointing to it. It exists, it has a URL, and it may be indexed and even ranking, but nothing on your own site links to it, so a visitor (or a crawler following links) cannot reach it by navigating. Orphans accumulate naturally: an old campaign page, a post whose category was removed, an attachment page, a piece of content published and then unlinked. Because they are invisible in normal navigation, they tend to be forgotten, which is exactly why they need finding deliberately rather than by browsing.

Why orphans matter before a redesign

A redesign is the moment orphans are most likely to be lost, and most worth saving. Teams rebuild what they can see in the menus and the link structure, so unlinked pages simply do not make the list. If an orphan was earning traffic, dropping it loses that traffic; if it was dead weight, carrying it over blindly clutters the new site. Either way, you want the decision to be conscious. The traffic stakes are real because traffic is uneven: the Ahrefs search traffic study found a small share of pages earns most visits, and an orphan can occasionally be one of them.

How to find them: crawl, index, and analytics

No single source reveals orphans, because an orphan is defined by a gap between sources. A crawl shows what is reachable by internal links. The sitemap and the index show what pages exist. Analytics and Search Console show what gets visits and clicks. An orphan appears as a page that shows up in the index or analytics but not in the crawl of internal links. So finding orphans is fundamentally a comparison: linked versus existing. This is why pulling a complete URL list, as in finding all URLs, is the necessary first half of the job.

The three-source method

In practice, combine three lists and look for the difference. First, crawl the site and record every internally linked URL. Second, gather the full set of URLs from the sitemap and from Search Console, including pages that receive clicks. Third, subtract: any URL in the full set that the crawl never reached through internal links is an orphan candidate. The 2024 Web Almanac is a reminder that sites carry more URLs than owners expect, so the orphan list is often longer than anticipated. Reviewing that difference is the whole technique.

What to do with each orphan

Finding orphans is only useful if each gets a decision. There are three sensible outcomes. Relink the valuable ones: if a page is good and should be found, add internal links to it from related content, which also helps it rank, since links are a ranking signal per Backlinko’s analysis. Keep and redirect the ranking ones: if it earns traffic, make sure it survives the redesign and its URL is preserved or redirected. Retire the dead weight: if a page is thin and pointless, let it go on purpose, rather than dragging it into the new site. The point is a deliberate choice per page.

Do not carry orphans into the new site blindly

The opposite mistake to dropping orphans is importing all of them without thought. A redesign is a chance to clean up, so a thin or outdated orphan that adds nothing should not be rebuilt just because it exists. The discipline is the same as for the internal link structure generally, covered in what happens to internal links in a redesign: decide what the new site should contain, then make the link graph reflect it. Orphans handled well make the new site cleaner; orphans ignored make it either thinner or more cluttered.

A worked example

A 400-page WordPress site planned a redesign. Crawling the internal links reached 320 pages. The full URL list, from the sitemap and Search Console, held 400. The 80-page difference was the orphan set: old campaign pages, unlinked posts, and attachment pages. Reviewing them, the team found a dozen that still earned search traffic, which they relinked and kept with their URLs preserved, per Google’s site move guidance. Another fifty were thin and retired on purpose. The rest were folded into related pages. The redesign launched cleaner, and the valuable orphans kept their traffic instead of disappearing.

Common mistakes

  • Assuming the navigable pages are all the pages, and missing the orphans entirely.
  • Comparing only one source instead of crawl versus full URL list.
  • Dropping orphans in the redesign without checking which earn traffic.
  • Importing every orphan blindly, carrying thin pages into the new site.
  • Relinking nothing, so found orphans stay unreachable after the rebuild.

Key points to remember

You find orphan pages by comparing the internally linked pages from a crawl against the full URL list from the sitemap and Search Console; the gap is your orphans. Do it before a redesign, because a rebuild that only covers linked pages drops the orphans silently, including any that earn traffic. Then give each orphan a deliberate decision: relink the valuable, keep and redirect the ranking, retire the dead weight. That makes the new site cleaner and protects the traffic you would otherwise lose by accident. WPBuildAI crawls the site and lists the orphan pages before the rebuild. Send your site URL for a free readiness assessment.

Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.