How to Find Orphan Pages: Checker Tools and a Manual Workflow

An orphan pages checker cannot be a normal crawler alone. A crawler finds pages by following links from its starting URLs; a true orphan page has no crawlable internal path from the pages being crawled. To discover candidates, compare the crawler’s reachable URL set with independent sources that can reveal URLs from outside the internal link graph: XML sitemaps, analytics landing pages, Google Search Console, backlink data, CMS or database exports, and server logs.

The practical workflow is a set comparison: URLs known from other sources minus URLs reached through internal links = orphan candidates. Then validate each candidate. Some will be redirects, non-canonical URLs, old campaign pages, utility URLs, or pages that were intentionally removed from navigation. The parent orphan pages guide covers how to evaluate and fix those outcomes; this page focuses on finding them reliably.

Why a crawler by itself misses orphan pages

Google says crawlable links help it find other pages, but URLs can also be discovered through sitemaps and other sources. That means “not found in my crawl” and “unknown to Google” are different statements.

Suppose a site has 10,000 URLs in its CMS. An HTML crawl from the homepage reaches 8,400. The remaining 1,600 are not automatically orphans. Some might be redirected, blocked, non-indexable, unpublished, API endpoints, or duplicates. The job is to reconcile datasets until each URL has an intended state.

The data sources an orphan-page checker should combine

Workflow A: use a crawler with external URL-source integrations

Some crawlers can import URLs from sitemaps, analytics, and Search Console, then flag URLs that were discovered externally but had no inlinks in the main crawl. Screaming Frog documents this exact approach in its orphan pages tutorial: combine an internal crawl with XML sitemap, Google Analytics, and Search Console sources, run crawl analysis, and review orphan-URL reports.

Configuration sequence

1. Define the canonical host and crawl scope. Decide whether subdomains, parameters, staging areas, language directories, or private sections belong in the analysis.
2. Crawl from the normal site entry points. Use homepage/navigation paths rather than seeding every known URL, otherwise you lose the distinction between linked and externally discovered pages.
3. Import XML sitemap URLs. Keep source attribution so you know a candidate came from the sitemap.
4. Connect analytics landing-page data. Use a window long enough to capture low-frequency but real pages; document the date range.
5. Connect Search Console page data. Pull pages with impressions/clicks and preserve the property/date range.
6. Optionally import CMS and backlink exports. These can expose additional live URLs.
7. Run post-crawl analysis. Separate URLs reached through internal links from URLs discovered only through imported sources.
8. Export candidates with source labels. A page found in GSC + sitemap + logs has a different evidence profile from a page found only in an old CMS export.

Workflow B: a manual orphan-page checker in a spreadsheet or database

You can reproduce the logic without a crawler integration. The important part is preserving one canonical URL key and source flags.

1. Build the reachable set

Export every internal HTML URL reached by the crawler from your chosen start points. Include at least:

• Final normalized URL.
• Status code.
• Canonical URL.
• Crawl depth.
• Number of inlinks.
• Indexability.

2. Build the known-URL set

Append URLs from independent sources. Add one Boolean/source column for each:

• In sitemap?
• In analytics?
• In Search Console Performance?
• Known in Page indexing or URL Inspection sample?
• Has external backlink?
• Seen in server logs?
• Published in CMS?

3. Normalize URLs before comparing

False orphan reports often come from URL-format differences. Normalize carefully:

• Preferred protocol and hostname.
• Trailing slash policy.
• Case rules where the platform treats case consistently.
• Tracking parameters that should not define a separate canonical page.
• Known redirect aliases.

Do not strip parameters blindly. On some sites a parameter creates a genuinely different page state or canonical URL.

4. Create the candidate rule

A simple candidate is:

Published/known URL = yes AND reached by internal crawl = no.

Then add confidence tiers:

Method 1: find orphan candidates from XML sitemaps

Google’s sitemap guidance says sitemaps should include the canonical URLs you want to appear in search results, while submitting a sitemap is a hint rather than a guarantee of crawling or indexing. This makes the sitemap an excellent comparison source.

1. Export all sitemap URLs.
2. Compare them to the crawler’s internally reached URLs.
3. Filter for sitemap URL = yes and crawler inlinks = 0 / not reached.
4. Check status, canonical, indexability, and page purpose.

A sitemap-only URL may be a valuable orphan, but it may also be a stale sitemap entry. Fix the source of truth, not only the report.

Method 2: find orphan candidates from analytics

Analytics can reveal pages users reached from ads, email, bookmarks, direct links, external links, or old search results even when those pages are not linked internally.

1. Export landing pages for a documented date range.
2. Normalize them to canonical URL format.
3. Left-join against the crawl set.
4. Investigate landing pages with real activity but no internal crawl path.

Check tracking quality before drawing conclusions. A page with no analytics data is not proof that nobody uses it.

Method 3: use Search Console Performance and Page indexing

The Search Console Performance report can show pages that received impressions or clicks from Google Search. If such a page is missing from the internal crawl, it deserves review because Google and users can reach a URL the site architecture does not expose.

The Page indexing report provides a broader view of URLs Google knows about and their indexing state. Google notes that if it does not know about a URL, that URL will not appear in the indexed or non-indexed totals. For specific URLs, use URL Inspection.

Do not treat Search Console as a perfect URL inventory. Google documents data limitations, and the Links report is also a sample rather than a complete list. Combine sources.

Method 4: use backlinks to uncover externally discoverable pages

A page can lose all internal links but continue to receive visits and crawler discovery through external links. Search Console’s Links report can show externally linked pages, although Google states that the report is not a comprehensive list of every link.

1. Export top externally linked pages or use a trusted backlink dataset.
2. Compare target URLs with the crawl set.
3. Prioritize live 200 pages that still receive relevant external links.
4. Decide whether to restore internal links, consolidate to a successor, or redirect if the content is retired.

Method 5: use server logs to find requested but unlinked URLs

Server logs answer a different question: which URLs were actually requested? They can reveal Googlebot requests, old campaign URLs, parameter variants, and externally discovered pages that your internal crawl does not reach.

1. Choose a representative log window; include longer windows for low-frequency sections.
2. Normalize requested URLs carefully.
3. Verify Googlebot or other bots if bot-specific conclusions matter.
4. Separate status codes and user agents.
5. Compare live 200 URLs with the internal crawl set.
6. Review repeated bot or user requests to unlinked pages as high-priority candidates.

Logs do not tell you whether a page should be linked. They prove requests happened. The editorial/technical decision still requires page purpose and business context.

False positives to rule out before fixing anything

JavaScript or crawler configuration hid the link

If a link appears only after rendering, behind interaction, or outside the crawler’s configured scope, the page may not be truly orphaned. Compare rendered HTML and crawl settings. Google’s link guidance says crawlable links are normally anchor elements with an href.

The URL is a redirect or non-canonical alias

An old URL with backlinks may correctly redirect to a current page. Do not add internal links back to the old address. Normalize to the preferred destination and update important external references when practical.

The page is intentionally unlinked

Some confirmation, account, testing, paid-campaign, or utility pages should not sit in public navigation. Check indexability, user need, and privacy/security requirements before “repairing” them.

The page is intentionally retired

A 404 or 410 can be the correct outcome when content has no relevant successor. The task is cleanup: remove it from sitemaps and stale internal references, and decide how to handle external links.

What to do with confirmed orphan pages

When adding links, use pages where the relationship helps a reader. The site’s internal linking strategy guide covers crawlable links, useful source pages, and architecture decisions. The Internal Linking Audit Template provides a workbook for tracking URL inventory, orphan candidates, anchors, and fixes.

Validate after remediation

1. Re-crawl from normal site entry points without seeding the repaired URLs.
2. Confirm the page now has one or more useful crawlable inlinks.
3. Verify the source page and destination are both canonical/current URLs.
4. Check that sitemap membership matches the page’s intended indexation role.
5. Use URL Inspection for important Google-specific cases.
6. Monitor Search Console, analytics, and logs over an appropriate period without claiming that the link alone caused later ranking or traffic changes.

Minimal data model for an orphan-page checker

The key rule

Do not ask one tool to “find all orphan pages.” Build two sets: what the internal graph can reach and what the organization, users, search engines, or external sites know exists. The gap between those sets is where orphan investigation starts.

Sources and verification

• Google Search Central: Link best practices
• Google Search Central: Build and submit a sitemap
• Google Search Console: Performance report
• Google Search Console: Page indexing report
• Google Search Console: Links report
• Screaming Frog: How to find orphan pages