llms.txt Guides & Examples
Everything you need to ship a spec-compliant llms.txt — from the exact format to real-world examples.
llms.txt and Schema.org: Do You Need Both? (2026)
llms.txt is a site-level index that tells an agent which pages are worth reading; Schema.org JSON-LD is page-level labeling that tells a parser what each page means. What the v2 spec actually says about referencing structured data, what Google's May 2026 FAQ deprecation and June AI-guide mythbusting changed, the four consistency rules that stop the two files contradicting each other, and a copyable matching pair.
Read article →How to Validate an llms.txt File: Spec, Links and Delivery (2026)
Validation reads the text of your file, not the response that delivers it — which is why a clean validator run can still leave you with a file nobody reads. The three-layer check: structure and the only element the spec requires, a curl loop that catches 404s, redirects and duplicates, and the path, content-type, status and cache tests that catch the rest.
Read article →ai.txt vs llms.txt: Which AI File Should You Ship in 2026?
ai.txt declares permissions — may this media be mined or used for training? llms.txt declares content — here is what the site contains. How the two files differ, where the W3C TDM Reservation Protocol, the TDM-Reservation header and noai fit, the December 2025 German ruling that made machine-readable opt-outs the standard, and the four-signal stack worth shipping.
Read article →Markdown for Agents vs llms.txt: Content Negotiation or Curated Index? (2026)
llms.txt is a curated index that tells agents what exists; Markdown for Agents is HTTP content negotiation that changes the format one page arrives in. The Feb 2026 data on which agents send Accept: text/markdown, how Cloudflare and Vercel implement the delivery layer, and how Markdown twins + rel="alternate" connect the two.
Read article →AGENTS.md vs llms.txt: Two Files, Two Readers (2026)
Both are plain Markdown conventions and both get called "the file that tells AI about your project" — but one is read inside your repository and the other is fetched from your website. Side-by-side comparison, what belongs in each, the new link relations in llms.txt v2, the Claude Code holdout and the documented imports that fix it, plus what the ETH Zurich study of AGENTS.md files actually found.
Read article →llms.txt Maintenance: How to Keep Your File From Going Stale (2026)
A published llms.txt decays quietly: renamed URLs, deleted pages, a summary describing a product you repositioned months ago. A three-layer maintenance system — a link check that fails your build, a split between what you generate and what you curate, and a quarterly review list you can finish in ten minutes.
Read article →llms.txt Not Working? 7 Delivery-Level Fixes (Content-Type, Redirects, WAF, 2026)
Seven delivery-level reasons a published llms.txt never gets read — a catch-all rewrite answering text/html, rewrite rules that map the path onto robots.txt, redirect chains, case-sensitive paths, WAF and robots.txt blocks, files that never shipped in the build, and a stale edge cache — each with the curl command that proves which one you have.
Read article →llms.txt for Multilingual Websites: One File or One Per Language? (2026)
A file covers the URLs under its path and the most specific one wins — that single spec rule is what makes per-language llms.txt files work. Three structures (single root file, root index plus /en/ and /de/ files, root plus Optional section), how to keep it aligned with hreflang and canonicals, a curl-verified table of what Stripe, Cloudflare, Shopify, GitLab and Wikipedia actually ship on September 14, 2026, and a five-minute verification pass.
Read article →llms.txt vs MCP: The Read Layer vs the Action Layer for AI Agents (2026)
llms.txt answers "what is on this site?", MCP answers "what can I do here?" — and the 2026-07-28 MCP revision made the action layer stateless. How the two protocols differ, why MCP has no discovery of its own, where WebMCP and Lighthouse's Agentic Browsing audits fit, and the five-step adoption order for the next quarter.
Read article →How to Measure Whether AI Engines Read Your llms.txt (Logs, GA4 and Cloudflare, 2026)
A three-layer measurement framework for llms.txt: count direct /llms.txt fetches in your access logs, track AI crawler hits on the pages your file lists, and read AI referral sessions in the GA4 AI Assistant channel (added May 13, 2026) plus Cloudflare AI Crawl Control — with the exact log commands, the two GA4 caveats, and a 30-day benchmark table.
Read article →robots.txt for AI Crawlers in 2026: Allow, Block or Feed GPTBot, ClaudeBot and PerplexityBot
Training, search-index and user-triggered: the three classes of AI crawler decide what blocking actually costs you. The 2026 token reference for GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended and CCBot, two ready-to-paste robots.txt policies, Cloudflare Content Signals, and where your llms.txt file takes over.
Read article →llms.txt Case Studies 2026: Inside the Files of Vue.js, Nuxt, Cloudflare, OpenAI and Anthropic
Six production llms.txt files, curl-verified on September 10, 2026: how Vue.js, Nuxt, Cloudflare Developers, OpenAI and Anthropic structure their files — hierarchical tables of contents, markdown twins, subpath hubs and llms-full.txt — plus the five patterns worth copying.
Read article →How to Add llms.txt to Nuxt (public/, Server Routes, nuxt-llms, 2026)
Nuxt ships no llms.txt output, but its public/ directory serves a static file at the site root in 60 seconds, a server/routes handler generates one per request, and NuxtLabs' nuxt-llms module prerenders llms.txt and llms-full.txt at every build — with Nuxt Content 3.2+ integration. Includes nuxt.com's own file, curl-verified.
Read article →How to Add llms.txt to Shopify: Replace the Default File (2026)
Shopify now auto-generates an llms.txt for every store at yourstore.com/llms.txt — but the default reads like Shopify's pitch, not yours. Override it with a templates/llms.txt.liquid theme file (the robots.txt.liquid mechanism, confirmed on the Shopify developer community): what to include, exact admin clicks, a ready-to-copy store sample and a curl check.
Read article →How to Add llms.txt to Jekyll (GitHub Pages, 2026)
Jekyll has no built-in llms.txt support, but its root-file rules make it easy: a static file in 60 seconds, a Liquid template that re-lists every post at every build (no plugin, so GitHub Pages accepts it), or the jekyll-llms-output plugin for llms.txt + llms-full.txt. Includes real config, the GitHub Pages plugin whitelist caveat and a curl check of a live Jekyll site.
Read article →How to Add llms.txt to VitePress (Static or Auto-Generated, 2026)
No native llms.txt support in VitePress, but public/ ships a static file in 60 seconds and vitepress-plugin-llms — used in production by Vue.js, Vite and Vitest — generates llms.txt, llms-full.txt and per-page Markdown at every build. Real config plus a curl check.
Read article →How to Add llms.txt to MkDocs (Material for MkDocs, 2026)
MkDocs has no built-in llms.txt support, but docs/ files are copied verbatim to the site root and the mkdocs-llmstxt plugin generates a spec-compliant file at every build — with .md page versions, llms-full.txt and Read the Docs subpath support. Includes real mkdocs.yml config and a curl check.
Read article →How to Add llms.txt to Hugo (Static or Auto-Generated, 2026)
Hugo has no built-in llms.txt support as of 2026, but its static/ folder and custom output formats make it one of the easiest SSGs to add one: a hand-written file in 60 seconds, or a file auto-generated from your content at build time. Includes real hugo.toml config and a curl check.
Read article →How to Add llms.txt to Docusaurus (Docs Sites, 2026)
No official plugin yet, but docs sites are llms.txt's best use case: ship a static file in static/ in 60 seconds, or generate llms.txt and llms-full.txt from your docs with the docusaurus-plugin-llms community plugin — plus a checklist and curl verification.
Read article →How to Add llms.txt to an Astro Site (Static or Generated, 2026)
Astro has no llms.txt file convention, but public/ files and src/pages endpoints make it trivial: a static public/llms.txt, a build-time .ts endpoint, or the astro-slop integration — with examples and a curl check.
Read article →How to Add llms.txt to Next.js (App Router, 2026)
No native llms.txt convention in Next.js yet — here is how to ship one today: a static public/llms.txt file, a dynamic app/llms.txt route handler, or ISR, plus verification.
Read article →Which AI Engines Actually Read llms.txt? (2026 Crawler Data)
Two years of crawler audits show 97% of llms.txt files get zero requests — here is the evidence from 500M+ AI bot requests, Google's on-the-record stance, and the realistic playbook.
Read article →6 llms.txt Mistakes That Make AI Engines Ignore Your File
Placement, format, links, curation, tone and metrics: the six errors that get your llms.txt skipped — plus a five-minute verification checklist.
Read article →llms.txt v2: What Changed in the 2026 Spec Update
The first major revision of the llmstxt.org spec: two markdown URL forms, officially defined subpath files, rel=alternate and rel=describedby link relations, and what happened to llms_txt2ctx.
Read article →llms.txt Best Practices 2026: The 9 Rules for a File AI Engines Trust
Format, curation, and maintenance rules that separate an llms.txt agents actually use from one they ignore — with a complete reference example.
Read article →Does llms.txt Affect SEO? What Google Actually Says (2026)
Google says llms.txt has no effect on rankings. Here is the evidence, the nuance, and where the file genuinely pays off for AI visibility.
Read article →llms.txt vs sitemap.xml: Why AI Engines Need a Different File
sitemap.xml lists every URL for search engines; llms.txt curates the pages that matter for AI agents. When you need both and how they work together.
Read article →How to Add llms.txt to Cloudflare Pages (Astro, React, Plain HTML)
Publish llms.txt on Cloudflare Pages in 5 minutes — static file, dashboard upload, or a Pages Function for dynamic generation — plus verification.
Read article →llms.txt vs llms-full.txt: What's the Difference and Which Do You Need?
The curated index vs the full Markdown dump: what each is for, when you need llms-full.txt, and how to link them correctly.
Read article →The Complete llms.txt Format Guide
Every element of the llmstxt.org v2 spec, element-by-element, with a valid end-to-end example and the mistakes people make.
Read article →How to Create an llms.txt File: Step-by-Step Guide
Create your llms.txt in 10 minutes: pick your 5–15 best pages, format them per the spec, publish at your site root, and validate.
Read article →llms.txt Examples: Real Files for Every Site Type
Complete llms.txt files for SaaS docs, e-commerce, blogs and corporate sites — copy the structure that fits your site.
Read article →llms.txt vs robots.txt vs sitemap.xml: What's the Difference?
What each root-level file does, who reads it, and how the three work together for AI engines and search crawlers.
Read article →How to Add llms.txt to WordPress (2026 Guide)
Three ways to ship llms.txt on WordPress — upload the file, use a plugin, or add it with code — plus the pitfalls that break it.
Read article →What is llms.txt? The Complete Guide
What llms.txt is, why it matters for AI engines like ChatGPT and Claude, and how it fits with robots.txt and sitemap.xml.
Read article →Need it done for you?
Paste your sitemap.xml into the generator and get a spec-compliant llms.txt in seconds.
Open the Generator →