How to use it
- 1
Confirm that the project uses the intended origin and a public sitemap urlset.
- 2
Run the bounded crawl and wait for the stored result.
- 3
Review each candidate against navigation, contextual links, and broader evidence before changing the site.
What the tool can do
- Compares normalized URLs from one sitemap urlset with discovered internal links.
- Stays on one origin and does not treat cross-origin URLs as part of the project.
- Shows candidates from the stored crawl together with the sitemap sample size.
Common use cases
- Find URLs for manual internal-link review.
- Compare a small sitemap sample with links actually discovered.
- Review candidates after changing navigation or section structure.
How it works inside
A candidate is the difference between sitemap URLs and the discovered link graph after same-origin normalization.
The term orphan is intentionally not used as a confirmed status without a complete graph and additional evidence.
Questions and answers
Is a candidate definitely an orphan page?
No. It only means no link was found in the bounded sample. Manual or broader verification is required.
Why is a sitemap index not expanded?
The current scope is intentionally bounded to one urlset and 25 HTML pages. Index support needs a separate safe limit and contract.