Ryan Howard

Our roadmap is based on what we’re seeing in real-life data. That proposal is a suggested starting point but llms.txt is still experimental. We plan to keep md for individual pages on the back burner until we get confirmation from AI search crawlers or or evidence that md actually moves the needle.

@bbole llms.txt for generative engine optimization is experimental. The plugin does not generate md per post as in Jeremy’s proposal and we won’t be extending to support md until we have strong evidence that doing so is worth dev time.

@beeexquise – Send me an example please. If you don’t want to post publicly, you can provide it here: https://www.websitellm.com/listing/

As of now the plugin excludes individual pages and posts marked as no index by most SEO plugins and you can select which post types are included. We will be adding manual entry field on the next release that will give users additional fine tune control.

For even more control, you have the option of using our plugin to produce an initial draft of your llms.txt file, copy/paste that into a text document until you get it designed exactly to your specifications, deactivate our plugin, and remove or paste over the auto-generated llms.txt file using your own llms.txt file uploaded to the root of your website.

Hi Alex,

Thanks for the questions. Here’s as much as we know so far:

1. Should we block Googlebot from indexing /llms.txt? Why include it in the sitemap?

There’s no need to block Googlebot from accessing /llms.txt, as it doesn’t index this file by default — similar to how it treats robots.txt. The /llms.txt file is meant to be read, not indexed, and it helps LLMs understand your content structure. Including it in your sitemap ensures AI agents can reliably discover it.

2. Should I use /llms-full.txt as well, or is it unnecessary if /llms.txt includes the full article?

There’s no hard and fast rule here, but the short answer is yes, /llms.txt is typically sufficient. If you’re already including full articles (or near-complete ones) in that file, there’s usually no need for a separate /llms-full.txt unless you have a very specific use case.

3. Regarding “Maximum words” — full article or summary?

Our plugin sets a default character limit to avoid unnecessary server strain, but you can increase that limit if you want to expose more. LLM context windows are getting longer, but if you have a large site, be strategic about what you include.

4. When does it make sense to use /llms.txt, and when have you seen traffic growth?

It makes the most sense if your site has at least 20–30 pages of original, valuable content. The same kinds of quality signals that matter for traditional SEO apply. We’ve seen early traction from sites in evergreen niches that used /llms.txt to surface well-structured articles and it’s way to future-proof your content for LLM visibility. There are a number of new tools cropping up that measure LLM visibility in addition to traditional SEO rank trackers that offer AIOverview data.

• This reply was modified 1 year ago by Ryan Howard.

Thanks John! We do aim to please 🙂

Hi Colin,

Try changing the update frequency to daily (instead of immediate) and let us know if that helps.

🚨 Mise à jour : Nous avons supprimé la fonctionnalité /ai-sitemap du plugin.

Créer votre propre page explicative originale pour les LLMs ne pose aucun problème, mais nous avons réalisé qu’en ajouter une automatiquement pouvait entraîner des problèmes SEO inutiles.

Merci encore à toutes celles et ceux qui ont partagé leurs retours — nous restons engagés à garder le plugin utile, léger et en phase avec les bonnes pratiques du référencement.

Fair question 🙂

We plan to support it for the foreseeable future. We’ve made an update at least once a week since launch, and we have good traction and positive responses so far.

I haven’t made our roadmap public yet as we are still testing ideas, but there are a number of enhancements we’d like to integrate to make website data more accessible for site users and LLMs.