Crawvix

Orphan Pages: How to Find Pages With No Internal Links and Fix Them

Crawvix Editorial Team · Published October 29, 2026 · Last updated October 29, 2026 · 10 min read

An orphan page is a page on your website that no other page on the same website links to. A visitor cannot reach it by clicking through the site. A search engine that discovers pages by following links will not find it that way either. The page may still exist, load fine and even sit in your sitemap, but nothing in the site's own structure leads to it.

Orphan pages appear quietly. A landing page is built for a campaign and the campaign link is removed. A product is hidden from a category but stays live. A redesign drops a menu item. An old guide loses its only link when a related-posts block is changed. This guide is for site owners, editors and developers who want to find these pages and decide what to do with each. By the end you will have a list of orphans, a decision for every one and a way to stop new ones appearing.

Connecting an orphan page makes it reachable. It does not mean a search engine will index it or rank it.

Before you begin

You will need:

  • Access to the list of pages your site really has. That might be a CMS export, a database table, or your XML sitemap.
  • A way to crawl your own site, which can be a desktop crawler, a command line tool or a site scanner, so you can see which pages are reachable by links.
  • A Google Search Console property. See Set Up Google Search Console if you need one.
  • Editing access to menus, templates and content.
  • A spreadsheet. Plan for one to three hours on a small site.

The main risk is deleting something that matters. Do not remove or redirect a page until you know why it is an orphan. Some orphan pages are intentional, such as a thank-you page after a form or a private page for a campaign.

Why orphan pages matter

Google's guidance on links says that every page you care about should have a link from at least one other page on your site. Google discovers most new pages by following links, so a page with no incoming links depends on other discovery routes. A sitemap can be one such route, but Google describes a sitemap submission as a hint, and says it does not promise to download or use the file.

An orphan page also gives visitors no path to it. If the page is useful, that is a missed chance. If the page is outdated or not meant to be public, an orphan can be the sign of content you forgot about.

Step-by-step instructions

Step 1: Build a list of pages you believe exist

Collect every public URL you think the site has, from as many sources as you can:

  • The XML sitemap. Fetch it and copy the <loc> addresses. Large sites may have a sitemap index with several files; see Split Large Sitemaps into a Sitemap Index.
  • Your CMS or database. Export published posts, pages and products with their URLs.
  • Analytics. Pages that received visits, particularly from search or direct traffic, even if no internal link exists.
  • Search Console. The pages that appear in your performance data or in the page indexing report.
  • Server logs, if you have them, for URLs that crawlers and visitors requested.

Put all addresses in one column, remove duplicates, and normalise them: one protocol, one host, a consistent trailing slash, no tracking parameters. Mixed forms will create false orphans in the comparison.

What success looks like: one clean column of canonical-looking URLs, with a note of which source each came from.

Start a crawl at the home page and let it follow only internal links, as a search engine would. Export the list of every URL the crawler reached. Set the crawler to follow links in the HTML and not to read the sitemap as a source of URLs, because the whole point is to find pages that links do not reach.

Make sure the crawl is complete. A crawl that stops at a page limit will show many false orphans, since pages it never reached may in fact be linked from pages it never read. Crawvix handles this by declining to call anything an orphan when a crawl was cut short. Do the same with your own crawl: check that the total looks right and that the stopping reason is not a limit.

If your site builds links with JavaScript, check that the crawler renders them or look at the rendered HTML. Google can find links added by JavaScript only if they use <a href> markup, so links that rely on click handlers will not count. See JavaScript SEO: Rendering Basics.

What success looks like: a complete export of linked pages, with the crawl finishing normally.

Step 3: Compare the two lists

In a spreadsheet, mark each URL from Step 1 as found or not found in the Step 2 crawl. The ones not found are your orphan candidates. Add a column for the source where each came from, because a page listed only in the sitemap behaves differently from one that appears only in analytics.

Two kinds need extra care:

  • Pages that are linked only from other orphans. They look reachable in the crawl only if the crawl began somewhere that links to them. A cluster that links among itself but not from the main site is still disconnected.
  • Pages linked only from themselves. A page that links to its own address, for example in a breadcrumb, is not reachable. A link from a page to itself does not make it findable.

Also check the opposite problem. Pages the crawl found but that are missing from your sitemap may need adding. Sitemap entries should be the canonical URLs you want in search results, and Google notes that they should be absolute addresses.

What success looks like: a short list of URLs with no incoming internal link, each with its source.

Search Console's Links report, under Internal links and Top linked pages, shows which pages receive the most links from your own site, and selecting a URL shows its linking pages. Tables are capped at 1,000 rows and the report is a sample, so a page that is not listed is not proven to be an orphan. Use it to cross-check. If a URL on your orphan list shows linking pages in Search Console, find out why your crawl missed them.

What success looks like: your orphan list is confirmed or trimmed using a second source.

Step 5: Decide what each orphan should be

Sort every orphan into one of five groups.

  1. Keep and link. The page is useful and should be found. Add links to it. This is the common case.
  2. Keep but do not link. The page is meant to be hidden, such as a thank-you page, a private offer or a landing page for paid traffic. If it should not appear in search results, add a noindex rule and leave it out of the sitemap. Do not block it in robots.txt if you want Google to see the noindex tag. Google cannot read a noindex on a page that robots.txt blocks, and the page can still be indexed from links elsewhere.
  3. Merge. The content overlaps a stronger page. Move any useful text there and redirect the orphan with a 301 to it. See 301 vs 302 Redirects.
  4. Redirect. The page has been replaced. Send it with a permanent redirect to the page that replaced it.
  5. Remove. The page has no value. Return a 404 or 410 status so that search engines learn it is gone, and take it out of the sitemap. Never redirect many unrelated pages to the home page.

Write the decision next to each URL. Do not delete anything until the decision is recorded.

What success looks like: each orphan has one of the five decisions and a named owner.

For pages you are keeping and linking, choose where the links belong. Good places are:

  • A category, hub or index page for the topic.
  • Related-article or related-product blocks.
  • Contextual links inside body text of closely related pages.
  • The main menu or footer, only for pages that deserve site-wide prominence.

Use real <a href> links with descriptive anchor text, such as the product or topic name, not "click here". The method for choosing and wording these links is in Internal Linking Strategy. Add at least two or three links from relevant pages, not just one, so that one future template change does not orphan the page again.

What success looks like: each kept page now has several incoming links from relevant pages.

Step 7: Fix the sitemap to match

After the changes, the sitemap should contain the pages you want indexed and nothing else. Add the kept pages. Remove pages you merged, redirected or deleted, because sitemaps should list canonical, indexable URLs and not redirects or errors. See How to Create a Valid XML Sitemap and Find and Fix 404 and 500 Errors in XML Sitemaps.

What success looks like: every sitemap URL returns a 200 status, is canonical and is linked from at least one other page.

Step 8: Re-crawl and set up prevention

Run the crawl again and repeat the comparison. The orphan list for kept pages should be empty. Then build a habit into publishing: a new page is not finished until at least two relevant pages link to it. Re-run the comparison every quarter and after any redesign, menu change or template change, since these are the usual causes. Crawvix's "No orphan pages" check compares the addresses in your sitemap with the links found during a scan, which is one way to repeat the process automatically.

What success looks like: the second crawl finds no unplanned orphans, and publishing has a linking step.

Final verification checklist

  • You compiled a list of known URLs from the sitemap, the CMS and at least one other source.
  • A complete crawl followed internal links and was not cut short by a limit.
  • Every orphan has a recorded decision: link, hide, merge, redirect or remove.
  • Pages you kept have several relevant incoming links with descriptive anchors.
  • Hidden pages use noindex and are not blocked in robots.txt.
  • Merged or replaced pages return a permanent redirect to a relevant page.
  • Removed pages return 404 or 410 and are out of the sitemap.
  • A re-crawl confirms the fix and the sitemap lists only live, canonical pages.

Common mistakes to avoid

  • Treating the sitemap as the fix. A sitemap helps discovery, but Google calls submission a hint. Add links too.
  • Comparing unnormalised URLs. http against https, or a trailing slash against none, produces false orphans. Normalise first.
  • Trusting an incomplete crawl. If the crawl stopped early, unreached pages look orphaned. Finish the crawl.
  • Linking from a page that is itself an orphan. The chain must lead back to a page that the site links to.
  • Deleting before deciding. Some orphans are deliberate. Record the reason first.
  • Redirecting everything to the home page. Redirects should go to a relevant replacement. Irrelevant ones are poor for visitors.
  • Blocking hidden pages in robots.txt and expecting noindex to work. Google must be able to fetch the page to see the tag.
  • Linking with click handlers. A link without an href does not count as a crawlable link.

Frequently asked questions

Are orphan pages bad for SEO?

They are a risk, not a penalty. A page nothing links to is harder to find, to crawl and to give context, and it gives visitors no path. If the page matters, link it. If it does not, decide whether to remove it.

Can Google index an orphan page?

It can. Google may know the URL from a sitemap, an external link, or a past crawl. But Google treats links as the main discovery route, and a page with no internal links gives it little context. Do not rely on indexing without links.

Is a page in the sitemap but not linked an orphan?

Yes, for this purpose. It is reachable only through the sitemap file, not through the site's own navigation.

Should I noindex orphan pages I do not want to delete?

If you do not want the page in search results, a noindex rule is the right tool, and the page must stay crawlable for Google to read it. If you no longer need the page at all, remove it or redirect it instead.

How often should I check for orphans?

After any redesign, migration, menu change or bulk content change, and at least once a quarter on an active site.

Official references

Next step: See how Crawvix checks a website and capture a baseline once scanning opens. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.

In this category

All 19 Crawlability guides