Overview

llms.txt is a proposed standard (see llmstxt.org) that provides a curated, LLM-friendly index of a website at /llms.txt.
It helps large language models and AI agents discover the most relevant pages of a store without having to crawl the full HTML site.

The PWA follows the v2 revision of the proposal (August 2026).

The /llms.txt file is served as static content by the Nginx layer and does not require server-side rendering.

File Location and Naming

The content files are located in the nginx/llms/ folder.
Each file is named after the channel it belongs to, following the pattern <channel>_llms.txt.

This naming links every file to a channel from the multi-channel configuration so that the correct file is served automatically for each domain.
If no file matches a domain's channel, Nginx falls back to nginx/llms/default_llms.txt.
For example:

Discoverability (rel="describedby")

The v2 revision adds a way for agents to find the llms.txt file that covers a page without guessing the URL: the page links to it with the rel="describedby" link relation.

The PWA declares this once in src/index.html so that every route of the single-page application advertises it, in both client-side and server-side rendered responses:

<link href="/llms.txt" rel="describedby" />

The root-relative /llms.txt href intentionally ignores the <base href> so that it always resolves to the domain root file that Nginx serves for the current channel, including in Multi-Base-Href Setups where the base href becomes /en, /de, etc.

Single-Channel Setup

For the default configuration in nginx/multi-channel.yaml, where every host maps to the default channel, the file is:

nginx/llms/default_llms.txt

The file is served at /llms.txt for all domains.
If you explicitly define the default channel, the corresponding multi-channel configuration is as follows:

MULTI_CHANNEL: |
  .+:
    channel: default

However, setting MULTI_CHANNEL is optional for this case.

Alternatively, set the single channel to a specific, named channel instead of default.
In that case, /llms.txt serves that channel's file,for example, nginx/llms/inSPIRED-inTRONICS_Business-Site_llms.txt:

MULTI_CHANNEL: |
  intershoppwa\..+:
    channel: inSPIRED-inTRONICS_Business-Site

Multi-Channel Setup

If a single deployment serves multiple domains with different channels or themes (for example, a B2B and a B2C storefront), provide one file per channel, so that every domain serves its own /llms.txt:

• https://intershoppwa.azurewebsites.net/llms.txt serves the B2B channel file nginx/llms/inSPIRED-inTRONICS_Business-Site_llms.txt.
• https://intershoppwa-b2c.azurewebsites.net/llms.txt serves the B2C channel file nginx/llms/inSPIRED-inTRONICS-Site_llms.txt.

The corresponding multi-channel configuration is as follows:

MULTI_CHANNEL: |
  intershoppwa\..+:
    channel: inSPIRED-inTRONICS_Business-Site
  intershoppwa-b2c\..+:
    channel: inSPIRED-inTRONICS-Site

Multi-Base-Href Setup

A single domain can also serve several channels under different base href paths (for example, /en, /de, /fr, and /b2c), as configured in a list in the multi-channel configuration.
In this case, there is only one /llms.txt at the domain root, and it uses the channel of the first list entry.
As with all other setups, a missing channel file falls back to nginx/llms/default_llms.txt.

For example, if the first list entry uses inSPIRED-inTRONICS_Business-Site, the domain root serves nginx/llms/inSPIRED-inTRONICS_Business-Site_llms.txt.
The individual base href paths (such as /b2c) do not get their own llms.txt.

The matching multi-channel configuration looks as follows:

MULTI_CHANNEL: |
  .+:
    - baseHref: /en
      channel: inSPIRED-inTRONICS_Business-Site
      lang: en_US
    - baseHref: /b2c
      channel: inSPIRED-inTRONICS-Site
      theme: b2c

Behavior by Configuration

Further References

• The /llms.txt file proposal
• Guide - Building and Running nginx Docker Image
• Guide - Multi-Site Configurations
• Concept - Search Engine Optimization (SEO)