GEO-300 · Lesson 3 of 12 · Module 1: Let AI In · 3:03
What fetchers see
A fetcher receives one HTTP response. Googlebot and Applebot render JavaScript; the crawlers and user fetchers from OpenAI, Anthropic and Perplexity did not in the largest published study (Vercel and MERJ, 2024), and none of them documents rendering as of October 2026, so a page whose facts arrive only through scripts is empty to them. (Browser agents are a different case: Lesson 07.) Test it: fetch the page as the bot with JavaScript off and read the HTML. Serve the facts in that first response with server-side rendering, static generation or pre-rendering, and keep the status honest: a 200 for real pages, a real 404 for missing ones, no consent walls, interstitials or geo-blocks in front of bots, and no "soft 404" shells.

What you will learn
- Test what a fetcher receives
- Serve key facts in the first HTML response
- Keep status codes and walls honest for bots
The one thing to remember
If the first response has no facts, the fetcher has no facts.
Common mistake: Trusting what you see in your browser
Your browser runs the scripts; most AI fetchers do not, so they see an empty shell.
The fix: Check the raw HTML as the bot, and render the facts on the server.
Key terms
- Raw-HTML test
- Fetch a page as the bot, with JavaScript off, and read what comes back.
- Server-side rendering
- The server sends finished HTML, so the facts are readable without running scripts.
- App shell
- An HTML page that is empty until JavaScript fills it; empty to most fetchers.
- Soft 404
- A page that says "not found" but returns 200, so bots keep fetching it.
Part of Technical GEO Specialist (GEO-300)
For developers and technical SEOs: build a site AI can fetch, read and act on, and keep it that way.
12 lessons, practice quizzes, a final exam and the Sophyx Certified Technical GEO Specialist – Professional certificate. Regular price USD 129. Your first certification is free. Free with any paid Sophyx plan.
Start the course free