LLMs.txt for WordPress: V2 Format, Lighthouse and Plugins

Updated 9 November 2026 · Standard formula, shown below

To add an llms.txt file to WordPress, use a plugin that generates it or create the file yourself and place it at your site’s root; the V2 format is a proposed, Markdown-based way to summarize a site for language-model tools. Lighthouse does not currently provide a standard built-in audit for whether llms.txt exists or follows that format, so check the file directly and treat any plugin’s Lighthouse-related feature as a separate, plugin-specific claim.

What llms.txt is—and what V2 means

llms.txt is a proposal for a plain-text Markdown file at a website’s root, typically reachable at https://example.com/llms.txt. It is intended to give language-model systems a concise, organized orientation to useful site material, with links to fuller sources. It is not a WordPress standard, a search-engine sitemap, or a recognized directive that guarantees a model will crawl, cite, or obey a site.

“V2” is used by some tools and discussions to refer to a newer or more structured interpretation of the proposal, but there is no universally enforced V2 validator or WordPress core format. Implementations can differ in headings, metadata, link presentation, and whether they create a companion file such as llms-full.txt. Check the documentation for the particular generator you use. Avoid assuming that a plugin’s label “V2” means every reader or crawler recognizes a formal standard.

How to add the file to WordPress

The goal is to publish a readable text file at the root of the public site, not merely to create a WordPress page whose URL happens to look similar. A typical workflow is:

Choose what to include. Identify stable, useful pages such as documentation, product guides, policies, and key reference material. Link to canonical public URLs, not drafts, private pages, or temporary query-string URLs.
Generate or write the Markdown. Use a plugin if its format and update behavior suit you, or prepare the file yourself. Keep descriptions factual and concise; do not claim that a page covers information it does not contain.
Publish at the root. A plugin may serve the file dynamically, while a manually uploaded file can be placed in the web root using your host’s file manager or deployment process. Confirm the location with your host, especially if WordPress is installed in a subdirectory.
Open the public URL. Visit https://yourdomain.com/llms.txt in a browser and confirm it returns the expected text without a login, redirect loop, or error page.
Recheck after changes. Review links and descriptions when important content moves, is removed, or becomes restricted.

Back up the site before changing files or server rules. Do not overwrite an existing file without checking what created it, and do not edit WordPress core files: updates can replace them. If a caching layer or CDN is in use, purge its cache after publishing and test the public URL again.

What Lighthouse can and cannot check

Google Lighthouse audits areas such as performance, accessibility, best practices, and search-engine optimization. Its standard audit categories do not include a dedicated check for the presence or correctness of llms.txt, and a good Lighthouse score does not verify the file. Conversely, a missing file does not by itself establish that a site has a Lighthouse problem.

You can still use Lighthouse for the site’s normal quality checks, then verify llms.txt separately. Open the URL in a browser or request it with a command-line HTTP client; check that the response is successful, the content is plain text or otherwise served as intended, and the links work. A custom Lighthouse audit or third-party service could inspect a URL, but that is not the same as a built-in Lighthouse standard. Confirm what such a tool tests before treating its result as authoritative.

Five WordPress plugin options to investigate

Plugin directories and features change, so verify current maintenance, compatibility, reviews, documentation, and the exact output before installing. These are options to investigate, not endorsements or a claim that each supports a particular V2 interpretation:

Website LLMs.txt — a plugin name used for generating an llms.txt file from WordPress content. Check whether its current release lets you control included post types and exclusions.
LLMs.txt Generator — a generator-style option to look for when you want WordPress content turned into a linked text file. Confirm its output location and update schedule.
LLMs.txt for WordPress — a straightforward search term and plugin listing name to check in the WordPress directory; confirm the exact developer and current feature set because similar names may be used.
Rank Math SEO — an established SEO plugin to check for any current, documented support relevant to AI-crawler files. Do not assume general SEO functionality means it generates a conforming llms.txt.
Yoast SEO — another established SEO plugin whose current documentation can be checked for related functionality. Verify explicitly whether the installed version creates this file; XML sitemap support alone is not the same thing.

The last two are included as products to investigate, not as a guarantee that they generate llms.txt. If a plugin does not document the feature, use a dedicated generator or a manually managed file instead. A plugin listing may also disappear, change names, or stop being maintained; check the live directory rather than relying on an old recommendation.

Choosing an approach and avoiding common problems

A dedicated plugin is convenient when it automatically reflects published content and offers clear inclusion controls. Manual creation gives you tighter editorial control and avoids adding a plugin, but someone must keep the file current. Before choosing, look at:

Whether the plugin documents its format and the meaning of any “V2” label.
Whether you can exclude private, outdated, thin, or sensitive pages.
Whether output is actually at the root and remains available after caching.
Whether the file updates when content changes and whether you can preview it.
Whether the plugin is maintained and compatible with your WordPress setup.

Common failures include publishing the file under a subdirectory, serving an old cached copy, linking to redirects or 404 pages, and exposing URLs that should not be public. Remember that a link in this file is not access control: never include confidential material or assume the file makes private pages safe. Also avoid presenting llms.txt as a replacement for robots directives, XML sitemaps, canonical URLs, or ordinary site navigation; each serves a different purpose.

Frequently Asked Questions

Does WordPress create llms.txt automatically?
No. WordPress core does not generally create this proposed file automatically. A plugin, a hosting or deployment process, or a manually uploaded text file is needed.

Does Lighthouse require llms.txt?
No standard Lighthouse audit requires it. Lighthouse results do not establish whether the file exists or is valid; test the URL and its content separately.

Is llms.txt V2 an official web standard?
It is a proposal with implementations that can vary, not a universally enforced web standard. Read the generator’s documentation and inspect its output rather than relying on the “V2” label alone.

Will adding the file make AI tools use or cite my website?
There is no guarantee. The file can provide a convenient index, but whether a particular service fetches or uses it depends on that service’s systems and policies.

Can I create llms.txt without a plugin?
Yes. Write a plain-text Markdown file, upload it to the site root using a safe hosting or deployment method, then check the public URL and maintain its links yourself.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.