APAndriy Pyvovarchukinllmstxt.hashnode.dev·Aug 6 · 3 min readHow to test your llms.txt before you ship itAn llms.txt is easy to write and easy to get subtly wrong. The file can look perfectly fine in your editor and still be malformed, or point at pages that 404 — and unlike a broken web page, nothing vi00
APAndriy Pyvovarchukinllmstxt.hashnode.dev·Aug 6 · 3 min readWhich AI crawlers actually read your llms.txt? (GPTBot, ClaudeBot & friends)You added an llms.txt. Reasonable next question: who's actually reading it? The honest answer surprises people — so let's clear it up, and more importantly sort out which bots you should care about an00
APAndriy Pyvovarchukinllmstxt.hashnode.dev·Aug 4 · 4 min readI made my website callable by another AI agent — here's the actual JSON-RPCMost "AI integration" still means a human reads your docs and writes a client. A2A flips that: another agent reads a small machine description of what your service does and calls it directly — no brow00
APAndriy Pyvovarchukinllmstxt.hashnode.dev·Jul 26 · 3 min read7 llms.txt mistakes I see constantly (and the 30-second fix for each)llms.txt is deceptively simple — it's just Markdown — so most people write one in five minutes and move on. The problem: a file can look perfectly valid and still be broken in ways that quietly waste 00
APAndriy Pyvovarchukinllmstxt.hashnode.dev·Jul 26 · 3 min readllms.txt vs robots.txt vs sitemap.xml: what actually does whatIf you run a website in 2026 you now have three plain-text files that can live at your root and all look suspiciously similar: robots.txt, sitemap.xml, and the newcomer, llms.txt. They get confused co00
