Skip to content
Tityra
Login
Start for free
HomeAboutWho It's For
  • Publishers & Media
  • Ecommerce & Retail
  • SaaS & Technology
  • Agencies
  • Government & Public Sector
  • Financial Services & Insurance
PricingFAQBlog
info@tityra.com
XLinkedIn
  1. Home
  2. /
  3. Blog
  4. /
  5. Content access

Do AI crawlers
render JavaScript?

What major providers document about JavaScript rendering, what crawler studies found and how to interpret the evidence for your website.

5 min read

Tom Cranstoun · 12 November 2026

Read the article

Used by many

  • Onedio
  • Maçkolik
  • Webtekno
  • Yemek.com
  • Mynet
5/51 review on G2
Start for free

UNDERSTAND CONTENT DELIVERY

Learn what a tested client receives.

FOLLOW THE EVIDENCE

See how observations become findings.

PUT GUIDANCE INTO PRACTICE

Find changes your team can investigate.

Read the article

In this article

There isn't one rendering rule for AI crawlersWhat the providers actually documentWhy crawler research needs a dateA browser visit doesn't prove crawler supportRendering doesn't settle whether the information arrivesCheck the client you need to reach
How we audit
Table of Contents
There isn't one rendering rule for AI crawlersWhat the providers actually documentWhy crawler research needs a dateA browser visit doesn't prove crawler supportRendering doesn't settle whether the information arrivesCheck the client you need to reach
How we audit

Copy linkThere isn't one rendering rule for AI crawlers

The answer depends on the client. Google Search documents JavaScript rendering, while the public bot overviews reviewed here for OpenAI, Anthropic and Perplexity don't specify whether their named crawlers render JavaScript. A blanket yes or no would go beyond those documents.

Rendering means processing the page in a browser environment, where scripts can build or change its content. Downloading a JavaScript file doesn't establish that the client executed it, and fetching a URL successfully doesn't establish that the information added by that script was available.

If essential information depends on code running after the HTML arrives, look for evidence about the client that retrieves it and the conditions under which it visits. A provider's product name alone doesn't identify that route.

Copy linkWhat the providers actually document

Bot documentation often explains why a client visits and how website owners can control access. That purpose is useful to know, but a search crawler, a training crawler and a user-triggered fetcher can have different jobs within the same service.

The table separates those documented roles from an explicit rendering statement. Google Search is included as a familiar comparison because its documentation does describe JavaScript rendering; that statement applies to Google Search and shouldn't be extended to every Google AI product.

This is a review of the cited documentation, checked on 12 November 2026, alongside the dated study discussed below. It doesn't report a new experiment with the providers' crawlers.

What the cited documentation establishesDocumentation checked 12 November 2026
ServiceClients and documented purposeJavaScript rendering
OpenAIOpenAI bot overviewOAI-SearchBot for search, GPTBot for potential training use and ChatGPT-User for user-triggered visits.Not specified in the cited bot overview.
AnthropicAnthropic crawler guidanceClaudeBot for training, Claude-SearchBot for search and Claude-User for user-directed retrieval.Not specified in the cited crawler guidance.
PerplexityPerplexity crawler guidancePerplexityBot for search and Perplexity-User for fetching pages in response to a user question.Not specified in the cited crawler guidance.
Google SearchGoogle: JavaScript rendering and crawlingGooglebot crawls pages for Google Search, with rendering described as a separate processing step.Yes. Google Search documents JavaScript rendering with evergreen Chromium.

'Not specified' means the cited document doesn't state the capability. It isn't a finding that the client can't render JavaScript.

Copy linkWhy crawler research needs a date

On 17 December 2024, Vercel and MERJ published crawler research that reported no JavaScript rendering observed for the AI crawlers they studied, including OpenAI bots, ClaudeBot and PerplexityBot. Their investigation used nextjs.org and Vercel network data, with additional checks on Resume Library and CV Library.

That's useful empirical evidence for those clients and sites at that time. It supports a dated statement about what the researchers observed, rather than a permanent claim about every visit made by those services. Their distinction between downloading scripts and executing them is also important when interpreting server logs.

Keep the publication date and method alongside the conclusion when using a study to make an implementation decision. The 2024 observation doesn't resolve an unspecified capability in current documentation.

Copy linkA browser visit doesn't prove crawler support

An AI application can use more than one tool to reach the web. Cloudflare's web fetch documentation, updated on 12 October 2026, describes retrieving a page over HTTP and converting its HTML into readable content. It directs agents towards a browser tool when the task requires JavaScript-rendered content or browser interaction.

An application could read a dynamic page through a browser even if an HTTP fetch receives only its initial HTML. That doesn't establish the behaviour of an unrelated provider's crawler.

When someone says that an assistant read their JavaScript page, establish how it reached the information before applying that result elsewhere. A successful browser visit leaves the rendering behaviour of the service's indexing crawler unresolved.

How AI agents interact with websites

Copy linkRendering doesn't settle whether the information arrives

Even an explicit rendering capability leaves questions about the page being visited. Google documents a rendering queue and explains that blocked resources can prevent it from rendering a page's JavaScript. Its guidance therefore gives website teams conditions to check alongside the capability itself.

Consider a product page that displays specifications after a request to another service. A rendering client would still need that request to succeed, and a specification behind a tab might require a further interaction. Those are possible dependencies to investigate, rather than proof that a named crawler succeeds or fails on your page.

Keep the observed result specific. If the specification is absent from the returned content, record that absence and the route used to retrieve it. Calling the entire website 'invisible to AI' would hide the practical question of which information was missing and under what conditions.

Google: JavaScript rendering and crawling

Copy linkCheck the client you need to reach

Start with the outcome you need, such as making a public service description available to a search retrieval client. Find the provider's current guidance, identify the relevant client and record the URL and date of that guidance. Where the rendering behaviour is unspecified, keep that uncertainty visible in your assessment.

For a practical check, preserve the page URL, time and response, along with the real client or tool used. A request from your own machine with a bot's user-agent string can help inspect your server's response to that header, but it doesn't reproduce the provider's rendering system or prove that its crawler visited.

Putting essential public information into readable HTML removes its dependence on later JavaScript execution for clients that can retrieve that response. You can verify that delivery change directly, then assess any search or assistant outcome separately.

Why AI crawlers may miss JavaScript-rendered content

Copy linkSources and further reading

  1. OpenAI: overview of crawlers and user-triggered visits
  2. Anthropic: crawler roles and site-owner controls
  3. Perplexity: crawlers and user fetchers
  4. Google: JavaScript rendering and crawling
  5. Vercel and MERJ: The rise of the AI crawler, 17 December 2024
  6. Cloudflare: web fetch, updated 12 October 2026
Tom Cranstoun

About the author

Tom Cranstoun

Tom Cranstoun is a co-founder of Tityra and a content systems architect. His work spans the BBC's electronic newsroom, Adobe Experience Manager and Edge Delivery Services. He writes about how people and AI agents access and use published content.

More about Tom

Compare the HTML with the browser result

Use the downloadable example to see which information depends on JavaScript and record a check your team can repeat.

Read the HTML delivery guide
Share this article

Share this article

Keep exploring

Content access

Why AI crawlers may miss JavaScript-rendered content

Your browser can show a complete page while another client receives only a loading message. Here's how to check where the content appears.

Read article

Agent Experience

How AI agents interact with websites

AI agents can read pages, use browser controls or call tools directly, with each route shaping what they can see and do.

Content access

Why AI agents may miss website content

A page can look complete in a browser while another client misses its content or context. Compare responses to find where delivery or interpretation fails.

Turn findings into
clear next steps.

Start for free
BlogAudit methodologyAPI docsMCP docsCLIGitHubContact

TITYRA LTD

120 Main Street
Largs, Scotland, KA30 8JN
info@tityra.com
HomeAbout
Who It's For
  • Publishers & Media
  • Ecommerce & Retail
  • SaaS & Technology
  • Agencies
  • Government & Public Sector
  • Financial Services & Insurance
PricingFAQ

© 2026 TITYRA LTD. All rights reserved. Registered in Scotland, company SC908253.

PrivacyTerms and ConditionsCookie informationCookie preferences

We value your privacy

By clicking "Accept all cookies", you agree to the storing of optional analytics cookies on your device to help us understand site usage and improve our website. You may click the customise button to choose which optional cookies you would like to allow.

Strictly necessary (2)

We save your cookie choice in this browser for six months, so you don't have to choose on every visit. This storage is always on.

Show detailsHide details for strictly necessary
  • Name
    tityra_analytics_consent_v1
    Provider
    Tityra (tityra.com)
    Type
    HTML local storage
    Maximum storage duration
    Persistent

    Remembers whether you accepted or rejected analytics. Your choice is valid for 180 days (six months), after which we ask again. The stored record remains until it is replaced or you clear your browser storage.

  • Name
    tityra_analytics_consent_v1_refusal
    Provider
    Tityra (tityra.com)
    Type
    HTML session storage
    Maximum storage duration
    Browser tab session

    Keeps analytics off if your browser can't save a rejection in local storage. This fallback is only used when needed and is cleared when a subsequent choice is successfully saved.

Google Analytics helps us understand page visits, content engagement, interest in audit packages and account signup link clicks. It only loads after you accept. Advertising features are disabled.

Show detailsHide details for analytics
  • Name
    _ga
    Provider
    Google Analytics (tityra.com)
    Type
    HTTP cookie
    Maximum storage duration
    Up to 180 days (six months)

    Distinguishes visitors to help us understand how the website is used. Set only after you accept analytics; advertising features are disabled.

  • Name
    _ga_*
    Provider
    Google Analytics (tityra.com)
    Type
    HTTP cookie
    Maximum storage duration
    Up to 180 days (six months)

    Maintains analytics session information, such as visits and interactions with the website. Set only after you accept analytics. The asterisk represents the identifier in the cookie name.

You control whether optional analytics runs on this website. We remember your choice for six months, and you can change it at any time using Cookie preferences in the footer.

Rejecting or withdrawing consent stops analytics and removes the Google Analytics cookies this website can access.

The details list the name, provider, purpose, type and storage duration of each entry. Contact details and private account information aren't included in website analytics.

Counts describe the entries listed, including the fallback and cookie name pattern, rather than cookies currently stored on your device.

Read our cookie information