Expertise

Mapping a Page’s Internal Links and Rechecking Weak Routes

The guide explains how to map internal links to a target page, identify weak routes in a bounded crawl, choose relevant fixes, and recheck what the sample…

Mapping a Page’s Internal Links and Rechecking Weak Routes
Contents

Mapping a page’s internal links means tracing which pages on the same site link to it, what those links say, and how many followed links separate the page from your crawl’s starting point. To recheck a weak route, keep the target URL exact, record the crawl’s scope, and compare the same details after any link change. That tells you what the crawl found; it doesn’t, by itself, establish whether the target is indexed.

Summary

A reliable internal-link map starts with a public URL, an exact target URL, and a record of what the crawl included. If you want to compare the crawl with a known set of pages, add a same-host sitemap or URL list.

Read the results as a route, not just a link count: note distinct source pages, anchor text, repeated layout links, and the target’s reported depth and crawl status.

When a route looks weak, check the crawl scope and known URL inventory before changing the site. If you do add a relevant contextual link, rerun the crawl and compare the route; treat index status as a separate question.

Set the crawl’s starting point and define the page you’re tracing

Start with a public URL on the same site as your target, then enter the target’s full URL exactly as it appears in your page inventory. The starting point determines which same-host links the crawl can follow, so record it rather than relying on memory.

Use the Internal Link Analyzer to submit a public starting URL. It follows same-host links found in returned HTML and crawls up to 100 HTML pages. If the starting URL redirects, the crawl stays on the final hostname. If you want to compare discovered pages with URLs you already know about, you can also provide a same-host sitemap or URL list; the comparison can include up to 1,000 URLs, but those inventory URLs don’t seed the crawl.

1

Choose a public starting URL on the target’s host, such as the homepage or a relevant section page. Record the exact starting URL.

Enter the target URL exactly, including its path and any relevant URL variation. Use the same version when you locate the target in the results.

Decide whether to add a same-host sitemap or URL list. Add one when you need to compare the crawl with known URLs, and record that choice.

Before interpreting the report, write down the starting URL, the target URL, whether you supplied an inventory, and the crawl cap shown for the run.

The exact target matters because a report about one URL doesn’t automatically describe another version of the page. If your inventory and the target use different URL forms, first make sure you’re comparing the intended page rather than treating two entries as interchangeable.

A useful record is brief: starting URL, target URL, inventory source if used, and crawl cap. Those details let you interpret a later run against the same scope, or explain why two reports may not be directly comparable.

To map the target’s route, open its details in the crawl report and list the distinct pages that link to it. Then record the anchor text and identify whether each link appears in page content or in a repeated layout area.

The Internal Link Analyzer reports source pages, targets, anchor text, and inbound counts. Its guidance distinguishes repeated navigation occurrences from separate source pages and from in-content links. That distinction changes what a count means: repeated links in a menu are not the same as links from several different articles.

Internal links connect one page to another page on the same site. Descriptive anchor text can also give readers and search engines context about the destination, as explained in Internal Linking for SEO: A Complete Guide for 2022.

Use a simple route map rather than relying on the inbound total alone:

  1. Find the exact target URL in the page table and open its details.
  2. Make one row for each distinct source page that links to it.
  3. Record the anchor text and where it appears: in the page body or in a repeated area such as a menu, sidebar, or footer.
  4. Note repeated link occurrences separately, so they don’t look like additional source pages.
  5. Arrange the source pages into a readable list or diagram, keeping the target at the end of each route.

For example, a route map might show a section page and a related article as two distinct sources, even if the section page repeats its link in the site layout. The map helps you see which pages provide a path to the target and whether the link tells a reader what they’ll find by following it.

Read crawl depth without treating it as an indexing verdict

Use the reported depth to describe how far the target is from the crawl’s starting URL in this run, and check separately whether the crawl fetched the target. Depth describes a path found through followed links; it isn’t an index-status label.

Reported depthMeaning in the crawl
0The URL is the starting point.
1The URL was found directly from the starting URL.
Higher than 1Each higher value adds another followed link along the route found.
-1The URL was discovered but not crawled before a limit, timeout, skip rule, or fetch failure.

Read the target’s depth alongside its individual crawl outcome. If it has a numbered depth, note that path length and whether the report lists it as crawled. If its depth is -1, record that it was discovered but not fetched in the crawl; don’t describe that as a completed page inspection.

A depth value can help you compare routes within your report, but don’t turn it into a universal ranking or indexing threshold. The analyzer describes depth as a navigation clue, not a universal ranking cutoff. Instead, state what the report actually shows: the starting URL, the target’s depth, and whether the target was crawled.

That wording keeps the finding useful without stretching it. “The target was discovered at depth 3 in this run” describes the report. It does not say whether a search engine has indexed the page.

RelatedHow to Trace an Orphan URL to the Internal Links It Needs→

Decide whether a weak route needs attention

A weak route is a reason to inspect the links and crawl scope, not an automatic instruction to change the site. First decide whether the report shows no inbound link in its sample, a small set of distinct source pages, or a route that is several followed links from the start.

ℹ️
Note
The crawl is bounded: it follows same-host links in returned HTML and crawls up to 100 HTML pages. It may miss pages beyond that limit, JavaScript-only links, other hostnames, and URLs it never discovers through links. A sitemap or URL list helps compare known same-host URLs with the crawl, but inventory URLs don’t seed it. A zero-inbound result is a candidate within the sample, not proof that the page has no internal link anywhere on the site.

Use the report and inventory together:

  1. If the target has zero inbound links in the report, mark it as an unlinked candidate in that sample. Check whether the target appears in the sitemap or URL list you supplied.
  2. If the target has inbound links, count distinct source pages separately from repeated occurrences. Record the anchors and the target’s depth.
  3. If the target appears in the inventory but not among crawled pages, check whether the run’s page cap or other recorded scope could explain the difference.
  4. Choose a response only after reviewing those details. If a relevant source page exists, consider a contextual link; if the apparent gap comes from scope, refine the next comparison before concluding that the page lacks a route.

An orphan page is one with no internal links pointing to it, but a zero-inbound report result alone doesn’t establish that the page is a site-wide orphan. A known URL list makes the comparison more informative; it doesn’t make the crawl exhaustive. Keep your conclusion tied to the evidence: “no inbound links found in this crawl” is more precise than “no internal links exist.”

If a related page can naturally help readers reach the target, add or improve a contextual link from that page and use anchor text that describes the destination. A link should make sense in its surrounding content, not just exist to change a count.

The sources describe contextual links as links embedded in body content between related pages, with descriptive anchors helping explain what the destination is about. Navigation links serve a different purpose: they appear in areas such as menus, sidebars, and footers to help people move around the site. Your Internal Linking Blueprint For Better SEO describes those layout links alongside contextual links.

1

Choose a source page that is relevant to the target’s subject and useful to someone reading that page. Use the source-page list from your route map to identify candidates.

Add or revise a contextual link where it fits the source page’s content. Write anchor text that describes the destination rather than using wording that gives no clue where the link goes.

Check the link in the page content and confirm that its destination is the exact target URL you intend to connect.

Record the source page, anchor text, and target URL so you can compare them with the next crawl.

A navigation link may be appropriate when the destination belongs in the site’s wider structure, but don’t treat a repeated menu or footer link as equivalent to several independent in-content routes. Consider what the page is for and how readers would use the link.

If you can’t identify a relevant source page, don’t add an unrelated link just to increase the inbound count. The useful outcome is a clearer path between related pages, not a larger number detached from context.

Recheck the route and keep discovery separate from index status

After changing a link, rerun the crawl with the starting URL and scope recorded, then compare the target’s source pages, anchors, depth, and crawl outcome with your earlier map. That comparison shows whether the route changed in the crawl; it doesn’t settle whether the target is indexed.

For a meaningful comparison, keep the target URL exact and note any differences in the start URL, inventory, or crawl cap. The analyzer recommends recording the crawl date, starting URL, and cap. Its report includes linking pages, anchors, and depth, which gives you specific fields to compare rather than a vague impression that the page is “more connected.”

  1. Run the crawl again after the link change, using the recorded start URL and scope where possible.
  2. Find the exact target URL in the new report and open its details.
  3. Compare the distinct inbound source pages with the earlier map. Check whether the intended source page appears.
  4. Compare the anchor text and depth, and confirm whether the target was crawled or only discovered.
  5. Record whether the route changed in this crawl. If the intended link is absent, review the source page, destination URL, and crawl scope before deciding what to adjust.

Hypothetical example: Assume the target is /guides/internal-links/, and the first report shows zero inbound links in the sample. That is an assumed input, not a performed test or a finding about a real site. If the sitemap or URL list contains the target, or the crawl scope may account for the missing route, review those details before choosing a relevant source page. If you add a contextual link, rerun the crawl and check whether that source page and its anchor appear in the target’s details.

Keep the conclusion bounded: a changed source list or depth means the report found a different route. The supplied sources don’t give a specific procedure for verifying whether a URL is indexed, so don’t use the link crawl as a substitute for that separate check.

Last content update: November 15, 2026.

Sources