49
AI Access Score
chatgpt.comPartially blocked
ChatGPT, Claude and Perplexity cannot read chatgpt.com. When a buyer asks them for a recommendation in your category, the answer is built from other websites. Your robots.txt tells them to stay out, so this is a setting someone can change.
A critical finding caps the composite score at 49.
AI Access Score 49 is higher than 3 of the 84 B2B SaaS sites in our September 2026 benchmark (median 91). See the benchmark
Scanned Sep 26, 2026, 09:52 UTC
This is the permanent public report page for chatgpt.com. It always shows the latest scan of the domain and stays online.
43
Live Answer Visibility
86
Search Index Foundation
50
Training Data Presence
How this score is measured

The overall score weights Live Answer Visibility at 45%, Search Index Foundation at 30% and Training Data Presence at 25%, rounded to the nearest point. Critical findings can cap the score lower; any applied cap is stated next to it. Live Answer Visibility and Training Data Presence reflect crawler access plus on-page structure, with Training Data Presence also counting Common Crawl. Search Index Foundation reflects Googlebot and bingbot access plus indexability, sitemap and response health.

Our crawler tests send each bot's user agent from our own servers, not from the AI companies' verified IP ranges. Some firewalls, including Cloudflare, verify crawlers by network identity rather than user agent. That means a site can challenge our test request while allowing the real, verified crawler. When that happens this scan over-reports blocking; it never under-reports it. The Googlebot result is the most exposed to this, because fake Googlebots are the most common spoof and are policed hardest.

This scan of chatgpt.com checked 15 AI crawlers across 21 automated checks on 1 page. 11 of 13 scored crawlers are currently blocked. AI Access Score: 49/100 (Partially blocked).

Critical: 6 findings hiding you from AI

CRITICALOAI-SearchBot blocked by firewall (Cloudflare)

Your robots.txt allows OAI-SearchBot, but the server refused its request. Your stated policy says yes; your firewall says no, and you probably did not choose this. The site blocks automated traffic broadly, not only AI crawlers. Our test sends this crawler's name from outside OpenAI's network; a firewall that verifies crawler identity can still admit the real crawler, so your server logs are the final word.

Cloudflare manages AI crawlers per behavior category (Search, Agent, Training) under Security Settings, then Configure AI bot policies. As of September 15, 2026, new Cloudflare domains block Agent and Training crawlers on pages with ads by default, so this block may be a default nobody chose.

Verify it yourself
curl -sI -A "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-SearchBot/1.0; +https://openai.com/searchbot" "https://chatgpt.com/" | head -5
CRITICALChatGPT-User blocked by firewall (Cloudflare)

Your robots.txt allows ChatGPT-User, but the server refused its request. Same firewall pattern as the OAI-SearchBot finding above; one firewall change covers every crawler it blocks, and the same server-log caveat applies.

Verify it yourself
curl -sI -A "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/bot" "https://chatgpt.com/" | head -5
CRITICALClaude-SearchBot blocked by firewall (Cloudflare)

Your robots.txt allows Claude-SearchBot, but the server refused its request. Same firewall pattern as the OAI-SearchBot finding above; one firewall change covers every crawler it blocks, and the same server-log caveat applies.

Verify it yourself
curl -sI -A "Mozilla/5.0 (compatible; Claude-SearchBot/1.0; +https://www.anthropic.com/claude-searchbot)" "https://chatgpt.com/" | head -5
CRITICALClaude-User blocked by firewall (Cloudflare)

Your robots.txt allows Claude-User, but the server refused its request. Same firewall pattern as the OAI-SearchBot finding above; one firewall change covers every crawler it blocks, and the same server-log caveat applies.

Verify it yourself
curl -sI -A "Mozilla/5.0 (compatible; Claude-User/1.0; +https://www.anthropic.com/claude-user)" "https://chatgpt.com/" | head -5
CRITICALDuckAssistBot blocked by firewall (Cloudflare)

Your robots.txt allows DuckAssistBot, but the server refused its request. Same firewall pattern as the OAI-SearchBot finding above; one firewall change covers every crawler it blocks, and the same server-log caveat applies.

Verify it yourself
curl -sI -A "Mozilla/5.0 (compatible; DuckAssistBot/1.0; +https://duckduckgo.com/duckassistbot)" "https://chatgpt.com/" | head -5
CRITICALEvery live-answer AI bot is blocked

ChatGPT, Claude, Perplexity and DuckAssist all fail to fetch this site; you cannot be cited in live AI answers.

Verify it yourself
curl -sI -A "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-SearchBot/1.0; +https://openai.com/searchbot" "https://chatgpt.com/" | head -5

The bot matrix

robots.txt policy next to what actually happened when each bot knocked. Rows where your policy says yes but the server says no are highlighted; those are the silent failures.

Live-answer botsFetch content in real time to build the answers and citations users see today.
BotOwnerrobots.txt policyReal fetchVerify
OAI-SearchBot
Powers ChatGPT search results
OpenAIPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
ChatGPT-User
User-triggered fetches from ChatGPT; Cloudflare classes this as Agent traffic, blocked by default on ad pages for new Cloudflare domains
OpenAIPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
PerplexityBot
Index for Perplexity answers
PerplexityBlocked
line 40: Disallow: /
Refused (403)
Perplexity-Userinformational
User-triggered; may ignore robots.txt
PerplexityPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
Claude-SearchBot
Claude search indexing
AnthropicPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
Claude-User
User-triggered fetches from Claude; Cloudflare classes this as Agent traffic, blocked by default on ad pages for new Cloudflare domains
AnthropicPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
DuckAssistBot
DuckAssist answers
DuckDuckGoPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
Training crawlersCollect content for model training. Blocking them removes you from future models' memory.
BotOwnerrobots.txt policyReal fetchVerify
GPTBot
Training corpus
OpenAIPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
ClaudeBot
Training corpus
AnthropicPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
CCBot
Feeds many labs' training data; blocking it is the quietest way to disappear from future models
Common CrawlBlocked
line 4: Disallow: /
Refused (403)
Meta-ExternalAgent
Llama training
MetaPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
Amazonbot
Alexa and Amazon AI features
AmazonPartial
line 218: Disallow: /auth/logout
Blocked by firewall (Cloudflare)
Policy says yes; firewall says no.
Bytespiderinformational
Known to sometimes ignore robots.txt
ByteDanceBlocked
line 34: Disallow: /
Refused (403)
Search-index foundationCopilot rides Bing's index and AI Overviews rides Google's. If these starve, the AI layer above them starves.
BotOwnerrobots.txt policyReal fetchVerify
Googlebot
Google Search index; AI Overviews rides this. Cloudflare treats it as mixed Search and Training, so as of September 15, 2026 Cloudflare AI training blocks can hit it
GooglePartial
line 218: Disallow: /auth/logout
Reachable (200)
bingbot
Bing index; Copilot and ChatGPT search lean on it. Cloudflare treats it as mixed Search and Training, so as of September 15, 2026 Cloudflare AI training blocks can hit it
MicrosoftPartial
line 218: Disallow: /auth/logout
Reachable (200)
Training opt-out tokensNot crawlers. Directives controlling whether already-crawled content trains AI.
TokenControlsYour robots.txt
Google-ExtendedGemini training use of Google's crawl
Blocking Google-Extended does NOT affect your Google Search ranking, but it does remove your content from Gemini training use.
Opted out
Applebot-ExtendedApple AI training use
Blocking Applebot-Extended does not affect Siri or Spotlight search.
Partial

Your scanned pages

Real defects live on money pages, not just homepages. We scanned 1 page: your homepage.

PageStatusIndexableCanonicalTitleWords
/200YesOKChatGPT: Chat, Work, Create & Code with AI97

Warnings (10)

WARNINGPerplexityBot blocked by robots.txt policy

Perplexity cannot fetch your content for live AI answers.

Governing rule (line 40): Disallow: /

Verify it yourself
curl -s "https://chatgpt.com/robots.txt"
WARNINGGPTBot blocked by firewall (Cloudflare)

Your robots.txt allows GPTBot, but the server refused its request. Same firewall pattern as the OAI-SearchBot finding above; one firewall change covers every crawler it blocks, and the same server-log caveat applies.

Verify it yourself
curl -sI -A "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; GPTBot/1.1; +https://openai.com/gptbot" "https://chatgpt.com/" | head -5
WARNINGClaudeBot blocked by firewall (Cloudflare)

Your robots.txt allows ClaudeBot, but the server refused its request. Same firewall pattern as the OAI-SearchBot finding above; one firewall change covers every crawler it blocks, and the same server-log caveat applies.

Verify it yourself
curl -sI -A "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)" "https://chatgpt.com/" | head -5
WARNINGCCBot blocked by robots.txt policy

Common Crawl's training crawler cannot read you; you are opting out of future models' memory.

Governing rule (line 4): Disallow: /

Verify it yourself
curl -s "https://chatgpt.com/robots.txt"
WARNINGMeta-ExternalAgent blocked by firewall (Cloudflare)

Your robots.txt allows Meta-ExternalAgent, but the server refused its request. Same firewall pattern as the OAI-SearchBot finding above; one firewall change covers every crawler it blocks, and the same server-log caveat applies.

Verify it yourself
curl -sI -A "Mozilla/5.0 (compatible; meta-externalagent/1.1; +https://developers.facebook.com/docs/sharing/webmasters/crawler)" "https://chatgpt.com/" | head -5
WARNINGAmazonbot blocked by firewall (Cloudflare)

Your robots.txt allows Amazonbot, but the server refused its request. Same firewall pattern as the OAI-SearchBot finding above; one firewall change covers every crawler it blocks, and the same server-log caveat applies.

Verify it yourself
curl -sI -A "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/600.2.5 (KHTML, like Gecko) Version/8.0.2 Safari/600.2.5 (Amazonbot/0.1; +https://developer.amazon.com/support/amazonbot)" "https://chatgpt.com/" | head -5
WARNINGSitemap declared in robots.txt returns HTTP 403

robots.txt points crawlers at https://chatgpt.com/sitemap.xml, and that URL returns HTTP 403. Crawlers that trust the declaration hit a dead end, and the conventional locations serve no sitemap either, so your money pages get crawled last or never.

Verify it yourself
curl -sI "https://chatgpt.com/sitemap.xml" | head -1
WARNINGOnly 97 words of extractable content on the homepage

AI systems have almost nothing to quote or cite from this page.

Verify it yourselfView source (Ctrl+U) and look for your page copy as plain text.
WARNINGHeading hierarchy issues: 2 H1s

LLM retrieval splits pages into chunks along heading structure; broken hierarchy produces orphan chunks with no context.

Verify it yourselfIn your browser console: [...document.querySelectorAll("h1,h2,h3,h4,h5,h6")].map(h => h.tagName + ": " + h.innerText.trim().slice(0,60)).join("\n")
WARNINGNo Organization schema on the homepage

Without a machine-readable identity, AI systems have to guess who you are instead of knowing.

Verify it yourselfPaste your URL into validator.schema.org and look for the Organization block.

Good to know (2)

INFONo llms.txt found

llms.txt is an emerging convention some AI crawlers read for site guidance. Adding one is a five minute quick win.

Verify it yourself
curl -sI "https://chatgpt.com/llms.txt" | head -1
INFOVerify your Bing index manually

Copilot and ChatGPT search lean on Bing's index; if Bing has not indexed you, two of six AI platforms cannot cite you. Automated Bing verification is unreliable without authenticated APIs, so we will not fake it.

Verify it yourselfSearch "site:chatgpt.com" on bing.com and confirm your key pages appear.

Recommended robots.txt additions (free, no email needed)

# Recommended AI crawler access, generated by the AI Crawler Access Report by Citant.ai
# Place these lines ABOVE any general User-agent: * block in robots.txt

User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: DuckAssistBot
Allow: /
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: CCBot
Allow: /
User-agent: Meta-ExternalAgent
Allow: /
User-agent: Amazonbot
Allow: /
User-agent: Googlebot
Allow: /
User-agent: bingbot
Allow: /

# Optional training opt-outs. These are business decisions, not defects:
# blocking Google-Extended removes you from Gemini training but does NOT
# affect Google Search ranking. Leave them out to stay fully open.
# User-agent: Google-Extended
# Disallow: /

Your prioritized fix plan

Criticals first. CMS not detected; generic instructions shown. Open the print-ready report to save it as a PDF.

1. Allow AI crawlers through your firewall or CDN

Fixes: OAI-SearchBot blocked by firewall (Cloudflare)

  1. Your robots.txt allows these bots but your server refuses their requests, which means a firewall or bot-protection layer is overriding your stated policy. Most site owners do not know this is happening.
  2. In the Cloudflare dashboard, go to Security Settings, then Configure AI bot policies. Cloudflare manages AI crawlers in three behavior categories: Search (crawlers that index content to answer questions later), Agent (real-time fetches on a person's behalf, such as ChatGPT-User), and Training (crawlers that collect content to train or fine-tune models). Set the category that matches the blocked bot to 'Allow (do not block)'.
  3. Category map for the bots in this report: Search covers OAI-SearchBot, PerplexityBot, Claude-SearchBot, DuckAssistBot, Googlebot and bingbot. Agent covers ChatGPT-User, Claude-User and Perplexity-User. Training covers GPTBot, ClaudeBot, CCBot, Meta-ExternalAgent, Amazonbot and Bytespider.
  4. While you are there, confirm the legacy 'Block AI bots' toggle is off. Cloudflare deprecated that toggle on September 15, 2026, and as of that date a Training block also applies to mixed-purpose crawlers such as Googlebot, Applebot, and bingbot. Akamai and Imperva have equivalent verified-bot allowlists.
  5. Verify with the per-bot command in this report; the response should change from 403/503 to 200.
Verify it yourself
curl -sI -A "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-SearchBot/1.0; +https://openai.com/searchbot" "https://chatgpt.com/" | head -5

2. Unblock AI crawlers in robots.txt

Fixes: PerplexityBot blocked by robots.txt policy

  1. Add the recommended snippet below ABOVE any general User-agent: * block; specific user-agent groups override the general one.
  2. Deploy the updated robots.txt and confirm by opening https://yourdomain/robots.txt in your browser.
  3. Re-run this scan; blocked rows should flip to Allowed.
Your recommended robots.txt additions
# Recommended AI crawler access, generated by the AI Crawler Access Report by Citant.ai
# Place these lines ABOVE any general User-agent: * block in robots.txt

User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: DuckAssistBot
Allow: /
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: CCBot
Allow: /
User-agent: Meta-ExternalAgent
Allow: /
User-agent: Amazonbot
Allow: /
User-agent: Googlebot
Allow: /
User-agent: bingbot
Allow: /

# Optional training opt-outs. These are business decisions, not defects:
# blocking Google-Extended removes you from Gemini training but does NOT
# affect Google Search ranking. Leave them out to stay fully open.
# User-agent: Google-Extended
# Disallow: /
Verify it yourself
curl -s "https://chatgpt.com/robots.txt"

3. Fix your sitemap

Fixes: Sitemap declared in robots.txt returns HTTP 403

  1. Ensure /sitemap.xml returns 200 and lists your live URLs; remove entries that 404.
  2. Reference it from robots.txt with a Sitemap: line so crawlers find it without guessing.
Line to add to robots.txt
Sitemap: https://yourdomain.com/sitemap.xml
Verify it yourself
curl -sI "https://chatgpt.com/sitemap.xml" | head -1

4. Add extractable main content

Fixes: Only 97 words of extractable content on the homepage

  1. The page carries under 150 words of extractable main content; AI systems have almost nothing to quote or cite.
  2. Write the page copy into the HTML itself rather than images or embedded widgets.
Verify it yourselfView source (Ctrl+U) and look for your page copy as plain text.

5. Repair the heading hierarchy

Fixes: Heading hierarchy issues: 2 H1s

  1. Use exactly one H1 per page and do not skip levels; LLM retrieval splits pages into chunks along heading structure, and broken hierarchy produces orphan chunks with no context.
  2. Restructure headings in the page template rather than styling text to look like headings.
Verify it yourselfIn your browser console: [...document.querySelectorAll("h1,h2,h3,h4,h5,h6")].map(h => h.tagName + ": " + h.innerText.trim().slice(0,60)).join("\n")

6. Add Organization schema with sameAs links

Fixes: No Organization schema on the homepage

  1. Add the JSON-LD below to your homepage head, filling in your real details.
  2. The sameAs links are the entity-corroboration signal that connects your site to your LinkedIn and other profiles.
  3. Validate at validator.schema.org.
Starter Organization schema (edit the details)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Chatgpt",
  "url": "https://chatgpt.com",
  "logo": "https://chatgpt.com/logo.png",
  "description": "What Chatgpt does, in one sentence.",
  "sameAs": [
    "https://www.linkedin.com/company/chatgpt",
    "https://x.com/chatgpt"
  ]
}
</script>
Verify it yourselfPaste your URL into validator.schema.org and look for the Organization block.

7. Add an llms.txt file

Fixes: No llms.txt found

  1. Save the generated draft below as /llms.txt at your site root.
  2. It is a plain-markdown guide that tells AI systems what your most important pages are; adoption is emerging, and it costs nothing.
Your llms.txt draft, generated from your scanned pages
# Chatgpt

> One-sentence description of what chatgpt.com does, written for AI systems. Edit this line.

## Key pages

- [ChatGPT: Chat, Work, Create & Code with AI](https://chatgpt.com/): Use ChatGPT to answer questions, write, create images, complete work, and code—all in one place. Get started for free

## Contact

- [Contact](https://chatgpt.com/contact): How to reach Chatgpt
Verify it yourself
curl -sI "https://chatgpt.com/llms.txt" | head -1

This scan measures whether AI can READ you. It cannot measure whether AI RECOMMENDS you, or who it recommends instead. That requires prompt-testing against your named competitors across 6 platforms.

Fix what's broken, then measure your visibility

The AI Search Audit by Citant.ai diagnoses everything this scan found, hands you the exact fix for every critical, and measures where you stand against your named competitors across ChatGPT, Claude, Perplexity, Gemini, Copilot and Google AI Overviews. It includes a 30 minute walkthrough call.

Book the $440 AI Search Audit

The $440 is credited in full against the GEO Pilot if you sign within 30 days.