SEO Questions

Do Javascript Links Pass Link Equity?

By BacklinkPrice Team · Nov 18, 2026 · Updated Nov 20, 2026 · 8 min read
Illustrated cover for Do Javascript Links Pass Link Equity?

JavaScript links pass link equity when they render as real <a href> links. Links that exist only as click handlers pass nothing.

Yes, JavaScript links can pass link equity, but only when Google can find them as real links after rendering. A link that JavaScript builds into a normal <a href> element can pass value, while a click handler on a <div> or <span> passes none. The gap is discovery, not the script itself.

Key takeaways

  • Google can only crawl a link reliably when it is an <a> element with an href attribute, so a JavaScript link must end up as that markup (Google Search Central, 2026).
  • Google finds JavaScript-injected links after rendering, but slower: Onely's November 2022 test took 313 hours to reach the last JavaScript-linked page, against 36 hours for HTML links.
  • In Search Engine Land's August 2026 test, GPTBot and ClaudeBot crawled all 748 HTML-linked pages and none of the 293 JavaScript-linked pages.
  • A link with rel="nofollow", rel="sponsored", or rel="ugc" is a hint, and Google generally does not count it for ranking (Google, 2019).
  • Server-side rendering puts key links in the first HTML response, so Google and AI crawlers can find them without waiting for JavaScript.

Link equity is the ranking value one page passes to another through a link. It comes from the linking page's own standing, and it helps the destination page rank for related topics. Backlinks are the most common way this value moves between sites, and internal links move it between pages on the same site.

Equity only moves when a crawler can find and follow the link. A link that no crawler sees passes nothing, no matter how strong the linking page is.

Most pages earn little traffic. Ahrefs' 2024 list of Google search statistics reports that 96.55% of all pages get zero search traffic from Google, and that 94.74% of keywords get 10 monthly searches or fewer.

Google says a JavaScript link can pass equity when it becomes a real HTML link after rendering. Google Search Central states that Google can only crawl a link reliably when it is an <a> element with an href attribute, and most other formats will not be parsed.

Google's May 2020 FAQ on JavaScript and links gives the same answer. It says JavaScript-injected links are fine as long as they meet the crawlable-link rules, and Googlebot finds them when it renders the page. Links in the first server response are found a bit faster, because discovery happens before and after JavaScript runs.

Googlebot has run JavaScript with an evergreen Chromium browser since May 2019.

Anchor text also needs to survive rendering. Google says to place anchor text between <a> elements that Google can crawl, and to check the rendered HTML when JavaScript inserts that text. Descriptive anchor text tells Google what the linked page is about.

Google's crawlable-link page shows which patterns work:

  • Google can parse <a href="/products"> with an onclick handler added, because the href is still there.
  • Google cannot reliably parse <a onclick="goto('https://example.com')">, because there is no href to read.
  • Google cannot reliably parse <span href="https://example.com"> or <div href="https://example.com">, because neither tag is a link.
  • Google may still attempt to resolve <a href="javascript:goTo('products')">, but the page lists it as not recommended.

What studies and tests show

Tests agree: JavaScript links work for Google, but they are found later, and most AI crawlers do not find them at all.

Onely ran the clearest Google test in November 2022, with two chains of 7 pages each. Google took 313 hours to reach the last JavaScript-linked page, against 36 hours for the HTML chain, a ratio of about 8.7 to 1. Even the first JavaScript-injected link took 52 hours to follow, against 25 hours for its HTML match.

Search Engine Land published a 41-day test on August 19, 2026, on a site with 1,062 hierarchy pages. The test split them into 748 HTML-linked pages and 293 JavaScript-linked pages. GPTBot crawled all 748 HTML-linked pages and none of the JavaScript-linked ones, and ClaudeBot showed the same split.

Googlebot reached only 7 of the 293 JavaScript-linked pages, or 2%, against 35 of the 748 HTML-linked pages, or 5%. Six of the 10 JavaScript sections got no Googlebot hierarchy crawl at all in 27 days.

A December 2024 study by Vercel and MERJ, reported by Onely, found that none of the major AI crawlers render JavaScript. ChatGPT's crawlers downloaded JavaScript files in 11.50% of requests and Claude's in 23.84%, but neither ran them.

Fixing the links changed the result fast for AI crawlers. After the JavaScript links became plain HTML, GPTBot picked up 250 pages it had never crawled, in one sweep lasting under 3 hours and within 2 days.

Google has said the typical render wait is short: Martin Splitt said in November 2019 that the median time between crawling and rendering was 5 seconds.

CrawlerHTML-linked pages crawledJavaScript-linked pages crawled
Googlebot35 of 748 (5%)7 of 293 (2%)
GoogleOther495 of 748 (66%)142 of 293 (48%)
GPTBot748 of 7480 of 293
ClaudeBot748 of 7480 of 293
Bingbot282 of 7483 of 293

A JavaScript link passes equity when the rendered page holds a plain <a href> that points to a working address, and it passes none when no such link exists. The test is what the rendered HTML holds, not what a visitor sees in the browser.

A link passes equity when it meets these tests:

  • The script writes a normal <a href> into the page, with descriptive text between the tags.
  • The page is server-side rendered, so the link is in the HTML the server sends.
  • The href resolves to a real address, not a fragment that loads new content.
  • The link is a plain dofollow link, with no rel value that asks Google not to count it.

Click handlers fail the test. Screaming Frog's guide lists <span href>, <div href>, <a onclick> with no href, and <a href="javascript:goTo('products')"> as uncrawlable link types. Google's own list matches.

Qualifiers change the result even for a real link. Google's September 10, 2019 post introduced rel="sponsored" and rel="ugc", and moved all three values, with nofollow, to a hint model. Nofollow became a hint for crawling and indexing on March 1, 2020.

Google says it will generally still not consider such links for ranking, so a nofollowed JavaScript link rarely passes equity. The difference between dofollow and nofollow links decides whether equity is asked to flow at all.

A script that errors out before the link is built leaves the same gap: the rendered page holds no link. Keep the scripts that build key links small, fast, and free of errors.

What to do in practice

Put your key links in the HTML the server sends, and use JavaScript only to improve the page after that.

  • Render navigation, breadcrumbs, and in-content links on the server, or pre-render them at build time, so they exist before any script runs.
  • Write every link as <a href> with a real address and descriptive text, and keep click handlers as an extra, not as the link itself.
  • Compare the raw source with the rendered page after each deploy, and treat any link that appears only after rendering as a risk.
  • Check key pages with the URL Inspection tool in Google Search Console and confirm the links show in the rendered HTML Google kept.
  • Do not block JavaScript files in robots.txt, and fix script errors that stop links from being built.

Measure the fix by watching discovery, not by clicking the page yourself. A browser runs every script at once, so it hides the gap.

Common mistakes

  • Using a <div> or <span> with a click handler as the only route to a page, so crawlers never see a link at all.
  • Hiding key links behind a tab, filter, or menu that only appears after an action, so the rendered page may not hold them.
  • Counting GoogleOther crawls as search coverage, when Googlebot, the crawler that builds the index, reached only 2% of JavaScript-linked pages in the 2026 test.
  • Marking every JavaScript link nofollow to shape equity, which asks Google not to count links you actually want to pass value.
  • Buying links meant to pass ranking credit, because Google treats unqualified paid links as a link scheme and can hurt your SEO.

Frequently Asked Questions

Yes, when Google renders them into real <a href> links. Google treats a rendered link like a normal link, so it can pass PageRank and anchor text. A click handler with no href passes neither, because Google does not treat it as a link at all.

Yes, Googlebot renders JavaScript with an evergreen Chromium browser and finds links in the rendered HTML. Discovery can happen before and after rendering, so links in the first HTML response are found faster. Other crawlers may not render at all.

Mostly no. In the August 2026 test, GPTBot and ClaudeBot found none of the 293 JavaScript-linked pages, while Googlebot found 2%. If a page must appear in AI answers, its links need to be in the plain HTML the server sends.

Very little for rankings. Google treats nofollow as a hint and generally does not count it for ranking, a rule in place since September 2019. The link may still help a crawler find the page, but it rarely passes equity.

Compare the raw HTML source with the rendered page, then run the URL Inspection tool in Google Search Console. If a link appears only after rendering, move it into the server HTML. Re-check after each deploy, because a code change can hide links again.

Sources

If you want help earning links that Google can find, see our pricing page.

BacklinkPrice Team
Written by
BacklinkPrice Team
Link building and backlink pricing research

The BacklinkPrice Team researches backlink prices, publisher sites and link building tools. We check prices and plans against each provider's own pages and date them, so you know how current the numbers are.

More from BacklinkPrice Team

Related guides