Google Search can render JavaScript, but that does not mean every Googlebot visit produces an indexed page. OpenAI’s public crawler documentation does not say that its crawlers execute JavaScript; a December 2024 study observed that OpenAI crawlers did not execute it in the tests conducted. If important content must be available to both, serve it in the initial HTML rather than relying only on client-side rendering.
Does Googlebot render JavaScript?
Yes. Google Search documents a three-stage process: crawling, rendering and indexing. Googlebot fetches a page, then eligible pages can be queued for rendering with headless Chromium. Google uses the rendered HTML as part of its indexing process. Rendering may happen after a delay, and it is not a promise that a page will be indexed. Google’s JavaScript SEO guide describes the workflow.
As an Amazon Associate I earn from qualifying purchases.
Rendering depends on access and page status. Google says it does not render pages or files blocked from crawling, and non-200 responses may skip rendering. Its documentation says HTTP 200 pages are queued unless a robots meta tag or HTTP header tells Google not to index them. A page that returns successfully can still fail to expose its intended content if the required scripts or resources are unavailable.
Googlebot’s rendering has practical limits
Google’s Web Rendering Service is stateless: it clears local storage and session data between requests. Content that appears only after a user action, or depends on browser state that is not present in the rendering environment, may not be available to the renderer. Use Google’s JavaScript SEO guidance and its URL Inspection or Rich Results Test to check what Google can see.
#1 Best Overall
Google documents smartphone and desktop crawler types, and says most sites are primarily indexed using the mobile version. Both crawler types use the same robots.txt product token. Google’s March 31, 2026 article gives current fetch ceilings of 2 MB for supported non-PDF files and 64 MB for PDFs; JavaScript and CSS resources are fetched separately and have their own limits. Put essential text and metadata early in a lean initial document. Google’s explanation of crawling, fetching and processed bytes details these limits.
Can ChatGPT crawl a JavaScript website?
OpenAI’s public crawler documentation explains crawler roles and publisher controls, but it does not document a JavaScript rendering engine or state whether OAI-SearchBot executes JavaScript. That is different from an official claim that the crawler cannot render JavaScript.
The most direct evidence in the available published material is a Vercel and MERJ analysis from December 17, 2024. In its tests of major AI crawlers, including OAI-SearchBot, ChatGPT-User and GPTBot, the researchers observed that the crawlers did not execute JavaScript. They also found that ChatGPT crawlers fetched JavaScript files in 11.50% of requests in their dataset, without executing those scripts. That figure describes the study’s observed sample and period—not a current rate for every site or a binding specification of OpenAI’s infrastructure. Read the Vercel and MERJ analysis.
What do OAI-SearchBot and GPTBot control?
They serve different purposes. OpenAI says OAI-SearchBot helps public content be discovered and included in summaries and snippets in ChatGPT Search. GPTBot is a separate crawler control associated with content that publishers may exclude from potential training use. Allowing one does not amount to allowing the other. OpenAI advises publishers who want their content available for ChatGPT Search summaries and snippets not to block OAI-SearchBot. OpenAI’s publisher FAQ and its crawler overview explain the distinction.
Rank #3
Access is not a guarantee that ChatGPT Search will show, cite or rank a page. Review robots.txt rules for each crawler according to the use you intend to permit; do not treat OAI-SearchBot and GPTBot as interchangeable.
Googlebot and ChatGPT crawlers: what the evidence supports
| Question | Google Search | ChatGPT-related crawlers |
|---|---|---|
| Is JavaScript rendering officially documented? | Yes. Google documents rendering with headless Chromium for eligible pages. Google Search Central. | OpenAI’s reviewed crawler documentation does not describe JavaScript rendering. OpenAI crawler overview. |
| What do we know about script execution? | Google says its rendering stage executes JavaScript when resources and access allow; rendering is not guaranteed for every page. | Vercel and MERJ observed no JavaScript execution by the OpenAI crawlers in their December 2024 tests. This is a dated independent observation, not an OpenAI guarantee. Study. |
| What is the crawler for? | Googlebot supports Google Search crawling, rendering and indexing. | OAI-SearchBot supports discovery for ChatGPT Search; GPTBot is a separate control related to potential training use. OpenAI publisher FAQ. |
| Can a publisher control access? | Robots.txt and indexing directives affect crawling and indexing; blocked resources can prevent rendering. Google guidance. | OpenAI documents crawler-specific controls; check OAI-SearchBot and GPTBot separately. OpenAI crawler overview. |
How should you build a JavaScript site for search visibility?
Serve essential content in the initial HTML
For the broadest crawler compatibility, make the page’s core text, links, titles and structured data available in server-generated or prerendered HTML. Google specifically recommends server-side rendering or prerendering because not all bots can run JavaScript. This also means that a crawler which fetches the initial document without executing scripts has a chance to read the page’s essential content.
Rank #4
Keep Google’s resources crawlable
Check that robots.txt does not block JavaScript or CSS files needed to display the page. Confirm that the page does not depend on a click, login state, local storage or session data to reveal its main content. Then inspect the rendered result with Google’s URL Inspection or Rich Results Test.
Choose an architecture, not a crawler-specific workaround
Google recommends server-side rendering, static rendering or hydration for JavaScript sites. It calls dynamic rendering—a setup that serves a rendered version to crawlers and a client-rendered version to users—a workaround rather than a long-term solution. Google’s dynamic rendering guidance explains the trade-off.
For ChatGPT Search, separately check whether robots.txt permits OAI-SearchBot if you want public content to be eligible for discovery. Because OpenAI’s public documentation does not specify JavaScript execution, do not make client-side rendering the only way that content is delivered if crawler access matters.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
