Two paths into ChatGPT
OpenAI runs two crawlers. GPTBot indexes pages for inclusion in training data. OAI-SearchBot fetches pages live when ChatGPT users run searches. Blocking either reduces your visibility in the corresponding mode. A site that blocks GPTBot but allows OAI-SearchBot can still show up in ChatGPT search results but won't be referenced in conversations where the user hasn't explicitly turned on browsing — which is the majority of conversations.
How to check what ChatGPT actually sees
Open ChatGPT and ask: "Describe what [your domain] does. List your top three product features and your pricing." If the answer is accurate and specific, ChatGPT has a clean read on your site. If it's generic ("a software company"), vague, or wrong, you're either blocking crawlers, rendering content client-side without an SSR fallback, or your content lacks the structural signals AI engines use to extract facts. Read our DIY AI visibility audit for a 20-minute checklist.
The biggest blocker: client-side rendering
If your homepage's H1 and value proposition load via JavaScript only, AI crawlers may see an empty <body>. Test by viewing source (Cmd+Opt+U on Chrome) — if the actual page text isn't in the HTML, AI engines can't read it. Frameworks like Next.js, Astro, and Remix server-render by default. Pure client-side React without SSR is the most common cause of "ChatGPT can't see my page" — and it's fixable.