Orphan page finder

What is the Orphan page finder?

An orphan page is a page on your website that exists and is publicly accessible, but is not linked to from anywhere else on the site. No menu points to it, no related-article modules reach it, no footer link touches it. As far as the site's internal navigation is concerned, the page does not exist. The Orphan page finder is a tool that detects this problem by comparing the URLs listed in your XML sitemap against the URLs that actually receive internal links somewhere on the site. Whatever appears on the sitemap side but is missing from the linked side is flagged as orphaned.

The tool works with the two lists you already have or can generate quickly: the complete set of URLs your site considers important enough to submit in a sitemap, and the set of URLs that at least one internal link points to. When those two lists are aligned, every important page is reachable by crawling. When they are not, the gap between them is exactly where your orphan pages hide. The tool surfaces that gap as a clean, reviewable list so you can decide what to do with each orphaned URL rather than leaving it to chance.

What the Orphan page finder checks

The core comparison is deliberately simple and easy to reason about. You supply the sitemap URLs as the "should exist and be found" list, and you supply the linked URLs as the "is actually reachable" list. The tool checks every sitemap entry against the linked set and reports the entries that never appear as link targets. Because the comparison is based on exact URLs, it also catches inconsistencies in the way you present links, such as pages that are only ever referenced through a parameterized URL while the canonical version sits unlinked.

This is different from a few related checks you might be familiar with. A page that returns a 404 is broken, but an orphan page often returns a healthy 200 status; the problem is reachability, not response code. Similarly, a page that no sitemap mentions is simply unindexed by design, while an orphan page is one you explicitly asked to be found but forgot to connect. The tool concentrates on that specific gap: pages that pass your sitemap test but fail your internal-linking test.

The output is organized so you can act on it immediately. You see the exact URLs that are orphaned, which lets you check each one individually and ask the right question: should this page be linked into the main navigation, linked from a relevant body of content, merged into an existing page, or removed entirely? Not every orphaned page needs a link; some should be pruned or redirected. What matters is that the page is now a deliberate decision instead of an oversight.

How to use the Orphan page finder

You need two sources of truth to run the comparison, and both are standard artifacts that most sites already have. The steps below walk through gathering them and submitting them to the tool.

1. Open your XML sitemap and copy the full list of URLs it contains. If your site uses a sitemap index file, expand it so that every individual sitemap's URLs are included, then paste that combined list into the sitemap field.
2. Gather the list of URLs that receive internal links on your site. If you have crawl data from a site crawler, export the internal-link report and collect every distinct target URL. Otherwise, use a link-extraction report from your CMS or SEO platform that lists all internal link destinations.
3. Paste the sitemap URLs into the first field of the form and the linked URLs into the second field, keeping each URL on its own line and stripping any surrounding whitespace or HTML.
4. Submit the form and wait for the comparison to complete. The server processes both lists and returns the set of sitemap URLs that were not found among the linked URLs.
5. Review the returned list of orphaned pages. For each URL, decide whether to add internal links, merge the content elsewhere, set up a redirect, or remove the page, then make the change and re-run the check on a later crawl to confirm the gap is closed.

How to get better results

A few preparation habits make the comparison far more reliable. Treat the lists you paste as data to be cleaned, not just text to be copied.

• Standardize URL format before comparing. Decide on one presentation, such as a trailing slash or no trailing slash, http versus https, and apply it to both lists so the tool is not fooled by cosmetic differences.
• Strip tracking parameters and session IDs from both lists. If a page is linked as example.com/page?utm_source=menu but the sitemap lists example.com/page, the comparison may not recognize them as the same resource.
• Include every individual sitemap when you copy URLs from a sitemap index. Missing a sub-sitemap is the most common way to produce a false orphan report.
• Make sure your linked-URL list comes from a crawl that follows real navigation paths, including footer, sidebar, and breadcrumb links, not just body content links.
• Resolve canonical URLs before running the check. If pages share a canonical, map every linked variant back to the canonical form so the tool compares like with like.
• Re-run the check after you make fixes. Orphan detection is only useful when the result is measured, so schedule the comparison after content changes and confirm that newly linked pages disappear from the orphan list.

Why the Orphan page finder matters

Search engines find pages by following links. When a page has no internal links pointing at it, the crawler's only ways to discover it are external backlinks, direct submissions, or the sitemap itself. Relying on the sitemap alone is fragile because sitemaps are treated as hints, and a page that is neither linked internally nor referenced externally may never be crawled reliably. Orphan pages therefore waste your content budget: you invested time writing, designing, and optimizing a page, but you never gave search engines or users a dependable path to it.

Orphans also cost you in link equity distribution. Internal links are one of the clearest signals of a page's relative importance, and a page without links gets no internal equity flowing into it. Fixing an orphan is usually cheap, often just one or two contextual links from related content, but the payoff includes better crawl coverage, more pages indexed, and a site structure that matches the importance you assign to each page. The Orphan page finder turns this abstract risk into a concrete list you can clear in a single working session.

When to use the Orphan page finder

• After a site migration or redesign, when old URLs are moved, redirected, or reorganized and pages can easily fall out of the navigation structure.
• Before a seasonal campaign or product launch, when new landing pages are added quickly and might be published without being woven into the site's existing link architecture.
• When search console shows pages being indexed but earning no clicks and no impressions, which often signals a reachability problem rather than a content quality problem.
• After content pruning or consolidation, when merging pages or removing old content can leave remaining pages disconnected from the site's internal links.

Related SEO Tools

Complete your SEO workflow with these related free tools:

• Keyword research - Research the search volume, CPC, and competition of keywords.
• User-Agent parser - Parse a User-Agent into readable individual components. Identify browser, OS, and device details from a UA string.
• URL parser - Parse a URL into readable individual components. Break down scheme, host, path, query, and fragment for inspection.
• Word density counter - Count the number and density of each word in a text. Check keyword balance and avoid overuse in content.

Related SEO Guides

Learn more about this topic with our in-depth guides:

• On-Page SEO Checklist: The Complete Guide
• Page Speed Optimization: The Ultimate Guide
• HTML Minification: Reduce Page Size Without Breaking Code

Frequently asked questions

What exactly counts as an orphan page?

An orphan page is any page on your site that no other page links to, so it cannot be reached by crawling through the site's internal navigation. It may still be reachable by direct URL, by external backlinks, or via the sitemap, but internally it is disconnected. This tool identifies the subset of those pages that also appear in your sitemap, which is the most damaging case because the sitemap signals the page is important while the link structure fails to support it.

Does the Orphan page finder crawl my website?

No. The tool performs a comparison on the two lists you provide: the sitemap URLs and the linked URLs. It does not scan your site or follow links itself, so the accuracy of the result depends on how complete your linked-URL list is. For the most accurate results, pull that list from a full site crawl or a comprehensive internal-link export.

What URL formats does the tool accept?

The tool accepts plain URLs, one per line, in either the sitemap field or the linked-URL field. For reliable matching, keep the format consistent between the two lists, including the protocol, the subdomain, and the trailing slash, because the comparison treats URLs as literal strings.

Can an orphan page still be indexed by search engines?

Yes, it can be indexed if it receives external backlinks or if the sitemap is crawled and honored. That is precisely why orphans are dangerous: they can be indexed and even rank, while receiving none of the internal link equity or crawl priority that your other pages get, making their performance hard to explain and even harder to improve.

Should every orphaned page be given internal links?

Not necessarily. The right action depends on the page's purpose. High-value pages that you want to rank should be linked contextually from related content and, where appropriate, from navigation. Pages that are outdated, thin, or duplicated with other content should be merged or redirected instead. The tool gives you the list; you supply the judgment.