Release 46

Released November 10, 2026.

This release gives you control over what your site hands to AI tools. Your llms.txt file, the plain-markdown copy of each page, and llms-full.txt each have a setting of their own now, separate from your RSS feeds. Sitemaps also report when each page last changed.

New features

Choose which pages go into llms.txt

Each posts page type, such as a blog, now has an Include in LLMS feed checkbox in Settings → Page Types. When it is on, the page type’s pages are listed in your site’s llms.txt, and each page gets a plain-markdown copy at its URL with index.md added. When it is off, the pages are left out of both.

New page types start with the checkbox off, so pages like legal terms or landing pages stay out of AI tools unless you opt them in. Existing posts page types that had Show In Feeds on start with it on.

Show In Feeds now controls only your RSS, Atom and JSON feeds. Documentation and API pages are always in llms.txt. A page type set to Do Not Render is always left out, along with its markdown copies and any OpenAPI spec files.

The site’s AI agent follows the same rule: it only serves pages from posts page types that are in llms.txt.

Learn more: Configuring a page type, What your visitors get, Site AI agent.

Turn llms-full.txt on for the whole site

llms-full.txt, the single file holding the full text of your pages for AI tools, is now a site-wide setting. Find Generate LLMS Full in Settings → General. It is off by default. When you turn it on, llms-full.txt holds every page listed in llms.txt.

From the command line, set it with leed settings company set --generate-llms-full. Set a page type’s checkbox with --include-in-llms.

Learn more: General site settings, Settings field reference.

Edit a page type’s description

Settings → Page Types now shows a Description field under Name and Slug, on posts, documentation and API page types. The description appears under the page type’s heading in llms.txt.

Learn more: Configuring a page type.

Fixes

Sitemaps show when a page last changed

Sitemaps used to date each page by when it was first published, so a page you edited later still looked old to search engines. Each page’s <lastmod> now gives its last-modified date, so search engines pick up your updates sooner. The sitemap index takes the most recent change in each page type.

Sitemaps no longer include a <priority> value, which search engines ignore. The page type’s Sitemap Priority setting no longer has any effect.

Learn more: Feeds, sitemaps and robots.txt.

ESC