<?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: Reza Alpian</title>
    <description>The latest articles on DEV Community by Reza Alpian (@alpianreza).</description>
    <link>https://dev.to/alpianreza</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%2F4255262%2F2c7907b4-63f1-4525-8efd-eb6a9aacf07f.jpg</url>
      <title>DEV Community: Reza Alpian</title>
      <link>https://dev.to/alpianreza</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alpianreza"/>
    <language>en</language>
    <item>
      <title>Why ChatGPT &amp; Perplexity Ignore Newly Launched SaaS Sites — And the 6 Files That Fix It</title>
      <dc:creator>Reza Alpian</dc:creator>
      <pubDate>Fri, 20 Nov 2026 08:30:52 +0000</pubDate>
      <link>https://dev.to/alpianreza/why-chatgpt-perplexity-ignore-newly-launched-saas-sites-and-the-6-files-that-fix-it-ikd</link>
      <guid>https://dev.to/alpianreza/why-chatgpt-perplexity-ignore-newly-launched-saas-sites-and-the-6-files-that-fix-it-ikd</guid>
      <description>&lt;p&gt;Every week, hundreds of indie SaaS apps and developer tools launch with crisp Tailwind designs and fast Next.js or Astro builds—yet remain completely invisible when users ask ChatGPT, Perplexity, or Claude for recommendations in their category.&lt;/p&gt;

&lt;p&gt;The common assumption is that you need a $49/month "AI visibility tracker" to fix this. In practice, monitoring dashboards only tell you &lt;em&gt;whether&lt;/em&gt; an LLM mentioned you. Before paying for monitoring, most fresh launches fail basic technical retrieval checks that take 10 minutes to fix directly in your repository.&lt;/p&gt;

&lt;p&gt;Here are the 4 most frequent technical blockers and the exact 6 files that eliminate them.&lt;/p&gt;




&lt;h2&gt;
  
  
  1. Accidentally Blocking AI Search Bots in &lt;code&gt;robots.txt&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;Many boilerplates and WAF templates copied legacy "block all AI scrapers" snippets in 2024–2025. The problem in 2026 is that &lt;strong&gt;AI search/citation bots are now separate from model-training bots&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;AI Search &amp;amp; Live Citation Bots (you generally want &lt;code&gt;Allow: /&lt;/code&gt;):&lt;/strong&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;OAI-SearchBot&lt;/code&gt; (ChatGPT Search citations)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;ChatGPT-User&lt;/code&gt; (live retrieval when a user asks ChatGPT to check your page)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;PerplexityBot&lt;/code&gt; (Perplexity search &amp;amp; citations)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;ClaudeBot&lt;/code&gt; (Anthropic retrieval)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Model Training Bots (opt in or out independently):&lt;/strong&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;GPTBot&lt;/code&gt;, &lt;code&gt;Google-Extended&lt;/code&gt;, &lt;code&gt;Applebot-Extended&lt;/code&gt;, &lt;code&gt;Meta-ExternalAgent&lt;/code&gt;, &lt;code&gt;anthropic-ai&lt;/code&gt;, &lt;code&gt;Amazonbot&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A clean, explicit &lt;code&gt;robots.txt&lt;/code&gt; lets you keep search citations open even if you prefer to disallow training crawlers:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User-agent: *
Allow: /

# Allow AI Search &amp;amp; Citation Crawlers
User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

# Optional: Disallow training-only crawlers if desired
User-agent: GPTBot
Disallow: /

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

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;(You can paste your current &lt;code&gt;robots.txt&lt;/code&gt; into the free client-side &lt;a href="https://citeready.eiran.tech/#interactive-scanner" rel="noopener noreferrer"&gt;robots.txt AI Bot Checker&lt;/a&gt; to see all 10 bots evaluated locally with zero upload.)&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  2. Shipping Without a Valid &lt;code&gt;/llms.txt&lt;/code&gt; (&lt;code&gt;llmstxt.org&lt;/code&gt; Spec)
&lt;/h2&gt;

&lt;p&gt;Even when bots can crawl your HTML, modern landing pages wrap product facts inside nested &lt;code&gt;&amp;lt;div&amp;gt;&lt;/code&gt; grids, client-side modals, and marketing slogans.&lt;/p&gt;

&lt;p&gt;The official &lt;a href="https://llmstxt.org" rel="noopener noreferrer"&gt;&lt;code&gt;llmstxt.org&lt;/code&gt;&lt;/a&gt; convention gives AI agents a single clean Markdown index at &lt;code&gt;/llms.txt&lt;/code&gt; in a strict section order:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;H1 (&lt;code&gt;# Product Name&lt;/code&gt;)&lt;/strong&gt; — required first line.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Blockquote (&lt;code&gt;&amp;gt; 1–2 sentence factual summary&lt;/code&gt;)&lt;/strong&gt; — immediately after the H1.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Optional plain context&lt;/strong&gt; — paragraphs or bullet points, &lt;strong&gt;never&lt;/strong&gt; premature H3+ headings before link sections.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;H2 (&lt;code&gt;## Section&lt;/code&gt;) link lists&lt;/strong&gt; — &lt;code&gt;- [Page Title](https://...): concise note&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;## Optional&lt;/code&gt; section&lt;/strong&gt; — lower-priority links an agent can drop under tight context windows.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Minimal valid example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gu"&gt;# YourApp
&lt;/span&gt;
&lt;span class="ge"&gt;&amp;gt; Lightweight invoice reconciliation utility for solo consultants without monthly accounting software.
&lt;/span&gt;
&lt;span class="gu"&gt;## Core Pages
&lt;/span&gt;&lt;span class="k"&gt;- &lt;/span&gt;[Homepage](https://yourapp.com/): Overview, supported bank formats, and pricing.
&lt;span class="k"&gt;- &lt;/span&gt;[Docs](https://yourapp.com/docs): 5-minute CSV import and setup guide.

&lt;span class="gu"&gt;## Optional
&lt;/span&gt;&lt;span class="k"&gt;- &lt;/span&gt;[Full Context](https://yourapp.com/llms-full.txt): Single-fetch Markdown digest of key pages.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Pairing &lt;code&gt;/llms.txt&lt;/code&gt; with &lt;code&gt;/llms-full.txt&lt;/code&gt; (a single consolidated Markdown summary of your homepage, docs, pricing, and FAQs) makes retrieval dramatically cleaner for coding and research agents.&lt;/p&gt;




&lt;h2&gt;
  
  
  3. Missing or Broken JSON-LD Structured Data
&lt;/h2&gt;

&lt;p&gt;Unstructured marketing copy makes entity disambiguation hard. Four compact Schema.org JSON-LD blocks inside &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt; remove ambiguity for both classic search engines and LLM grounding pipelines:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;Organization&lt;/code&gt; (brand identity, canonical URL, logo)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;WebSite&lt;/code&gt; (site root identity)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;SoftwareApplication&lt;/code&gt; or &lt;code&gt;Product&lt;/code&gt; (category, OS, transparent &lt;code&gt;offers&lt;/code&gt; price/currency)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;FAQPage&lt;/code&gt; (mirroring real visible &lt;code&gt;&amp;lt;details&amp;gt;/&amp;lt;summary&amp;gt;&lt;/code&gt; FAQs on the page)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Always validate every &lt;code&gt;&amp;lt;script type="application/ld+json"&amp;gt;&lt;/code&gt; block with &lt;code&gt;JSON.parse&lt;/code&gt; during build—a single trailing comma silently invalidates the entire block.&lt;/p&gt;




&lt;h2&gt;
  
  
  4. Broken &lt;code&gt;og:image&lt;/code&gt;, Missing Canonicals, and No Pre-Deploy CI Gate
&lt;/h2&gt;

&lt;p&gt;The final silent killer right before a Product Hunt, Show HN, or Reddit launch:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;&amp;lt;meta property="og:image"&amp;gt;&lt;/code&gt; pointing to a relative path or returning HTTP 404 (killing click-through rates when your link is shared on X, Slack, or Discord).&lt;/li&gt;
&lt;li&gt;Missing &lt;code&gt;&amp;lt;link rel="canonical"&amp;gt;&lt;/code&gt; or &lt;code&gt;&amp;lt;html lang="en"&amp;gt;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Duplicate &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt; tags or missing &lt;code&gt;&amp;lt;main&amp;gt;&lt;/code&gt; / &lt;code&gt;&amp;lt;article&amp;gt;&lt;/code&gt; semantic landmarks.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Automating All 36 Checks Locally in CI
&lt;/h2&gt;

&lt;p&gt;Because I got tired of checking these manually on every launch, I built &lt;strong&gt;&lt;a href="https://citeready.eiran.tech" rel="noopener noreferrer"&gt;CiteReady&lt;/a&gt;&lt;/strong&gt; — a zero-dependency Node.js 18+ CLI (no &lt;code&gt;npm install&lt;/code&gt;, no LLM API keys) that runs 36 weighted checks across GEO, AI crawlers, JSON-LD, SEO, Open Graph, and HTML quality.&lt;/p&gt;

&lt;p&gt;You can run it against a live URL or directly against your static build folder in GitHub Actions before deploying:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;node bin/citeready.mjs --dir ./dist --url https://yourdomain.com --min-score 85
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free browser tools (no signup):&lt;/strong&gt; HTML GEO scanner, 10-bot &lt;code&gt;robots.txt&lt;/code&gt; checker, and &lt;code&gt;llms.txt&lt;/code&gt; spec validator at &lt;a href="https://citeready.eiran.tech" rel="noopener noreferrer"&gt;citeready.eiran.tech&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Free Lite CLI ($0 ZIP):&lt;/strong&gt; Runs all 36 checks in your terminal.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pro CLI ($19 one-time):&lt;/strong&gt; Multi-page crawl + auto-generates all 6 fix files (&lt;code&gt;llms.txt&lt;/code&gt;, &lt;code&gt;llms-full.txt&lt;/code&gt;, &lt;code&gt;robots.txt&lt;/code&gt;, &lt;code&gt;jsonld-snippets.html&lt;/code&gt;, &lt;code&gt;head-meta-patch.html&lt;/code&gt;, &lt;code&gt;nextjs-metadata.ts&lt;/code&gt;) + standalone white-label HTML/PDF report.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Which AI crawler policy are you using on your projects right now—allowing search bots while blocking training bots, or allowing both?&lt;/p&gt;

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