Check whether AI systems can actually read, interpret, and recommend your site.
GEO Fix team5 min read
You asked ChatGPT to recommend a company like yours. Competitors appeared. You didn't.
That's website not showing in chatgpt — and most owners misdiagnose it. They open a schema guide or commission new blog content. Often the real issue is simpler: AI search crawlers can't reach the site, or AI reads it but can't place you in the category.
This post is the diagnosis. Not a robots.txt tutorial. Not a fix checklist. Just how to figure out what's actually wrong before you change anything.
| What the owner checks first | What often turns out to matter |
|---|---|
| "Do we need more blog content?" | Search crawler can't reach the site |
| "Should we add schema?" | Crawler block — before markup is even evaluated |
| "Is our copy good enough?" | Wrong category detected (crawlers OK, structure weak) |
| "Did we block GPTBot?" | Often irrelevant — GPTBot is training, not search |
A common surprise: Owners assume they have a content or markup problem. In practice, crawler access is the first thing worth ruling out — ahead of schema, llms.txt, and copy rewrites. Many sites pass traditional SEO audits while AI crawlers never reach the homepage.
Industry context: BuzzStream found 49% of top news sites block OAI-SearchBot — the crawler ChatGPT Search uses for live web results. Business sites follow the same pattern when Cloudflare or a security plugin blocks "AI bots" without distinguishing search from training.
When a site is not showing in ChatGPT, it falls into one of three buckets. Your first job is identifying which — not fixing everything at once.
The site ranks on Google. An SEO audit scores 90+. But AI search crawlers — like OAI-SearchBot — can't reach the homepage. Common causes: Cloudflare bot rules, a security plugin, or a robots.txt line that blocks search bots along with training bots.
What this looks like:
| Check | Typical result |
|---|---|
| Google rankings | Fine |
| SEO audit | Green |
| AI search crawlers | Blocked at WAF or robots.txt |
| Owner's assumption | "We need schema" |
The technical fix lives in our GPTBot and OAI-SearchBot guide and AI bots in robots.txt. This post doesn't repeat those rules — read them if Bucket 1 is your result.
Crawlers reach the site. But AI misclassifies the business — thinks you're a "marketing agency" when you're an MSP, or a "software company" when you're HR consulting.
ChatGPT doesn't recommend you because it can't confidently place you in the category query. Competitors with plain-text service pages win — even with worse products.
See why ChatGPT recommends competitors when Bucket 2 blends into authority gaps.
Crawlers OK. Category OK. Competitors still appear because they have more third-party citations — reviews, directories, comparison articles. No robots.txt change fixes this in a week.
G2 found half of B2B software buyers now start vendor research in an AI chatbot. Bucket 3 is a longer game; Buckets 1 and 2 are fixable on the technical layer.
Overlap exists, but the search intent is different.
| Query mindset | Best post |
|---|---|
| "Why doesn't ChatGPT know us?" (general) | Chat GPT SEO Google |
| "Our website specifically isn't showing" (diagnosis) | This post |
| "How do I test it?" | Check if website in ChatGPT |
| "What do I deploy?" | Fix ChatGPT visibility |
For general "why doesn't ChatGPT know us?" questions, see Chat GPT SEO Google. To test visibility, use check if website in ChatGPT. To deploy fixes, see fix ChatGPT visibility.
Identify your bucket first. No tool promises Bucket 3 disappears overnight.
Different systems, different crawlers. Bucket 1 — crawler block — is the most common technical cause for sites with strong Google rankings.
Usually no. GPTBot is for training. ChatGPT search uses OAI-SearchBot. [Full bot breakdown →](/blog/gptbot)
Use the [visibility test methodology](/blog/website-not-showing-in-chatgpt/how-to-check-chatgpt-visibility) — category prompts plus a crawler access check.
No application for typical business sites. OpenAI crawls public pages via OAI-SearchBot if you haven't disallowed it. Being crawlable ≠ being recommended.
Key takeaways
Find technical blockers, missing context, and weak AI-readiness signals in minutes.
No payment, no subscription.
