Lab · 5
Can AI build an infinite-scroll page that stays fully visible to AI?
This started as two separate experiments — pagination for the Lab, infinite scroll for Thinking — before a working session collapsed them into one question. Real pagination means real page-2 URLs, which felt like overhead this site doesn’t need yet. Real infinite scroll usually means fetching more as you scroll, which is exactly the pattern most AI crawlers can’t see through, since most of them never execute JavaScript at all. So the actual test became narrower: can AI build something that feels like infinite scroll to a person, while every item still ships in the page’s raw HTML — nothing fetched, nothing hidden from a machine that only ever reads the source?
Hypothesis
AI can build a page that scrolls like infinite scroll for users but stays fully visible to AI for AEO/GEO.
Finding
TBD — this experiment is still ongoing.
The mechanism below is live on /lab/ and /thinking/, but the finding hasn’t been written yet — it needs time to hold up against real crawl behavior, not just a working demo.
Method
What was built, and how the work split between AI and Dr. Paul.
What was built
A progressive scroll reveal, layered onto the existing content toolbar organism from Experiment 4 rather than built as a separate system. Every entry on /lab/ and /thinking/ still renders in full in the page’s HTML at load — a new .scroll-sentinel marker just tells the shared script to reveal the next batch, via a new .is-scroll-hidden state class, as a person scrolls near the bottom. Nothing is fetched, and the reveal coordinates with the existing filter/sort/search logic: changing a filter or sort resets the reveal back to the first batch, so it never shows a stale mix. Confirmed against current research before building: most AI crawlers (GPTBot, ClaudeBot, PerplexityBot, and others) don’t execute JavaScript at all — they read the raw HTML response, so content present in the markup but visually staged behind a CSS class is fully available to them regardless of scroll state.
AI handled
- Researching current SEO/AEO/GEO crawling behavior for paginated and infinite-scroll content
- Identifying that most AI crawlers don’t render JavaScript, which shaped the actual design
- Designing progressive reveal (not fetch-based infinite scroll) so nothing is ever hidden from a non-rendering crawler
- Writing the CSS/JS and wiring it into the existing shared toolbar script
- Building it directly on both live pages
Dr. Paul handled
- Setting the original two-experiment idea (pagination for Lab, infinite scroll for Thinking)
- Deciding, after working through the SEO/AEO/GEO tradeoffs, to collapse it into one experiment instead
- Setting the final hypothesis
- Moving the avatar/chatbot Next Question down a slot
- Will set the finding once there’s enough to report
Finding
TBD — this experiment is still ongoing.
The build is live. What’s not yet known is whether it actually holds up — that takes time, not just a working demo.
Implication
To follow once the finding is confirmed.
Next Question · 6
Should Dr. Paul become an avatar?
Talking avatar, text chatbot, or shelved entirely?
Back to the Lab