LLMs.txt Curator

01 / SOURCE DETAILS

About this tool

LLMs.txt Curator gives you control over what your website tells AI systems and other machines about itself. It finds the public content on your site, publishes it to llms.txt and llms-full.txt , and then lets you curate that representation: review what was found, write descriptions, arrange the order machines read, mark what matters most, and ask Curator why any individual page is or is not included. Version 2.0 is a rebuild around that idea. Every page, custom URL and fact is a Resource with its own editorial state and a recorded origin, so Curator can always answer three questions: what am I publishing, where did it come from, and why. New in 2.2 Markdown pages that match the page. With Markdown pages on, Curator takes a snapshot of each page in your llms.txt as a logged-out visitor sees it, in the background, and builds the Markdown from that. Content added by page builders and block templates, which is not in the stored post, is now included. Menus, headers, footers, comments, share buttons and “More posts” lists are left out. A better converter. Tables come out as tables, code keeps its indentation, numbered lists keep their numbers and nested lists stay nested. The same converter writes llms-full.txt and every .md address, so they always agree. See what machines receive. Open “Markdown” on any page in Your llms.txt to see its Markdown version laid out for reading, exactly as served, and how it was made: whether it came from a snapshot or the stored content, which part of the page was used, what was removed, and what was kept. “Take a snapshot now” refreshes it on the spot. Checks for every page. A new Pages group in Checks reports pages built from stored content because a snapshot failed (and why), pages with very little text, unrendered shortcodes, leftover markup, repeated text, uneven tables and menus that leaked into the content. “Check what visitors receive” now also checks a sample of .md addresses for the right type, the noindex and canonical headers, and revalidation. Never out of date. A snapshot is retired the moment its page, its approved comments or a synced pattern it uses changes, and the stored content is served until a new one is taken. When a post is unpublished, made private or given a password, every snapshot that links to it is retired too, so it leaves lists of posts straight away. Changes to your theme, templates, menus or plugins renew snapshots in the background. Answer requests for Markdown at the page’s own address (optional, off). A request for the normal page that asks for text/markdown in its Accept header gets the Markdown version. These replies are never stored by shared caches, and “Check what visitors receive” tells you if a CDN mixes them up. Read-only access for tools and agents. Through WordPress’s own Abilities API, signed-in tools can list what your llms.txt publishes, get a page’s Markdown version exactly as its .md address serves it, and ask what changed since they last looked. With WordPress’s MCP Adapter installed, AI clients such as Claude can use the same abilities. Nothing they do can change your curation, settings or what you publish, and they see only what you already publish. A new Agents group in Checks shows whether this is working. New in 2.1 Notes for machines: your own answer to “What would a machine get wrong about your site?”, published as written. Checks: Structure, Content, Delivery and Ownership. Observed facts, not a score. Ownership: anything else that answers, or could answer, /llms.txt. Bring in an existing llms.txt: staged for review, approved in one step, undoable. Also: links to Markdown pages, the Optional section, Site Health, a block editor panel and the Abilities API. What 2.0 gives you Automatic discovery, human curation. Curator finds your public content and publishes it straight away, marked as found automatically rather than reviewed. You promote what you have checked, exclude what you do not want, and nothing waits on you to be represented. Your llms.txt. Arrange sections and pages with exactly what machines receive shown beside you as you work, in readable form or as the Markdown that gets published. Drag if you like; every move is also a button. Why? Open any resource and see the decisions behind it, separated into what Curator observed about the page and what you decided, ending with the exact line it contributes to the file. Representation coverage. Not a score. Curator tells you whether it can account for every resource it found: represented, excluded by you, unavailable to visitors, or not yet checked. The goal is zero unexplained. Unpublished changes. When your curation differs from the published file, Curator says so, shows what changed including the old and new wording, and publishes when you are ready. Check what visitors receive. After publishing, Curator looks at your public file and tells you plainly whether visitors get the new version, or whether a cache or an old file is serving an older copy. Markdown pages (optional). Switch on to offer each page in your llms.txt as Markdown at its address plus index.md, for example /about/index.md, following the llms.txt proposal. Off by default. Suggested descriptions, honestly labelled. Curator can fill empty descriptions from what the page already publishes (schema, SEO meta, excerpt, Open Graph, page content) and tells you which one it used. A suggestion stays marked as a suggestion until you accept or edit it. Curator does not write text for you. Site details. Describe the organisation behind the site once, and Curator publishes it above the first section. Where WordPress or your SEO plugin says something different, Curator shows you both and publishes your choice. Facts and custom URLs. Publish a short factual statement that does not deserve its own page, or a URL Curator did not find on its own. Curator stores and represents a URL; it never fetches it. Safe by default Both files are generated as a logged-out visitor, not with the permissions of the administrator who publishes. Drafts, private pages, password-protected pages and noindex pages are left out, and so are pages restricted by Paid Memberships Pro, MemberPress, Restrict Content Pro or WooCommerce Memberships. Any other membership or access plugin can mark content as restricted through the llmscu_is_restricted filter. Curator explains each exclusion. An llms.txt this plugin did not create is never overwritten. No AI ranking claims, no scores, no data sent anywhere. The only requests Curator makes are to your own site: to check what visitors receive, and, with Markdown pages on, to take snapshots of your own public pages in the background. Snapshots come from your server’s own address, so if your site shows extra content to requests from the server itself (an IP allow list, or a maintenance mode that lets the server through), leave Markdown pages off. What llms.txt is, and what it isn’t (June 2026) Being straight with you matters more than overselling. Google Search ignores llms.txt : it will not help or harm your Google rankings, and Google confirmed in June 2026 that it is fine to maintain the file for other systems that do read it. So this plugin is not an “AI ranking” tool. Where the file genuinely earns its place: on-site navigation for agents already on your site, the surfaces that actually read it (such as Perplexity and coding agents), and passing Chrome’s Agentic Browsing audit. The honest, useful question is not “does this rank me” but “which AI bots are actually reading my file”, and this plugin answers it from your own server logs. What makes this different Most llms.txt plugins treat the file as a static output. LLMs.txt Curator treats it as a living asset: Description coverage : Curator shows how many published resources have a description and which still need one. It is a count, not a score. Suggested descriptions : fills empty descriptions from what the page already publishes (schema, SEO meta, excerpt, Open Graph, page content), names the source it used, and leaves each one marked as a suggestion until you accept or edit it. Never overwrites what you wrote. Change detection : the header tells you when your curation differs from the published file, and Publish brings it up to date. Per-Page Title Override : set a different title for each page specifically for AI consumption, without touching your on-site SEO. Safety checks : Curator will not publish a file with missing or duplicated pages or broken formatting. Includes an on-demand format check with plain-English results. AI Crawler Analytics : see which bots visited in the last 7 days, with a visual bar chart. OpenAI, Anthropic, Perplexity, Google: know who is actually reading your file. Core features Visual composition : arrange sections and pages in Your llms.txt, with the resulting file shown beside you; each section becomes an ## heading per the spec llms-full.txt generation : the companion file with full Markdown content for each curated page Five SEO plugin integrations : Rank Math, Yoast SEO, All in One SEO, SEOPress, The SEO Framework Schema-aware descriptions : uses structured data before falling back through the description chain When to publish : Instant (about 30 seconds after a change), Daily, Weekly, or only when you click Publish WooCommerce support : SKU, price, stock, categories, dimensions; respects product visibility WordPress Multisite : network-activate across all sites; each site manages its own independent llms.txt; a network screen to publish each site or all of them Pre-built templates : Business, E-commerce, SaaS, Blog, Local Business Show the whole file : read the exact file before you publish, in readable form or as Markdown Markdown pages : optional per-page Markdown for everything in your llms.txt, built from a snapshot of the public page, with excluded and non-public pages returning not found Import / export : move your configuration between sites as JSON WP-CLI : wp llms-txt regenerate , wp llms-txt status , wp llms-

02 / SOURCE DETAILS

Getting started

Upload the llms-txt-curator folder to /wp-content/plugins/ . Activate through the ‘Plugins’ menu. Open LLMs.txt in the admin menu to begin curating. Settings are under LLMs.txt -> Settings . Or install directly from the WordPress plugin repository by searching for “LLMs.txt Curator”.

03 / SOURCE DETAILS

Frequently asked questions

What is llms.txt? llms.txt is a proposed standard (llmstxt.org) that provides AI systems with a curated, Markdown-formatted overview of a website’s most important content. A strategic selection of the pages you want AI to know about, not a sitemap. Can AI tools and agents use Curator? Yes, read only, and only when signed in as a user who can manage Curator. Curator registers abilities with the WordPress Abilities API (WordPress 6.9 or later): get-site, list-resources, get-resource, get-representation, get-changes, get-published-file, explain-resource and get-diagnostics. They are available through PHP and the REST API. If you install WordPress’s MCP Adapter plugin, AI clients that speak MCP can use four of them: get-site, list-resources, get-representation and get-changes. Curator does not include an MCP server of its own. “Public” in an ability’s settings means listed for tools; it never means anyone can call it. Every call checks the signed-in user. To keep Curator’s abilities out of MCP lists, return false from the llmscu_abilities_public filter. The abilities answer only from what you publish. A draft, private, password-protected or excluded page gets the same “not available” answer as an address that does not exist. A page’s Markdown is returned only if a logged-out visitor can read the page now, and only if you publish Markdown (Markdown pages or llms-full.txt). Calling them never changes your settings, curation or what you publish, and Curator takes no snapshots and makes no requests to answer them. (When a page’s Markdown comes from its stored content, its blocks are rendered as they are when the page is viewed, and a block that fetches something, such as an RSS block, still does.) get-changes counts publishes, not time. Each publish has a number; a tool keeps the number it was given and asks what was added, changed or removed since. Pages whose content changed without their llms.txt line changing have a new fingerprint in list-resources, so a tool can tell what to fetch again. Page text in a returned Markdown version is written by your site’s authors and visitors, and tools should treat it as content, not instructions. What is llms-full.txt? A widely used companion to llms.txt , rather than part of the llms.txt proposal itself. While llms.txt contains links and short descriptions, llms-full.txt contains the full Markdown content of each page. Optional: enable it in Settings when ready. Do I need both files? No. llms.txt alone is sufficient. llms-full.txt is useful if you want AI systems to have immediate access to your full content without additional crawling. What does Description Suggestions do? Scans every curated page and fills missing descriptions using a five-step fallback chain: schema markup -> SEO meta -> excerpt -> Open Graph -> page content. Pages with descriptions already set are never touched. What is description coverage? A count of how many listed pages have descriptions, shown in the admin with the pages that still need one. It is not published in the file. What does Title Override do? Lets you set a different title for a page in your llms.txt output without changing it on your site. Useful when your WordPress title includes your site name but you want AI to see a cleaner, more descriptive title. What do the safety checks do? They run before every publish. If errors are found, the file is not published and the results are shown immediately, so a broken or malformed file never goes live. Switch them on or off in Settings. Which SEO plugins are supported? Rank Math, Yoast SEO, All in One SEO, SEOPress, and The SEO Framework. Which AI bots does the crawler log detect? GPTBot (OpenAI), ChatGPT-User, ClaudeBot (Anthropic), PerplexityBot, Google-Extended, Applebot-Extended, Meta-ExternalAgent, Bytespider (ByteDance), CCBot (Common Crawl), Cohere, DeepSeek, and Amazonbot. What if my host blocks file writes? The plugin has a rewrite rule fallback that serves both files via WordPress. Choose between “Direct file”, “Rewrite rule only”, or “Both” (recommended) in Settings. Does this work on multisite? Yes. Activate network-wide from Network Admin > Plugins, or activate per-site on individual sub-sites. Each site manages its own independent llms.txt ; there is no shared network file. The Network Admin overview page (Network Admin > Settings > LLMs.txt Curator) shows every site’s generation status and lets you regenerate any site, or all sites at once, without leaving the network admin. The main site writes a physical file. Sub-sites, on both subdirectory networks ( example.com/site1 ) and subdomain networks ( site1.example.com ), share the main site’s document root, so they serve llms.txt via WordPress rewrite rule from the database instead. This is correct and functionally identical. WP-CLI works per-site using the standard --url= flag: wp llms-txt regenerate --url=https://site1.example.com Which pages are left out of the files? Password-protected pages are always left out, and so are pages your membership plugin restricts. Both files are generated as a logged-out visitor, so members-only sections inside a public page are left out too. Pages your SEO plugin marks as noindex are left out while “Leave out noindex pages” is ticked (the default). Items whose content type is not ticked under Content Types are left out too, and the validator lists each one so nothing disappears silently. My SEO plugin also makes llms.txt. What happens? Rank Math, Yoast SEO and All in One SEO can generate llms.txt too. This plugin never overwrites a physical llms.txt it did not create. If it finds one, the status panel says so and offers “Replace existing file”, which writes and checks the new file first, then moves the old one to a protected backup folder in uploads (with a random file name). If anything fails part-way, the original is put back. Switch the llms.txt feature off in one of the two plugins so they do not compete. How are the Markdown pages made? With Markdown pages on, Curator requests each page in your llms.txt from your own site, as a logged-out visitor with no cookies, in the background. It uses the page’s main content area, leaves out menus, headers, footers, comments and share buttons, and converts what remains. If a snapshot cannot be taken (a password-protected staging site, a maintenance page, a host that cannot answer its own requests), the page’s stored content is used instead and the Markdown page says which. A snapshot is never used after its page has changed. Does Curator request my pages? Will it slow my site? Only with Markdown pages on, only for pages in your llms.txt, and only in the background: never while a visitor is waiting. Up to 20 pages are requested at a time, a minute or so apart, until all have a snapshot; then each is renewed about once a day, or sooner when the page changes. If your site cannot answer its own requests, Curator stops trying and waits longer each time. With llms-full.txt on and Instant publishing, llms-full.txt is rebuilt after new snapshots; on Daily, Weekly or Manual it changes only when you publish. Can I change what is left out of a page’s Markdown? Yes, with the llmscu_extraction_noise filter. Each rule names a tag, id, class or attribute to remove from the content area. The Inspector’s Diagnostics view lists what was removed from each page. Is any data sent externally? No. Everything stays on your server. No telemetry, no external API calls, no cookies. Crawler IP addresses are anonymised before storage.

Explore related topics