Generate, publish, then audit
Create a WordPress llms.txt file, then verify AI discovery.
As of August 2026, llms.txt is best treated as an orientation file, not a ranking promise. For WordPress sites, the practical workflow is to generate a clean starter file from the sitemap, publish it at the domain root, and audit whether AI crawlers can use the site.
- Sitemap
- WordPress source
- Use the WordPress sitemap to choose important public URLs.
- Root
- /llms.txt
- Publish the file at the domain root so crawlers can find it consistently.
- Audit
- Verify access
- Check robots.txt, sitemap, schema, and discovery signals after publishing.
How to create llms.txt for WordPress
Start from the WordPress sitemap, then keep only the URLs that help an AI system understand the site: homepage, service or product pages, pricing, documentation, guides, research, about, and contact. The file should describe the site and point to canonical URLs, not list every archive page.
After generating the file, publish it at /llms.txt on the same domain. Then run the AI SEO audit to verify that robots.txt, sitemap, schema, and core content are still accessible.
What llms.txt cannot fix on WordPress
llms.txt cannot fix a blocked crawler, a slow server, missing schema, thin service pages, or claims hidden inside images. It is a map, not the destination. The pages listed in the file still need clear headings, extractable HTML, concrete facts, and internal links that explain the entity.
For commercial pages, pair the file with structured data and answer-first copy. If the goal is citation, use the Perplexity citation checker after the technical audit is clean.
How llms.txt fits into a WordPress AI discovery workflow
The file helps orientation, but it does not fix blocked crawlers, weak schema, or thin content by itself.
| Signal or question | What the free check gives you | When paid monitoring matters |
|---|---|---|
| WordPress sitemap discovery | The generator can start from the WordPress sitemap and create a simple file from public URLs. | Use Pro when sitemap, robots.txt, and discovery files need recurring checks. |
| Publishing at /llms.txt | The page explains where the file should live and links to the generator. | Use Pro when deploys or plugin changes can remove the file silently. |
| AI crawler access | Run the AI SEO audit to verify whether AI crawlers can reach the site after the file is published. | Use Pro when crawler access must be monitored after WordPress updates. |
| Citable content structure | The audit checks whether important WordPress pages are structured for extraction, not only listed in llms.txt. | Use Studio when citations and competitor prompts need tracking. |
Free check to paid loop
Use Pro when WordPress updates can break discovery.
WordPress themes, SEO plugins, security plugins, and redirects can change crawler access and discovery files. Pro keeps the domain on a recurring technical audit loop.
- Monitor robots.txt and llms.txt.
- Catch schema and metadata regressions.
- Keep score history after plugin changes.
Frequently asked questions
Do WordPress sites need llms.txt?
WordPress sites do not need llms.txt as a guaranteed ranking factor. The file is useful as an orientation layer that points AI systems to important pages, docs, pricing, and canonical resources.
Where should llms.txt go in WordPress?
Publish llms.txt at the root of the domain, for example https://example.com/llms.txt. It should be publicly reachable and linked to canonical pages that already work for human readers and crawlers.
Can a plugin replace an AI SEO audit?
No. A plugin can help publish a file, but an audit is still needed to check crawler access, schema, metadata, content structure, and whether important pages are citable.
What should a WordPress llms.txt include?
Include the homepage, product or service pages, pricing, documentation, guides, research, contact or about pages, and any canonical resource that explains the entity clearly.
Next step
Turn the search intent into a measurable audit.
Start with a free page-level check. If the score exposes a technical or citation gap, move the same domain into monitoring instead of repeating manual checks.