<?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: Santiago Griman</title>
    <description>The latest articles on DEV Community by Santiago Griman (@xwickz).</description>
    <link>https://dev.to/xwickz</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%2F4250041%2F51a2722b-29db-4226-b82e-b9bc249bd5e1.png</url>
      <title>DEV Community: Santiago Griman</title>
      <link>https://dev.to/xwickz</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/xwickz"/>
    <language>en</language>
    <item>
      <title>I audited 286 developer portfolios: 1 in 3 is a blank page to ChatGPT</title>
      <dc:creator>Santiago Griman</dc:creator>
      <pubDate>Tue, 17 Nov 2026 14:18:40 +0000</pubDate>
      <link>https://dev.to/xwickz/i-audited-286-developer-portfolios-1-in-3-is-a-blank-page-to-chatgpt-3ko4</link>
      <guid>https://dev.to/xwickz/i-audited-286-developer-portfolios-1-in-3-is-a-blank-page-to-chatgpt-3ko4</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; I ran 300 random developer portfolios through the same checks AI crawlers depend on. Of the 286 that loaded, &lt;strong&gt;34% show fewer than 20 words to a bot that doesn't run JavaScript&lt;/strong&gt;, which is how GPTBot and ClaudeBot read the web. Only 15% have an &lt;code&gt;llms.txt&lt;/code&gt;, and 7% block AI crawlers outright, usually without the owner knowing.&lt;/p&gt;

&lt;p&gt;People increasingly ask ChatGPT, Claude or Perplexity things like &lt;em&gt;"find me a React developer who has built e-commerce sites"&lt;/em&gt;. If those tools can't read your portfolio, you're not in the answer.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fc310be8aq2gpmsp30d1r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fc310be8aq2gpmsp30d1r.png" alt="Bar chart: what AI crawlers find on 286 developer portfolios" width="800" height="464"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How I measured it
&lt;/h2&gt;

&lt;p&gt;I took a reproducible random sample of 300 sites from &lt;a href="https://github.com/emmabostian/developer-portfolios" rel="noopener noreferrer"&gt;developer-portfolios&lt;/a&gt;, the biggest public list of portfolios on GitHub (2,100+ entries). Each one went through &lt;a href="https://audit.wickz.dev/en/?utm_source=devto&amp;amp;utm_campaign=ai-visibility" rel="noopener noreferrer"&gt;site-audit&lt;/a&gt;, a free tool I built that checks SEO, security headers and AI readiness.&lt;/p&gt;

&lt;p&gt;The key detail: the audit reads the &lt;strong&gt;raw HTML the server returns&lt;/strong&gt;, without running JavaScript. That's what AI crawlers see. 11 sites timed out or were down, and 3 returned an error, which leaves &lt;strong&gt;286 live portfolios&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 1: a third of portfolios are blank without JavaScript
&lt;/h2&gt;

&lt;p&gt;98 portfolios (34%) contain &lt;strong&gt;fewer than 20 visible words&lt;/strong&gt; in their HTML. Most are single-page React, Vue or Vite apps that render everything in the browser. To a human they look great. To a crawler that doesn't execute JavaScript, they look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;body&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;div&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"root"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"module"&lt;/span&gt; &lt;span class="na"&gt;src&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/assets/index-4f3a.js"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/body&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No name, no skills, no projects. Google renders JavaScript, so these sites may still rank there. But &lt;a href="https://vercel.com/blog/the-rise-of-the-ai-crawler" rel="noopener noreferrer"&gt;Vercel's analysis of AI crawler traffic&lt;/a&gt; found that OpenAI's and Anthropic's crawlers fetch JavaScript files without executing them.&lt;/p&gt;

&lt;p&gt;Widen the threshold to 250 words and it's &lt;strong&gt;54%&lt;/strong&gt; of portfolios. 35% have no &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt; in the HTML at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; pre-render. Use static generation (Astro, Next.js &lt;code&gt;output: 'export'&lt;/code&gt;, Nuxt &lt;code&gt;generate&lt;/code&gt;, SvelteKit &lt;code&gt;prerender&lt;/code&gt;) or a pre-render plugin for your Vite app. A portfolio is static content. It doesn't need to be built in the visitor's browser.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 2: 7% block AI crawlers, and most don't know it
&lt;/h2&gt;

&lt;p&gt;19 portfolios block GPTBot, ClaudeBot and Google-Extended in &lt;code&gt;robots.txt&lt;/code&gt;. When I opened those files, &lt;strong&gt;17 of the 19 were written by Cloudflare&lt;/strong&gt;, not by the owner. Cloudflare's managed &lt;code&gt;robots.txt&lt;/code&gt; adds the blocks for you when the AI crawler setting is on.&lt;/p&gt;

&lt;p&gt;If you put your portfolio on Cloudflare and want AI assistants to find you, open &lt;code&gt;yourdomain.com/robots.txt&lt;/code&gt; and check. To allow them explicitly:&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: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

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

&lt;/div&gt;



&lt;h2&gt;
  
  
  Finding 3: almost nobody gives AI the context it needs
&lt;/h2&gt;

&lt;p&gt;AI assistants prefer content they can quote with confidence: who wrote it, when, and what question it answers. Portfolios mostly skip this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;91%&lt;/strong&gt; have no publish or update date anywhere (meta tag, JSON-LD or &lt;code&gt;&amp;lt;time&amp;gt;&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;88%&lt;/strong&gt; have no question-and-answer structure (headings phrased as questions, or FAQ schema).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;85%&lt;/strong&gt; have no &lt;code&gt;llms.txt&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;63%&lt;/strong&gt; have no structured data (JSON-LD) at all.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;49%&lt;/strong&gt; don't declare an author.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The cheapest fix for most of these is one block of JSON-LD in your &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"application/ld+json"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Person"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Your Name"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"jobTitle"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Frontend Developer"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://yourdomain.com"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"sameAs"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"https://github.com/you"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"https://linkedin.com/in/you"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"knowsAbout"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"React"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"TypeScript"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"Accessibility"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And an &lt;code&gt;llms.txt&lt;/code&gt; at the root of your site, a plain Markdown summary written for language models:&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;# Your Name
&lt;/span&gt;
&lt;span class="ge"&gt;&amp;gt; Frontend developer in Lisbon. I build fast, accessible React apps for startups.
&lt;/span&gt;
&lt;span class="gu"&gt;## Projects
&lt;/span&gt;&lt;span class="k"&gt;- &lt;/span&gt;[Project A](https://yourdomain.com/projects/a): e-commerce checkout, 40% faster load
&lt;span class="k"&gt;- &lt;/span&gt;[Project B](https://yourdomain.com/projects/b): open-source date picker, 2k stars

&lt;span class="gu"&gt;## Contact
&lt;/span&gt;&lt;span class="k"&gt;- &lt;/span&gt;Email: you@yourdomain.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;llms.txt&lt;/code&gt; is a proposal, and no major AI company has confirmed it reads it. It takes five minutes, though, and it doubles as a clean summary of your work.&lt;/p&gt;

&lt;h2&gt;
  
  
  The classic SEO basics are missing too
&lt;/h2&gt;

&lt;p&gt;These aren't AI-specific, but they decide what shows up when someone shares your link:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;44%&lt;/strong&gt; have incomplete Open Graph tags, so a link on LinkedIn, Slack or X shows no image or the wrong text.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;58%&lt;/strong&gt; have a meta description that is missing (17%) or outside the 50–160 character range.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;57%&lt;/strong&gt; have no sitemap.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The median portfolio failed &lt;strong&gt;14 of 33 checks&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A 15-minute checklist for your portfolio
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;View source (&lt;code&gt;Ctrl+U&lt;/code&gt;). If you can't read your name and projects there, pre-render.&lt;/li&gt;
&lt;li&gt;Open &lt;code&gt;/robots.txt&lt;/code&gt; and make sure you aren't blocking crawlers you want.&lt;/li&gt;
&lt;li&gt;Add one &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt; with your name and role.&lt;/li&gt;
&lt;li&gt;Add Person JSON-LD and a meta author.&lt;/li&gt;
&lt;li&gt;Add &lt;code&gt;og:title&lt;/code&gt;, &lt;code&gt;og:description&lt;/code&gt; and &lt;code&gt;og:image&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Write an &lt;code&gt;llms.txt&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Add a sitemap.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Or &lt;a href="https://audit.wickz.dev/en/?utm_source=devto&amp;amp;utm_campaign=ai-visibility" rel="noopener noreferrer"&gt;run your portfolio through the audit&lt;/a&gt;. It's free, needs no sign-up and checks all of the above in about ten seconds, with the exact fix for each item.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I don't name any individual site: the point is the pattern, not the people.&lt;/em&gt;&lt;/p&gt;

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