Crawlable internal links

Definition: Crawlable internal links connect pages within the same website using a format from which a crawler can extract a destination web address and request it.

Key facts

• As of October 2026, Google's link best practices recommend an HTML anchor element, written <a>, with an href attribute that identifies the destination address.
• Google's JavaScript SEO documentation describes extracting links from both the initial HTML response and the HTML produced after JavaScript runs.
• Search Console's URL Inspection documentation identifies separate fields for permission to crawl a page and the outcome of fetching it: Crawl allowed? and Page fetch.

What markup makes an internal link crawlable?

The href attribute supplies the address that the crawler can request. Google's link guidance accepts relative addresses, including paths beginning with /. These examples follow that format:

<a href="/products">Our products</a>
<a href="/services">Our services</a>

Google treats script-only anchors and a span used as a link as less reliable formats for extracting URLs. An anchor can include both href and a click handler.

How does JavaScript affect link extraction?

Rendering is the process of running page code to produce the HTML available after JavaScript executes. Google's JavaScript SEO guide describes an initial extraction of URLs from href attributes, followed by another extraction from rendered HTML. Links inserted by JavaScript can therefore be processed when they produce the required anchor markup.

For applications that load different page views, the guide recommends the History API, the browser interface for updating navigation history, instead of fragment-based routes such as #/products. Its example uses /products and /services in ordinary anchors.

The guide also recommends server-side rendering or pre-rendering because some bots cannot execute JavaScript. Providing links in the initial HTML makes them available to those crawlers.

How can the links be checked?

The page containing the links is the starting point. Google's URL Inspection tool accepts a complete URL within the selected Search Console property. Test live URL checks the current page; View tested page exposes additional data, including HTML, loaded resources and JavaScript console output.

Inspecting the HTML for the expected anchor and destination tests the markup requirement. For the destination page, Crawl allowed? reports whether a robots.txt rule permits Google's crawl, while Page fetch reports whether Google retrieves the page successfully. These checks address both link extraction and access to the linked address.

Related terms

• JavaScript rendering and AI crawlers
• Rendered DOM
• robots.txt
• Googlebot

FAQ

Does every important page need an internal link?

Google's internal linking guidance recommends that each page that matters has a link from at least one other page on the site. You can use that criterion when reviewing important destination pages.

Can I rely on a menu that works when clicked?

Check whether its links contain an href with a web address. Google's link examples distinguish anchors with that attribute from navigation implemented only through script events.

Where should I look for links added by JavaScript?

Inspect the rendered HTML. Google's JavaScript documentation describes extracting links again after rendering, so you can check whether the expected anchors appear at that stage.

Sources

1. Google Search Central, "Link best practices for Google", updated 10 December 2025
2. Google Search Central, "Understand the JavaScript SEO basics", updated 4 March 2026
3. Google Search Console Help, "URL Inspection tool", accessed 17 October 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer