Adding llms.txt to WordPress takes about five minutes: create a plain text file named llms.txt, put an H1 with your site name, a one-line summary, and a few links to your most important pages, then upload it to your site’s root so it loads at yoursite.com/llms.txt. A plugin can automate that, or you can do it by hand with no plugin at all. The harder question is whether it does anything. Neither OpenAI’s nor Google’s own documentation lists llms.txt as something their systems read, and an independent scan of 137,000 domains found 97% of published llms.txt files got zero requests. This piece covers the setup honestly, then the evidence, using this site’s own llms.txt as the working example.
llms.txt showed up in a lot of “AI SEO checklist” content over the past year, usually presented as a settled best practice. It is not settled. It is a proposal from one developer, adopted by some sites, and not confirmed as read by any major AI platform. Here is what the file actually is, how to add it to WordPress with or without a plugin, and what the traffic data says about whether it is worth your five minutes.
What llms.txt actually is
llms.txt is a plain markdown file proposed by developer Jeremy Howard in September 2024, meant to sit at the root of a website the same way robots.txt or sitemap.xml does. The idea: give AI systems a short, structured index of a site’s most important content, since large language models have limited context windows and cannot easily process a full page the way a search crawler can.
The spec itself is short. Per the official documentation, a valid file needs exactly one required part – “an H1 with the name of the project or site” – plus a few optional ones: a blockquote with a short summary, any free-form paragraphs, and then H2-headed sections that function as link lists, each entry a markdown link with an optional note after it. The spec also proposes a more involved second layer: clean markdown mirrors of individual pages, served at the same URL with .md appended, so an AI system fetching a specific page gets a lightweight version instead of full HTML. Most sites that adopt llms.txt stop at the root file and skip the per-page mirrors, which is a meaningfully bigger project.
Nothing about this is a ratified web standard. There is no governing body, no required adoption, and no guarantee any given crawler even requests the file, let alone parses it.
Adding it in WordPress: plugin vs manual
Both routes work. Neither requires much.
The manual route: write a plain text file following the structure above and upload it to your WordPress site’s root directory via SFTP or your host’s file manager, so it resolves at yoursite.com/llms.txt. That is the entire task. No plugin, no database entry, no build step. The only real constraint is that your hosting setup needs to let you place a static file at the root, which most standard WordPress hosts do but some managed or sandboxed setups restrict.
The plugin route trades a few minutes of manual work for automatic upkeep. Several free plugins are listed on the official WordPress.org plugin directory that generate and serve an llms.txt file, with some pulling your site’s title, tagline, and published post list into the file automatically and updating it as content changes, and others adding rewrite rules so the file is served without ever touching the filesystem directly. If your site changes often and you want the file to track that without manual edits, a plugin removes the maintenance step. If your site is small and mostly static, hand-editing a text file once is arguably less overhead than adding another plugin.
Either way, keep the file honest. List pages that actually explain what your site or product does, not a dump of every URL on the domain – the spec’s own guidance treats it as a curated index, not a sitemap duplicate.
The evidence problem: who actually reads it
This is the part most llms.txt guides skip. Adding the file is trivial. Whether anything reads it is a separate, weaker claim.
Start with what the platforms themselves say. OpenAI’s developer documentation for its crawlers – GPTBot, OAI-SearchBot, ChatGPT-User – describes each one’s purpose in detail and does not mention llms.txt as an input to any of them. The one place llms.txt appears on OpenAI’s own developer docs is a navigation link to their own documentation index, not a statement about how their crawlers treat other sites’ files.
Google’s position is more direct. John Mueller of Google’s Search team was asked on Bluesky whether llms.txt files appearing on some Google properties amounted to an endorsement of the format. His answer: “I’m tempted to say something snarky since this has come up so often, but to be direct, no.” Reporting on that exchange notes Google’s Search team has separately said no one uses llms.txt files, that Google will not use them, and that sites publishing one should consider adding a noindex header to it.
Then there is the traffic data. Ahrefs analyzed crawler logs across 137,000 domains and found that 97% of published llms.txt files received zero requests in the measurement window. Of roughly 38,000 domains with a valid file, only about 1,100 saw any traffic to it at all – and among the requests that did happen, SEO audit tools and unidentified bots accounted for more volume than anything resembling an AI assistant. Bots tied to ChatGPT and Perplexity made up only about 1% of the requests among files that got traffic at all.
Put together: the format exists, some sites publish it, and the systems it was built for have not confirmed they read it.
This site’s own llms.txt, as the example
This site publishes its own llms.txt, and it is a reasonable template to copy. It opens with an H1 naming the project, a one-paragraph summary blockquote, and then H2 sections – “Core pages,” “Source,” “Articles” – each a short list of markdown links with brief notes. The summary paragraph states plainly that this site “does not claim llms.txt improves AI visibility; the evidence for that is weak.” That line is there because publishing the file and overselling what it does are two different decisions, and only one of them is defensible.
Verdict
Adding llms.txt to a WordPress site costs almost nothing – five minutes by hand, or a free plugin if you want it to stay current automatically. On that basis alone it is a reasonable thing to do, the same way adding a sitemap.xml is a reasonable thing to do even without proof any specific crawler fetches it that day. What is not reasonable is expecting it to move AI citations or traffic. No major platform has confirmed it reads the file, and the best independent data available shows the overwhelming majority of published llms.txt files sit unread. Do the setup if you want to, keep it accurate if you do, and do not count it as an AI-SEO strategy on its own.
Frequently asked questions
Do I need a plugin to add llms.txt to WordPress?
No. llms.txt is a plain text file that only needs to exist at your site’s root, so uploading one manually via SFTP or your host’s file manager works the same as any other method. A plugin only helps if you want the file to update automatically as your content changes, which matters more for large or frequently updated sites than small ones.
Does ChatGPT or Google actually read llms.txt files?
There is no confirmation that either does. OpenAI’s crawler documentation does not list llms.txt as an input for GPTBot, OAI-SearchBot, or ChatGPT-User. Google’s John Mueller directly said Google does not endorse the format, and separate reporting says Google’s Search team has stated no one uses these files. Independent traffic analysis across 137,000 domains found 97% of published llms.txt files got zero requests.
Is adding llms.txt to a WordPress site worth doing?
It costs very little to add, so it is a low-risk addition if you want one. But current evidence does not support treating it as something that will increase AI citations or visibility, since no major AI platform has confirmed reading it and most published files receive no traffic at all. Treat it as optional housekeeping, not a growth tactic.
For the fuller technical picture of what AI crawlers document about themselves and how that compares to llms.txt, how to get cited by ChatGPT and Perplexity covers OpenAI’s and Perplexity’s own crawler documentation in detail. The general WordPress setup this file fits into is covered in the WordPress SEO checklist. For where llms.txt sits inside the broader terminology, GEO vs SEO vs AEO and does schema markup help AI citations cover adjacent tactics with the same evidence-first approach.
Leave a Reply