Orphan pages: what they are and how to fix them

The short answer

An orphan page is a page on your own site that no other page links to. Visitors cannot click their way to it and search engines may miss it or treat it as unimportant. To fix one, find it, decide whether it deserves to exist, then link to it from relevant pages, merge it into another page or remove it.

What counts as an orphan page

Picture a shop with a back room nobody has told customers about. The room is real and stocked, but there is no sign and no door from the shop floor. An orphan page is the web version: it has an address and content, but no menu, button, text link or other page on the same site leads to it.

Orphans appear in several ways. A campaign landing page is published and then removed from the menu. A product is hidden from categories but left live. A redesign drops old links but not old pages. A page is created as a draft, shared once by email and forgotten.

Note the definition: no internal links. A page can have links from other websites and still be an orphan within its own site.

Why orphan pages are a problem

• Discovery. Search engines find pages mainly by following links and by reading sitemaps. A page with neither may be found late, or not at all. Check the current documentation on how Google finds pages.
• Importance signals. Internal links help show which pages matter. A page nobody links to sends a signal that you do not care about it.
• Visitors. If useful content cannot be reached by browsing, it is wasted.
• Stale information. Forgotten pages often hold old prices, old staff names or old offers that still appear in search.

Not every orphan is bad. A thank-you page after a form is meant to be reached only through the form. The aim is to know which orphans are intended and which are accidents.

How to find orphan pages

You find orphans by comparing two lists: pages that exist, and pages that are linked to. Anything in the first list but not the second is an orphan.

1. List the pages that exist. Use your XML sitemap, your content management system's page list, and the pages Google reports in Search Console.
2. List the pages that are linked. Run a crawler that starts at the home page and follows links. Whatever it reaches is linked.
3. Compare. Paste both lists in a spreadsheet and look for addresses in the first not in the second.
4. Add traffic data. Check your analytics for pages that get visits but never appear in the crawl. These are orphans that someone still finds, perhaps from old links or bookmarks.

Several crawling tools can do the comparison for you if you connect your sitemap and analytics. Check the current features of whichever tool you use, since they change.

Sort the orphans before you act

Be patient with this step. Deleting a page that earns visits or has outside links can lose more than it gains.

How to link an orphan back in

Adding the page to the menu is rarely the right first step. Instead, ask where a visitor would naturally want to go next, and put a link there.

• Add contextual links in the body text of related pages, using descriptive words rather than "click here".
• Link to it from a hub page or category page that covers the wider topic. Our guide to topic clusters and pillar pages shows how a hub and its spokes are organised.
• Add it to breadcrumbs if it has a clear parent; see how breadcrumbs help.
• Put it in the XML sitemap, as a safety net, but do not rely on the sitemap alone.

Aim for a handful of relevant links rather than dozens of loose ones. Each link should make sense to a reader.

When to merge, redirect or remove

If a page is weak, you have three honest options.

Merge. Move the useful parts into a better page, then send the old address to the new one with a permanent redirect. This keeps any value the old page had.

Redirect. If the page is gone but a close match exists, redirect to it. Do not redirect everything to the home page; it confuses visitors. Check how to avoid redirect chains and loops first.

Remove. If nothing is similar, let the page return a not found or gone response so that search engines drop it over time. Our guide to HTTP status codes explains the difference.

For pages that must stay live but should not appear in search, use a noindex instruction rather than leaving them hidden and forgotten.

A small worked example

This is an invented example. A training firm runs a spring promotion with its own page. In May the promotion link is removed from the home page, but the page stays live. The sitemap export, run in June, lists it. The crawl, which follows links from the home page, does not reach it. That mismatch marks it as an orphan.

The team checks the page. It still mentions spring dates, so it is out of date. But it also contains a useful section on course formats that no other page covers. The decision: move the course-format section into the main course page, then permanently redirect the old promotion address to that course page. The orphan is resolved, the useful content survives, and visitors with old bookmarks land somewhere sensible.

Writing down the reasoning for each decision takes a minute and saves arguments later.

Stopping orphans coming back

Orphans are a process problem. Fix the process and the list stays short.

1. Add a rule to your publishing checklist: every new page needs at least two internal links in, from relevant pages, before it goes live.
2. When removing a menu item, ask what happens to the page behind it.
3. Before a redesign, export the full list of addresses so none are lost.
4. Re-run the comparison every few months. Quarterly is a sensible rhythm for most small sites.
5. Keep a record of intentionally unlinked pages, so nobody mistakes them for a mistake.

Structure helps too. Clear folders and tidy addresses make gaps easier to spot; see URL structure best practices. And if your site is small, a regular manual walk through the menus may be all you need.

After you fix a batch, wait for the next crawl and check that the pages are now reached from the home page in only a few clicks. If a key page sits many clicks deep, treat that as a related fault and bring it closer to the surface.

Related guides

• SEO services
• URL Structure Best Practices for SEO
• Redirect Chains and Loops: How to Find and Fix Them
• Internal linking for seo simple rules
• Website wireframes what they are
• Website content audit how to review your pages

Questions and answers

Are orphan pages bad for SEO?

They can be, because search engines find and value pages partly through links. Intentional orphans such as thank-you pages are fine.

Does a sitemap fix an orphan page?

A sitemap helps discovery, but internal links also signal importance and help visitors, so add links as well.

Can an orphan page rank?

It can be indexed, particularly if it has outside links or is in the sitemap. It tends to be weaker than a well-linked equivalent.

How often should I check for orphan pages?

Every few months is reasonable for most sites, and always before and after a redesign or migration.

Should I delete all orphan pages?

No. Review each. Some are valuable and need links, some are intentional, and only the outdated or duplicate ones should go.