JavaScript Links Can Make Your Pages Invisible to AI Search

" Google renders JavaScript " has been the standard answer to client side rendering concerns for years, and it got easier to believe in 2019, when Googlebot went evergreen, continuously running on the latest version of Chromium. The increasing flow of search traffic through AI assistants renders that wisdom incomplete because the crawlers for AI assistants behave nothing like Googlebot.

To get numbers rather than assumptions about what that means for JavaScript links, I ran a controlled experiment. I set up one site with half its internal links hard coded in HTML and the other half injected by JavaScript (JS).

How the experiment worked

The test site is a Brazilian business classification directory with roughly 2,400 pages, a project I own and operate. The experiment ran on the site's hierarchy: 21 top level sections branching into divisions, groups, and classes, 1,062. Local visibility depends on whether the details across pages, profiles, categories, reviews, photos, and service descriptions reinforce the same answer for a specific location based query.

The operational question is whether the public business data is complete enough to support the query. Hours, categories, services, reviews, photos, and page content need to reinforce each other so Google can understand the business in a specific situation, not only as a generic listing.

Phase 1: Crawlers arrive as the test begins

Crawlers arrived fast and crawled hard for the first 72 hours. GPTBot swept the site within hours of deployment and crawled all 759 pages of the HTML group on day one, all the way down to class level. In the JS group, it hit all 10 section. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

The practical value is in connecting the idea to an observable signal. That means deciding what should be checked, what would prove the issue is real, and where the team should make the smallest useful improvement first.

Only Google executed the JavaScript

The full scorecard at the end of Phase 1, after 27 days, displays counts covering hierarchy pages only (division level and deeper), where a JS group hit is unambiguous proof of JavaScript execution. One sizing note: The HTML sections hold. The practical question is what this changes in the system: the page structure, the evidence presented, the measurement habit, or the way the topic is connected to related work.

Even Google barely touched the JavaScript pages

The two Google rows are doing very different jobs, and the difference matters more than the raw counts. Google's crawler stack, GoogleOther, passed the rendering test. Googlebot, the crawler that feeds Search, mostly sat it out. This means. The practical read is that brand signals need to be consistent enough for both people and AI systems to form a stable view of the company, its expertise, and its trust signals.

The useful check is whether this improves the system behind search performance, not only the words on the page. Internal links, crawlable content, clear entities, current evidence, and a sensible page structure all help the recommendation become easier to trust.

All other crawlers ignored the JavaScript group

My middleware initially lumped Meta ExternalAgent and Amazonbot into a generic "unknown bot" bucket, but splitting the logs by user agent revealed them as two of the heaviest crawlers on the site, with roughly 2,000 hits each. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

The risk is usually hidden in the execution layer. A page can look fine to a human and still fail for an automated visitor if the form, call to action, rendering path, or confirmation step is not accessible enough for the agent to complete the task.

Something odd happened with Bingbot

Bingbot did reach three JS group hierarchy pages on days 26 and 27, after three weeks of daily recrawls that never went past the section level. However, the crawl pattern points to discovery through another path rather than JavaScript. The practical question is what this changes in the system: the page structure, the evidence presented, the measurement habit, or the way the topic is connected to related work.

User requests from AI could not reach JavaScript links

ChatGPT User deserves attention because it represents real user demand. This is the agent that fetches pages when someone asks ChatGPT a question. During the experiment, real user queries pulled it to dozens of HTML linked pages. Pages. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

Crawl logs don't reveal indexing

Everything above is discovery, not indexing. A page can be crawled and still not make it into the index, and indexing determines whether the page shows up in Search at all. Server logs are the right tool for proving what a crawler could. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

Phase 2: Not all crawlers passed the recovery test

After 27 days, I converted all JavaScript links to hard coded HTML and watched what happened. Nothing about the pages themselves changed here. The URLs, the content, and the server were identical to Phase 1. The one thing I touched was the. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

Some crawlers were quick to catch up

GPTBot responded within two days. It swept every formerly blocked section in a single sweep lasting under three hours and picked up 250 pages it had never crawled before, against zero in 27 days of Phase 1. Bingbot followed with a. The strategic issue is whether automated visitors can understand, trust, and complete the same journey a human visitor can. Agent readiness is partly technical, but it is also about clear tasks, accessible flows, and reliable evidence.

What the visibility signal actually changes

What the visibility signal actually changes: javaScript Links Can Make Your Pages Invisible to AI Search: the Strategic Visibility Angle should be treated as a visibility signal, not a standalone headline. Introduction " Google renders JavaScript " has been the standard answer to client side rendering concerns for years, and it got easier to believe in 2019, when Googlebot went evergreen, continuously running on the latest version of Chromium. The increasing. This connects with What AI Says About Your Locations when the same signal needs a clearer operating decision. A useful companion note is Real Reason Internal Links Quietly Decay &, because it looks at a nearby part of the same system.

What the visibility signal actually changes: the practical question is whether the page, brand evidence, and surrounding content make the answer easier to trust. If that support is weak, search systems can still understand the topic but fail to connect it confidently to the brand. The same pattern also shows up in AI Search Cites Reddit, where the practical question is how the signal becomes visible.

What the visibility signal actually changes: that is why the response should begin with an audit of the evidence already on the site before creating a new asset. The fastest improvement is often a clearer page, a better internal link, or a stronger explanation of why the brand belongs in the answer.