How long should llms.txt be?

Usually one screen of markdown — key services, docs, and policies. If it grows past routine maintenance, split detail into HTML pages or consider llms-full.txt with an owner.

Should llms.txt repeat my full navigation menu?

No. Link only to URLs you want AI systems to prioritize, not every footer link. Quality and accuracy beat length.

Do llms.txt best practices guarantee AI citations?

No. They improve orientation after crawlers can read your site. Citations still depend on relevance, trust, and each platform's policies.

AI search fix

llms.txt best practices for AI search

llms.txt best practices start with crawl access: robots.txt and your CDN must allow trusted AI bots before you publish /llms.txt. Keep the file short, use the llmstxt.org layout, link only to public 200 URLs, date your updates, and avoid duplicating your entire sitemap. Google does not require llms.txt for generative AI in Search when crawlability and helpful content are solid. The file is optional GEO preparation for other AI systems — not a ranking switch.

Review llms.txt after pricing, product, or policy changes. Remove broken links and login-gated PDFs. If you need long excerpts, consider llms-full.txt with a maintenance owner — otherwise stay with a lean llms.txt map.

llms.txt best practices checklist

Allow GPTBot, PerplexityBot, ClaudeBot, or other bots you trust in robots.txt first.
Use a clear H1, one-line summary, and markdown links to canonical HTML pages.
Limit sections to what you can keep accurate within one business day of edits.
Add an Updated line with an ISO date after each meaningful site change.
Validate /llms.txt returns 200 over HTTPS without auth walls or redirect loops.

You'll get an HTML report on /llms.txt reachability and whether AI crawlers are blocked on your domain.

Run Express Check

Updated 2026-05-20

llms.txt best practices for AI search

llms.txt best practices checklist

Related questions