The llms.txt WordPress plugin
that stays current by itself.
Generate llms.txt and llms-full.txt from your published content, serve them at /llms.txt, and regenerate on every save - free, with zero external HTTP calls. Hand-written llms.txt files go stale the day you publish; a generated one cannot.
Generate, serve, verify.
The plugin walks your published posts and pages and writes a structured llms.txt index plus an expanded llms-full.txt - no hand-maintained file to forget about.
Served dynamically at yoursite.com/llms.txt with a 1-hour cache and regenerated on every save_post. Publish a post, and the index already knows.
The plugin links to the free llms.txt checker at citevera.com/tools, which fetches your file the way a crawler would - including the plain-permalinks homepage-in-disguise failure it specifically detects.
What llms.txt does and does not buy you.
We sell an llms.txt generator, so read this section skeptically - and then check it yourself. The llms.txt convention is real and tooling around it is growing, and some AI crawlers do fetch the file, which your own server logs can confirm. What nobody can honestly claim: that any major engine has publicly committed to consuming it, or that shipping one causes more citations. The evidence that exists is correlational.
Our recommendation is unchanged by that honesty: generate it anyway. The cost is one plugin install, the maintenance burden with generation is zero, there is no downside, and the fetches are verifiable. We wrote up what llms.txt is in the llms.txt explainer, the format details in how to generate llms.txt and how to write llms-full.txt, and every statistic with its framing on the AI search statistics page.
llms.txt is also just one of the plugin's three free pillars - schema injection and AI-crawler access control ship in the same install. The full plugin page covers all three, and the WordPress AI visibility audit shows how to measure your site before and after.
Everything llms.txt-related ships free.
- Dynamic /llms.txt generated from published content, 1-hour cache.
- llms-full.txt for engines that want depth, same source of truth.
- Automatic regeneration on every save_post - never stale.
- Endpoint health check inside wp-admin tells you /llms.txt is actually served.
- Rewrite rules flushed on activation; pretty-permalinks requirement surfaced, not hidden.
- Zero external HTTP calls in the free tier, enforced by a CI guard on every build.
llms.txt plugin FAQ
What does an llms.txt WordPress plugin do?
It generates an llms.txt file - the emerging convention for a curated, AI-readable index of your site - from your published content and serves it at yoursite.com/llms.txt. Citevera regenerates the file automatically on every save_post, so it never drifts from what you actually publish, and caches it for an hour for performance.
Is the Citevera llms.txt plugin free?
Yes. llms.txt and llms-full.txt generation, serving, and automatic regeneration are all in the free tier, which makes zero external HTTP calls - a CI guard script enforces that on every build. Install it from the WordPress.org directory or upload the zip from citevera.com.
Why is my llms.txt returning my homepage instead of the file?
Almost always plain permalinks. WordPress can only route /llms.txt to the plugin when pretty permalinks are enabled; with plain permalinks the request falls through to the homepage. The plugin flushes rewrite rules on activation and its endpoint health check tells you whether /llms.txt is actually being served. You can verify from outside your server with our free llms.txt checker - it specifically detects the homepage-in-disguise case.
What is the difference between llms.txt and llms-full.txt?
llms.txt is the curated index: a short, structured map of your most important pages with one-line descriptions. llms-full.txt is the expanded version carrying substantially more content for engines that want depth. The plugin generates both from the same source of truth - your published posts and pages.
Does llms.txt actually help with AI citations?
Honest answer: the spec is real and some AI crawlers fetch the file - which you can verify in your own server logs - but no engine has publicly committed to consumption guarantees, and the correlational evidence that exists does not establish causation. We recommend shipping it anyway: the cost is near zero, the downside is none, and the fetches are log-verifiable. We keep the full evidence picture on our AI search statistics page.
Does the plugin do more than llms.txt?
Yes - llms.txt is one of its three free pillars. It also injects schema.org JSON-LD (deferring to Yoast, RankMath, and AIOSEO to avoid duplicates) and gives you per-agent Allow/Disallow control over 13 AI crawlers. Paid tiers add cloud audits, Gutenberg rewrites, and full schema coverage.
Install free, verify from the outside.
Activate the plugin, then run the free llms.txt checker against your domain and watch the verdict flip.