AI crawlers don't render JavaScript – I audited my own 11 production sites
From the Journal · July 27, 2026 Your site welcomes AI crawlers. I measured what that difference costs across eleven of my own production sites — and three of them were invisible. Smith · 9 min read · Published July 27, 2026 Key takeaways AI crawlers do not execute JavaScript.
- ▪From the Journal · July 27, 2026 Your site welcomes AI crawlers.
- ▪I measured what that difference costs across eleven of my own production sites — and three of them were invisible.
- ▪Smith · 9 min read · Published July 27, 2026 Key takeaways AI crawlers do not execute JavaScript.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,524 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Smith App Studio |
| Canonical URL | https://www.smithappstudio.com/blog/ai-crawlers-cant-see-your-spa-2026/ |
| Publication time | Tue, 28 Jul 2026 04:48:46 +0000 |
| Retrieval time | 2026-07-28T04:54:38.932Z |
| Last seen | 2026-07-28T04:54:38.932Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | OUtsuK3sb6rD · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
From the Journal · July 27, 2026 Your site welcomes AI crawlers. Mine was serving them six words. Google’s crawler runs JavaScript. ChatGPT’s does not. I measured what that difference costs across eleven of my own production sites — and three of them were invisible. By Dr. Maasi J. Smith · 9 min read · Published July 27, 2026 Key takeaways AI crawlers do not execute JavaScript. GPTBot, ClaudeBot and PerplexityBot read your raw HTML once and move on. Googlebot renders JavaScript. They do not. A client-rendered single-page app is therefore invisible to them — not badly ranked, invisible. I measured eleven of my own production sites. Three served AI crawlers fewer than ten words. All three had perfect robots.txt files explicitly inviting those crawlers in.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Smith App Studio.
Discussion
0 commentsMore from Smith App Studio
