<?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: Shahid Saleem</title>
    <description>The latest articles on DEV Community by Shahid Saleem (@shahidsaleem_).</description>
    <link>https://dev.to/shahidsaleem_</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%2F4161519%2F031234cb-e29a-4ecf-b80f-862223ca825e.png</url>
      <title>DEV Community: Shahid Saleem</title>
      <link>https://dev.to/shahidsaleem_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shahidsaleem_"/>
    <language>en</language>
    <item>
      <title>Why modern sites are invisible to AI search engines (and how to test raw HTML)</title>
      <dc:creator>Shahid Saleem</dc:creator>
      <pubDate>Sun, 04 Oct 2026 12:07:42 +0000</pubDate>
      <link>https://dev.to/shahidsaleem_/why-modern-sites-are-invisible-to-ai-search-engines-and-how-to-test-raw-html-2p7e</link>
      <guid>https://dev.to/shahidsaleem_/why-modern-sites-are-invisible-to-ai-search-engines-and-how-to-test-raw-html-2p7e</guid>
      <description>&lt;p&gt;Most modern web applications look great in the browser. But if you rely on client-side rendering or heavy hydration, AI search engines—like OpenAI's OAI-SearchBot, PerplexityBot, and Claude-SearchBot—might be seeing a completely blank page.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Headless Bot Bottleneck
&lt;/h3&gt;

&lt;p&gt;Unlike Google's full-rendering web crawlers, AI search engines crawl on strict compute and latency budgets. When an LLM crawler fetches your URL:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It frequently captures &lt;strong&gt;raw HTML&lt;/strong&gt; without waiting for client-side JavaScript to execute.&lt;/li&gt;
&lt;li&gt;It scans for structured metadata (&lt;code&gt;schema.jsonld&lt;/code&gt;) and clean text blocks directly in the initial response.&lt;/li&gt;
&lt;li&gt;It inspects your &lt;code&gt;robots.txt&lt;/code&gt; for explicit bot permissions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your content only lives after hydration, answer engines will silently skip citing your domain.&lt;/p&gt;

&lt;h3&gt;
  
  
  How to Inspect What Bots See
&lt;/h3&gt;

&lt;p&gt;You can run a quick terminal test using &lt;code&gt;curl&lt;/code&gt; with a bot user-agent to see your raw server response:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-A&lt;/span&gt; &lt;span class="s2"&gt;"OAI-SearchBot"&lt;/span&gt; &lt;span class="nt"&gt;-L&lt;/span&gt; &lt;span class="s2"&gt;"[https://usecrawlable.com](https://usecrawlable.com)"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If that command returns empty &lt;code&gt;&amp;lt;div&amp;gt;&lt;/code&gt; containers or boilerplate loading states, bots cannot cite you.&lt;/p&gt;

&lt;p&gt;We built an open diagnostic engine called &lt;a href="https://usecrawlable.com" rel="noopener noreferrer"&gt;Crawlable&lt;/a&gt; to automate this. It crawls up to 40 pages without JavaScript, evaluates token density and bot policies, and generates production Fix Kits (&lt;code&gt;robots.txt&lt;/code&gt;, &lt;code&gt;llms.txt&lt;/code&gt;, and JSON-LD).&lt;/p&gt;

&lt;p&gt;How is your engineering team preparing for Generative Engine Optimization (GEO)?&lt;/p&gt;

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