<?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: sadik sajid</title>
    <description>The latest articles on DEV Community by sadik sajid (@sadiksjaid).</description>
    <link>https://dev.to/sadiksjaid</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%2F4213030%2F95241083-66a2-4cd6-92c6-9317b376c73d.jpg</url>
      <title>DEV Community: sadik sajid</title>
      <link>https://dev.to/sadiksjaid</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sadiksjaid"/>
    <language>en</language>
    <item>
      <title>How AI Assistants Became the #1 Traffic Source for My Website (robots.txt + llms.txt)</title>
      <dc:creator>sadik sajid</dc:creator>
      <pubDate>Sat, 07 Nov 2026 10:31:06 +0000</pubDate>
      <link>https://dev.to/sadiksjaid/how-ai-assistants-became-the-1-traffic-source-for-my-website-robotstxt-llmstxt-ab6</link>
      <guid>https://dev.to/sadiksjaid/how-ai-assistants-became-the-1-traffic-source-for-my-website-robotstxt-llmstxt-ab6</guid>
      <description>&lt;p&gt;I run Soundy.cloud (&lt;a href="https://soundy.cloud" rel="noopener noreferrer"&gt;https://soundy.cloud&lt;/a&gt;), a free sound-effects and MP3 library for streamers and creators. When I checked Google Analytics for the last 30 days, I found this:&lt;/p&gt;

&lt;p&gt;AI Assistant: 144 sessions&lt;br&gt;
Direct: 102 sessions&lt;br&gt;
Organic Search: 39 sessions&lt;br&gt;
Unassigned: 16 sessions&lt;br&gt;
Cross-network: 10 sessions&lt;br&gt;
Referral: 1 session&lt;/p&gt;

&lt;p&gt;AI assistants sent almost 4x more sessions than Google search. I never ran ads or did classic SEO campaigns. What I did was make the site easy for machines to understand, using two small text files.&lt;/p&gt;

&lt;p&gt;Note: I can’t prove these files are the cause. No major AI provider has officially confirmed that it reads llms.txt. This is what I did, and what I observed.&lt;/p&gt;

&lt;p&gt;File 1: robots.txt (the door)&lt;/p&gt;

&lt;p&gt;robots.txt tells crawlers what they may access. If it blocks AI bots, assistants can’t read your pages, so they can’t recommend you.&lt;/p&gt;

&lt;p&gt;My setup allows the major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Googlebot and others) and blocks only private areas: /staff/ and /api/staff/. I also declare my sitemap at the bottom of the file.&lt;/p&gt;

&lt;p&gt;A gotcha: a crawler with its own group ignores the general (*) group, so you must repeat your Disallow rules in every group.&lt;/p&gt;

&lt;p&gt;Live file: &lt;a href="https://soundy.cloud/robots.txt" rel="noopener noreferrer"&gt;https://soundy.cloud/robots.txt&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;File 2: llms.txt (the cheat sheet)&lt;/p&gt;

&lt;p&gt;llms.txt is a plain-text Markdown file at the root of your site, written for language models. Instead of guessing what your site is from thousands of pages, an assistant can read one short file.&lt;/p&gt;

&lt;p&gt;My structure:&lt;/p&gt;

&lt;p&gt;Title and summary: the site name and a one-paragraph description of who it is for&lt;br&gt;
Preferred citation: how models should name the site&lt;br&gt;
Direct answers: short answers to questions like “What is it?”, “Is it free?”, “Account required?”&lt;br&gt;
Getting started: links to the home page, the library, the legal pages and the sitemap&lt;br&gt;
Categories and tags: links to the main sections&lt;br&gt;
How pages work: URL patterns such as /sound/{slug} for sound pages, /a/{slug} for audio and /sounds?q={query} for search&lt;br&gt;
License and use: a clear statement of what is free&lt;br&gt;
Optional: links to robots.txt and other extras&lt;/p&gt;

&lt;p&gt;What I think makes it useful:&lt;/p&gt;

&lt;p&gt;A short summary at the top. The first lines are what a model is most likely to quote.&lt;br&gt;
Direct answers. They match the questions people ask assistants.&lt;br&gt;
URL patterns. An agent can navigate your site without guessing.&lt;br&gt;
Explicit licensing and contact info. Assistants repeat these to users, so be clear.&lt;br&gt;
A preferred citation line. It tells models how to name you.&lt;/p&gt;

&lt;p&gt;Live file: &lt;a href="https://soundy.cloud/llms.txt" rel="noopener noreferrer"&gt;https://soundy.cloud/llms.txt&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Mistakes to avoid&lt;br&gt;
Inconsistent brand names. I had “Soundyz” in one place and “Soundy.cloud” in another, and my analytics even showed two page titles. Pick one name and use it everywhere.&lt;br&gt;
Repeating yourself. My FAQ answered the same question three times. Keep the file concise.&lt;br&gt;
Fake-looking numbers. Identical counts on every category look auto-generated. Use real data.&lt;br&gt;
Vague licensing. If your content is third-party, say who owns the rights.&lt;br&gt;
Treating robots.txt as security. Listing /staff/ also tells people where it is, so protect it with real authentication.&lt;br&gt;
Checklist&lt;br&gt;
Don’t block AI crawlers in robots.txt&lt;br&gt;
Add a Sitemap line (use a sitemap index if you have more than 50k URLs)&lt;br&gt;
Publish /llms.txt with a summary, key links and FAQs&lt;br&gt;
Add licensing and contact info&lt;br&gt;
Keep one consistent brand name&lt;br&gt;
Check GA4 for AI referral traffic (Reports &amp;gt; Acquisition &amp;gt; Traffic acquisition)&lt;br&gt;
Final thoughts&lt;/p&gt;

&lt;p&gt;Search is changing. People increasingly ask an assistant instead of googling, and being easy for those systems to read costs almost nothing. Both files took me under an hour.&lt;/p&gt;

&lt;p&gt;Are you seeing AI traffic in your analytics? I’d like to compare notes in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>seo</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>CISA Says a WordPress Core Flaw Is Being Exploited: What to Do Today</title>
      <dc:creator>sadik sajid</dc:creator>
      <pubDate>Thu, 05 Nov 2026 15:09:17 +0000</pubDate>
      <link>https://dev.to/sadiksjaid/cisa-says-a-wordpress-core-flaw-is-being-exploited-what-to-do-today-3b4f</link>
      <guid>https://dev.to/sadiksjaid/cisa-says-a-wordpress-core-flaw-is-being-exploited-what-to-do-today-3b4f</guid>
      <description>&lt;p&gt;On November 4, 2026, CISA added a WordPress Core vulnerability to its Known Exploited Vulnerabilities (KEV) catalog. That means attackers are already using it in the wild.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we know
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The flaw is in WordPress Core, not in a plugin.&lt;/li&gt;
&lt;li&gt;Wordfence reported that exploiting it does not require an account on the site.&lt;/li&gt;
&lt;li&gt;It relates to predictable, web-accessible staging paths used during full-package core upgrades.&lt;/li&gt;
&lt;li&gt;A fix has already been released.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What to do today
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Update WordPress core&lt;/strong&gt; to the latest security release.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check your logs&lt;/strong&gt; for strange requests, especially around upgrade time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confirm your backups work&lt;/strong&gt; by restoring one on a test server.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Turn on automatic security updates&lt;/strong&gt; if your setup allows it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review file permissions&lt;/strong&gt; and remove leftover upgrade files.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The bigger lesson
&lt;/h2&gt;

&lt;p&gt;A patch only protects you after you install it. The gap between "fix released" and "fix installed" is where most attacks happen.&lt;/p&gt;

&lt;p&gt;If you manage many sites, track every site's core version in one place, so you can see in minutes which ones are behind.&lt;/p&gt;

&lt;h2&gt;
  
  
  Question for you
&lt;/h2&gt;

&lt;p&gt;How soon do you update after a security release: the same day, this week, or later? Tell me in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Sources: The Hacker News and BleepingComputer, November 4, 2026.&lt;/em&gt;&lt;br&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%2Fuixz0vyx0dm4jtujjlee.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%2Fuixz0vyx0dm4jtujjlee.png" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devops</category>
      <category>webdev</category>
      <category>security</category>
      <category>wordpress</category>
    </item>
    <item>
      <title>New Linux Kernel Vulnerability (CVE-2026-98432): What to Do Now</title>
      <dc:creator>sadik sajid</dc:creator>
      <pubDate>Fri, 30 Oct 2026 17:19:49 +0000</pubDate>
      <link>https://dev.to/sadiksjaid/new-linux-kernel-vulnerability-cve-2026-98432-what-to-do-now-582c</link>
      <guid>https://dev.to/sadiksjaid/new-linux-kernel-vulnerability-cve-2026-98432-what-to-do-now-582c</guid>
      <description>&lt;p&gt;On October 29, a security vulnerability was announced in the Linux kernel: &lt;strong&gt;CVE-2026-98432&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It affects how Linux handles new network connections and, in some cases, could let an attacker take control of a server remotely. Almost every Linux distribution is affected, including the ones commonly used on VPS.&lt;/p&gt;

&lt;h2&gt;
  
  
  The permanent fix
&lt;/h2&gt;

&lt;p&gt;The permanent fix is a kernel update for your operating system. Not every distribution has released one yet, so here is what to do for each.&lt;/p&gt;

&lt;h3&gt;
  
  
  Debian 12 or 13: fix available now
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;apt update &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; apt upgrade
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then restart your server.&lt;/p&gt;

&lt;h3&gt;
  
  
  Ubuntu: fix not released yet
&lt;/h3&gt;

&lt;p&gt;Once the fix is released, run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;apt update &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; apt upgrade
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then restart your server.&lt;/p&gt;

&lt;h3&gt;
  
  
  AlmaLinux, Rocky Linux and other RHEL-based systems: fix not released yet
&lt;/h3&gt;

&lt;p&gt;Once the fix is released, run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dnf update kernel
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then restart your server.&lt;/p&gt;

&lt;h2&gt;
  
  
  A restart is required
&lt;/h2&gt;

&lt;p&gt;Automatic updates can install the new kernel, but your server keeps running the old one until it restarts. Restart with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;reboot
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To check which kernel you're currently running:&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;uname&lt;/span&gt; &lt;span class="nt"&gt;-r&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Distribution&lt;/th&gt;
&lt;th&gt;Fix status&lt;/th&gt;
&lt;th&gt;Command&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Debian 12 / 13&lt;/td&gt;
&lt;td&gt;Available now&lt;/td&gt;
&lt;td&gt;&lt;code&gt;apt update &amp;amp;&amp;amp; apt upgrade&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ubuntu&lt;/td&gt;
&lt;td&gt;Not released yet&lt;/td&gt;
&lt;td&gt;&lt;code&gt;apt update &amp;amp;&amp;amp; apt upgrade&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AlmaLinux / Rocky / RHEL-based&lt;/td&gt;
&lt;td&gt;Not released yet&lt;/td&gt;
&lt;td&gt;&lt;code&gt;dnf update kernel&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Always reboot after the update. If you manage Linux servers, share this with your team.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>security</category>
      <category>devops</category>
      <category>sysadmin</category>
    </item>
    <item>
      <title>AI Makes Building SaaS Faster. So Why Is It Harder to Commit to One Idea?</title>
      <dc:creator>sadik sajid</dc:creator>
      <pubDate>Wed, 28 Oct 2026 12:57:05 +0000</pubDate>
      <link>https://dev.to/sadiksjaid/ai-makes-building-saas-faster-so-why-is-it-harder-to-commit-to-one-idea-2p3k</link>
      <guid>https://dev.to/sadiksjaid/ai-makes-building-saas-faster-so-why-is-it-harder-to-commit-to-one-idea-2p3k</guid>
      <description>&lt;p&gt;As a solo founder, I've been struggling with a new kind of fear.&lt;/p&gt;

&lt;p&gt;AI tools like Claude make building software faster than ever. What used to take months can sometimes be built in days.&lt;/p&gt;

&lt;p&gt;But that creates a strange problem.&lt;/p&gt;

&lt;p&gt;Why spend 6–12 months building a SaaS product when someone with more money could copy the idea in a weekend and outspend you on marketing?&lt;/p&gt;

&lt;p&gt;The technical barrier to building software keeps getting lower. But finding customers, earning their trust, and building a sustainable business are still hard.&lt;/p&gt;

&lt;p&gt;I have several products that work, but getting consistent traffic and paying customers remains a challenge. Sometimes, committing to one idea for another six months feels risky when the market is moving so quickly.&lt;/p&gt;

&lt;p&gt;At the same time, constantly switching projects means never giving any of them enough time to succeed.&lt;/p&gt;

&lt;p&gt;So I'm trying to figure out where to draw the line between staying focused and adapting to a changing market.&lt;/p&gt;

&lt;p&gt;How do you deal with this?&lt;/p&gt;

&lt;p&gt;Do you commit to one product for 6–12 months, regardless of what competitors are doing?&lt;/p&gt;

&lt;p&gt;Do you prioritize marketing and customer relationships over building more features?&lt;/p&gt;

&lt;p&gt;Or do you keep experimenting until you find something that gains traction?&lt;/p&gt;

&lt;p&gt;I'd love to hear from other indie hackers and solo founders. How do you stay focused when AI makes it feel like someone could build your idea tomorrow?&lt;/p&gt;

</description>
      <category>sass</category>
      <category>saas</category>
      <category>ai</category>
      <category>agents</category>
    </item>
  </channel>
</rss>
