← Class Library
0 / 8 lessons

Check That AI Can Reach Your Site

20 min

What you'll be able to do

  • Find your robots.txt file and understand what it tells AI crawlers
  • Know which bots you must allow to be cited, and which ones are a business decision
  • Make sure your site is indexed in Bing, not just Google

▶ Video coming soon

Walkthrough for this lesson

KEY TAKEAWAYS

  • If an AI engine's crawler can't reach your site, nothing else in this course matters
  • There are three families of AI bots: retrieval crawlers, user-triggered fetchers, and training collectors. They are not the same decision
  • Allow the retrieval and fetch bots. Blocking those removes you from the answers entirely
  • ChatGPT and Copilot lean on Bing's index, so register with Bing Webmaster Tools even though it feels dated
  • llms.txt is ignored by every major engine today. Skip it and spend the time on your content

The one thing that can undo everything else

Every AI engine reaches your website through an automated visitor called a crawler or bot. Your site can quietly tell those bots to go away, often without anyone intending it. Security plugins, a nervous web developer, a hosting provider's default setting, or a well-meaning “block AI scrapers” checkbox can all shut the door. It is worth twenty minutes to check, because if the door is shut, the best-written page in your industry will never be quoted.

How to find your robots.txt

Type your website address into a browser and add /robots.txt at the end, like yourbusiness.com/robots.txt. It's a plain text file that every site has, and it lists which automated visitors are welcome. Select all the text and copy it. If you get a “not found” page, that usually means nothing is being blocked, which is fine, though the prompt below will tell you what's worth adding.

The three families of AI bots

  • Retrieval crawlers build the index the AI searches when answering. These include OAI-SearchBot (ChatGPT search), PerplexityBot, Claude-SearchBot, plus Bingbot and Googlebot. These are your citation pipeline.
  • User-triggered fetchers show up when a real person asks an assistant to read a specific page: ChatGPT-User, Perplexity-User, Claude-User. Someone is actively looking at you when these visit.
  • Training collectors gather text used to train future models: GPTBot, ClaudeBot, CCBot, Google-Extended, Applebot-Extended. These feed the model's long-term background knowledge of your brand, not today's answer.

Which ones to allow

For a small business whose goal is to be found, the answer for the first two families is straightforward: allow them. Blocking a retrieval crawler or a user fetcher removes you from the fastest-growing discovery channel there is, which is precisely the opposite of what you're here to do. Big news publishers often block these bots deliberately, because their content is their product and they want licensing leverage. That calculation does not apply to a business that wants customers to find it.

Training collectors are a genuine business decision, not a visibility requirement. Allowing them means your content may inform how future models describe your industry and your brand, even without a link. Blocking them is a reasonable stance if you'd rather not contribute your writing to model training. Either way, it will not remove you from tomorrow's ChatGPT answer, and blocking is forward-looking only: it does nothing about content that has already been collected.

Don't forget Bing

Most owners haven't thought about Bing in a decade, and that's a mistake now. ChatGPT and Microsoft Copilot lean on Microsoft's index, so if Bing hasn't properly indexed your site, a huge slice of AI search simply can't see you. Bing Webmaster Tools is free, takes a few minutes to set up, and lets you submit your sitemap directly. Do the same with Google Search Console if you haven't already.

What about llms.txt?

You may run into advice telling you to add a file called llms.txt to help AI understand your site. As of today, no major AI engine uses it. Google has said plainly that it does not support it and has no plans to, and server logs show the engines don't even check whether the file exists. One study of about 300,000 domains found roughly one in ten had added it, with no measurable effect on citations. It costs almost nothing to add, but it will not help, so don't let anyone sell it to you as an AEO service.

Step by step

  • Visit yourbusiness.com/robots.txt and copy everything you see.
  • Run the AI Crawler Access Check prompt below, pasting the file in where it asks.
  • Read the bot-by-bot table it gives back, and decide your position on the training bots.
  • If changes are needed, send the corrected file it produces to whoever manages your website. This is usually a two-minute edit.
  • Set up Bing Webmaster Tools and submit your sitemap while you're at it.

Put it into practice

Pull up your robots.txt, run the crawler access prompt, and either confirm you're wide open to the retrieval bots or send the corrected file to your web person today.

PROMPTS FOR THIS LESSON

Copy these into your AI tool. They auto-fill with your business profile. Browse the full library.

OperationsQuarterly

AI Crawler Access Check (robots.txt)

Paste your robots.txt and get a bot-by-bot report of which AI crawlers can reach your site, what it costs you, and a corrected file to hand your web person.

OperationsQuarterly

AI Crawler Access Check (robots.txt)

You are a technical SEO and AEO auditor. I want to know whether AI search engines are allowed to reach my website. My website: [WEBSITE URL] HERE IS MY robots.txt FILE: [PASTE THE FULL CONTENTS OF yourwebsite.com/robots.txt HERE. If you got a "not found" page, write NOT FOUND instead.] Analyze ONLY what is in the file above. Do not guess about anything the file does not say, and do not assume rules that are not written there. SECTION 1: BOT-BY-BOT TABLE A table with one row per crawler below. Columns: bot name, what it does, which AI engine it feeds, and whether my file currently ALLOWS or BLOCKS it (say "allowed by default" where the file simply does not mention it). Retrieval crawlers (these build the index the AI searches when answering): - OAI-SearchBot (ChatGPT search) - PerplexityBot - Claude-SearchBot - Bingbot - Googlebot User-triggered fetchers (a real person asked an assistant to read a page): - ChatGPT-User - Perplexity-User - Claude-User Training collectors (they gather text for training future models): - GPTBot - ClaudeBot - CCBot - Google-Extended - Applebot-Extended SECTION 2: WHAT THIS COSTS ME For anything currently blocked, explain in one plain-English sentence what I lose. Be direct: blocking a retrieval crawler or a user fetcher removes me from those AI answers entirely. SECTION 3: MY RECOMMENDATION - State clearly that the retrieval crawlers and user fetchers should be allowed for a business that wants to be found. - Treat the training collectors as a genuine business decision, not a visibility requirement. Give me two sentences of pros and cons so I can decide, and note that blocking them only affects future collection. - Flag any other problem you can see in the file, such as a blanket rule that blocks everything, or important pages being disallowed. SECTION 4: CORRECTED FILE Give me a complete, copy-paste-ready robots.txt with the fixes applied, keeping any legitimate existing rules intact. Add a short comment line above each change explaining what it does, so my web developer understands it. SECTION 5: WHAT NOT TO BOTHER WITH Confirm in two sentences that llms.txt is not currently read by any major AI engine, so I should not spend time or money on it.
After you run this: Send the corrected robots.txt to whoever manages your website, it is usually a two-minute edit. Then set up Bing Webmaster Tools and submit your sitemap, because ChatGPT and Copilot lean on Bing's index.

What's next

The door is open. Next you'll find out whether what's behind it is actually worth quoting.