<?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: Ed Grows</title>
    <description>The latest articles on DEV Community by Ed Grows (@edgrows).</description>
    <link>https://dev.to/edgrows</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%2F4207042%2Ff7203fab-b287-4198-9db1-deae5ba24218.png</url>
      <title>DEV Community: Ed Grows</title>
      <link>https://dev.to/edgrows</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/edgrows"/>
    <language>en</language>
    <item>
      <title>How to add SoftwareApplication JSON-LD to a Next.js app (typed, escaped and tested)</title>
      <dc:creator>Ed Grows</dc:creator>
      <pubDate>Mon, 09 Nov 2026 13:22:45 +0000</pubDate>
      <link>https://dev.to/edgrows/how-to-add-softwareapplication-json-ld-to-a-nextjs-app-typed-escaped-and-tested-56h1</link>
      <guid>https://dev.to/edgrows/how-to-add-softwareapplication-json-ld-to-a-nextjs-app-typed-escaped-and-tested-56h1</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; render a &lt;code&gt;&amp;lt;script type="application/ld+json"&amp;gt;&lt;/code&gt; tag from your &lt;code&gt;page.tsx&lt;/code&gt;, build the object from the same data the page shows, escape &lt;code&gt;&amp;lt;&lt;/code&gt; before you inject it, and type it with &lt;code&gt;schema-dts&lt;/code&gt;. For Google's software app rich result you need &lt;code&gt;name&lt;/code&gt;, &lt;code&gt;offers.price&lt;/code&gt; and either &lt;code&gt;aggregateRating&lt;/code&gt; or &lt;code&gt;review&lt;/code&gt;. With no real ratings, ship the markup anyway and leave the rating fields out.&lt;/p&gt;

&lt;p&gt;I run a small software directory, &lt;a href="https://www.website.show" rel="noopener noreferrer"&gt;website.show&lt;/a&gt;, where every product page carries a &lt;code&gt;SoftwareApplication&lt;/code&gt; block. Most of what follows comes from wiring that up in the App Router and from fixing the mistakes I made on the way.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is SoftwareApplication JSON-LD?
&lt;/h2&gt;

&lt;p&gt;It is a schema.org type that describes an app: its name, what it does, what it costs, which platform it runs on and where to get it. JSON-LD is the format Google recommends for structured data, because it sits in one script tag and does not touch your markup.&lt;/p&gt;

&lt;p&gt;There is also &lt;code&gt;WebApplication&lt;/code&gt;, a subtype for software that runs in the browser. Either works for a SaaS. The full property list is on &lt;a href="https://schema.org/SoftwareApplication" rel="noopener noreferrer"&gt;schema.org/SoftwareApplication&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does Google require for the software app rich result?
&lt;/h2&gt;

&lt;p&gt;Google's &lt;a href="https://developers.google.com/search/docs/appearance/structured-data/software-app" rel="noopener noreferrer"&gt;software app documentation&lt;/a&gt; lists three required pieces:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Property&lt;/th&gt;
&lt;th&gt;Required?&lt;/th&gt;
&lt;th&gt;Notes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;name&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;The app's name&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;offers.price&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Use &lt;code&gt;0&lt;/code&gt; for a free app; add &lt;code&gt;priceCurrency&lt;/code&gt; when the price is above 0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;aggregateRating&lt;/code&gt; or &lt;code&gt;review&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;One of them&lt;/td&gt;
&lt;td&gt;Must follow the review snippet rules&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;applicationCategory&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Recommended&lt;/td&gt;
&lt;td&gt;One of Google's fixed values, like &lt;code&gt;BusinessApplication&lt;/code&gt; or &lt;code&gt;DeveloperApplication&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;operatingSystem&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Recommended&lt;/td&gt;
&lt;td&gt;For a web app, &lt;code&gt;Web&lt;/code&gt; or a browser list is common&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The rating line is where most SaaS sites go wrong. The &lt;a href="https://developers.google.com/search/docs/appearance/structured-data/review-snippet" rel="noopener noreferrer"&gt;review snippet guidelines&lt;/a&gt; say ratings must come from real users and be visible to them on the page. A hard-coded &lt;code&gt;4.9&lt;/code&gt; that nobody gave is the fastest way to a manual action. If you have no ratings, drop the field. You will not get stars, but the rest of the markup still tells search engines and AI crawlers what the page is about.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add JSON-LD in the Next.js App Router?
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://nextjs.org/docs/app/guides/json-ld" rel="noopener noreferrer"&gt;Next.js JSON-LD guide&lt;/a&gt; recommends a plain script tag in &lt;code&gt;layout.tsx&lt;/code&gt; or &lt;code&gt;page.tsx&lt;/code&gt;. There is no special Metadata API field for it.&lt;/p&gt;

&lt;p&gt;Here is a version for a product page. It builds the object from the same record the page renders, so the markup never drifts from what users see.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="c1"&gt;// app/product/[slug]/page.tsx&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;SoftwareApplication&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;WithContext&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;schema-dts&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;getProduct&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@/lib/products&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;ProductPage&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="nx"&gt;params&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;params&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;string&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;})&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;slug&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;params&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;product&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;getProduct&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;jsonLd&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;WithContext&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nx"&gt;SoftwareApplication&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@context&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;https://schema.org&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@type&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;SoftwareApplication&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;description&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tagline&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;website&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;applicationCategory&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;googleCategory&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="c1"&gt;// e.g. "DeveloperApplication"&lt;/span&gt;
    &lt;span class="na"&gt;operatingSystem&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Web&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;offers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@type&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Offer&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;price&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;price&lt;/span&gt; &lt;span class="o"&gt;??&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;priceCurrency&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;USD&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;...(&lt;/span&gt;&lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;ratingCount&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;aggregateRating&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@type&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;AggregateRating&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;ratingValue&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;ratingAverage&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;ratingCount&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;ratingCount&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;}),&lt;/span&gt;
  &lt;span class="p"&gt;};&lt;/span&gt;

  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;main&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;script&lt;/span&gt;
        &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"application/ld+json"&lt;/span&gt;
        &lt;span class="na"&gt;dangerouslySetInnerHTML&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
          &lt;span class="na"&gt;__html&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;jsonLd&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sr"&gt;/&amp;lt;/g&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="se"&gt;\\&lt;/span&gt;&lt;span class="s2"&gt;u003c&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
        &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;h1&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;product&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;h1&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="cm"&gt;/* the rest of the page */&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;main&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three details in that snippet are easy to miss.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The &lt;code&gt;.replace(/&amp;lt;/g, "\\u003c")&lt;/code&gt;.&lt;/strong&gt; &lt;code&gt;JSON.stringify&lt;/code&gt; does not escape HTML. If a product description contains &lt;code&gt;&amp;lt;/script&amp;gt;&lt;/code&gt;, it closes your tag early and whatever follows runs as markup. The Next.js docs call this out as an XSS risk. Swapping &lt;code&gt;&amp;lt;&lt;/code&gt; for its unicode escape keeps the JSON valid and the tag closed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The conditional rating.&lt;/strong&gt; The spread only adds &lt;code&gt;aggregateRating&lt;/code&gt; when real ratings exist. No ratings, no field, no fake stars.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;schema-dts&lt;/code&gt; types.&lt;/strong&gt; &lt;code&gt;WithContext&amp;lt;SoftwareApplication&amp;gt;&lt;/code&gt; catches typos like &lt;code&gt;aplicationCategory&lt;/code&gt; at build time. Install it with &lt;code&gt;npm i -D schema-dts&lt;/code&gt;; it ships types only, nothing reaches the client bundle.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Which applicationCategory should you use?
&lt;/h2&gt;

&lt;p&gt;Google accepts a fixed list. The ones that fit most SaaS products:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;DeveloperApplication&lt;/code&gt; for dev tools, APIs, CLIs&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;BusinessApplication&lt;/code&gt; for CRM, invoicing, analytics, most B2B&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;DesignApplication&lt;/code&gt; for design and image tools&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;UtilitiesApplication&lt;/code&gt; for small single-purpose tools&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;FinanceApplication&lt;/code&gt;, &lt;code&gt;EducationalApplication&lt;/code&gt;, &lt;code&gt;HealthApplication&lt;/code&gt; for those niches&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A free-text value like &lt;code&gt;"Productivity"&lt;/code&gt; or &lt;code&gt;"AI tool"&lt;/code&gt; is valid schema.org, but Google treats it as unknown. If your app has its own category names, keep them for the UI and map them to Google's list in one small function:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;GOOGLE_CATEGORY&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Record&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kr"&gt;string&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kr"&gt;string&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;developer-tools&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;DeveloperApplication&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;marketing&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;BusinessApplication&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;design&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;DesignApplication&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;finance&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;FinanceApplication&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;googleCategory&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;string&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;GOOGLE_CATEGORY&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;??&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;UtilitiesApplication&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Should the homepage and product pages use the same type?
&lt;/h2&gt;

&lt;p&gt;Not always. A rough rule:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your own SaaS homepage:&lt;/strong&gt; &lt;code&gt;SoftwareApplication&lt;/code&gt; (or &lt;code&gt;WebApplication&lt;/code&gt;) describing your product, plus an &lt;code&gt;Organization&lt;/code&gt; block for the company.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A page that lists many apps&lt;/strong&gt; (a directory, a marketplace category): an &lt;code&gt;ItemList&lt;/code&gt; of links, not one big &lt;code&gt;SoftwareApplication&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A page about one app you do not own&lt;/strong&gt; (a review, a directory listing): &lt;code&gt;SoftwareApplication&lt;/code&gt; is fine, with &lt;code&gt;url&lt;/code&gt; pointing to the app's own site.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Add a &lt;code&gt;BreadcrumbList&lt;/code&gt; on deep pages too. It is cheap, and it often shows in results even when nothing else does.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you test SoftwareApplication markup?
&lt;/h2&gt;

&lt;p&gt;Check it at three levels, from fastest to slowest.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Unit test the object.&lt;/strong&gt; Your JSON-LD is a plain object, so test it like one. Assert that &lt;code&gt;name&lt;/code&gt; and &lt;code&gt;offers.price&lt;/code&gt; exist, and that &lt;code&gt;aggregateRating&lt;/code&gt; is absent when &lt;code&gt;ratingCount&lt;/code&gt; is 0. This catches regressions on every commit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validate the syntax.&lt;/strong&gt; Paste the rendered HTML or a URL into the &lt;a href="https://validator.schema.org/" rel="noopener noreferrer"&gt;Schema Markup Validator&lt;/a&gt;. It checks against schema.org itself, so it flags unknown properties and wrong types.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check Google's view.&lt;/strong&gt; Google's Rich Results Test, linked from the &lt;a href="https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data" rel="noopener noreferrer"&gt;structured data introduction&lt;/a&gt;, shows whether the page is eligible for the software app result and lists missing required fields. Without ratings it will tell you the rating is missing. That is expected.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A minimal Vitest check:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;describe&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;it&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;expect&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;vitest&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;buildJsonLd&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@/lib/jsonld&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="nf"&gt;describe&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;SoftwareApplication JSON-LD&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;it&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;never invents ratings&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;ld&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;buildJsonLd&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Demo&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;price&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;ratingCount&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
    &lt;span class="nf"&gt;expect&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;ld&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;toBe&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Demo&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="nf"&gt;expect&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;ld&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;offers&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;toMatchObject&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;price&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
    &lt;span class="nf"&gt;expect&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;ld&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nx"&gt;not&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toHaveProperty&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;aggregateRating&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="nf"&gt;it&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;escapes closing script tags&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;html&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;serialize&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;description&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;&amp;lt;/script&amp;gt;&amp;lt;b&amp;gt;x&amp;lt;/b&amp;gt;&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
    &lt;span class="nf"&gt;expect&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;html&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nx"&gt;not&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toContain&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To make the second test work, move the &lt;code&gt;JSON.stringify(...).replace(...)&lt;/code&gt; call into a small &lt;code&gt;serialize()&lt;/code&gt; helper instead of inlining it in JSX.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Copying a generator block with a rating in it.&lt;/strong&gt; Remove any rating you cannot back with real reviews shown on the page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Markup that disagrees with the page.&lt;/strong&gt; A price of 0 in JSON-LD and "$29/month" in the pricing table is a mismatch. Build both from one source.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rendering JSON-LD only on the client.&lt;/strong&gt; If the script is added by a client component after hydration, crawlers that do not run JavaScript never see it. Keep it in a server component.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One giant block for a listing page.&lt;/strong&gt; Ten apps on a category page should be an &lt;code&gt;ItemList&lt;/code&gt;, not ten &lt;code&gt;SoftwareApplication&lt;/code&gt; objects that all claim to be the main entity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forgetting &lt;code&gt;priceCurrency&lt;/code&gt; on paid apps.&lt;/strong&gt; Google will guess, and it can guess wrong.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do I need JSON-LD if I already have good meta tags?&lt;/strong&gt;&lt;br&gt;
They do different jobs. Meta tags describe the page; JSON-LD describes the thing the page is about. Search engines and AI assistants use the second to understand entities.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I use the Next.js Metadata API for JSON-LD?&lt;/strong&gt;&lt;br&gt;
No. The current recommendation is a script tag in the page or layout.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SoftwareApplication or WebApplication?&lt;/strong&gt;&lt;br&gt;
Both are accepted. &lt;code&gt;WebApplication&lt;/code&gt; is more precise for a browser-only SaaS. Pick one and stay consistent across pages.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will this get me review stars?&lt;/strong&gt;&lt;br&gt;
Only with real ratings that follow Google's review snippet rules. Without them you still get a clearer entity for search and AI answers, just no stars.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where can I read more about the rating rules?&lt;/strong&gt;&lt;br&gt;
I wrote up &lt;a href="https://www.website.show/blog/softwareapplication-schema" rel="noopener noreferrer"&gt;the rating rules and a full SaaS example&lt;/a&gt; in more detail, including which fields to leave out when you are just starting.&lt;/p&gt;

</description>
      <category>nextjs</category>
      <category>seo</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Is your site invisible to ChatGPT? robots.txt, llms.txt and JavaScript checks for AI crawlers</title>
      <dc:creator>Ed Grows</dc:creator>
      <pubDate>Sun, 25 Oct 2026 17:22:03 +0000</pubDate>
      <link>https://dev.to/edgrows/is-your-site-invisible-to-chatgpt-robotstxt-llmstxt-and-javascript-checks-for-ai-crawlers-57k5</link>
      <guid>https://dev.to/edgrows/is-your-site-invisible-to-chatgpt-robotstxt-llmstxt-and-javascript-checks-for-ai-crawlers-57k5</guid>
      <description>&lt;p&gt;If ChatGPT, Claude or Perplexity never mention your product, the reason is often boring and fixable: the assistant cannot read your homepage in the first place. Before you think about content strategy for AI search, check three things on the technical side. Can AI crawlers fetch the page? Does the page contain real text without JavaScript? Does it say clearly what the product is?&lt;/p&gt;

&lt;p&gt;I run &lt;a href="https://www.website.show" rel="noopener noreferrer"&gt;website.show&lt;/a&gt;, a small directory of software built by indie makers, and every listing there gets an automated check of exactly these signals. After reading a lot of these reports, the same handful of mistakes keeps showing up. Here they are, with the fix for each.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which AI crawlers should you allow in robots.txt?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; allow the search bots if you want to be quoted in AI answers. Decide separately about the training bots.&lt;/p&gt;

&lt;p&gt;There are two families of AI crawlers, and they do different jobs:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;th&gt;OpenAI&lt;/th&gt;
&lt;th&gt;Anthropic&lt;/th&gt;
&lt;th&gt;Perplexity / Google&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Fetch pages for answers&lt;/td&gt;
&lt;td&gt;OAI-SearchBot&lt;/td&gt;
&lt;td&gt;Claude-SearchBot&lt;/td&gt;
&lt;td&gt;PerplexityBot&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Collect pages for training&lt;/td&gt;
&lt;td&gt;GPTBot&lt;/td&gt;
&lt;td&gt;ClaudeBot&lt;/td&gt;
&lt;td&gt;Google-Extended&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Blocking a search bot can keep your pages out of that assistant's answers. Blocking a training bot keeps new pages out of future models and leaves the answers alone. Google says Google-Extended does not affect Google Search, and Googlebot itself should never be on a block list: it is how pages reach Google Search, AI Overviews included.&lt;/p&gt;

&lt;p&gt;If you are not sure what your robots.txt actually does, paste your domain into an &lt;a href="https://www.website.show/tools/ai-crawler-checker" rel="noopener noreferrer"&gt;AI crawler checker&lt;/a&gt;. It reads only robots.txt and shows which bots get in.&lt;/p&gt;

&lt;h2&gt;
  
  
  The robots.txt group trap most people fall into
&lt;/h2&gt;

&lt;p&gt;This one surprised me the first time. Under RFC 9309, the robots.txt standard, a crawler follows &lt;strong&gt;only&lt;/strong&gt; the group that names it. It falls back to &lt;code&gt;User-agent: *&lt;/code&gt; only when no group names it.&lt;/p&gt;

&lt;p&gt;So this looks harmless:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight conf"&gt;&lt;code&gt;&lt;span class="n"&gt;User&lt;/span&gt;-&lt;span class="n"&gt;agent&lt;/span&gt;: *
&lt;span class="n"&gt;Disallow&lt;/span&gt;: /&lt;span class="n"&gt;admin&lt;/span&gt;/
&lt;span class="n"&gt;Disallow&lt;/span&gt;: /&lt;span class="n"&gt;api&lt;/span&gt;/

&lt;span class="n"&gt;User&lt;/span&gt;-&lt;span class="n"&gt;agent&lt;/span&gt;: &lt;span class="n"&gt;OAI&lt;/span&gt;-&lt;span class="n"&gt;SearchBot&lt;/span&gt;
&lt;span class="n"&gt;Allow&lt;/span&gt;: /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;But now OAI-SearchBot ignores the &lt;code&gt;*&lt;/code&gt; group completely, which means &lt;code&gt;/admin/&lt;/code&gt; and &lt;code&gt;/api/&lt;/code&gt; are open to it. You wanted to welcome one bot and you exposed your private paths to it instead.&lt;/p&gt;

&lt;p&gt;The safer pattern: let the bots you allow fall through to &lt;code&gt;*&lt;/code&gt;, and give a group only to the bots you block:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight conf"&gt;&lt;code&gt;&lt;span class="n"&gt;User&lt;/span&gt;-&lt;span class="n"&gt;agent&lt;/span&gt;: *
&lt;span class="n"&gt;Disallow&lt;/span&gt;: /&lt;span class="n"&gt;admin&lt;/span&gt;/
&lt;span class="n"&gt;Disallow&lt;/span&gt;: /&lt;span class="n"&gt;api&lt;/span&gt;/

&lt;span class="n"&gt;User&lt;/span&gt;-&lt;span class="n"&gt;agent&lt;/span&gt;: &lt;span class="n"&gt;GPTBot&lt;/span&gt;
&lt;span class="n"&gt;User&lt;/span&gt;-&lt;span class="n"&gt;agent&lt;/span&gt;: &lt;span class="n"&gt;ClaudeBot&lt;/span&gt;
&lt;span class="n"&gt;User&lt;/span&gt;-&lt;span class="n"&gt;agent&lt;/span&gt;: &lt;span class="n"&gt;Google&lt;/span&gt;-&lt;span class="n"&gt;Extended&lt;/span&gt;
&lt;span class="n"&gt;Disallow&lt;/span&gt;: /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That file keeps AI search bots able to read the site and keeps the training bots out. If you would rather not write it by hand, a &lt;a href="https://www.website.show/tools/robots-txt-generator" rel="noopener noreferrer"&gt;robots.txt generator for AI crawlers&lt;/a&gt; builds this structure for you and runs in the browser, so nothing you type is sent anywhere.&lt;/p&gt;

&lt;p&gt;Two more rules from the standard worth knowing: when an Allow and a Disallow both match, the longer rule wins and Allow wins a tie. A missing robots.txt means every crawler may read the site, while a server error on robots.txt makes crawlers treat the whole site as closed. That last one bites people with misconfigured hosting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does your page have text without JavaScript?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; if your homepage builds its text on the client, some crawlers see an empty page.&lt;/p&gt;

&lt;p&gt;Not every crawler runs JavaScript. A single-page app that ships a &lt;code&gt;&amp;lt;div id="root"&amp;gt;&amp;lt;/div&amp;gt;&lt;/code&gt; and fills it later can look blank to them. Quick test:&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;-s&lt;/span&gt; https://yoursite.com | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; &lt;span class="s2"&gt;"your main headline"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the headline is not in the raw HTML, server-render or pre-render at least the homepage. For most frameworks that is a config flag, not a rewrite.&lt;/p&gt;

&lt;h2&gt;
  
  
  robots.txt is not the whole story
&lt;/h2&gt;

&lt;p&gt;Even with a clean robots.txt, a bot can be turned away earlier:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CDN or firewall rules.&lt;/strong&gt; Bot protection can block crawlers before they ever reach the file.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User-triggered fetches.&lt;/strong&gt; OpenAI says robots.txt rules may not apply to ChatGPT-User, and Perplexity says Perplexity-User generally ignores them. These are fetches a person asks for in a chat, and they behave differently from the crawlers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The guide &lt;a href="https://www.website.show/blog/is-your-site-blocking-chatgpt" rel="noopener noreferrer"&gt;Is your site blocking ChatGPT?&lt;/a&gt; goes through each case with links to the vendors' own documentation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Should you add llms.txt?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; it is cheap, so yes, but do not expect miracles.&lt;/p&gt;

&lt;p&gt;llms.txt is a proposed file at the root of a site that gives AI assistants a short Markdown map: a title, a one-line summary, then links to the pages worth reading. It is a proposal, not a standard, and it does not grant or refuse access. robots.txt still decides that.&lt;/p&gt;

&lt;p&gt;A minimal one:&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="gh"&gt;# Your Product&lt;/span&gt;
&lt;span class="gt"&gt;
&amp;gt; One sentence that says what the product does and for whom.&lt;/span&gt;

&lt;span class="gu"&gt;## Docs&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;Getting started&lt;/span&gt;&lt;span class="p"&gt;](&lt;/span&gt;&lt;span class="sx"&gt;https://yoursite.com/docs/start&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;: install and first run
&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;Pricing&lt;/span&gt;&lt;span class="p"&gt;](&lt;/span&gt;&lt;span class="sx"&gt;https://yoursite.com/pricing&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;: plans and limits
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can write it by hand in five minutes, or start from a draft made from your homepage with an &lt;a href="https://www.website.show/tools/llms-txt-generator" rel="noopener noreferrer"&gt;llms.txt generator&lt;/a&gt; and then trim it. More background is in &lt;a href="https://www.website.show/blog/llms-txt-what-it-is" rel="noopener noreferrer"&gt;What llms.txt is&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Say what the product is, in a way a machine can parse
&lt;/h2&gt;

&lt;p&gt;Assistants answer questions like "what is a good tool for X". If your homepage hero says "Build the future of work" and nothing else, there is nothing to quote. Two fixes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;One plain sentence near the top: what it is, who it is for.&lt;/li&gt;
&lt;li&gt;Structured data. A &lt;code&gt;SoftwareApplication&lt;/code&gt; JSON-LD block with name, category, price and URL gives crawlers the facts in a predictable shape. There is a walkthrough in &lt;a href="https://www.website.show/blog/softwareapplication-schema" rel="noopener noreferrer"&gt;this SoftwareApplication schema guide&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A five-minute checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;robots.txt: search bots allowed, training bots by your choice, no accidental &lt;code&gt;Allow&lt;/code&gt; groups.&lt;/li&gt;
&lt;li&gt;Homepage text present in raw HTML.&lt;/li&gt;
&lt;li&gt;No CDN rule blocking known AI bots.&lt;/li&gt;
&lt;li&gt;One clear sentence about what the product does.&lt;/li&gt;
&lt;li&gt;SoftwareApplication structured data.&lt;/li&gt;
&lt;li&gt;llms.txt with your key pages.&lt;/li&gt;
&lt;li&gt;The usual search basics: indexable page, title, meta description, H1, canonical, sitemap, link previews, image alt text.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you want all of that in one pass, the free &lt;a href="https://www.website.show/score" rel="noopener noreferrer"&gt;site check for AI search&lt;/a&gt; runs fifteen checks (seven for AI assistants, eight for search engines) and gives a score out of 100 with what to fix first. No AI model is involved in the check itself, so the same page always gets the same result. It does not tell you whether an assistant actually mentions you; it tells you whether it can read and understand you, which has to come first.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Will blocking GPTBot remove me from ChatGPT answers?&lt;/strong&gt;&lt;br&gt;
No. GPTBot collects training data. Answers in ChatGPT search rely on OAI-SearchBot. Block GPTBot if you do not want to be in training data, and keep OAI-SearchBot allowed if you want to be quoted.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does Google-Extended affect my Google rankings?&lt;/strong&gt;&lt;br&gt;
Google says it does not affect Google Search.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is llms.txt required?&lt;/strong&gt;&lt;br&gt;
No. It is a proposal. It helps assistants find your important pages, but robots.txt and readable HTML matter more.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My robots.txt is fine but nothing changes. Why?&lt;/strong&gt;&lt;br&gt;
Check your CDN or firewall bot rules and whether the homepage text exists without JavaScript. Those two cover most of the remaining cases.&lt;/p&gt;




&lt;p&gt;I build website.show in the open. If you shipped something recently, you can list it there for free and its page will run these checks every week: &lt;a href="https://www.website.show" rel="noopener noreferrer"&gt;https://www.website.show&lt;/a&gt;&lt;/p&gt;

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