Orphan Page Finder

Orphan Page Finder produces crawl URLs that are absent from the sitemap. The finder crawls the same registrable host as the sitemap, at most 30 HTML pages, depth 2, two pages at a time. A URL found in that sample crawl and missing from the sitemap is listed as a possible orphan. You can paste XML into the box, or you can enter a public sitemap URL and let the server fetch it. A pasted urlset is parsed on the server without a second copy of the parser in the browser. The form stays near the top of the page, under the single title. (Orphan Page Finder, guide 1.)

Use https://example.com/sitemap.xml as the file you are checking and https://example.com/ as a page address you expect to see or not see, depending on the job. The note on the result says this is a sample crawl. A page that is three clicks from the homepage can be absent from both lists. Absence from this crawl is not proof the page does not exist. If the file is a sitemap index, child documents such as https://example.com/hidden-landing are fetched only when you supplied the index URL, only while the depth is within 2, and only until 20 child sitemap requests have been made. (Orphan Page Finder, guide 2.)

Orphan Page Finder shares one fetcher with the other sitemap tools. The fetcher allows http and https only. It rejects file, gopher, and data URLs, then blocks localhost, loopback, link-local, private ranges, CGNAT space, and the cloud metadata address before it opens a socket. DNS answers are checked before the connection, and a redirect is checked again. A redirect loop is reported instead of being followed forever. Three hops is the maximum. (Orphan Page Finder, guide 3.)

Large files are cut at 5 MB, and the stored page list stops at 5,000 URLs. Gzip responses and addresses that end in .gz are decompressed before parsing. A DOCTYPE or an entity declaration is rejected so the parser cannot expand an external entity. An HTML document or a Cloudflare challenge body is reported as not a sitemap. The raw response body is not written to the log. (Orphan Page Finder, guide 4.)

When a URL must be fetched, the page sends the job to the server and shows a short progress line while it polls. Small pastes return immediately with the same result shape: source URL, index or urlset, child sitemaps, page rows, errors, duplicates, redirect hops, status, truncated flag, and counts. Repeat fetches of the same normalized URL can reuse a finished parse for 10 minutes. Jobs sit in a file folder so more than one server process can see them, and they expire after 30 minutes. (Orphan Page Finder, guide 5.)

Calling the list a complete orphan report. Thirty pages cannot describe a large site. After you read that distinction, look at the severity of any finding. An error means the document or the fetch failed the check this page is responsible for. A warning, such as a duplicate loc or a truncated file, means the rest of the result is still usable. A note explains a cap, a paste that did not download child files, or a sample crawl. (Orphan Page Finder, guide 6.)

A concrete pass through Orphan Page Finder starts with https://example.com/sitemap.xml. If that address is an index whose first child is https://example.com/hidden-landing, the file list and the page list answer different questions. The page address https://example.com/ belongs in the page list only when a urlset contains it. Keep the two lists apart when you copy them into a spreadsheet or a ticket. (Orphan Page Finder, guide 7.)

The result panel uses the same dark block as the other tools on this site. Copy is there when a text result is useful. A download button appears only for a file this page actually builds, such as CSV, XLSX, XML, or llms.txt. Orphan Page Finder does not add a second title to the page, and it does not restyle the tools around it. (Orphan Page Finder, guide 8.)

Take Orphan Page Finder as one step. The next page in this set is Sitemap vs Crawl, which answers a different question about the same sitemap. Sitemap URL Extractor is the other close check. Finish the reading on this page before you switch, so you do not mix crawl URLs that are absent from the sitemap with a different report. (Orphan Page Finder, guide 9.)