How to Trace an Orphan URL to the Internal Links It Needs

Tracing an orphan URL back to the internal pages that should expose it takes more than finding the URL in a crawl report. A crawl can show that it wasn’t reached through links during that crawl. Screaming Frog’s Orphan Pages report also has a “Source” column, but that identifies the source of discovery—such as GA, GSC, or Sitemaps—not the internal page linking to the target. Treat those as separate tasks: establish what the crawl says, compare the URL with other known site URLs, and name a linking page only when your evidence identifies that page and its link to the target.

Summary

• “Orphan” can mean a page with no inbound internal links or a URL that a particular crawl didn’t discover through internal links. Those descriptions aren’t interchangeable.
• A blank crawl depth is evidence about that crawl, not proof that no page on the site links to the URL. Sitemap, Search Console, analytics, and log records can surface URLs or activity; Screaming Frog’s report labels the source of discovery, which is not necessarily a page linking to the target.
• To report a confirmed internal-link source, identify the internal page and the link to the target. If the page is worth keeping, a contextual link from a relevant, already-linked page is a supported next step; adding it and verifying it are separate actions.

Define what “orphan” means for the URL you’re tracing

Start by deciding whether you’re investigating a lack of inbound internal links or a URL that one crawl didn’t reach. The word “orphan” is used for both, and the evidence needed to support each description differs.

Conductor defines an orphan page as an indexable page with no inbound internal links. That definition concerns whether any page on the site links to the target. Screaming Frog describes identifying URLs that cannot be found by crawling internal links and says URLs not discovered naturally through internal links during a crawl have no crawl depth. That description concerns what happened in a particular crawl.

These meanings shouldn’t be treated as a universal test. A blank crawl depth may show that the crawler didn’t reach a URL through links during that crawl; it doesn’t, on its own, establish that no internal page links to it. Conversely, finding a link between two pages doesn’t tell you whether the crawler discovered the target in a particular run.

Keep “not found through internal links” separate from “not indexable,” too. Conductor’s article discusses indexability and later explains that a sitemap or other references can make an orphan URL discoverable, without guaranteeing that it will be indexed. A URL’s presence in a sitemap or another source therefore isn’t evidence of an internal link, and discovery isn’t the same as indexing.

Before tracing, write down which claim you need to establish. If the question is whether a particular crawl reached the URL, interpret that crawl’s findings. If the question is whether any internal page links to it, you need evidence about those source pages. If the available report answers only the first question, don’t stretch it into an answer to the second.

Use crawl evidence to identify an orphan URL—not its linking pages

A crawl report can help you decide whether the URL was reached through internal links in that crawl. It doesn’t necessarily identify pages linking to the target, so treat the crawl finding as a candidate for further investigation rather than a complete trace.

Screaming Frog says that URLs not discovered naturally through internal links during a crawl have no crawl depth. Within that crawl, a blank crawl depth is a clue that the crawler didn’t find the URL by following internal links. Its scope is important: the finding describes the crawl, not a complete inventory of every link that may exist on the site.

Check the URL’s reported condition before drawing conclusions about what to do next. A blank crawl depth means the URL wasn’t discovered naturally through internal links during that crawl; it doesn’t establish whether the URL currently returns a successful response, errors, or redirects. Treat the crawl finding as evidence about discovery, and assess the URL’s condition separately before deciding whether it needs a link.

For each candidate, keep the crawl finding precise: for example, “this URL had no crawl depth in this crawl.” Avoid turning it into “no internal page links to this URL” unless you have evidence that supports that broader claim.

And don’t mistake a list of candidate URLs for a list of linking pages. Screaming Frog’s Orphan Pages report can export a combined list of discovered orphan URLs, and its “Source” column identifies their discovery source, such as GA, GSC, or Sitemaps. That column names where the URL was found, not necessarily an internal page linking to it. If your task is to name those pages, keep the discovery record separate from evidence identifying a link source.

Compare the orphan URL with known site URLs to narrow the investigation

Compare the crawl with other known URL records before treating an absent URL as a confirmed orphan. A crawl shows what its crawler can reach by following links; it isn’t necessarily a complete inventory of the site’s URLs.

Search Atlas recommends cross-referencing a site crawl with known URLs because a crawl alone shows only pages the crawler can reach by following links. That comparison helps identify URLs that may exist but weren’t reached in the crawl. It narrows the investigation; it doesn’t establish which internal page, if any, links to each candidate.

Think of the two sets of information as answering different questions. The crawl provides evidence about pages reached by following links in that crawl. Other URL records may reveal pages the crawl didn’t reach. If a URL appears in a known-URL source but not among the pages reached in the crawl, that difference tells you the crawl and the other record don’t cover the same set. It doesn’t tell you why they differ or prove there are no links to the URL.

This comparison is useful when you’re deciding which candidates need attention. A URL present in another record can be added to the investigation even if the crawl didn’t reach it. A URL absent from a crawl shouldn’t be discarded just because it wasn’t discovered there. At the same time, don’t treat appearance in a second source as proof of internal linking: the source may establish that a URL is recorded or discovered, not that another page on the site links to it.

The distinction matters when reporting results. You can say that a URL was present in a known-URL source but not reached in a particular crawl, if that’s what your records show. You can’t infer from that mismatch alone whether the page has no inbound internal links, whether the crawl missed an available path, or which page should link to it. The comparison identifies candidates; confirm a linking source by identifying the internal page and its link to the target.

Use sitemap, Search Console, analytics, and logs as discovery clues

Use sitemap, Search Console, analytics, and log records to find or assess candidate URLs and activity. Screaming Frog describes using sitemap, analytics, and Search Console data to find orphan URLs; Search Atlas describes indexing reports, logs, and analytics for the different checks outlined below. Keep those discovery and activity observations distinct from evidence identifying an internal page that links to a target.

Screaming Frog describes finding orphan URLs through sitemap, analytics, and Search Console data. Its examples include URLs listed in an XML sitemap that error or redirect, and pages found through Search Console data that exist but aren’t linked internally in the crawl. The key distinction is that such records can surface URLs that deserve review; appearing in one doesn’t, by itself, show that a site page contains a link to the URL.

Search Atlas describes using Search Console indexing reports to examine which URLs are indexed, discovered but not indexed, or excluded, along with the reported reasons. It also names server logs as a way to investigate whether crawlers visited a URL, and analytics as a secondary way to find pages with organic sessions but no traffic arriving from internal site links. These clues answer different questions: indexing reports concern reported indexing states, logs concern recorded crawler visits, and analytics can help flag pages for review. Those observations, as described here, do not themselves name an internal page containing a link to a particular target.

Keep a record of what each source actually tells you. For instance, a URL in a sitemap is evidence that it appears there; a crawler visit in logs is evidence of that recorded visit; and a Search Console status is evidence of the status shown for the URL. Don’t turn any of those observations into a claim about an internal link unless the evidence also identifies the linking page.

This approach avoids confusing existence, discovery, crawling, and linking. A URL can be known to one source without being reached in a crawl, and a crawl or visit doesn’t necessarily establish that a user-facing internal link exists. The sources described above can help you choose what to investigate; keep their URL, indexing, and activity observations separate from evidence naming a page that links to the target.

Confirm which internal pages link to the orphan URL

Call the trace confirmed only when your evidence identifies the internal page or pages linking to the target. A crawl result that names the target but not its linking pages doesn’t complete that task.

The distinction is simple but easy to lose in a report. The target URL is the page you want to reach. A source page is an internal page containing a link to that target. Evidence that the target exists, appears in a sitemap, has a crawl record, or was visited doesn’t identify a source page. Nor does a blank crawl depth tell you which pages might link to it; it says the URL wasn’t discovered naturally through internal links in that crawl.

For a complete trace, the evidence needs to connect the two: it must name an internal source page and establish that the page links to the target URL. Screaming Frog’s Orphan Pages report identifies the source of discovery for a candidate URL, such as GA, GSC, or Sitemaps; that field is not itself the internal page linking to the target. Keep candidate-discovery records distinct from evidence that identifies the source page and link.

So don’t fill that gap with a guess based on topic, site section, or likely navigation. A page that seems like a sensible place to add a link isn’t evidence that it already contains one. Likewise, don’t report a guessed page as the source simply because it appears related to the target.

If the available evidence doesn’t name the source page, label the trace incomplete. You can still report what is known—for example, that the URL appeared in a particular record or had no crawl depth in a crawl—but keep that observation separate from a claim that no internal page links to it. This gives the reader a useful finding without claiming more than the evidence supports.

Turn a confirmed internal-link gap into a supported next step

If the page is worth keeping and the evidence supports an internal-link gap, a contextual link from a relevant, already-linked page is a supported next step. Treat adding that link and verifying it as separate actions.

Search Atlas recommends giving a page worth keeping a contextual internal link from a relevant page that is already linked into the site. That recommendation gives the link a clear purpose for readers as well as placing the target in the site’s internal structure. It doesn’t mean every candidate URL should receive a link: first decide whether the page is worth keeping. Conductor advises checking the value of a page that no longer serves a purpose; if it has no value, remove it, and if it does, redirect it to the most relevant alternative page.

Choose a source page because its context makes the target useful there, not just because it could technically contain a link. The recommendation is to use a relevant, already-linked page; choosing a particular page and anchor text for a target requires a judgment about that site’s content. Don’t present a hypothetical source page as one that has been confirmed to link to the URL.

After adding a link, don’t claim that the URL is now exposed through internal links unless you have evidence of the completed change. The recommended action and its verification are different things. Verify the change with evidence that identifies the source page and target; until then, report the link as added but not confirmed.

A careful final report can therefore separate three outcomes: the URL was identified as a candidate; a relevant internal link was added, if that was the chosen fix; and the new link has or has not been verified with evidence that identifies the source page and target. If verification evidence is unavailable, report the change without claiming the trace is confirmed. That keeps the conclusion aligned with what the records actually show.

Updated November 7, 2026.