✅ Claude Code
✅ Claude Cowork
✅ Claude Design
✅ Claude Finance
✅ Claude Science
✅ Claude Teacher
✅ Claude Legal
✅ Claude Security
✅ Claude Healthcare
✅ Claude Research
✅ Claude HR
✅ Claude Analytics
✅ Claude Meetings
⬜ Claude Robotics
⬜ Claude Strategy
⬜ Claude Logistics
⬜ Claude Accounting
⬜ Claude OS
⬜ Claude Real Estate
⬜ Claude Autopilot
⬜ Claude Procurement
⬜ Claude Architecture
⬜ Claude Recruiting
⬜ Claude R&D
⬜ Claude Operations
Introducing Claude Meetings: add Claude to your team’s video call and it builds docs, whiteboards, and other artifacts with you while you’re still talking.
Starting to roll out in beta on Team and Enterprise plans.
Every week I check how ChatGPT fetches and reads pages.
This week I saw something different.
ChatGPT is reading JavaScript much better than before. It looks like it now has two ways to get your pages:
- The old one: ChatGPT-User. It fetches the page live, but it doesn’t execute JavaScript. Anything rendered client-side stays invisible.
- The new one: cached pages from its own search index, crawled by OAI-SearchBot. These copies are, at least to some extent, JavaScript-rendered.
I tested this on a JS-heavy product listing pages:
- Live fetch: a search box. That’s it.
- ChatGPT’s cached copy: full product grid, filters, prices, product counts.
Same URL, two completely different pages.
The log files support this too.
OAI-SearchBot has been requesting JavaScript, CSS and API files on and off for a while. But it’s never been at this level. October was the highest month so far, and November is already ahead of it. ChatGPT-User, on the other hand, still barely touches anything beyond HTML.
At the same time, ChatGPT-User is fetching a lot less, while OAI-SearchBot keeps growing its share.
Looking at the timeline, this shift started showing up in late September. Since mid-October, OAI-SearchBot has clearly taken over from ChatGPT-User. And in the last couple of weeks, the JavaScript activity has accelerated.
So overall, it looks like JavaScript rendering is coming to ChatGPT, through its own index and cache.
That’s good news for content that was invisible to ChatGPT before.
But keep in mind:
- The cached copy can be days or weeks old
- The live fetch and the cached copy can show two different versions of the same page
- You don’t control which one ends up in the answer
Check your log files. See whether OAI-SearchBot is hitting your JS, CSS and API endpoints, and compare it with what ChatGPT-User gets.
Instead of asking "how did you hear about us?" try these 👇
p.s. Thanks to @RossHudgens for having me on his show. Whole episode rocks thanks to his smart Qs & excellent editing.