Does ChatGPT Read JavaScript Dental Websites?

No major AI crawler runs JavaScript. GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot read the raw HTML only, so a page whose content is drawn by JavaScript can rank on Google and still be blank to ChatGPT. Google Gemini is the exception, because it uses Google's rendering service.

This difference is not obvious from a normal browser view. A browser can run a page's scripts before showing the page, while a crawler that does not run those scripts can receive only the original HTML.

Why does the same site behave differently for Google and ChatGPT?

A JavaScript-built homepage can send an HTML shell, then fill in the practice name, hours, services and reviews after the page loads. A browser runs that script before showing the completed page. A crawler that fetches the page without running the script sees only what the original HTML contains.

Google documents a rendering step for Google Search. The AI crawlers named above are addressed by the locked answer at the top of this page; the practical question for a practice is whether its key content is present in the raw HTML.

Crawler identity and JavaScript execution, per the relevant operator documentation. See sources below.
Crawler or service	Associated product	Executes JavaScript
GPTBot / OAI-SearchBot / ChatGPT-User	ChatGPT	No
ClaudeBot	Claude	No
PerplexityBot	Perplexity	No
Googlebot / Web Rendering Service	Google Search	Yes

What "no major AI crawler runs JavaScript" does not mean

It does not mean these crawlers cannot read your site at all. When a crawler can reach the server, placing the practice name, hours and services in the raw HTML makes those details available without JavaScript. It also does not mean fixing this guarantees a mention; being readable is a precondition, not a trigger. Whether a practice gets named still depends on what the engine's retrieval and ranking logic decides, which this page does not measure.

What does Citevio's own site data show about this risk?

The Citevio dental practice web anatomy study, 6–26 June 2026, covered 527 US dental practice websites, 7 US metros plus 9 smaller nearby towns. It recorded platforms, not rendering methods. The platform page reports one permitted figure: WordPress: 289 of 527 sites (54.8%). That figure does not establish how any individual site renders; use the raw-HTML check below.

Does JavaScript affect Google AI Overviews too?

How does this connect to page speed?

Rendering and speed are separate problems. In the Citevio dental practice web anatomy study, 6–26 June 2026, Citevio's speed page reports one permitted FCP figure: 130 of 256 measurable sites (50.8%) were over 3.0 seconds, Google's “Poor” line.

First Contentful Paint measured with Google's PageSpeed Insights API, mobile strategy, one reading per site. n = 256 of 527 practices scanned; the rest returned a measurement error. This is loading-speed data, not a measurement of AI visibility or citation outcomes.

How do I check my own site?

Load your homepage, then view the raw page source rather than the rendered page, and search for your practice name or a sentence from your homepage. If it is missing from that raw source, a crawler that does not run JavaScript will see the same emptiness.

Open your homepage in a desktop browser.
View the page source — right-click and choose "View Page Source," or use Ctrl+U / Cmd+Option+U. This shows the raw HTML before any script runs, which is close to what a non-rendering crawler receives.
Search that source (Ctrl+F / Cmd+F) for your practice name, phone number, or a sentence you know is on the homepage.
Read the result. Found it: the content is present in the raw HTML and readable to non-rendering crawlers. Not found: that content is being added by JavaScript after the page loads, and ChatGPT, Claude and Perplexity's crawlers will not see it.

This check only confirms whether content is present in the raw HTML. It does not test crawler access at the server level — a site can pass this check and still block a crawler outright, which is a different problem covered in open to AI on paper, blocked in practice. A fuller version, including how to check individual crawlers separately, is on how to test if AI can read your dental website.

Common questions

Does ChatGPT read JavaScript on my dental website?

Why can my site rank on Google but still be invisible to ChatGPT?

Because Google and the AI assistant crawlers do not read your site the same way. Googlebot renders JavaScript before indexing a page, which is why a JavaScript-built site can rank normally in Google Search. GPTBot, ClaudeBot and PerplexityBot do not render JavaScript, so if your practice name, hours or services only appear after a script runs, those crawlers see a page with little or nothing on it.

Is Gemini affected the same way as ChatGPT?

How do I check if my dental website is JavaScript-rendered?

Load your homepage in a browser, then view the page source (not the rendered DOM) and search for your practice name, phone number or a sentence of your homepage text. If it is missing from that raw source, your content is being drawn in by JavaScript after the initial load, and a non-rendering crawler will not see it. A step-by-step version of this check is on how to test if AI can read your dental website.

What platforms are more likely to have this problem?

Platform data does not show whether an individual site is server-rendered or JavaScript-rendered. The reliable check is to inspect the raw HTML your server returns for the practice's key content.

Sources: OpenAI crawler documentation; Anthropic crawler documentation; Perplexity crawler documentation; Google Search Central JavaScript documentation; Citevio dental practice web anatomy study, 6–26 June 2026 (own data, methodology: how we measure AI visibility).

See what ChatGPT, Claude and Perplexity actually see

Run a free check of your dental website's AI readiness, starting with whether its key content is available in raw HTML.

Run my free AI scan

No sales call — ever.