Customer Impact

Website & Development

Why JavaScript Websites Are Invisible to AI Search Engines

Copy for AI

A fully client-side rendered website is practically invisible to most AI search engines.

AI crawlers such as GPTBot (ChatGPT), ClaudeBot and PerplexityBot only fetch the raw HTML. They don’t execute any JavaScript.

If your site only builds its content in the browser, those crawlers see an empty shell.

That’s the core of the client side rendering SEO problem in the age of AI search.

The verdict: put your money pages in the raw HTML with server-side rendering (SSR) or static site generation (SSG); ranking in Google alone doesn’t prove AI can read you.

What exactly is client-side rendering?

It means the server sends an almost empty HTML page, and JavaScript builds the real content in the browser.

The visitor first gets a bare skeleton. Then scripts load in the text, headings and links.

Many single-page applications (SPAs), built with frameworks that assemble everything in the browser, work this way by default.

Why humans don’t notice

To a human opening the page, this is invisible.

The script runs in a fraction of a second and you see a complete page.

The difference lies in what an automated visitor gets.

A crawler that fetches the page but doesn’t run JavaScript is stuck on that empty skeleton.

Raw HTML versus rendered HTML

That gap between raw HTML and rendered HTML is the same Achilles heel we describe in JavaScript SEO: why Google sometimes can’t see your content.

With AI search engines, the impact is harsher. Here’s the difference in one view:

Client-side renderingSSR or SSG
What the server sendsan almost empty shell plus scriptsthe complete page
Who builds the contentthe visitor’s browserthe server, or the build
What a non-rendering crawler seesalmost nothingeverything
Typical useapps, dashboards behind a loginservice pages, articles, cases

Why don’t AI crawlers see my JavaScript content?

Because the major AI crawlers don’t run JavaScript.

They request your page, read the HTML the server returns directly, and stop there.

Anything that only appears through JavaScript simply doesn’t exist for them.

What Vercel measured

Vercel’s December 2024 analysis of AI crawler traffic shows this clearly: “none of the major AI crawlers currently render JavaScript.”

That applies to OpenAI’s bots, including GPTBot, which collects training data, and OAI-SearchBot, which surfaces sites in ChatGPT search.

It also applies to Anthropic’s ClaudeBot and to PerplexityBot.

These crawlers aren’t small. Here’s what Vercel counted on its network in one month:

VERCEL NETWORK, PAST-MONTH FETCHES, DECEMBER 2024 AI crawler volume, in millions GPTBot (no JS) 569M Claude (no JS) 370M AppleBot (renders JS) 314M PerplexityBot (no JS) 24.4M Lime = renders JavaScript. Source: Vercel, The rise of the AI crawler, 17 December 2024.

GPTBot alone made 569 million fetches in that month. Claude made 370 million.

PerplexityBot was far smaller, at 24.4 million. None of those three ran a single script.

AppleBot, at 314 million, was the one that did.

They download scripts, but don’t run them

Some of them do download your scripts.

JavaScript files made up 11.5% of ChatGPT’s crawler requests and 23.8% of Claude’s in that study.

But neither executes them.

The result is the same. Client-side rendered content never arrives.

What stays invisible

In practice, these stay invisible to the model a potential customer is consulting:

  • your product descriptions
  • your service pages
  • your case studies
  • your answers to frequently asked questions

Say someone asks ChatGPT or Perplexity for a supplier like you.

You simply can’t be included, because the AI was never able to read your content.

This is exactly the kind of technical blocker that generative engine optimization sets out to remove.

Our experience: in the log file analyses we run, the number of AI agents visiting websites grows significantly year over year. So the share of visitors that can’t run your JavaScript keeps rising.

Rendering is a separate question from access

Reading your HTML assumes the crawler may fetch it at all.

That’s a robots.txt question. It’s separate from rendering.

Ours has one rule that allows every crawler, plus the sitemap line:

The robots.txt file of customerimpact.be with one rule that allows every crawler plus the sitemap line, so AI crawlers can fetch the raw HTML that client side rendering SEO depends on Our own robots.txt, October 2026: one rule for all crawlers, so every AI bot, training and search, may read the site.

Our guide on how to allow AI crawlers covers that side.

But I do rank in Google, so how is that possible?

Because Googlebot renders JavaScript and most AI crawlers don’t.

Both can be true at once. That’s what makes the problem so treacherous.

How Googlebot handles JavaScript

Googlebot is one of the few crawlers that does render JavaScript.

Per Google’s JavaScript SEO documentation, it crawls your page, queues it for rendering in a headless Chromium, and then indexes the rendered HTML.

So a client-side site can still achieve solid rankings in the classic Google results.

Where the gap opens

The AI crawlers from OpenAI, Anthropic and Perplexity skip that rendering step.

Google’s Gemini, which runs on Googlebot’s infrastructure, and AppleBot are the exceptions Vercel found.

That creates a gap. The same page Google fully understands is a blank sheet to ChatGPT and Perplexity.

So “we rank in Google, so we’re fine” isn’t a conclusion you can draw.

The right question is whether your content is already in the raw HTML.

That’s the only version every crawler is guaranteed to see.

The shift inside Google too

Within Google the centre of gravity is shifting too. Slowly, but clearly.

Features such as AI Overviews lean on what Googlebot can fetch.

But the generative answers outside Google, in standalone AI tools, depend entirely on your raw HTML.

Watch out: anyone who steers on Google alone misses the part of the market that now does its research in a chat interface.

How do I check whether my site has this problem?

The quickest test takes half a minute. No tools needed.

Open your page and click “view page source” (the view-source, not the inspector).

Search for your most important text: your H1 and your service description.

If that text isn’t literally there, it’s probably only loaded client-side. Then the AI crawlers don’t see it.

Three extra checks

A few additional checks:

  • Compare raw and rendered HTML. If view-source shows mostly an empty skeleton and a few script tags while the visible page is full, you’re rendering client-side.
  • Disable JavaScript temporarily in your browser settings and reload. If an empty or half-empty page remains, an AI crawler experiences exactly the same.
  • Look page by page, not just at your homepage. The difference often sits in the deeper service and product pages that should bring in leads.

Look at the whole architecture

Rendering rarely stands on its own. It’s one layer of many.

To dig deeper into how crawlers fetch your pages and which content comes through, look at your website architecture and SEO as a whole.

Our AI visibility audit checks rendering next to the other blockers.

How do I fix client-side rendering?

Stop building your most important content in the browser.

Prepare it on the server instead. Or do it at build time.

There are roughly two routes for that.

Route 1: server-side rendering (SSR)

The server assembles the full page and sends ready-made HTML to both the visitor and the crawler.

No extra rendering step is needed, so nothing can go wrong in a bot’s browser.

Best for: sites with content that changes often or differs per user.

Route 2: static site generation (SSG)

Here your pages are converted into static HTML files during the build.

Every visitor, human or crawler, gets the complete page immediately.

Best for: content that doesn’t change by the second, such as service pages, knowledge articles and case studies. Those are exactly the pages that matter for B2B visibility.

Our own site works this way: it’s built with Astro and served as static HTML by default.

The same result, plus speed

Both routes deliver the same result for AI crawlers.

Your content sits in the raw HTML, readable without a single line of JavaScript having to run.

A pleasant side benefit is speed.

Less client-side JavaScript usually means a faster first render, which also helps your Core Web Vitals.

Here’s what that looks like in the field data for our own static site:

PageSpeed Insights field data for customerimpact.be on mobile: LCP 1.9 s good, CLS 0.13 needs improvement, the speed side of choosing SSR or SSG over client side rendering PageSpeed Insights field data for customerimpact.be on mobile, October 2026. LCP passes at 1.9 s; CLS at 0.13 still needs work.

Largest Contentful Paint lands at 1.9 seconds on mobile, inside Google’s 2.5-second threshold for good. Test your own pages with our website speed test.

Which route fits you

Which approach and platform fit best depends on your situation:

  • the volume of content
  • how often it changes
  • how your team works

A headless CMS setup can support SSR or SSG well, but it isn’t a requirement.

Our comparison of the best CMS for AI search helps you choose.

On our page about website development you can read how we make that choice case by case.

Do I have to rebuild my entire site now?

Not right away. And certainly not in a panic.

Start with the pages that make money

Start with your service pages, your most important landing pages and the content you want to be found for.

Check those first. If they sit in the raw HTML, you’ve covered the biggest risk.

An interactive dashboard behind a login can happily stay client-side, because no AI crawler is looking for it there.

Take rendering along in a rebuild

Planning a bigger intervention or a new site anyway?

Take rendering along from the start as a design choice, not a repair afterwards.

Do it during a website migration and you kill two birds with one stone.

You protect your existing visibility, and your content becomes readable for AI engines straight away.

Steer on leads, not on a checklist

Our stance is level-headed: steer on leads and revenue, not on an endless technical checklist.

A page nobody visits and that produces no leads doesn’t need to be rebuilt first.

To see how this fits into a broader build approach, read our guide to having a B2B website built.

Frequently asked questions

Does ChatGPT run JavaScript when it crawls my site?

No.

Vercel’s analysis found that none of the major AI crawlers render JavaScript.

GPTBot and OAI-SearchBot read the raw HTML only.

Is client side rendering bad for Google SEO?

Not necessarily.

Googlebot renders pages in a headless Chromium before indexing them.

The risk is mainly in AI search engines that skip that step.

Which AI crawlers do render JavaScript?

Vercel found Gemini, which uses Google’s infrastructure, and AppleBot render JavaScript. GPTBot, ClaudeBot and PerplexityBot don’t.

Is SSR or SSG better for AI visibility?

Both put your content in the raw HTML.

SSG suits content that rarely changes, such as service pages and articles; SSR suits content that changes often or per user.

Client-side rendering only makes your content appear in the browser. The major AI crawlers (GPTBot, ClaudeBot, PerplexityBot) don’t run JavaScript.

So you can rank comfortably in Google and be completely absent from ChatGPT, Claude and Perplexity.

The fix is to put your most important content in the raw HTML through SSR or SSG, starting with the pages that generate leads.

Then humans, search engines and AI all read the same complete page.

Want to know whether your site is visible to AI search engines, and what a sensible rendering approach looks like for you? Contact us and we’ll check your key pages with you, or see our AI website development service.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.