Does WordPress need an llms.txt file?

Treat llms.txt as orientation, not permission

An llms.txt file is an emerging convention for presenting a compact description and a curated set of important links. It does not replace robots.txt, page-level indexing controls, authentication, or a sitemap.

Do not use the file to make claims that the visible website does not support. The clearest version is short enough for a person to review during every meaningful site change.

Include only durable, public destinations

A practical WordPress file names the site, explains its purpose in one paragraph, and groups a small set of canonical links. Methodology, documentation, product or service pages, policies, and contact routes are stronger choices than tag archives or short-lived campaign URLs.

# Example Site

> A concise description of what the site provides and who it serves.

## Important pages
- [Documentation](https://example.com/docs/)
- [Methodology](https://example.com/methodology/)
- [Contact](https://example.com/contact/)

Choose how WordPress will publish it

A plugin may generate llms.txt dynamically, or the server may expose a physical file. Use one source of truth. Multiple plugins competing for the same route can create stale or contradictory output.

After changing permalinks, cache settings, or SEO plugins, fetch the public file in a logged-out browser. Confirm a plain-text response, a 200 status, and absolute HTTPS links.

• Keep the file at /llms.txt on the canonical hostname.
• Use UTF-8 plain text or Markdown-style content.
• Avoid private URLs, tracking parameters, and redirected links.
• Assign an owner and a review trigger.

Fix stronger signals first

If the site has an empty JavaScript shell, broken internal navigation, inconsistent canonicals, or no sitemap, llms.txt is not the priority. Fix the underlying pages first. Optional machine-facing summaries are only as trustworthy as the public content they point to.

Verification checklist

1. Confirm important pages are already public and canonical.
2. Keep the file concise and link only to durable URLs.
3. Return text/plain with a 200 response.
4. Check every link for redirects or errors.
5. Review the file whenever the site’s purpose or primary navigation changes.