<?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: Carlos Arias</title>
    <description>The latest articles on DEV Community by Carlos Arias (@carlosarias_).</description>
    <link>https://dev.to/carlosarias_</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3242762%2F9b221f1b-9c39-4f5f-aef5-b9e5ce7812f8.jpg</url>
      <title>DEV Community: Carlos Arias</title>
      <link>https://dev.to/carlosarias_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/carlosarias_"/>
    <language>en</language>
    <item>
      <title>I Built My Own Site Crawler</title>
      <dc:creator>Carlos Arias</dc:creator>
      <pubDate>Sun, 05 Apr 2026 16:24:25 +0000</pubDate>
      <link>https://dev.to/carlosarias_/i-built-my-own-site-crawler-hjl</link>
      <guid>https://dev.to/carlosarias_/i-built-my-own-site-crawler-hjl</guid>
      <description>&lt;p&gt;I lost my job last year.&lt;/p&gt;

&lt;p&gt;So I did what most engineers do when they don’t have a safety net. I started taking on clients. Mostly in the legal space, doing SEO and digital marketing.&lt;/p&gt;

&lt;p&gt;Very quickly, I noticed something stupid.&lt;/p&gt;

&lt;p&gt;Every project had the same workflow:&lt;br&gt;
Open the client’s website → copy content → paste into GPT → try to “train” it on their business. Over and over again.&lt;/p&gt;

&lt;p&gt;No structure. No consistency. Just manual work pretending to be “AI-powered.”&lt;/p&gt;

&lt;p&gt;So I looked for tools that could automate this. I found things like Firecrawl. On paper, it solves the problem.&lt;/p&gt;

&lt;p&gt;In reality:&lt;br&gt;
It gets expensive fast if you're doing this at scale&lt;br&gt;
It’s not always reliable; And it’s still not really built for how people actually use LLMs day-to-day&lt;/p&gt;

&lt;p&gt;Most of these tools feel like they were built for demos, not production workflows.&lt;/p&gt;

&lt;p&gt;So I built my own crawler.&lt;/p&gt;

&lt;p&gt;Not a “vibe coded” wrapper. An actual tool designed for one job:&lt;br&gt;
Extract clean, structured content from websites so it can be used directly with LLMs.&lt;/p&gt;

&lt;p&gt;No fluff. No unnecessary features. Just something that works.&lt;/p&gt;

&lt;p&gt;This is the part most people don’t want to hear:&lt;br&gt;
You can’t shortcut this with prompts and duct tape.&lt;/p&gt;

&lt;p&gt;If you actually rely on LLMs in real workflows, you need proper data pipelines. Crawling, cleaning, structuring—that’s the real work. Everything else is just UI.&lt;/p&gt;

&lt;p&gt;Anyway, I made it public.&lt;/p&gt;

&lt;p&gt;It’s free for now. If I turn it into a SaaS, it won’t be another overpriced tool trying to charge you per page like you're running a data center.&lt;/p&gt;

&lt;p&gt;If you’re doing anything with RAG, AI agents, or content pipelines, you’ll get it immediately.&lt;/p&gt;

&lt;p&gt;My Project: &lt;br&gt;
&lt;a href="https://carlosarias.com/tools/crawll" rel="noopener noreferrer"&gt;Carlos Arias - Site Crawler&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>crawler</category>
    </item>
  </channel>
</rss>
