# Meet AI Guide: llms.txt for WordPress, Done Honestly

> The emerging llms.txt convention, what it does for WordPress, and an honest look at where AI adoption actually stands in 2026.

*Source: https://plugins.viglan.com/meet-ai-guide-llms-txt-for-wordpress/*

AI assistants are quietly becoming a way people find things. They read the open web, summarise it, and answer in their own words — often without anyone clicking through. **llms.txt** is the emerging convention for giving those models a clean, readable map of your site instead of leaving them to scrape your theme markup, cookie notices and navigation menus.

We built **AI Guide** to add that layer to WordPress properly: spec-compliant, automatic, and honest about what it can and cannot do for you in 2026.

## What llms.txt actually is

The [llms.txt specification](https://llmstxt.org/) was proposed by Jeremy Howard of Answer.AI in September 2024. It is a single Markdown file at the root of your domain — `/llms.txt` — that hands a language model a curated summary of your site: an H1 with your site name, a short blockquote description, and lists of links to your most important pages with one-line notes. Think of it as a sitemap written for a reader rather than a crawler.

The convention has two companions. **llms-full.txt** inlines your key content into one long document, so a model can ingest everything in a single request. And a **Markdown copy of each page** — your-page.md alongside your-page — gives a clean, chrome-free version of the content itself.

## The honest part: where this stands in 2026

Most posts selling you an llms.txt plugin won’t tell you this, so we will. **No major AI company has officially committed to reading llms.txt in production.** Google’s John Mueller has said plainly that Search does not use it. OpenAI and Anthropic both point site owners to robots.txt for crawler control. Adoption studies in early 2026 put the file on roughly 10% of surveyed domains, and the majority of those files receive little or no direct AI traffic yet.

So why ship one? Two reasons that hold up. First, the clearest real-world win today is **AI developer tooling** — assistants like Cursor, GitHub Copilot and Claude fetch documentation live, and a good llms.txt points them at the right pages with far less wasted context. Second, it is **cheap, reversible insurance**: the file is trivial to serve, costs nothing in performance, and if the convention matures into something the big models consume, you are already there. If it doesn’t, you have lost nothing. We’d rather you decide that with the real numbers in front of you.

## What AI Guide does

- **Generates a spec-compliant llms.txt** automatically from your real content — pages, posts, and product types you choose — with no manual upkeep.
- **Builds an expanded llms-full.txt** for models that prefer everything in one request.
- **Serves a clean Markdown copy of every page**, stripped of theme markup, so the content reads the way a model wants it.
- **Puts everything in settings**, at maximum coverage by default. Toggle any file type, post type or section off in a click.
- **Shows you every file it serves** from a modern dashboard, with a setup wizard and a built-in guide.
- **Import and export settings** so you can move your configuration between sites.

It’s built the same way as the rest of our plugins: pure PHP, no framework, no ads, no upsell nags, effectively no front-end JavaScript. It generates text files and gets out of the way.

## One purchase, yours forever

AI Guide is a one-time purchase — no subscription, no per-site metering. If you want to make your WordPress site legible to the models that are increasingly reading it, [have a look at AI Guide](https://plugins.viglan.com/plugins/ai-guide-by-mhz/).