AEOSearch

Academy · Updated 2026-08-23 · 6 min read

AI crawler & citation checker: is your site in the evidence pool?

GPTBot, ClaudeBot, PerplexityBot, Google-Extended — which AI crawlers reach your pages, how to check your logs and robots.txt in minutes, and how to find out whether any engine actually cites you.

A grounded AI answer is built from pages the engine could fetch. If AI crawlers can't reach your product pages — or can, and never cite them — you are invisible in answers for reasons content work won't fix. Both conditions are checkable directly, and the checks take minutes, not a migration.

The user-agents that matter

Each vendor runs distinct crawlers for distinct purposes, and blocking one is not blocking the others. The strings to look for in logs and robots.txt:

AI crawler user-agents, by vendor and purpose
User-agentVendorWhat it does
GPTBotOpenAICrawls for model training
OAI-SearchBotOpenAICrawls for ChatGPT search results
ChatGPT-UserOpenAIFetches a page when a user's chat asks for it
ClaudeBotAnthropicCrawls for model training
Claude-UserAnthropicFetches a page on behalf of a Claude user
PerplexityBotPerplexityCrawls to index for answers
Perplexity-UserPerplexityFetches a page for a user's query
Google-ExtendedGoogleRobots token controlling use in Gemini training/grounding — not a separate crawler; Googlebot still crawls for Search and AI Overviews
CCBotCommon CrawlOpen web archive many models train on

Check 1 — your logs: are they visiting?

If you have server or CDN logs, one search answers it. Grep the last 30 days of access logs for the strings above — for example: grep -iE "gptbot|oai-searchbot|claudebot|perplexitybot|ccbot" access.log — and look at which paths they hit. Product pages being fetched by OAI-SearchBot or PerplexityBot is direct evidence you're reachable; a total absence across 30 days means either robots.txt blocks them or nothing points the crawlers at you. CDN dashboards (Cloudflare and others expose bot-traffic views) show the same thing without shell access.

Check 2 — robots.txt: are you blocking them?

Open yourdomain.com/robots.txt and read it against the table. Three findings matter. A blanket Disallow for a vendor's search or user-fetch agents (OAI-SearchBot, ChatGPT-User, PerplexityBot) removes you from those engines' grounded answers — that's usually an accident inherited from a "block AI" decision aimed at training crawlers. Blocking only training agents (GPTBot, ClaudeBot, Google-Extended, CCBot) is a legitimate policy choice, but know what it trades: absence from future training data also means weaker brand association in future models. And an empty robots.txt blocks nothing — absence of a rule is permission.

Check 3 — citations: reachable is not cited

The harder question: when engines answer your category's questions, do they ever cite your domain? Crawlability is a prerequisite, not a result — a reachable site with no citable pages still loses every answer. The only way to check is to ask the engines your buyers' questions with live search on and read the sources they return. Our audit does exactly this and reports a source map: every domain cited across all stored answers, ranked — your domain either appears in it or it doesn't.

We run this check on ourselves and publish the result: in our own 2026-08-23 baseline audit, no answer cited aeosearch.io — 4 of 5 prerequisites passed, and that one failed. The free scorecard runs the same readiness checks against your domain: crawler access, schema.org, llms.txt, and citation presence, alongside the visibility numbers themselves.

While you're in there: llms.txt and schema

Two low-cost additions ride the same deploy. An llms.txt at your root gives answer engines a curated, plain-language map of what your site is and where the substance lives — ours is at aeosearch.io/llms.txt as a working example. And schema.org structured data (Organization, Product, FAQPage on pages with real Q&A) gives extraction-driven engines typed facts instead of prose to parse. Neither guarantees a citation; both remove a reason to skip you.

Questions, answered straight

How do I know if AI tools are crawling my site?

Search your server or CDN access logs for the AI user-agent strings — GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, CCBot — and check which paths they fetch. Hits on your product pages are direct evidence you're reachable; thirty days of silence means robots.txt blocks them or nothing is leading crawlers to you.

Should I block GPTBot in robots.txt?

Blocking GPTBot only affects OpenAI's training crawler — it does not remove you from ChatGPT's live search answers, which use OAI-SearchBot and ChatGPT-User. The trade is real though: staying out of training data weakens the model's learned association with your brand. Decide it as policy, and never block the search agents by accident.

Does Google-Extended affect my Google rankings?

No. Google-Extended is a robots.txt token that controls whether your content is used for Gemini training and grounding; it is not a separate crawler and has no effect on Search indexing or ranking. Regular Googlebot continues to crawl for Search — and AI Overviews are served from ordinary Search indexing, not from Google-Extended.

How do I check if ChatGPT cites my website?

Ask it your category's buyer questions with search enabled and read the cited sources — repeatedly, because answers vary run to run. At scale, an audit does this systematically: ours stores grounded answers across five engines and reports every cited domain ranked, so "do we appear in the evidence pool" gets a measured yes or no.

Sources

  1. 1. OpenAI, "Overview of OpenAI crawlers" (bots documentation)
  2. 2. Google Search Central, "Google's crawlers and fetchers"

— The AEOSearch team

Start with the free scorecard.

Your buyers are already asking the engines. Get your grounded baseline.

$0 to start · no card required · every number traces to a stored answer