Orphan Page Finder
Check an inventory against a saved same-host link map or declared incoming counts. Review zero results, incomplete coverage, conflicting evidence and excluded home URLs.
Separate Zero Links From Missing Coverage
Orphan Page Finder: how to use it
- Paste page URLs and any saved URL -> URL links. You can add incoming counts with inlinks: N or supply an inventory CSV and a separate link CSV.
- Keep coverage partial unless your saved links cover the entire scope. Choose whether to exclude bare home URLs.
- Check incoming links and review the evidence for each result. Export the complete JSON with observed sources and declared counts.
Limits and notes
Up to 500 distinct pages, 5,000 link records and 250,000 UTF-16 units per input. URLs are read locally as text. Page matching removes fragments and retains paths, trailing slashes and query strings. Distinct same-host sources count once. A same-page link provides no incoming source from another page. Complete coverage is a declaration about the supplied capture.
How your privacy works →Orphan Page Finder: common questions
Can I identify an orphan page from a sitemap alone?
A sitemap or URL list provides pages to check. A saved link list or reported incoming count is needed to establish a result beyond unknown coverage.
What does a conflicting result show?
A declared incoming count is lower than the number of distinct supplied source pages, or two submitted counts for the same page disagree. Review the source exports.
Do links to a fragment count as proof of an incoming link?
A link from a different same-host page counts toward the target page after the fragment is removed.