Documentation: llms.txt and llms-full.txt generator for PrestaShop

The module writes llms.txt and llms-full.txt into the shop root — a concise description of the shop, its catalogue and categories, aimed at language models. This page covers the configuration and, honestly, what to expect from these files today.

What the module does

The generator builds two text files: llms.txt with a condensed map of the shop (company description, categories with URLs, product list) and llms-full.txt with fuller descriptions. Both land in the shop root and are served at /llms.txt and /llms-full.txt. The module also appends a rule to .htaccess forcing UTF-8 for these files — without it a browser may render accented characters as mojibake.

The files are generated in the shop's default language only.

Requirements

  • PrestaShop 1.7, 8 or 9.
  • Write permission in the shop root — the module writes three files there.
  • No ionCube.

Installation and configuration

  1. Back office → Modules → Module Manager → Upload a module.
  2. Fill in the store description (PD_LLMS_STORE_DESC) — this is the text that opens the file and the first thing a model reads. It should carry the company name, what it does, the scope of the offer and the purchase terms.
  3. Decide whether to skip product descriptions (PD_LLMS_NO_DESC_PROD) and category descriptions (PD_LLMS_NO_DESC_CAT). Skipping gives a shorter file but leaves less to quote.
  4. Click Generate. The last run timestamp is stored in PD_LLMS_LAST_GEN.

Automatic generation

The module ships an AdminPdLlmsGeneratorCron controller protected by a timing-safe token comparison. Scheduling it once a day is enough — the files are only useful while they keep up with the catalogue.

The robots.txt entry

Add to robots.txt:

Allow: /llms.txt
Allow: /llms-full.txt

PrestaShop overwrites robots.txt when you generate it from the back office (Traffic → SEO & URLs → Generate robots.txt file), so the entries have to be restored after every such run.

What to expect

Worth saying plainly: llms.txt is a proposed convention, not a standard supported by search engines. Google does not claim to read it. The file does no harm, costs a few kilobytes and can help when someone points a model at it by hand — but it does not replace what actually drives whether models cite a shop: content in ordinary HTML, structured data, and mentions in independent sources.

Troubleshooting

“Cannot write llms.txt”

The shop root is not writable by the web server user. On shared hosting it is usually enough to give the directory write permission for the account owner.

“Cannot write .htaccess”

Same cause. The encoding rule is optional — without it the file still works, it may just display with the wrong encoding in a browser.

The file does not contain new products

The files do not refresh themselves. Run the generation by hand or schedule the cron controller.

Module page in the shop

Back to top