Skip to content
Found in AI
ENESStart tracking

Technical foundations · 7 min read

Making Your Website Readable to AI Crawlers

If an AI tool cannot fetch and read your pages, nothing else in these guides matters. This is the technical check to run first.

The short answer

AI tools reach your site through crawlers such as OpenAI's GPTBot and OAI-SearchBot, Anthropic's ClaudeBot and PerplexityBot, plus Googlebot and Bingbot. Check that robots.txt does not block the ones you want, that your firewall or bot protection is not refusing them, and that your key text is in the HTML the server sends rather than added later by JavaScript.

Know which crawlers you are dealing with

The major AI companies publish the names their crawlers use, and several run more than one. OpenAI documents GPTBot (used to gather training data), OAI-SearchBot (used for search features in ChatGPT) and ChatGPT-User (used when a person asks ChatGPT to open a page). Anthropic documents ClaudeBot along with separate agents for search and for user-requested fetches. Perplexity documents PerplexityBot and Perplexity-User.

Google AI Overviews are built on Google Search, so the crawler that matters there is ordinary Googlebot. Google also documents a separate control called Google-Extended, which governs whether your content is used to improve Gemini models; Google states it does not affect inclusion in Search. Microsoft's Copilot draws on Bing, so Bingbot matters too.

  • OpenAI: GPTBot, OAI-SearchBot, ChatGPT-User
  • Anthropic: ClaudeBot and its search and user agents
  • Perplexity: PerplexityBot, Perplexity-User
  • Google: Googlebot (Search and AI Overviews), Google-Extended (Gemini training control)
  • Microsoft: Bingbot

Read your robots.txt with fresh eyes

Open yoursite.com/robots.txt in a browser. Look for any 'User-agent' line that names one of the crawlers above followed by 'Disallow: /'. Look also for a blanket 'User-agent: *' with 'Disallow: /', which blocks every crawler that respects the file. Old staging rules and copied templates are a common cause.

Blocking is a legitimate choice. Some businesses decide they do not want their content used for training and block GPTBot or Google-Extended while still allowing the search crawlers. That split is possible precisely because the companies separate the agents. What you want to avoid is blocking by accident, or blocking a search crawler while you are hoping to appear in that tool's answers.

Check the layer below robots.txt

A robots.txt file can say 'allow' while your hosting provider or security service refuses the request anyway. Bot protection products, firewalls and some CDN settings challenge or block unfamiliar crawlers by default. The crawler never gets past the challenge page, and nothing in your analytics tells you.

If you use a service like this, look for a setting covering verified or known bots, and review whether AI crawlers are included. Your server logs, or your host's log viewer, will show requests from these user agents and the status codes they received. A run of 403 responses is a clear sign something is in the way.

Put the words in the HTML

Many crawlers read the HTML your server sends and do little or no JavaScript processing. If your service descriptions, prices, hours or reviews only appear after a script runs in the browser, a crawler may see an empty shell. Googlebot does render JavaScript, but not every AI crawler is documented as doing so, and it is safer not to depend on it.

A quick test: view the page source (not the inspector, the raw source) and search for a sentence you can see on the page. If it is missing, that text is being added by JavaScript. Content inside tabs, accordions or 'read more' toggles is usually fine as long as it is present in the source.

llms.txt: useful, but not a switch

llms.txt is a proposed convention: a plain text file at the root of your site that summarises what the site is and links to its most useful pages, written for language models. It is cheap to add and harmless. It is also a community proposal rather than an adopted standard, and there is little public confirmation that the major AI tools read it when answering questions.

If you publish one, keep it accurate and short, and make sure it agrees with your homepage. Do not treat it as a substitute for readable pages and an open robots.txt.

Then watch what changes

Fixing a blocked crawler does not change answers overnight. Crawlers revisit on their own schedules, and models update on theirs. Found in AI needs nothing installed on your site; it reads what the tools answer. Run your tracked questions before and after a fix, and look at the trend rather than a single scan.

Your checklist

  1. Open your robots.txt and search for GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and 'Disallow: /'
  2. Decide deliberately which crawlers to allow, separating training crawlers from search crawlers
  3. Check your firewall, CDN or bot protection settings for rules that challenge AI crawlers
  4. Look in your server logs for these user agents and the status codes they received
  5. View the raw source of your top five pages and confirm the main text is there
  6. If you add llms.txt, keep it short, accurate and consistent with your homepage
  7. Note the date of any fix so you can compare scans before and after

Common questions

If I block GPTBot, will ChatGPT stop mentioning me?

Not necessarily. OpenAI documents GPTBot as its training crawler and OAI-SearchBot as the one used for ChatGPT's search features, so they can be controlled separately. Check OpenAI's current documentation before deciding.

Does blocking Google-Extended remove me from AI Overviews?

Google states that Google-Extended does not affect inclusion in Google Search. AI Overviews are part of Search and use Googlebot.

Do I need an llms.txt file?

It does no harm and takes minutes, but it is not a requirement and adoption by AI tools is unclear. Readable pages and an open robots.txt come first.

My site is built with a JavaScript framework. Is that a problem?

Only if the text arrives after the page loads. Many frameworks can render on the server. Check the raw page source for your main content.

Find out if you are found in AI.

Tracking starts at $149 a month, on the website you already have. You do not need a new site.