Websites that run themselves: weekly SEO fixes, daily bug repairs
Public government data is hard to get at. Claude built sites that present it clearly and email it weekly, then review their own SEO and fix the day's glitches. Subscribers are trickling in.
Done withClaudeSpotted· by HN user idopmstuff· Oct 17, 2026
Result Trickle of subscribers, climbing in search
“it's getting a trickle of subscribers and is slowly rising the SEO ranks, so for now I'm content to let it sit and see if it ever gets to the point of being monetizable.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
They had Claude set up several websites that pull together public but hard-to-access government data, present it clearly, and send out weekly emails. The system now runs itself in two layers: once a week it reviews Google Search Console and GA4 data and updates or writes new content to improve its SEO, and once a day it catches and fixes whatever went wrong since the previous day, usually a data-pulling glitch or bad prose.
How it went
They aren’t actively monitoring it day to day, but it’s picking up a trickle of subscribers and slowly climbing the SEO rankings on its own, so they’re letting it keep running to see if it becomes monetizable.
Try it yourself with Claude
Have an agent build a site around a useful, hard-to-access public data source and set up a weekly email digest for subscribers. Then give it two standing jobs: a weekly pass reviewing your search console and analytics data to update or add content for SEO, and a daily pass that checks for anything broken, such as data pulls or bad output, and fixes it, so the site keeps improving with minimal oversight from you.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
A technical SEO and UX audit for a new client site normally takes the writer 3.5 to 7 hours. Claude pulled client info from OneDrive, ran the audit, drove a remote PageSpeed tool, and produced a Word report in 0.5 hours.
A client needed posts going out on schedule to about 9 social networks. Built with Claude layer by layer and tested as it grew, it has run for months without a single error.
In a meeting about a bug in an app they didn't own, they told Claude to find out if it was user error, notify the user, and tell the developer what to fix. Fifteen minutes later, the developer asked: today or Tuesday?
After $45 in GitHub Actions overage in one month, a solo founder put an idle homelab to work as CI runners, with Claude making it easy to set up. Daily spend dropped from $2-4 a day to under $0.25.
A first homemade synth has 36 hall-effect keys and buttons and 7 rotary encoders. The firmware started by hand, then gentle prodding at Claude got everything needed much faster. Rev 2 of the PCB is nearly done.
A browser game where you answer with a power of ten leans on Claude for code and content: fact checking answers, writing explanations, and inventing new questions.