WordPress serves the site root from the web host’s document root (often public_html), not from the WordPress admin media library. To publish llms.txt, upload llms.txt and optionally llms-full.txt next to wp-config.php / index.php so they resolve at /llms.txt, or use a plugin/redirect that serves Markdown at those paths. Generate a draft with a free generator, review it, then upload. llms.txt is an emerging convention — not a proven citation boost.
What are the key takeaways?
On WordPress, llms.txt must resolve at the domain root — usually by uploading files into the host document root alongside WordPress core files, not as a Media Library attachment.
- Upload llms.txt (and llms-full.txt) via FTP, SFTP, or hosting file manager.
- Confirm https://yourdomain.com/llms.txt returns the Markdown body.
- Do not bury the file under /wp-content/uploads/ if you want the conventional root URL.
- Generate a draft with the free generator; human-review before upload.
- No published proof that WordPress + llms.txt alone increases AI citations.
Where does the file go on a typical WordPress host?
Place llms.txt in the same directory as WordPress’s index.php — commonly public_html, www, or htdocs depending on the host. That is the document root browsers hit for https://yourdomain.com/.
The Media Library stores uploads under /wp-content/uploads/, which is the wrong location for the llmstxt.org convention that expects /llms.txt at the root.
- 1Generate and review Markdown for llms.txt (and optionally llms-full.txt).
- 2Connect via FTP/SFTP or open the host file manager.
- 3Upload both files into the WordPress document root.
- 4Load /llms.txt in a browser and verify the content.
What if the host or security plugin blocks root uploads?
Some managed WordPress hosts restrict root file writes. Options then include: a small custom plugin that serves Markdown at /llms.txt, a rewrite rule that maps /llms.txt to a static file elsewhere, or asking host support to place the file for you.
Whatever path you choose, the public URL should still be /llms.txt with a text body — not an HTML theme template wrapped around the Markdown.
How do you keep the WordPress map up to date?
Regenerate after major site structure changes — new product or docs sections, removed flagship pages — and review at least quarterly on active sites. See how often to update llms.txt.
If you publish many posts weekly, curate only the evergreen money and docs pages in the map; do not dump every blog URL.
What should you check besides the file?
Confirm robots.txt does not block AI bots you care about, and that important pages return crawlable HTML (not empty client shells). A root Markdown map cannot fix blocked or empty pages.
For measured crawlability and extractability after you upload, use AEOForged. This site generates the content map only.
Frequently asked questions
Can I upload llms.txt through the WordPress Media Library?+
You can store a file there, but the conventional URL is /llms.txt at the site root. Media Library URLs live under /wp-content/uploads/, so prefer FTP/file manager upload to the document root (or a rewrite that exposes /llms.txt).
Does a WordPress SEO plugin create llms.txt automatically?+
Plugin support varies and changes over time. Check your plugin’s current docs. If it does not emit root /llms.txt, upload static files or a small serving plugin yourself.
Will llms.txt help my WordPress posts rank in ChatGPT?+
There is no public controlled evidence that publishing llms.txt increases AI citations. Treat it as optional hygiene after access and content quality — not a guaranteed ranking lever.