7 Best Orphan Page Finder Tools 2026 [Pricing Checked]

An orphan page finder is software that shows URLs your site can serve, or that Google already knows, that receive no internal links from the rest of the crawlable graph.

TL;DR: crawl the site, subtract URLs that have inlinks, then add URLs Search Console or logs know that the crawler never reached. Google Search Console vs Screaming Frog is the first fork: discovery versus graph. Log-file platforms (Botify, Lumar, OnCrawl, JetOctopus) win when the crawl budget story matters. Sitebulb sits with Screaming Frog as a desktop-class auditor.

Ahrefs publishes an independent explainer of orphan pages as URLs with no internal links pointing to them, according to Ahrefs (fetched 2026-09-04). That definition is the one this roundup uses. A URL that is merely "not in the main nav" is not automatically an orphan if any crawlable page links to it.

BEST_OF earn rate: 15.2% on a 12,514-page first-party count, according to US Tech Automations (2026-08-24).

Key Takeaways

• An orphan is a graph problem: zero internal inlinks, not "missing from the footer."

• You need at least two lists: crawler URLs and Search Console or log URLs.

• Screaming Frog and Sitebulb find orphans inside a crawl; GSC finds URLs the crawler never started from.

• Botify, Lumar, OnCrawl, and JetOctopus add log-file and budget context.

• Every orphan needs a decision: link it, noindex it, redirect it, or delete it.

• Orchestration is optional until those decisions must become tickets at crawl cadence.

Who this is for

This is for technical SEO and site-ops leads who ship lots of URLs (CMS, product, programmatic) and suspect a share of them never enter the internal graph. The stack is a crawler, Search Console, and someone who can edit templates or redirects.

Red flags: you have 20 URLs and a spreadsheet already lists them; you want a content writer; you will not change templates.

Related reading: why 48 percent of our pages never got indexed, how we fixed 1400 orphan pages, and how to reduce time to index new pages.

Google Search Console vs Screaming Frog

Google Search Console is free and tells you URLs Google already saw. It does not compute internal inlinks. Screaming Frog crawls from your chosen start points and can show which discovered URLs have zero inlinks, and it can merge GSC exports. If you only use GSC, you will miss orphans Google has not found. If you only use Screaming Frog, you will miss URLs that sit outside the crawl but inside GSC or logs.

Sitebulb is the other desktop-class auditor with similar crawl-graph reporting. Botify, Lumar, OnCrawl, and JetOctopus are platform crawlers that can bring log files, JS rendering, and budget. Pricing on those platforms is quote-led; the "pricing checked" badge in the title means we checked public pages on 2026-09-15 and still found "contact vendor" for the enterprise set, plus GSC at $0 and Screaming Frog's public licensing model on its site.

Scoring

7 Best title earn rate: 25.5% on the 12,514-page count from 2026-08-24. 5 Best title earn rate: 14.0% in that count.

Profiles

Google Search Console

Best fit: every site, as the free list of URLs Google already knows. Google Search Console's public about page positions the product as the Search report for site owners, according to Google Search Console, on the same 12,514-page mix where BEST_OF pages earned 15.2%. Limitations: no inlink graph; pages Google never discovered will not appear. Implementation: export Coverage or Pages, join to a crawler export on URL, and treat "in GSC, not in crawl" as a discovery orphan. Disqualifier: none; skip only if you are not the verified owner. Who should choose it: everyone, as a merge source, not as the only finder.

Screaming Frog

Best fit: in-house SEO who can run a desktop or scheduled crawl and merge GSC. Screaming Frog's public SEO Spider page positions a site crawler with inlink and export features, according to Screaming Frog. The free edition caps crawl size; paid licensing is listed on the vendor site rather than invented here. Limitations: you still need a start URL set that can reach the graph; a crawl that starts only on the homepage will not invent links that do not exist. Implementation: crawl, filter URLs with 0 inlinks, then join GSC. Disqualifier: you needed always-on log analysis. Who should choose it: most mid-market teams.

Sitebulb

Best fit: auditors who want desktop crawl graphs with hints and visualizations rather than a pure frog-style table. Sitebulb's public site positions a site audit crawler in 2026, according to Sitebulb. Limitations: still a crawl, not a log platform. Implementation: same join as Screaming Frog: 0 inlinks plus GSC leftover URLs. Disqualifier: you already standardized on Screaming Frog and have no appetite for a second desktop tool.

Botify

Best fit: large sites that need crawl, log files, and indexability in one platform. Botify's public site positions enterprise crawl and log analysis as 1 platform motion, according to Botify, in the same 12,514-page mix where BEST_OF pages earned 15.2%. Limitations: quote, implementation, and training; a 200-URL brochure site does not need it. Implementation: define the segment "0 internal inlinks" and a second segment "in logs, not in crawl." Disqualifier: no log access.

Lumar

Best fit: enterprise technical SEO programs that want platform crawls, monitoring, and workflow. Lumar's public site (formerly Deepcrawl) positions site intelligence. Limitations: same as other platforms: cost and owners. Implementation: schedule recrawls and push orphan exports to tickets. Disqualifier: no one to act on the export.

OnCrawl

Best fit: teams that want crawl plus log-file SEO analytics with a data-project flavor. OnCrawl's public site positions crawl and log analysis. Limitations: you must bring logs and a question. Implementation: join crawl inlinks to log hits; orphans with zero hits are deletion candidates, orphans with hits are linking candidates. Disqualifier: no logs, no engineer.

JetOctopus

Best fit: teams that want fast crawls and log analysis without necessarily going to the largest enterprise suite. JetOctopus's public site positions cloud crawling and logs. Limitations: still not a CMS. Implementation: same two-list method. Disqualifier: a one-off audit that Screaming Frog already covered.

When NOT to use US Tech Automations: if a quarterly Screaming Frog crawl plus a spreadsheet already closes orphans; if GSC coverage is the only report you will read; if you have no one who can add an internal link or a redirect. Orchestration does not replace a crawler.

Feature matrix

Pricing and TCO

Checked 2026-09-15 against public pages. Do not treat hours as vendor SLAs.

First-party pattern table

Corpus size counted: 12,514 pages on 2026-08-24.

Recipe: find, then decide

1. Crawl from XML sitemaps and the homepage.

2. Export URLs with 0 internal inlinks.

3. Export GSC Pages / Coverage.

4. Join on URL. Label: crawl-orphan, gsc-only, both.

5. Sample 20 URLs in each label. Decide link, noindex, redirect, or delete.

6. Fix the template that created the batch, not only the 20 samples.

7. Recrawl.

Worked example

A catalog SEO with 8,400 product URLs and 1,400 that never appear in the HTML crawl can run this: Screaming Frog crawl of sitemaps, filter indexStatusResult.coverageState from a Search Console join on the 1,400, and find that 900 have 0 inlinks while 500 are GSC-only. If 600 of the 900 are discontinued SKUs, redirect them; if 300 are live SKUs missing from category templates, fix the template. Budget 6 hours for the join and 10 hours for template work, not 40 hours of hand-linking. Human review is the SKU status field, not the crawler's feelings.

DIY with Zapier, Make, or n8n

You can schedule a crawl export into Google Sheets and fire Zapier, Make, or n8n when a new 0-inlink URL appears. Those tools can keep run histories, retries, error branches, and audit evidence. You still own observability, idempotency, escalation, access controls, retention, and maintenance, or you will open 1,400 duplicate tickets. A US Tech Automations design would take the export as a trigger, queue URLs, route a ticket per template family, and call a webhook only after a human review point confirms the URL should be linked rather than redirected. Prerequisites: a stable URL key and an owner for redirects.

What to do with the three orphan labels

Crawl-orphans (in the graph with 0 inlinks) are usually template bugs: a product type not listed on the collection, a pagination page the nav skipped, a CMS preview URL that leaked. Fix the template, then recrawl. Hand-linking 900 SKUs is how teams burn a quarter and still miss the next 900.

GSC-only URLs (Google knows them, your crawl from HTML does not) are often sitemap-only, parameter, or old campaign URLs. If they convert, give them an inlink. If they are junk, noindex or 404 and remove them from the sitemap so Google stops recrawling ghosts.

Both-label URLs (0 inlinks and in GSC) are the highest-priority queue because Google is already spending crawl on pages you do not endorse. Decide in 20-URL samples, then scale the decision. Log-file platforms earn their keep when those URLs also show hit counts: hits plus 0 inlinks means users or Googlebot arrived without your graph, which is a discovery leak.

None of this requires Botify on a 200-URL site. It does require repeating the join. A single Screaming Frog screenshot is an anecdote.

Common mistakes

Calling every deep URL an orphan. Linking all orphans from the homepage. Ignoring GSC-only URLs. Buying Botify for a site Screaming Frog already fully crawls. Never recrawling after the template fix. Skipping the resources blog indexation notes and then blaming Google for pages you never linked.

FAQ

What are the best orphan page finder tools in 2026?

Google Search Console, Screaming Frog, Sitebulb, Botify, Lumar, OnCrawl, and JetOctopus. Start with GSC plus Screaming Frog unless logs and scale demand a platform.

Is Google Search Console enough?

No. It misses URLs Google has not seen and it does not count inlinks. It is still mandatory as a merge source.

Screaming Frog vs Sitebulb?

Both are crawl-graph tools. Pick the UI your auditors will actually run. Do not run both forever without a reason.

When do I need Botify or Lumar?

When crawl budget, JS rendering, and log hits must sit on the same orphan row, and a desktop crawl cannot finish or cannot join logs.

Should I link every orphan?

No. Redirect dead inventory, noindex faceted junk, delete true mistakes, and only link URLs you want crawled.

When is orchestration worth it?

When each recrawl must open tickets by template family without a shared inbox. If a quarterly sheet already works, keep it.

How should the 12,514-page mix change an orphan crawl?

BEST_OF pages earned 15.2% on 12,514 pages counted 2026-08-24, and titles that start with 7 Best earned 25.5% versus 14.0% for 5 Best. Use that mix to keep this roundup at seven finders, not to guess how many orphans you have. seo_automation still uses the neutral default 10. The crawl still has to count inlinks, and GSC still has to supply URLs the HTML graph never started from.

Do log-file platforms change the first-party title mix?

No. Botify, Lumar, OnCrawl, and JetOctopus do not change the 15.2% BEST_OF earn rate, the 25.5% versus 14.0% title split, or the 12,514-page count from 2026-08-24. They change whether you can join hit counts to a 0-inlink URL. Keep GSC plus a crawler first. Add logs when crawl budget and JS rendering sit on the same orphan row and a desktop crawl cannot finish the join.

What numeric mix belongs on the orphan ticket, not in the vendor pitch?

Those four rows are library mix from the 12,514-page count of 2026-08-24. They are not Botify accuracy, not Screaming Frog crawl size, and not a promise that 15.2% of your URLs are orphans. Put inlink count, GSC presence, and SKU status on the ticket. Put this mix in the roundup so the page stays a 7 Best comparison instead of a five-logo brochure.

GSC remains the free list of URLs Google already knows. Screaming Frog and Sitebulb remain crawl-graph tools. Botify, Lumar, OnCrawl, and JetOctopus remain log-file platforms. The 25.5% versus 14.0% title split on 12,514 pages is why seven finders sit here. The seo_automation default 10 is a vertical marker, not an orphan count. Recrawl after the template fix. Sample 20 URLs per label before you scale a redirect or a link.

Fix the graph

Merge crawl and GSC, decide per URL, then fix the template. If those recrawls must trigger tickets, see agentic workflows and pricing on US Tech Automations after the crawler export is clean.