<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI Crawlers on RenderCache.com</title>
    <link>https://rendercache.com/tags/ai-crawlers/</link>
    <description>Recent content in AI Crawlers on RenderCache.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rendercache.com/tags/ai-crawlers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI Crawlers Like GPTBot and ClaudeBot See an Empty Shell on JavaScript Sites</title>
      <link>https://rendercache.com/ai-crawlers-like-gptbot-and-claudebot-see-an-empty-shell-on-javascript-sites/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rendercache.com/ai-crawlers-like-gptbot-and-claudebot-see-an-empty-shell-on-javascript-sites/</guid>
      <description>&lt;p&gt;Take a developer docs site built with a JavaScript framework. Every page is a route in one app, and the content loads from Markdown files after the app starts. Search works. The pages look right. Then someone on the team asks an AI assistant about their own API and gets an answer that&amp;rsquo;s a year out of date, or a shrug.&lt;/p&gt;&#xA;&lt;p&gt;One likely reason is in the server logs. GPTBot, ClaudeBot, PerplexityBot and the other AI crawlers have been fetching those pages for months. What they received was the app shell: a title, a script tag and an empty container. Most of these crawlers read the HTML they&amp;rsquo;re given and don&amp;rsquo;t run the JavaScript, so a page whose text only exists after rendering looks blank to them. Their capabilities differ and they change, but on a client-rendered site the safe assumption is that the words aren&amp;rsquo;t reaching them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
