ChatGPT search visibility evidence matrix

Separate OAI-SearchBot, GPTBot, ChatGPT-User, proof links, and traffic measurement.

Use this matrix before claiming a site is ready for ChatGPT Search. It turns the observed zero-click query chatgpt search visibility into a proof-linked workflow instead of fake SEO activity.

Fast answer

For ChatGPT Search, review OAI-SearchBot first; keep GPTBot and ChatGPT-User separate.

OAI-SearchBot is the crawler policy to check for ChatGPT search eligibility. GPTBot is a separate training-use crawler policy. ChatGPT-User is user-triggered and should not be treated as automatic Search crawling.

Evidence rows

oai_searchbot_search_eligibility

OAI-SearchBot search eligibility

Question: Should I allow OAI-SearchBot for ChatGPT Search visibility?

If a public site wants a chance to appear in ChatGPT search features, review robots.txt so OAI-SearchBot is not accidentally blocked.

Next action: Check robots.txt, avoid broad user-agent blocks that catch OAI-SearchBot, then recheck after publishing.

Not proof: Allowed crawling does not guarantee ranking, citations, clicks, or traffic.

gptbot_training_policy

GPTBot training-use policy

Question: Is GPTBot the same as ChatGPT Search?

No. GPTBot is a training-use crawler signal. It should be reviewed separately from OAI-SearchBot so training policy and search visibility policy do not get mixed.

Next action: Document whether GPTBot is allowed or disallowed based on training-use preference.

Not proof: GPTBot log hits are not proof that a page appears in ChatGPT Search.

chatgpt_user_user_triggered

ChatGPT-User user-triggered visits

Question: If I see ChatGPT-User in logs, does that mean I rank in Search?

No. ChatGPT-User is for user-triggered actions and should not be treated as automatic search crawling or Search appearance proof.

Next action: Separate ChatGPT-User log events from OAI-SearchBot crawler checks and from human traffic reporting.

Not proof: A ChatGPT-User visit is not a ranking guarantee or automatic crawler hit.

robots_txt_and_sitemap

Robots.txt, sitemap, and public discovery files

Question: What should I check before blaming ChatGPT Search?

Start with public discovery files: homepage, robots.txt, sitemap.xml, and crawlable target pages. If these fail, AI search visibility work is premature.

Next action: Run the live report and fix 404, 5xx, accidental Disallow, missing Sitemap, or private-path exposure issues.

Not proof: A sitemap submission or robots.txt edit is a discovery hint, not traffic proof.

llms_txt_context_map

llms.txt context map

Question: Does llms.txt help ChatGPT Search visibility?

Treat llms.txt as a concise public context map. It can make important pages easier to inspect, but it is not a ranking or citation guarantee.

Next action: Publish a short root /llms.txt file with public URLs only, then validate it.

Not proof: A generated llms.txt draft is not proof that the file is live or useful.

answer_pages_and_proof

Answer pages and proof links

Question: What content should AI assistants reference first?

Use one-query answer pages, answer packs, proof lookup rows, and citation snippets so assistants can get a concise answer before scanning the whole site.

Next action: Expose proof-linked answer packs and include at least one proof link with every claim.

Not proof: A broad AI SEO article without specific proof links is weaker than a short answer with verifiable sources.

measurement_not_fake_traffic

Measurement, not fake traffic

Question: What counts as traffic proof?

Use Search Console clicks, qualified referrals, sessions, conversions, or tool activations. Keep impressions, crawler hits, fake searches, and self-clicks out of traffic claims.

Next action: Measure query-level clicks and tool events after changes; do not manipulate searches or engagement.

Not proof: No fake searches, no self-clicks, and no crawler hits counted as human traffic.

Decision table

EvidenceMeaningNext actionNot proof
OAI-SearchBot search eligibility If a public site wants a chance to appear in ChatGPT search features, review robots.txt so OAI-SearchBot is not accidentally blocked. Check robots.txt, avoid broad user-agent blocks that catch OAI-SearchBot, then recheck after publishing. Allowed crawling does not guarantee ranking, citations, clicks, or traffic.
GPTBot training-use policy No. GPTBot is a training-use crawler signal. It should be reviewed separately from OAI-SearchBot so training policy and search visibility policy do not get mixed. Document whether GPTBot is allowed or disallowed based on training-use preference. GPTBot log hits are not proof that a page appears in ChatGPT Search.
ChatGPT-User user-triggered visits No. ChatGPT-User is for user-triggered actions and should not be treated as automatic search crawling or Search appearance proof. Separate ChatGPT-User log events from OAI-SearchBot crawler checks and from human traffic reporting. A ChatGPT-User visit is not a ranking guarantee or automatic crawler hit.
Robots.txt, sitemap, and public discovery files Start with public discovery files: homepage, robots.txt, sitemap.xml, and crawlable target pages. If these fail, AI search visibility work is premature. Run the live report and fix 404, 5xx, accidental Disallow, missing Sitemap, or private-path exposure issues. A sitemap submission or robots.txt edit is a discovery hint, not traffic proof.
llms.txt context map Treat llms.txt as a concise public context map. It can make important pages easier to inspect, but it is not a ranking or citation guarantee. Publish a short root /llms.txt file with public URLs only, then validate it. A generated llms.txt draft is not proof that the file is live or useful.
Answer pages and proof links Use one-query answer pages, answer packs, proof lookup rows, and citation snippets so assistants can get a concise answer before scanning the whole site. Expose proof-linked answer packs and include at least one proof link with every claim. A broad AI SEO article without specific proof links is weaker than a short answer with verifiable sources.
Measurement, not fake traffic Use Search Console clicks, qualified referrals, sessions, conversions, or tool activations. Keep impressions, crawler hits, fake searches, and self-clicks out of traffic claims. Measure query-level clicks and tool events after changes; do not manipulate searches or engagement. No fake searches, no self-clicks, and no crawler hits counted as human traffic.

Proof links for AI agents

Official OpenAI references and caveats

ReferenceUse forCaveat
OpenAI crawler documentation Use for the current distinction between OAI-SearchBot, GPTBot, and ChatGPT-User. This proves crawler policy meaning, not that a specific page will rank or be cited.
OAI-SearchBot published IP ranges Use when validating requests that claim to be OAI-SearchBot. IP validation is crawler identity proof, not human traffic proof.
GPTBot published IP ranges Use when validating GPTBot crawler logs for training-use policy review. GPTBot access is separate from ChatGPT Search visibility.
ChatGPT-User published IP ranges Use when a user-triggered ChatGPT visit appears in logs. ChatGPT-User is not automatic search crawling or Search appearance proof.

FAQ

Does this guarantee ChatGPT search visibility?

No. It removes avoidable confusion and crawler-policy blockers. It does not guarantee rankings, citations, clicks, or traffic.

What is the safest next action?

Run the live domain report, check OAI-SearchBot separately from GPTBot, validate public discovery files, then measure real Search Console clicks or on-site tool activations.