llms.txt is an emerging convention where websites publish a markdown file at /llms.txt listing the most valuable content for AI agents to consume. WordPress can serve llms.txt via dedicated plugins, manual file upload, or programmatic generation. This guide covers WordPress-specific implementation. Pair with llms.txt guide and agent compatibility.
Curated list of your most valuable, evergreen content. Not your full sitemap. Aim for 20-100 entries. Categories: documentation, key blog posts, FAQ pages, about/contact, pricing, integration pages.
Three options: (a) plugin: 'LLMs.txt for WordPress' or 'Website LLMs.txt' — auto-generated from posts. (b) Manual: upload static llms.txt via FTP to /public_html/. (c) Programmatic: register custom rewrite via theme functions.php that serves dynamic content.
LLMs.txt for WordPress plugin → Settings → choose content types to include → choose post statuses → set max entries → save. Plugin auto-generates llms.txt at yoursite.com/llms.txt.
Use a markdown editor. Structure: H1 (site name), short H2 description, then sections (H2) with bullet links. Example: '# Acme Corp' / '## Documentation' / '- [API reference](https://...) - REST API docs'. Upload via FTP to public_html/llms.txt.
Visit yoursite.com/llms.txt. Should serve raw markdown text, content-type text/markdown or text/plain. If 404: rewrite rules not generated (Settings → Permalinks → Save), or file in wrong directory.
Some AI agents look for llms-full.txt with complete content (not just links). Generate by concatenating full markdown of listed pages. Larger file but gives agents complete context without crawling links.
Server logs: search for requests to /llms.txt. Track which AI agents fetch it. Useful tools: Cloudflare analytics, WP Activity Log, custom log filters via plugin like Simple History.