Neue TYPO3-Extension llms_txt : Generate llms.txt Automatically with TYPO3

With llms_txt, we at WACON Internet GmbH have developed a new TYPO3 extension that automatically generates the llms.txt file from a TYPO3 website.

The idea behind it is simple: anyone who wants to provide an llms.txt for their website shouldn't have to maintain it by hand, separately from the actual website. After all, the essential information already exists in TYPO3.

Our extension therefore uses the TYPO3 page tree and dynamically generates a structured llms.txt from it. At the same time, editors can specifically control which pages appear in it and how they're described for AI systems.

What an llms.txt fundamentally is, and what role it can play in optimizing websites for AI agents, we explain in a separate article "What Is an llms.txt?".

In this article, we introduce our TYPO3 extension and its features in detail.

The Problem: A Static llms.txt Has to Be Maintained

An llms.txt is, in principle, very easy to create. It's essentially a structured markdown file with links and descriptions of a website's important content.

The real problem starts after that.

Websites aren't static. New pages get added, existing pages get moved or deactivated, URLs change, and entire sections disappear.

A manually maintained llms.txt would therefore need to be regularly checked and kept in sync with the current state of the website.

With a content management system like TYPO3, that seems unnecessary to us. After all, TYPO3 already knows:

• the website's structure,
• the pages that exist,
• the pages' URLs,
• page titles and descriptions,
• the publication status,
• access permissions,
• languages and translations.

Our extension uses exactly this information.

Generating llms.txt Automatically from the TYPO3 Page Tree

Once installed, the extension automatically makes the llms.txt available via the website.

From a TYPO3 page structure such as, for example,

a structured llms.txt can be generated automatically.

The first level of the page tree forms the thematic structure of the file. Subordinate pages are output as links.

For example:

The file doesn't need to be created separately and then maintained in parallel with the website.

Changes to the Website Are Taken Into Account Automatically

For us, this is one of the extension's most important advantages.

If a new page is published in TYPO3, it can automatically appear in the llms.txt. If a page is deactivated or deleted, it's correspondingly no longer output.

The llms.txt thus evolves together with the website.

This not only reduces maintenance effort, but above all the risk of an outdated file that points to URLs that no longer exist or doesn't know about important new content.

Editors Still Keep Control

A purely automatic takeover of the entire page tree wouldn't always make sense, though.

A website's structure was primarily designed for humans. For AI agents, different information or descriptions can be helpful.

That's why our extension complements automatic generation with editorial controls built directly into TYPO3.

Custom Description for a Page

A dedicated description can be set for individual pages.

A TYPO3 page might simply have the title:

TYPO3 Updates

In the llms.txt, that can become:

This gives a system processing the llms.txt a brief contextual summary in addition to the page title.

If no dedicated description is available, the extension can fall back on existing page information such as abstract or description.

The benefit for the editorial team: information doesn't necessarily have to be maintained twice.

Excluding Individual Pages or Entire Sections

Not everything that exists within a TYPO3 page tree needs to be part of the llms.txt as well.

That's why pages can be specifically excluded.

This is useful, for example, for technical helper pages or other content that isn't relevant for content orientation.

Typical TYPO3 settings are taken into account too. Pages that are hidden, not yet published, expired, or access-protected shouldn't simply appear in the file unchecked.

That means the llms.txt is not merely a copy of the TYPO3 page tree.

Marking Optional Content

Another feature of our extension is the ability to assign content to the Optional section.

This lets you distinguish core content from supplementary information.

On a company website, for example, the areas Products, Services, Industries, and References might be the focus, while other content is more supplementary in nature.

These can be output together under ## Optional.

This lets the editorial team further refine the automatically generated structure.

Navigation and llms.txt Don't Have to Be Identical

TYPO3 already offers nav_hide as a way to exclude pages from the regular navigation.

That doesn't necessarily mean, though, that those pages are also uninteresting for AI systems.

Our extension can therefore be configured for how such pages should be handled.

This is an important distinction:

A website's visible navigation and the information structure provided for machines don't necessarily have to be identical.

Configurable Page Tree Depth

Especially large TYPO3 installations can contain several hundred, or even thousands, of pages.

It wouldn't make much sense to generate a correspondingly huge llms.txt from that without filtering.

That's why you can configure how deep into the page tree should be considered.

This way, the file can deliberately be used as a compact overview of the website's essential content.

Integrating Additional External Resources

Not all of a company's relevant information necessarily lives within the TYPO3 website.

There might also be:

• external documentation,
• API documentation,
• a support portal,
• a GitHub repository,
• a knowledge base,
• other websites or applications.

Such resources can be included in the generated llms.txt as well.

This lets the file serve as a central entry point into further relevant information resources, beyond the actual TYPO3 page tree.

Multilingual TYPO3 Websites

TYPO3 is frequently used for international, multilingual websites.

That's why our extension also takes different site and language configurations into account.

Titles, descriptions, and URLs are generated in the context of the respective TYPO3 site and language.

This matters especially because a multilingual website doesn't necessarily have to have exactly the same content and structure in every language.

TYPO3 Multisite Is Supported Too

Another typical TYPO3 use case is multisite installations.

Within a single TYPO3 installation, several independent websites can be operated – for example for different brands, companies, or countries.

The extension therefore works in the context of the respective TYPO3 site.

This means each website can get its own appropriate llms.txt, even though several websites run within the same TYPO3 installation.

Dynamic – Yet Still Performant

Dynamic generation obviously shouldn't mean that the entire TYPO3 page tree has to be processed again on every single request.

That's why the extension includes caching.

The generated output can be cached and delivered quickly. If relevant content or the page structure changes, the cache can be invalidated and the file regenerated.

This lets the extension combine two seemingly opposing requirements:

The llms.txt stays dynamic and up to date, without having to be fully rebuilt on every request.

No Additional TYPO3 Page Required

We deliberately implemented the extension so that no additional page within the TYPO3 page tree is needed for the llms.txt.

A request to /llms.txt is processed directly, and the corresponding output is generated.

The generation itself is kept separate from determining the page tree. This keeps the extension clear and makes it easier to extend in the future.

Configuration via TYPO3 Site Settings

Global settings for the extension can be configured at the site level.

These include, for example:

• enabling llms.txt,
• the website's title,
• an introductory description,
• the depth of the page tree to read,
• how to handle certain page types or navigation settings,
• additional external resources.

Page-specific decisions, by contrast, are made directly on the respective TYPO3 page.

This follows a principle we consider generally important in TYPO3 projects:

Basic technical settings belong in the site configuration – content decisions belong as close to the editorial team as possible.

Why We Developed This Extension

Website optimization is changing.

Alongside usability, accessibility, search engine optimization, and structured data, the question of how well a website's content can be understood and accessed by AI systems and AI agents is becoming increasingly relevant.

At WACON, we're therefore increasingly focused on the AI readability of TYPO3 websites.

That said, we think it's important not to implement new developments as a short-term trend, but to integrate them sensibly into the CMS and existing editorial processes.

That's exactly where llms_txt came from.

If a TYPO3 website already knows what content exists, how it's structured, and which of it is published, an llms.txt should be generatable from that too.

The editorial team then only needs to step in where targeted optimization makes sense.

Another Building Block for AI-Friendly TYPO3 Websites

An llms.txt alone doesn't make a website "AI-optimized," of course.

Clean semantic HTML, an understandable accessibility tree, structured data, Schema.org, a good information architecture, and technically sound content remain at least as important.

But the llms.txt can add a further layer through which websites provide their most important content, structured specifically for AI agents.

The underlying llms.txt concept continues to evolve and has been available in a revised version since August 2026. Even so, it remains a proposed convention rather than a binding web standard. Accordingly, we don't want to tie any ranking or visibility promises to our extension either.

Our approach is more pragmatic:

If website owners want to provide an llms.txt, TYPO3 should take as much of the work off their hands as possible.

With llms_txt, the file is therefore not treated as an additional static document, but as a dynamic part of the TYPO3 website.