What an orphan page is
An orphan page is a page on your site that no other page of your site links to. It exists at its own address, and a visitor could open it if they knew the address, but nothing in your menus, text or lists leads there.
Orphans arise easily. A page is published but never added to a menu. A section is redesigned, and old links are dropped. A product is removed from a category yet its page stays online. A landing page was created for a campaign and forgotten. Over time, a site with frequent editing often collects a few.
Why orphans matter
Visitors cannot find them. If a page can only be reached through a direct address, nearly all the people on your site will never see it.
Search engines may not find them. Crawlers rely mainly on links to discover pages. An orphan can still be found through an XML sitemap, an outside link or a past visit, but without internal links it receives little of the attention that internal linking provides. Search engines may treat it as less important, or may visit it rarely.
They hide problems. Orphans are often old, outdated or duplicate. They can contain stale prices, previous branding or content that contradicts the current site, and nobody notices because nobody sees them.
They can waste effort. If you are maintaining, reporting on or paying to host pages that have no place in the site, that is clutter.
Some orphans are harmless or intentional. A thank-you page after a form, a private download page or a landing page used only in email campaigns might legitimately have no internal links. The problem is with unintentional orphans that you want people to find.
How to find orphan pages
The trick is that a normal crawl cannot find them, because a crawl follows links and an orphan has none pointing at it. You have to compare two lists: the pages a crawl reaches by following links, and pages that exist by other evidence.
- Crawl the site starting from the home page. Save every address found.
- Gather lists from other sources. Useful ones include:
- Your XML sitemap.
- The list of pages in your content management system or database.
- Pages that received visits according to your analytics.
- Pages that appear in search performance reports.
- Addresses from server logs, if you have access.
- Pages that other sites link to, from your backlink profile review.
- Compare. Any address that appears in the other lists but not in the crawl is a candidate orphan.
- Check each candidate. Confirm that the page loads normally, and look at what links to it. Some candidates turn out to be redirects, error pages or parameter variants rather than real orphans.
Many crawling programs can import extra lists and report the difference automatically. No particular product is required.
A hypothetical example: a crawl finds 200 pages by following links. The sitemap lists 230. Comparing the two shows 35 addresses in the sitemap but not in the crawl, and 5 addresses in the crawl but not in the sitemap. The 35 are candidate orphans, and the 5 suggest the sitemap itself needs tidying. (Some of the 35 may be redirects or removed pages rather than live orphans.)
Deciding what to do with each one
For every orphan, ask three questions: Is the page useful? Is it accurate? Does it belong on the site?
Reconnect it. If the page is useful, current and distinct, give it a proper place. Add it to a relevant category or hub page, and link to it from two or three related pages where a link makes sense for readers. Make sure it has a descriptive title and suits its section. This also shortens its click depth.
Update, then reconnect. If the content is valuable but out of date, refresh it first. Content freshness matters most for topics that change.
Merge it. If it overlaps with another page, combine the best parts into one page and redirect the orphan to it. This is one use of content pruning, and it avoids having two pages that compete.
Retire it. If the page has no value, remove it. Where it has links from other sites or past traffic, use a permanent redirect to the most relevant remaining page. Where it has none, a clear “gone” response is fine. Avoid sending everything to the home page.
Leave it alone intentionally. For pages that are meant to be hidden from the site’s navigation, make sure that is a conscious choice. If they should not appear in search at all, a noindex setting and exclusion from the sitemap are the usual approach, but check the details before applying them.
Preventing new orphans
- When you publish a page, link to it from somewhere sensible the same day.
- Before deleting or moving a page, find what links to it and update those links.
- During a redesign or migration, compare the page lists before and after.
- Include an orphan check in your monthly routine, even a quick one.
- Keep your sitemap limited to pages you actually want found; it should not be the only path to a page.
An orphan check is a modest task, but it often turns up forgotten pages that are worth reconnecting and old ones that are better removed.