Guide

Adding llms.txt to a static site generator

Published: 2026-06-29

Static site generators have a folder whose contents are copied verbatim to your published site root — so adding an llms.txt is just dropping the file in the right place and rebuilding.

Where the file goes, per generator

• Astro — public/llms.txt (everything in public/ is served from the root).
• Hugo — static/llms.txt (the static/ directory is copied to the output root). A custom output format also works for generating it.
• Eleventy (11ty) — add a passthrough copy, e.g. eleventyConfig.addPassthroughCopy("llms.txt"), so the file lands in the output.
• Jekyll — put llms.txt in the project root; Jekyll copies static files through to _site as-is.

Build and verify

Run your build (astro build, hugo, npx @11ty/eleventy, jekyll build) and confirm llms.txt appears at the root of the output directory, then deploy.

Generate it from your content (optional)

For docs-style sites, plugins exist (for Astro Starlight, Docusaurus, MkDocs, VitePress and others) that build the file from your pages automatically. Handy when content changes often — but keep the output curated.

Validate

Paste your domain into the validator to confirm the file is reachable as plain text and every linked URL resolves.

Keep reading

• Adding llms.txt to Next.jsTwo clean ways to serve a spec-compliant llms.txt from a Next.js app — the public/ folder for a static file, or a route handler for generated content — plus how to verify it.
• llms.txt for documentation sitesDocs sites are the ideal llms.txt use case. How to generate one for Docusaurus, MkDocs, Mintlify and others — plus when to add llms-full.txt and Markdown page versions.

Validate your llms.txt →