Insights · Question
Why is our site invisible to ChatGPT?
Usually for one of four reasons, in this order of likelihood. The crawler is blocked: a hosting default, a bot-protection rule or an old robots.txt line keeps OAI-SearchBot out, and the site still works in every browser so nobody notices. The content is rendered by JavaScript, so the crawler receives an empty shell. The pages do not answer any specific question, so there is no passage to cite. Or the entity is inconsistent across the web, so the engine cannot connect the organization to its pages. Each is diagnosed by fetching the site as the crawler, reading the logs and reviewing the pages; each is fixable.
In more detail
The reasoning.
Start with access. Fetch the home page and three deep pages as OAI-SearchBot, GPTBot, ClaudeBot and PerplexityBot and compare with a browser view. Read the served robots.txt, which may differ from the file in the repository if a managed version is injected. Check the CDN and firewall settings and then the logs: a crawler that never arrives is blocked somewhere.
Then rendering. Load the page with scripts disabled. If the content disappears, most AI crawlers never saw it. Pre-rendering fixes this permanently.
Then substance and entity. A service page that says the firm is trusted and experienced contains nothing an engine can quote; a page with a declarative answer, a named author and consistent facts does. See Cloudflare’s default AI crawler block, why JavaScript-rendered content is invisible and crawl and render readiness.
By David Selakovic · Published 2026-10-16 · Revised 2026-10-16 · Reviewed every 90 days