---
title: "Comment by Jonas on \"JavaScript Links Can Hide Content From AI Crawlers, a 41-Day Test Shows\" | Hashnode"
description: "This is a good example of why “it works in the browser” is not enough. If the important navigation only appears after JS runs, some crawlers never really see th"
url: "https://hashnode.com/posts/javascript-links-ai-crawlers-41-day-test/6a87a6b43dca225165d44806/comment/6ab11fe656811492e977bcd7"
---

[Discussion](https://hashnode.com/posts/javascript-links-ai-crawlers-41-day-test/6a87a6b43dca225165d44806)

Comment [JavaScript Links Can Hide Content From AI Crawlers, a 41-Day Test Shows](https://hashnode.com/posts/javascript-links-ai-crawlers-41-day-test/6a87a6b43dca225165d44806)

[Jonas](https://hashnode.com/@jonasb)

[Sep 21](https://hashnode.com/posts/javascript-links-ai-crawlers-41-day-test/6a87a6b43dca225165d44806/comment/6ab11fe656811492e977bcd7)

This is a good example of why “it works in the browser” is not enough. If the important navigation only appears after JS runs, some crawlers never really see the site structure at all. For category, docs and product trees I’d still want the important links in the first HTML response. We check this kind of crawler-facing HTML in Prerender Buddy as well, because it is very easy to miss from the normal rendered page.
