cd /news/agent-protocols/adding-llms-txt-to-a-small-business-… · home › topics › agent-protocols › article
[ARTICLE · art-174151] src=dev.to ↗ pub= topic=agent-protocols verified=true sentiment=· neutral

Adding llms.txt to a Small Business Website: What We Learned Shipping It in 2026

A developer at Nexpro Softwares, a software and web development company in Bhubaneswar, India, published an llms.txt file at the site root to make the business's key pages easier for AI assistants to read, following the llmstxt.org format of an H1, blockquote summary and described links. The team also wrote a shell script that crawls the listed URLs and flags any returning non-200 status codes. The developer said it is too early to measure any direct effect, but the exercise surfaced inconsistent entity facts across the site and listings, which benefits conventional local SEO.

key takeaway

Publishing an llms.txt with an H1, blockquote summary and described links is low-effort, and a curl loop that flags any listed URL not returning HTTP 200 catches broken links while forcing consistent entity facts across the site.

by read1 min views1 publishedNov 22, 2026

AI assistants increasingly answer "which company should I hire for X in my city?" before a person ever opens a search result. For a services business, that means the website needs to be easy for a language model to read, not just for a crawler to index. One lightweight step is publishing an llms.txt file at the site root.

The llmstxt.org proposal is simple: a Markdown file at /llms.txt with an H1 (the site or company name), a short blockquote summary, and sections of links with one-line descriptions. Some sites also publish /llms-full.txt, a longer clean-Markdown version of the key facts. It is not a ranking switch and no assistant is obliged to read it. Think of it as a tidy, machine-friendly index of the pages you most want understood.

For our own company site we kept it boring on purpose:

curl -s https://example.com/llms.txt | grep -oE 'https?://[^) ]+' | while read u; do
  code=$(curl -s -o /dev/null -w '%{http_code}' "$u"); [ "$code" = "200" ] || echo "BROKEN $code $u"
done

Honestly, it's too early to measure directly. What we can say is that the exercise forced us to fix inconsistent entity facts across the site and listings, which helps classic local SEO regardless. If you want to see a real example, ours lives at https://nexprosolution.com/llms.txt (I work at Nexpro Softwares, a software and web development company in Bhubaneswar, Odisha).

Low effort, no downside, and a good excuse to clean up your site's facts.

── more in #agent-protocols 4 stories · sorted by recency
── more on @nexpro softwares 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/adding-llms-txt-to-a…] indexed:0 read:1min 2026-11-22 · —