Summary
- Separate discovery, crawling, indexing, and search presence. Internal links can help Google find URLs, but they don’t guarantee inclusion or visibility.
- Compare your important URLs with crawlable incoming links and crawl depth. Treat both as prioritization signals, not universal pass-or-fail thresholds.
- Fix weak paths with contextual links, verify the source and destination, then use Search Console URL Inspection on properties you control to compare indexed information with a live test.
Set the indexing scope for an internal links audit
Start by defining which important URLs need a reliable internal path, then separate link discovery from the later stages of indexing and search visibility. That keeps an internal links audit for Google indexing focused on a problem it can actually address.
A URL can be discovered when Google learns its address, crawled when Google fetches it, and indexed when Google stores it for possible use in search. Search presence is a separate question: an indexed URL is not necessarily shown for a particular query. Internal links can help with discovery and crawling, but they can’t guarantee indexing or a search result.
Make a working list of the URLs that matter to your site. Depending on the project, that might include core service or product pages, useful guides, and other pages you want people to find through search. Keep the list focused. A large inventory of low-value or intentionally excluded URLs can make it harder to spot a meaningful gap.
For each URL, record the intended destination and whether it is a priority for the audit. Include the preferred version of the page rather than treating every URL variant as equally important. If a URL redirects or another URL is intended to represent the content, note that before counting links; otherwise, your audit may celebrate links pointing to the wrong destination.
Also decide what the audit is meant to establish. A practical scope is: “Can Google follow a crawlable internal link from another page to each important URL?” That is narrower than “Will Google index everything?” and gives you a result you can verify.
Map internal links to find poorly connected URLs
Map links from pages on your site to your priority URLs, then use incoming-link counts and crawl depth to decide which paths need attention. These measures help you compare URLs; neither is a universal guarantee of discovery or indexing.
Run a crawl of the site and collect the internal links it finds. For each priority URL, look for the pages that link to it, the link destination, and the anchor text. A crawl-depth field can also help show how far a page sits from the crawler’s starting point. Internal Linking Audit With the SEO Spider describes checking crawl depth in a site crawl. The precise screens and reports depend on the crawler you use, so focus on the information rather than assuming every tool labels it the same way.
Compare the crawl results with your priority list. A page with no incoming internal links deserves a closer look. So does a page linked only from a remote or unrelated part of the site, or one that appears much deeper in the crawl than comparable pages. These are investigation signals, not proof that Google cannot find the URL. A crawler’s view of your site is a diagnostic sample, not a record of everything Google has discovered.
Use link context as well as counts. A link from a relevant page can help readers understand why the destination is useful. A large number of repeated links in navigation or a footer may inflate the count without making the page’s purpose any clearer. The question is not just “How many links point here?” but “Can a visitor and a crawler follow a sensible path to the intended page?”
Keep the source and destination visible in your audit notes. That makes the fix actionable: you can return to the source page, check the actual link, and verify that it leads to the right URL. If the crawl doesn’t show a link you know exists, check how the link is implemented before concluding that the page is unlinked.
Identify orphan pages and weak internal connections
Flag priority URLs that have no crawlable internal links, then review weak connections in context rather than applying a fixed link-count rule. An orphan page is a useful audit label for a page the crawl can’t reach through the internal links it found; it isn’t, by itself, proof that Google has never discovered or indexed that URL.
Start with the pages in your priority list that have zero incoming links in the crawl. Confirm that each URL is supposed to be part of the site and that the crawler included the relevant sections. Then inspect the page’s likely parent topics, category pages, and related resources to find appropriate places for links. If the destination is intentionally isolated or not meant for search, don’t add links just to make the report look cleaner.
Next, review pages with incoming links but weak connections. Consider whether the sources are relevant, whether the path to the page makes sense, and whether the destination is buried compared with similar important pages. Crawl depth helps identify candidates to inspect, but it does not create a universal cutoff. A deeper page may still have a clear, useful path; a shallow page may still be linked incorrectly.
There’s a real difference between Google’s guidance and some practitioner benchmarks. Google Search Central’s link best practices says pages you care about should have at least one internal link and warns there is no magical ideal number of links per page. A practitioner guide, Internal Link Audits Made Easy in 7 Steps , suggests at least five incoming links as a baseline. That five-link figure is a heuristic, not a Google requirement. Fixed click-depth limits are also heuristics, not proof that a page beyond a particular depth won’t be crawled or indexed.
For an audit, use the practical middle ground: make sure each important URL has at least one crawlable internal link, then use count and depth to prioritize pages that still look disconnected or awkward to reach. Don’t add irrelevant links simply to hit a target. Relevant links improve the path for both visitors and crawlers; a made-up threshold does not establish that Google will index the destination.
Check that internal links can lead Google to the right URL
Check the actual link markup and destination: Google generally parses an HTML anchor element with an href that resolves to a usable web address. A link that looks clickable to a person may not give a crawler the same clear route.
On the source page, inspect the link itself. Confirm that it is an <a> element with an href, and that the href points to the intended destination. Google’s link documentation
says Google can generally crawl links in that form. It also explains that links relying on other tags or script events without a usable anchor and href may not be parsed reliably. JavaScript can insert links dynamically, but the resulting markup still needs to use the crawlable anchor pattern.
Check the visible anchor text, too. It should make sense in the sentence or surrounding context and give readers a reasonable idea of what they’ll reach. Avoid relying on vague wording when the link could be described more clearly. Anchor text is not a substitute for a working link, but useful wording helps people understand the connection between the source and destination.
Then follow the link and confirm that it reaches the intended page. Check whether it lands on a different URL, redirects, or ends at a page that is unavailable. A link to an old URL may technically lead somewhere while still failing to take visitors to the page the source text promises. A 404 response means the requested URL was not found; it does not, by itself, prove that the URL is absent from Google’s index.
If a link appears in the browser but not in the crawl, inspect the rendered page or its markup to see whether the crawler can see a usable anchor and destination. If the source page links to a redirect or an unintended URL, update the link where appropriate and recrawl it. Keep the record of the original source and intended target so the verification is about the path you meant to fix—not merely whether some link exists.
Fix internal link gaps and verify each change
Fix a weak path by adding or correcting a contextual link on a relevant source page, then recrawl both source and destination to confirm the route works. The goal is a useful, crawlable connection—not a higher link count for its own sake.
For each priority URL with no suitable incoming link, choose a source page that naturally helps readers reach it. A related guide, category page, or overview may make sense if it gives the destination context. Add a link where it supports the reader’s next step. Avoid inserting links into unrelated copy simply to change an audit report.
Use an anchor element with a working href that points to the intended URL. Check the destination after making the change. If it leads somewhere unexpected, update the href rather than assuming the link is fixed because it is clickable. If the destination URL itself is not the page you intend people to use, resolve that separately before treating the internal-link gap as closed.
For a page that already has incoming links, decide whether the issue is relevance, clarity, or reachability. A better contextual link from an appropriate page may be more useful than adding several redundant links. If crawl depth made the page stand out, look for a sensible route from a more connected part of the site—but don’t treat a particular depth as a pass-or-fail rule.
After editing, crawl the source page again and confirm that the link appears as a crawlable anchor and points to the intended destination. Then check that the crawler can reach the destination through that link. Review the destination’s incoming links and depth again to see whether the path changed as intended. If the fix doesn’t appear, verify that the source edit was published and that the crawl included the changed page; don’t assume a report reflects an edit it hasn’t crawled.
This verification closes the internal-links part of the audit. It does not establish that Google has crawled or indexed the destination. Keep those outcomes separate in your notes so a working site path isn’t mistaken for proof of search visibility.
Recheck internal-link discovery and indexing in Search Console
Use Search Console URL Inspection on a property you control to compare Google’s indexed information for a URL with a live test of its current page. These views answer different questions: neither a successful live test nor an indexing request proves that the URL has entered Google’s index.
Enter the fully qualified URL in the URL Inspection field for the relevant Search Console property. The property must include that URL, and you can inspect only properties you control. The indexed information describes the version Google most recently indexed; it is not a live reading of what is on the page now. If the page has changed since Google last saw it, the report may not reflect the current version.
Use the live test when you need to check the page as it is currently available to Google. It’s a diagnostic check, not proof that Google has indexed the page. Google’s URL Inspection documentation explains both the indexed-version report and live test, and states that an indexing request does not guarantee inclusion.
When you review discovery and referring-page information, use it as a clue about how Google may have found the URL. A referring-page field may be absent even when a referring page exists, so don’t treat a blank field as conclusive proof that your internal links aren’t working. Pair what Search Console shows with your site crawl and the link verification you performed. URL Inspection also doesn’t test every condition that may affect appearance in Google, including all quality, security, or removal-related issues.
Here’s a hypothetical case. Assume /guides/internal-link-audit-example/ is an important guide on a site you control, and a site crawl finds no crawlable internal link to it. First, inspect likely related pages and add a contextual anchor with a working href to the guide. Recrawl the source page and confirm the destination is reachable through that link. Then inspect the guide in the correct Search Console property. If indexed information still reflects an earlier version, compare it with the live test; if the live test can access the current page, that still does not establish indexing. Review discovery or referring-page details where available, then check URL Inspection again later as part of follow-up. Don’t infer a guaranteed outcome from the request or from the link fix.
The internal links indexing checklist is straightforward: identify the important URLs, find pages that link to them, check crawlable markup and destination, correct relevant gaps, recrawl, and use URL Inspection to distinguish Google’s indexed view from the current page. That gives you a verified internal path and a clearer diagnosis without confusing discovery with indexing.
Article updated on October 6, 2026.