To add an llms.txt file to a WordPress site, install a compatible plugin, choose only the public content you want agents to discover, generate the file, and verify that https://yourdomain.com/llms.txt is publicly reachable. The file is an emerging Markdown convention for giving AI agents concise site context and links to more detailed pages. It is not a guaranteed way to improve ChatGPT visibility or search rankings.
What llms.txt does
The llms.txt proposal describes “a proposal to standardise on using an /llms.txt file to provide information to help agents use a website.” Jeremy Howard published the proposal on September 3, 2024, and modified it on August 10, 2026. A file normally lives at the site root, although a subpath can be used.
It is written in Markdown. The only required part of the format is an H1 heading. A blockquote summary, explanatory text, and H2 sections containing links are recommended. The purpose is to give an agent a compact map of the site, then point it to detailed Markdown or HTML pages when it needs more information.
What it cannot promise
Do not present llms.txt as an SEO switch. WordPress.com says that not all AI systems use it, and Project LLMs.txt documentation states that no major search engine or LLM provider has officially announced that it seeks out llms.txt files. Treat it as an interoperability aid that may help compatible agents understand your site, not as a ranking or inclusion guarantee.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
Choose a WordPress plugin
Two commonly documented routes are Website LLMs.txt and Project LLMs.txt. A third option, Open-WP-Club’s open-source generator, is aimed at developers who need hooks and alternate delivery formats.
| Option | Installation and requirements | Output and automation | Notable controls |
|---|---|---|---|
| Website LLMs.txt | Install from Plugins → Add New. Its documentation describes normal WordPress installation and a Settings → LLMs.txt screen. | Generates /llms.txt; can regenerate immediately, daily, or weekly. Rewrites can serve the file when the host cannot write the web root. |
Integrates with Yoast SEO, Rank Math, SEOPress, and AIOSEO. Restricted or non-public content is excluded by default. |
| Project LLMs.txt | WordPress 6.4 or newer and PHP 8.1 or newer. WooCommerce 7.0 or newer is optional for products. | Can produce /llms.txt, /llms-full.txt, and optional per-page /llms/*.md files. |
Scans posts, pages, products, and custom post types. Physical-file mode requires permission to write in the site root. |
| Open-WP-Club generator | WordPress 6.4 or newer, PHP 8.2 or newer, and Composer. | Supports /llms.txt, .md URLs, and Accept: text/markdown responses; caching is available. |
SEO metadata, custom taxonomies, and developer filters for custom integrations. |
Compare the plugins on the controls that matter to your site: whether they write a physical root file or use rewrites, how they regenerate, whether noindex and private content are filtered, whether Markdown page variants are available, and whether your WooCommerce or custom post types are supported. Check the plugin’s current maintenance and security information before installing it.
Install and configure Website LLMs.txt
- Back up your site. Export a database backup and confirm that you can restore it before changing plugins or rewrite rules.
- Open the installer. In WordPress admin, go to Plugins → Add New, search for Website LLMs.txt, install it, and select Activate.
- Open its settings. Go to Settings → LLMs.txt, the path documented by the plugin.
- Enter site details. Set the site title and a short description that accurately explains what the site publishes.
- Select public content. Choose the post types, pages, products, or custom post types that should be discoverable. Leave out private, noindex, nofollow, membership-only, draft, and access-controlled material.
- Choose regeneration timing. Use immediate generation for a small site or after a major edit. Daily or weekly regeneration is useful when content changes routinely.
- Generate and verify. Save the settings, generate the file, then open
https://yourdomain.com/llms.txtin a private browser window. Confirm that it returns Markdown rather than a login page, redirect loop, or 404.
If the host prevents writing to the document root, the plugin’s rewrite method can serve the URL without a physical file. Test the public URL after enabling rewrites and purge any page or CDN cache that still contains an earlier response.
Install and configure Project LLMs.txt
- Confirm that the server runs WordPress 6.4+ and PHP 8.1+. If you want WooCommerce product scanning, use WooCommerce 7.0+.
- Install and activate Project LLMs.txt from the WordPress plugin directory or the developer’s distribution channel.
- Open the plugin’s own admin sidebar entry.
- Select the post types, pages, products, and custom post types to scan. Exclude anything that is private, noindex, nofollow, or protected by access control.
- Choose the outputs you need:
/llms.txtfor the concise index,/llms-full.txtfor an expanded version, and optional per-page/llms/*.mdfiles. - If you select physical-file mode, grant the web root the required write permission using your host’s documented method. Avoid making the entire WordPress directory broadly writable.
- Generate the files and test each public URL from a logged-out browser and with an HTTP client.
Build a useful llms.txt file
A generated file should remain curated and small enough to fit in an agent’s context. Quality is more useful than listing every URL. A practical structure is:
Rank #2
# Example Site Name
> A concise description of what this site offers and who it serves.
Use the links below for the site’s authoritative information. Prefer the documentation and policy pages when answering questions.
## Products and services
- [Service overview](https://example.com/services/): What is included and who it is for.
- [Pricing](https://example.com/pricing/): Current plans and billing details.
## Documentation
- [Getting started](https://example.com/docs/start/): Installation and first steps.
- [API reference](https://example.com/docs/api/): Endpoints, parameters, and examples.
## Policies
- [Privacy policy](https://example.com/privacy/): Data handling and user rights.
- [Terms](https://example.com/terms/): Conditions of use.
Use canonical, descriptive links
Write full absolute URLs and short descriptions. Link to the canonical version of each page, not tracking URLs, search results, tag archives, or duplicate print pages. If your platform offers clean Markdown pages, link those versions for agent consumption.
Keep sensitive material out
An llms.txt file is public. Never include unpublished product plans, customer records, internal URLs, private documentation, admin links, or pages that require authentication. Filtering a page from search with noindex is not a substitute for access control, but it is a useful exclusion signal when a plugin supports it.
Advertise alternate Markdown representations
The proposal recommends marking a page’s Markdown representation with rel="alternate" type="text/markdown". The covering llms.txt file can be identified with rel="describedby". These relations can be supplied as HTML <link> elements or HTTP Link headers. Use them only when the referenced Markdown URL is actually available and stable.
WordPress.com: upload the file manually
On WordPress.com, the documented manual route is available on Business and Commerce plans. First identify high-value pages such as services or products, About, documentation, policies, and important articles. Write the links and descriptions in Markdown, save the file with the exact name llms.txt, and upload it to the site root through SFTP. Then visit the public URL and inspect the response while logged out.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #3
Because this route is manual, update the file whenever a URL, product, policy, or documentation page changes. A stale link list can be less useful than a shorter, maintained one.
Verify the response like an agent
- Request the exact root URL:
https://yourdomain.com/llms.txt. - Check for an HTTP 200 response, the expected Markdown body, and a content type such as
text/plainor another type your host documents for text files. - Test without administrator cookies and from a second network or a private window.
- Follow every link in the file and remove redirects, login gates, 404s, and links that expose content you meant to exclude.
- If you publish Markdown variants, request one representative
.mdURL or sendAccept: text/markdownand verify that the server returns the intended representation. - After editing content, regenerate the file and purge WordPress, reverse-proxy, and CDN caches so agents do not receive an old copy.
Troubleshooting common failures
The URL returns 404
Regenerate the file, save the plugin’s settings again, and flush rewrite rules by visiting Settings → Permalinks and selecting Save Changes. Check that another plugin or server rule is not intercepting the /llms.txt path.
The URL redirects to a login page
The file is probably behind membership protection, a staging lock, or a security plugin. llms.txt must be publicly readable to be useful. Exclude private content from the generated list instead of making the entire file private.
The file is empty or includes the wrong posts
Review selected post types and taxonomies, publication status, noindex settings, and plugin exclusions. Regenerate after changing those settings. For custom post types, confirm that the type is publicly queryable and supported by the plugin.
Free tools Windows power users keep installed
One-click scans. No signup required.
Physical-file generation fails
Check the PHP version and the plugin’s documented root-write requirement. On managed hosting, use rewrite serving or ask the host to provide a narrowly scoped writable location. Do not solve the error by granting unrestricted write access to the whole site.
Changes are not visible
Inspect response headers and clear page, object, reverse-proxy, and CDN caches. A daily or weekly schedule also means a newly published page may not appear until the next run unless you trigger immediate regeneration.
Markdown negotiation does not work
Not every host or plugin implements content negotiation. Verify that the page has a real Markdown endpoint and that the server honors Accept: text/markdown. Otherwise link directly to the published .md URL or omit the alternate relation.
Or skip the browser setup
If you also need clean screenshots of the public llms.txt page or other site pages, ScreenshotNeo provides a single-call website screenshot API. Before capture it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. It also offers an MCP server for AI agents with take_screenshot, get_page_info, and capture_pdf.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For API parameters and authentication, see the ScreenshotNeo documentation. This cURL request captures the public file as WebP:
Best Value
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/llms.txt -o llms.webp
The equivalent Python and Node.js calls are:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/llms.txt"}, timeout=90)
open("llms.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/llms.txt' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is included on every plan. Create a free ScreenshotNeo account.
Cost, reliability, and maintenance
The WordPress plugins described here do not make AI systems consume the file, so the main ongoing cost is maintenance: keeping links current, avoiding accidental disclosure, and ensuring scheduled generation continues after WordPress, PHP, theme, or plugin updates. Add a simple monitoring check for the root URL and review the file whenever you change navigation, products, documentation, or policies.
The proposal author describes thousands of sites publishing llms.txt as of August 10, 2026, but no methodology or independent market study accompanies that qualitative statement. It should not be treated as an adoption rate or performance statistic.
Recommended Free Tools
Frequently Asked Questions
Where should llms.txt live?
Use the public site root at https://yourdomain.com/llms.txt unless your platform or plugin documents a subpath or rewrite URL.
Should every WordPress page be listed?
No. Curate high-value public pages and link to detailed documentation rather than dumping every archive, tag, or duplicate URL.
Does llms.txt make ChatGPT cite my website?
No. Current documentation does not establish that major LLM providers seek out the file, so it cannot guarantee crawling, citations, or visibility.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

