Skip to content
Search & AI DiscoveryIntermediate8 min read

How AI Crawlers Work

AI systems fetch the web for training, for live retrieval, and for answering a question you asked a moment ago. Those are three different crawlers with three different consequences.

Written by Daksh BathlaFounder — Technology, Product & Business
Published 7 August 2026 · Updated 11 August 2026

Three kinds of AI fetching

Treating "AI crawlers" as one thing leads to blocking decisions that don't do what people expect. There are three distinct behaviours, and they have different consequences for you.

What each one is doing
KindPurposeIf you block it
Training crawlerCollecting text to train future modelsYour content is less likely to be in future model weights
Retrieval/search indexBuilding an index the assistant searches when answeringYou can't be cited in AI answers
Live user-agent fetchFetching a URL because a user just asked about itThe assistant can't read your page for that user

Providers publish separate user-agent names for these, precisely so the decisions can be made separately. Check the current names in each provider's documentation rather than copying a robots.txt from a blog post — the list changes.

How they differ from a search crawler

  • They usually don't render JavaScript. Search engines will, on a second pass. A retrieval fetch typically takes the raw HTML and moves on — so client-rendered content is often simply absent
  • They extract passages, not pages. The unit that matters is a paragraph that survives being lifted out of context
  • They are far more sensitive to contradiction. Two conflicting facts about your pricing means neither is safe to state, and a competitor's clearer page gets used
  • They may not send a referrer, so the traffic is often invisible in analytics even when you influenced the answer
  • A live fetch happens once, immediately, with no second chance — a slow or erroring page is just missing from that answer

llms.txt, honestly

llms.txt is a proposed convention: a Markdown file at your site root that points AI systems at a clean, structured summary of your most useful content, so a model doesn't have to reconstruct it from navigation and marketing pages.

llms.txt
# Navital Learning > Practical lessons on building a business: business, design,> development, AI, search, and marketing. Written by the people> who build the products at Navital Labs. ## Lessons- [What Is an MVP?](https://navitallabs.com/learning/lessons/what-is-an-mvp):  The smallest thing that completely finishes one job for one person.- [What Is SEO?](https://navitallabs.com/learning/lessons/what-is-seo):  Making a site easy to crawl, understand, and trust. ## Reference- [Business Dictionary](https://navitallabs.com/learning/dictionary):  23 terms with definitions, examples, and why each matters.

The reason to add one anyway is that writing it forces a useful exercise: stating, in one file, what your site actually offers and which twenty pages matter. Most sites find that harder to answer than they expected, and the answer improves the site.

Preparing a page to be used accurately

  1. Put the content in the HTMLIf it needs JavaScript to appear, assume a retrieval fetch won't see it.
  2. Make each key claim complete in one paragraphA fact assembled across three paragraphs cannot be lifted without being reconstructed, and reconstruction is where errors enter.
  3. State facts once, consistently, everywherePricing, founding date, product names. Fix or remove stale pages that contradict the current one.
  4. Date the page, visibly and in structured dataRetrieval systems prefer content they can tell is current.
  5. Decide your crawler policy deliberately, then be consistentBlocking retrieval and hoping to be cited is wanting both sides of one decision.

Common mistakes

  • Blocking all AI user-agents and then wondering why you're never cited
  • Copying a robots.txt AI block list from a post written a year ago
  • Assuming a retrieval crawler runs your JavaScript
  • Treating llms.txt as a standard or as a permissions file
  • Leaving contradictory facts across old pages, directories, and profiles

Key takeaways

  • Training, retrieval, and live fetches are three behaviours with different consequences
  • AI crawlers mostly don't render JavaScript and extract passages rather than pages
  • llms.txt is a cheap, voluntary convention — useful, not decisive
  • Consistency and server-rendered, self-contained paragraphs are what make you usable

Try it yourself

Load your most important page with JavaScript disabled in the browser. Whatever is missing is what a retrieval crawler most likely doesn't see either — and that gap is usually larger than people expect.

TERMS USED HERE