<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Peter Panda</title>
    <description>The latest articles on DEV Community by Peter Panda (@pandawm).</description>
    <link>https://dev.to/pandawm</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4201222%2F6518f313-5e17-48b9-acce-181f192a6612.png</url>
      <title>DEV Community: Peter Panda</title>
      <link>https://dev.to/pandawm</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pandawm"/>
    <language>en</language>
    <item>
      <title>How to check whether AI crawlers can read your site (robots.txt and server logs)</title>
      <dc:creator>Peter Panda</dc:creator>
      <pubDate>Thu, 22 Oct 2026 20:56:36 +0000</pubDate>
      <link>https://dev.to/pandawm/how-to-check-whether-ai-crawlers-can-read-your-site-robotstxt-and-server-logs-3c86</link>
      <guid>https://dev.to/pandawm/how-to-check-whether-ai-crawlers-can-read-your-site-robotstxt-and-server-logs-3c86</guid>
      <description>&lt;p&gt;AI answer engines only recommend or cite what they can fetch. Before you invest in GEO, confirm the crawlers can actually read your site. Here is a quick check.&lt;/p&gt;

&lt;h2&gt;
  
  
  The user agents to know
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GPTBot&lt;/strong&gt; – OpenAI's crawler, used to collect content that may be used to train models.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ClaudeBot&lt;/strong&gt; – Anthropic's crawler.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PerplexityBot&lt;/strong&gt; – indexes pages so Perplexity can cite them in answers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google-Extended&lt;/strong&gt; – a robots.txt token (not a separate bot) that controls whether Google may use your content for Gemini and AI features.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Note that OAI-SearchBot and ChatGPT-User also exist for search and live browsing, so check them if you want ChatGPT to cite you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: read your robots.txt
&lt;/h2&gt;

&lt;p&gt;Open &lt;code&gt;https://yourdomain.com/robots.txt&lt;/code&gt;. A blanket &lt;code&gt;Disallow: /&lt;/code&gt; under &lt;code&gt;User-agent: *&lt;/code&gt;, or a rule copied from a security plugin, often blocks AI bots by accident. To explicitly allow them:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight apache"&gt;&lt;code&gt;&lt;span class="nc"&gt;User&lt;/span&gt;-agent: GPTBot
&lt;span class="nc"&gt;Allow&lt;/span&gt;: /

&lt;span class="nc"&gt;User&lt;/span&gt;-agent: ClaudeBot
&lt;span class="nc"&gt;Allow&lt;/span&gt;: /

&lt;span class="nc"&gt;User&lt;/span&gt;-agent: PerplexityBot
&lt;span class="nc"&gt;Allow&lt;/span&gt;: /

&lt;span class="nc"&gt;User&lt;/span&gt;-agent: Google-Extended
&lt;span class="nc"&gt;Allow&lt;/span&gt;: /

Sitemap: https://yourdomain.com/sitemap.xml
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you prefer to keep some areas private, add &lt;code&gt;Disallow: /private/&lt;/code&gt; inside the relevant block.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: check the server access logs
&lt;/h2&gt;

&lt;p&gt;robots.txt is a request, not enforcement, and CDNs or firewalls (Cloudflare bot rules, WAFs) can block bots before they ever see it. Your access log shows what really happens:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-Ei&lt;/span&gt; &lt;span class="s2"&gt;"GPTBot|ClaudeBot|PerplexityBot"&lt;/span&gt; /var/log/nginx/access.log | &lt;span class="nb"&gt;tail&lt;/span&gt; &lt;span class="nt"&gt;-n&lt;/span&gt; 20
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Count hits per bot and status code:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-Ei&lt;/span&gt; &lt;span class="s2"&gt;"GPTBot|ClaudeBot|PerplexityBot"&lt;/span&gt; /var/log/nginx/access.log | &lt;span class="nb"&gt;awk&lt;/span&gt; &lt;span class="s1"&gt;'{print $9}'&lt;/span&gt; | &lt;span class="nb"&gt;sort&lt;/span&gt; | &lt;span class="nb"&gt;uniq&lt;/span&gt; &lt;span class="nt"&gt;-c&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Look at the status codes. 200 means the bot read the page. 403 or 429 means your firewall or rate limiter is rejecting it. No hits at all over a couple of weeks may mean it is blocked upstream, or simply that your site is not yet discovered. Note that Google-Extended will not appear in logs, since Googlebot does the fetching.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: fix and re-test
&lt;/h2&gt;

&lt;p&gt;Whitelist the bots in your CDN or WAF, keep pages server-rendered (many AI crawlers do not run JavaScript), and make sure your sitemap lists the key pages. Then re-check the logs after a week.&lt;/p&gt;

&lt;p&gt;We wrote a longer glossary of overseas-ad and AI-search terms here: &lt;a href="https://www.pandawm.com/blog/overseas-advertising-glossary.html" rel="noopener noreferrer"&gt;https://www.pandawm.com/blog/overseas-advertising-glossary.html&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
