AI LLM Feed

The AI LLM Feed extension adds a tool to OpenCart 3 and ocStore 3 for creating a structured store description for language models and AI agents in llms.txt and Markdown format.

The extension creates llms.txt and llms-full.txt files, as well as separate Markdown files for products, categories, manufacturers, and information pages. Updates are processed through a queue and Cron, allowing the extension to be used in stores with large catalogues.

Important information about llms.txt

llms.txt is a proposed open format for presenting essential website information to language models and AI agents. It helps provide an AI system with a clear website description and structured links to important pages without requiring it to analyse menus, JavaScript, and the entire HTML layout.

The llms.txt protocol is not currently used by every AI system. Its support and practical use are still developing, so publishing these files does not guarantee website crawling, inclusion of its pages in AI answers, or improved search rankings.

The extension does not replace XML or HTML Sitemaps, robots.txt, canonical URLs, Schema.org structured data, conventional SEO, internal linking, or page content available to users. It is an additional technical channel that helps prepare a website for the future development of AI search and AI agents.

The llms-full.txt file in this extension is an extended index containing links to selected sections. The extension intentionally does not combine the entire catalogue into one large text file: complete data is stored in separate Markdown files, making it easier to update and use.

Important information about URL generation

The extension includes its own mechanism for building links to products, categories, manufacturers, and information pages. SEO URLs are generated using the standard seo_url table, the category_path structure, and the extension’s own URL settings.

During generation, the extension does not call OpenCart’s standard URL rewriting mechanism and does not depend on third-party SEO modifications being executed. This reduces the risk of errors caused by conflicts or special behaviour in third-party SEO URL and multilingual extensions.

The link format must be configured to match the website’s actual structure: select language folders or separate domains, a full or short category path, and a URL suffix. Before starting a full generation, we recommend opening the product preview and confirming that the generated links match the storefront URLs.

Extension features

• Create the root llms.txt file
• Create the additional llms-full.txt file
• Create separate Markdown files for products
• Create separate Markdown files for categories
• Create separate Markdown files for manufacturers
• Create separate Markdown files for information pages
• Create section indexes and a language index
• Export all, selected, or no records for each entity type
• Create a separate set of files for each active store language
• Add separate titles, descriptions, static text, and Sitemap URLs for each language
• Add separate HTML and XML Sitemaps to llms.txt and llms-full.txt
• Automatically add queue jobs when catalogue data changes
• Process the queue in batches via Cron

Content modes

The extension lets you choose how llms.txt and llms-full.txt are generated.

• Links only — the extension creates indexes, entity files, and structured links
• Static text only — llms.txt and llms-full.txt are created from the specified title, short description, manual text, and Sitemap URLs
• Static text + links — manual text is displayed after the short description, followed by automatically generated links

Separate title, short description, text, HTML Sitemap, and XML Sitemap fields are provided for llms.txt and llms-full.txt. Values are configured separately for each active language.

Export settings

One of three modes can be selected for products, categories, manufacturers, and information pages.

• Export all records
• Export selected records only
• Do not export this entity type

When “Selected only” is enabled for categories or manufacturers, these settings are also applied to products. For example, files can be created only for products from selected categories or only for products from specific manufacturers.

Product Markdown file content

Depending on the settings, a product file can contain:

• Product name and short description
• Link to the product page
• Product ID
• Model and SKU
• Manufacturer
• Main category
• Regular and special prices
• Availability status
• Last update date
• Product attributes
• Available options
• Cleaned description in plain text or Markdown format
• Main image
• Additional images with a configurable limit

URL settings

The extension allows you to configure the link format to match the structure of a particular website.

• Short SEO URLs
• Full URLs with parent category paths
• Product URLs with a full category path
• Category URLs with the complete hierarchy
• URL endings: no suffix, /, or .html
• Files for the default language only or for all active languages
• Language folders such as /ru/ or /en/
• Separate domains, subdomains, or base URLs for different languages

The internal OpenCart language code, such as uk-ua or en-gb, is used only for file storage and is not added to public URLs.

URL configuration examples

Website without language folders

When only the default language is exported and it does not use a language folder, the public URLs will look like this:

• https://example.com/llms.txt
• https://example.com/llms-full.txt
• https://example.com/llms/products/145.md

Default language without a folder, other languages with folders

If the default language opens without a prefix while other languages use folders, leave the default language field empty and enter the appropriate values for the other languages.

• https://example.com/llms.txt
• https://example.com/ru/llms.txt
• https://example.com/en/llms.txt
• https://example.com/en/llms/products/145.md

Languages on separate domains or subdomains

If separate domains or subdomains are used for languages, specify the base URL for each language in the extension settings.

• https://example.com/llms.txt
• https://ru.example.com/llms.txt
• https://en.example.com/llms.txt

SEO URLs ending in .html

If the store pages end in .html, specify it in the SEO URL suffix setting.

• https://example.com/product-url.html
• https://example.com/category/product-url.html

Automatic file updates

The extension uses standard OpenCart events. When a product, category, or information page is added, edited, deleted, or has its status changed using the quick action, the corresponding entity is added to the queue. Manufacturer changes are also added to the queue.

When a category is changed, the extension also adds related products and child categories to the queue. When a manufacturer is changed, its products are added to the queue. This is required because category names, paths, and manufacturers are used in product files and indexes.

Direct SQL queries do not trigger OpenCart events. If a third-party import changes the database directly, updating date_modified alone will not create a job. After such an import, run Full Reconcile or add the full catalogue to the queue manually.

Cron jobs

The extension provides separate URLs for different scenarios.

• Regular Cron without action — processes the existing queue in batches. Add this URL to the scheduler with an interval of approximately 1–5 minutes
• action=full — adds the entire current catalogue to the queue. Run it manually after installation or when all files need to be generated again
• action=index — adds only root files and indexes to the queue. Use it after changing titles, descriptions, Sitemap URLs, language URLs, or section placement
• action=reconcile — removes stale records and adds the current catalogue to the queue. Run it manually after a direct import, bulk deletion, or file synchronisation problem

URLs containing action=full, action=index, or action=reconcile should not be added to the regular recurring Cron job. They are intended for separate manual scenarios.

Queue, files, and log

• View queued jobs
• Queue pagination and sorting
• Process the queue manually
• Delete an individual job
• View generated files and their public URLs
• File list pagination and sorting
• Delete an individual file
• Delete all generated files
• Localised operation, change, and error log
• Log pagination and sorting
• Clear the log
• Protection against simultaneous manual and Cron processing

Advantages

• Structured catalogue representation for AI systems
• Preparation for the future development of AI search and AI agents
• No API keys or paid AI services required
• Automatic file updates after standard catalogue changes
• Batch processing for large catalogues through a queue and Cron
• Flexible selection of products, categories, manufacturers, and information pages
• Separate content for each language
• Built-in link generation mechanism
• Support for language folders, domains, and subdomains
• Result monitoring through the file list and log
• Built-in detailed help with configuration examples

Compatibility

• OpenCart 3.x / ocStore 3.x
• PHP 7.x–8.x
• Ukrainian, English, and Russian localisations
• Access to a Cron scheduler
• Write permission for the OpenCart storage directory

Installation

1. Upload the extension archive through Extensions / Installer
2. Go to Extensions / Modifications and click Refresh
3. Go to Extensions / Extensions
4. Select the Feeds extension type
5. Find AI LLM Feed and click Install

Recommended configuration sequence

1. Enable the extension
2. Enable llms.txt and, if required, llms-full.txt
3. Select the content mode
4. Enter the title, short description, text, and Sitemap URLs for the required languages
5. Select the entity types and their export modes
6. Configure the product Markdown file content
7. Configure language folders or domains to match the website structure
8. Configure the full category path and SEO URL suffix
9. Check the generated Markdown using the product preview
10. Save the settings
11. Add a full generation to the queue once
12. Configure a regular Cron job to process the queue
13. Check the public llms.txt and llms-full.txt URLs

If the server returns a 403 error when opening llms.txt or llms-full.txt, you may need to add an exception for these files to the standard FilesMatch rule in the .htaccess file. An example rule is provided in the extension help section.

DEMO

• Admin Page
• login/password: demo/demodemo

• llms.txt
• llms-full.txt

Licence

The licence covers one domain and its subdomains.