LLMs.txt Generator for Magento 2

Your store, readable by every AI assistant. Generates and serves /llms.txt and /llms-full.txt — the emerging llmstxt.org standard — so ChatGPT, Claude, Perplexity, Gemini and other LLM-powered search tools can ingest your catalog, policies and company info as structured, token-efficient Markdown instead of scraping your HTML.

Panth LLMs.txt v1.2 publishes a machine-readable, AI-optimized Markdown index of your Magento 2 store at two well-known URLs:

• /llms.txt — compact, LLM-friendly site map: store overview, company info, priority URLs, admin-curated collections, key CMS pages, hierarchical category tree (no more flat duplicated names), and three curated product blocks (Featured, Best Sellers, Recent Arrivals) with prices, SKUs, categories and auto-generated short descriptions.
• /llms-full.txt — expanded variant: everything in llms.txt plus the complete text of your Shipping, Returns, FAQ and About-Us policy pages inline so LLMs can quote you verbatim instead of paraphrasing.

Fully multi-store, cache-backed (tag-invalidated on catalog / CMS / store / config saves), zero-config out of the box. Works identically on Hyva and Luma.

Get a free quote for your project in 24 hours — custom modules, Hyva themes, performance optimization, M1→M2 migrations, and Adobe Commerce Cloud.

Visit our website: kishansavaliya.com  |  Get a quote: kishansavaliya.com/get-quote

• Why llms.txt Matters for SEO in 2026
• What's New in v1.2
• Key Features
• Screenshots
• Example Output
• How It's Generated (No Cron Needed)
• Compatibility
• Installation
• Configuration
• Usage — How It Works
• Module Architecture
• Multi-Store Support
• Caching
• SEO Value — What You Actually Get
• Troubleshooting
• FAQ
• Support
• About Panth Infotech
• Quick Links

The SEO landscape has shifted. Shoppers now ask ChatGPT, Claude, Perplexity and Gemini questions like "What's the best running jacket under $80 at Luma?" or "Does store X ship to Germany?" — and those LLMs answer based on what they can read from your site. Without guidance, they crawl your full HTML (slow, noisy, often blocked by JS-heavy themes) or fall back to their pre-training snapshot (outdated).

llms.txt — an emerging standard proposed by Jeremy Howard and supported by an active community — solves this cleanly. You serve a small, well-structured Markdown file at /llms.txt that gives every LLM a curated map of your site's most important URLs + context. The spec is deliberately designed to be:

• Crawler-friendly — plain text, no CSS/JS, parseable in kilobytes instead of megabytes
• Markdown-native — every token the LLM reads is signal, not noise
• Hierarchical — H1 title → summary → sections (## Store Overview, ## Category Tree, ## Featured Products, etc.)

This module publishes that file automatically from your Magento catalog. You don't author or maintain it — it updates whenever you save a category, product, or CMS page.

The v1.2 rewrite is a major output upgrade driven by real LLM-readability feedback. Every change exists to reduce token waste and improve semantic clarity:

Everything from v1.1 still works — caching, per-store emulation, tag-based invalidation, the dedicated cache type, company info section, URL rewrites. v1.2 is additive + quality-focused.

Structured Output Built for LLMs

• Hierarchical Category Tree via proper Markdown nesting (no duplicate labels)
• Store Overview metadata block at the top — URL, type, store view, currency, locale, generation timestamp
• Priority URLs — admin-authored list of "read these first" URLs with auto-inferred labels
• Collections — separate from main taxonomy so LLMs understand "promotional landing page" vs "browse category"
• Key Pages (CMS) — filtered to drop Magento scaffolding (no-route, cookie notices, etc.)
• Company block — email, phone, address, country, VAT — pulled from general/store_information

Curated, Not Dumped, Products

• Featured Products — merchant-flagged via a configurable yes/no EAV attribute (default is_featured)
• Best Sellers — Magento's sales_bestsellers_aggregated_yearly aggregate (top ordered qty, indexer-driven, O(1) queries)
• Recent Arrivals — created_at DESC
• Each product line: [Name](url) — Price — SKU — Category with optional one-line short description
• Short description resolver: short_description → meta_description → first sentence of full description → auto-generated "Name — Category" fallback

Dual-Format Output

• /llms.txt — compact Markdown (5–10 KB)
• /llms-full.txt — expanded with inline Shipping, Returns, FAQ, About-Us policy bodies (10–50 KB)
• Same renderer pipeline for both — consistent structure, no drift

Built-In Caching (see "How It's Generated")

• Dedicated cache type panth_llms_txt in System → Cache Management
• Tag-invalidated on any admin catalog / CMS / store / config save — no cron needed
• 3.4× cold→warm speedup measured in production-grade tests

Multi-Store + Multi-Language Ready

• Full Magento\Store\Model\App\Emulation wrap — URLs, currencies, and locales render in the target store's context regardless of which hostname the request came in on
• Per-store summary, limits, exclude list, priority URLs, collections
• Multi-brand merchants can run distinct /llms.txt files per website or store view

SEO-Friendly HTTP Layer

• Content-Type: text/plain; charset=utf-8
• X-Robots-Tag: noindex — prevents Google indexing the raw file as a page
• X-Content-Type-Options: nosniff
• Content-Disposition: inline; filename="llms.txt"
• Cache-Control: public, max-age=3600 — CDN-friendly

Zero Maintenance

• No database tables
• No cron jobs
• No external API calls
• Cache auto-invalidates on merchant edits
• URL rewrites installed once via a Magento data patch (idempotent on re-run)

Admin Configuration — Stores → Configuration → Panth Extensions → LLMs.txt

v1.2 admin form: four collapsible fieldsets mirror the output sections. General owns the enable toggle, site summary, priority URLs and collections category IDs. Content Limits caps the category tree depth, CMS page count and exclude list. Curated Products drives the three product blocks (Featured / Best Sellers / Recent Arrivals) with per-block max counts, toggles and a short-description switch. llms-full.txt maps the four policy CMS identifiers (Shipping / Returns / About Us / FAQ). Every setting is store-view scoped.

/llms-full.txt — Default Store View (Hyva)

/llms-full.txt — Luma Store View

Same renderer, different store view. Store emulation ensures every URL resolves in the correct store context.

The improved /llms.txt looks like this (actual output from a Magento sample-data catalog):

# Your Store Name

> Short one-line store summary goes here (configurable in admin).

## Store Overview

- URL: https://yourstore.com/
- Type: E-commerce catalog (Magento 2)
- Store View: Default Store View
- Currency: USD
- Language: en_US
- Generated: 2026-04-23 12:00:00 UTC

## Company

- Email: hello@yourstore.com
- Phone: +1-555-0000
- Address: 100 Main Street
- City: Anytown
- Zip: 00000
- Country: US

## Priority URLs

- [Sale](https://yourstore.com/sale.html)
- [New Arrivals](https://yourstore.com/what-is-new.html)
- [Size Guide](https://yourstore.com/size-guide)

## Collections

- [Eco Friendly](https://yourstore.com/collections/eco-friendly.html)
- [Performance Fabrics](https://yourstore.com/collections/performance-fabrics.html)

## Key Pages

- [About us](https://yourstore.com/about-us): Our story and mission
- [Customer Service](https://yourstore.com/customer-service)
- [Shipping Policy](https://yourstore.com/shipping-policy)
- [Returns & Refunds](https://yourstore.com/returns)
- [FAQ](https://yourstore.com/help-center-faq)

## Category Tree

- [Women's Fashion & Clothing](https://yourstore.com/women.html)
 - [Tops](https://yourstore.com/women/tops-women.html)
 - [Jackets](https://yourstore.com/women/tops-women/jackets-women.html)
 - [Tees](https://yourstore.com/women/tops-women/tees-women.html)
 - [Bras & Tanks](https://yourstore.com/women/tops-women/tanks-women.html)
 - [Bottoms](https://yourstore.com/women/bottoms-women.html)
 - [Pants](https://yourstore.com/women/bottoms-women/pants-women.html)
 - [Shorts](https://yourstore.com/women/bottoms-women/shorts-women.html)
- [Men](https://yourstore.com/men.html)
 - [Tops](https://yourstore.com/men/tops-men.html)
 - [Jackets](https://yourstore.com/men/tops-men/jackets-men.html)
 - [Tees](https://yourstore.com/men/tops-men/tees-men.html)
 - [Bottoms](https://yourstore.com/men/bottoms-men.html)
- [Gear](https://yourstore.com/gear.html)
 - [Bags](https://yourstore.com/gear/bags.html)
 - [Fitness Equipment](https://yourstore.com/gear/fitness-equipment.html)
 - [Watches](https://yourstore.com/gear/watches.html)

## Featured Products

- [Push It Messenger Bag](https://yourstore.com/push-it-messenger-bag.html) — $45.00 — SKU 24-WB04 — Bags
 Slim, durable messenger bag perfect for daily commutes.
- [Summit Watch](https://yourstore.com/summit-watch.html) — $54.00 — SKU 24-MG03 — Watches
 Rugged GPS watch built for outdoor adventures.

## Best Sellers

- [Ina Compression Short](https://yourstore.com/ina-compression-short.html) — $49.00 — SKU WSH11 — Shorts
 Compression running short with exceptional support and comfort.
- [Erika Running Short](https://yourstore.com/erika-running-short.html) — $45.00 — SKU WSH12 — Shorts
 Body-hugging running short for runners who prefer a fitted cut.

## Recent Arrivals

- [Sample Product](https://yourstore.com/sample.html) — $99.99 — SKU sample-001 — Bags
 New arrival sample product description.

## Sitemaps

- https://yourstore.com/sitemap.xml
- https://yourstore.com/robots.txt
- https://yourstore.com/llms-full.txt

/llms-full.txt adds full policy bodies inline:

## About Us
[full About-Us page text, HTML stripped]

## Shipping Policy
[full Shipping-Policy page text]

## Return Policy
[full Returns-Policy page text]

## Frequently Asked Questions
[full FAQ page text]

This module is pull-based, not push-based. There is no cron job, no scheduled writer, no file on disk.

The flow:

1. An LLM crawler (or a curious human) hits https://yourstore.com/llms.txt
2. A Magento controller receives the request
3. The controller asks the Builder for the rendered Markdown
4. The Builder looks in its dedicated cache (panth_llms_txt cache type)

• Cache hit: returns the cached body immediately (~50 ms)
• Cache miss: composes fresh output from Magento's store / catalog / CMS APIs, caches it, then returns (~200 ms)

5. Controller adds the correct HTTP headers and streams the body back

When does the output refresh?

Practical refresh time: within seconds of any admin edit — the next request after save regenerates. Worst case on an idle store: stale by at most 1 hour.

Why pull-based instead of a cron:

• Always fresh on edits — admin saves invalidate immediately; no "wait for next cron tick"
• No wasted work — files that are never crawled are never built
• No disk state to get out of sync — cache entries live in Redis/FPC alongside everything else
• Simpler ops — nothing to monitor, nothing to restart, nothing to misconfigure

Composer Installation (Recommended)

composer require mage2kishan/module-llms-txt
bin/magento module:enable Panth_Core Panth_LlmsTxt
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush

Manual Installation via ZIP

1. Download the latest release ZIP from Packagist
2. Extract to app/code/Panth/LlmsTxt/
3. Ensure Panth_Core is installed (required dependency)
4. Run the same commands as above starting from bin/magento module:enable

Verify Installation

bin/magento module:status Panth_LlmsTxt
# Expected: Module is enabled

curl https://yourstore.com/llms.txt
# Expected: Markdown body starting with "# Your Store Name"

Navigate to Admin → Stores → Configuration → Panth Extensions → LLMs.txt. Settings are grouped into four fieldsets:

General

Content Limits

Curated Products

llms-full.txt (Expanded)

1. Install + enable once

Composer install, enable, cache flush. /llms.txt starts serving immediately with sensible defaults.

2. Customize per store

Go to admin config and override per store view if needed:

• Write a store-specific Site Summary
• Point Collections at your promotional landing category IDs (Sale, Eco, Seasonal)
• List Priority URLs — the pages you most want LLMs to know about
• Enable llms-full.txt and map the four policy CMS pages so AIs have your exact shipping / returns / FAQ wording

3. Flag featured products (optional)

If you already have an is_featured yes/no attribute on products, the module picks it up. Otherwise:

bin/magento attribute:create \
 --code is_featured \
 --label "Featured" \
 --input boolean \
 --source Magento\\Eav\\Model\\Entity\\Attribute\\Source\\Boolean

(Or create it from Stores → Attributes → Product.) Flip the flag on 6–10 hero SKUs, save, done.

4. Let it run

That's it. Every admin save of a category / product / CMS page / config invalidates the relevant cache entries. The next crawler hit regenerates. No maintenance.

5. Verify

curl https://yourstore.com/llms.txt | head -40
curl -I https://yourstore.com/llms.txt | grep -iE 'content-type|cache-control|x-robots'

The v1.2 rewrite is section-based. Each content block lives in its own small class implementing SectionInterface::render(int $storeId): string[]:

Panth\LlmsTxt\
 ├── Controller\Llms\
 │ ├── Index.php → serves /llms.txt (sets HTTP headers, calls Builder)
 │ └── Full.php → serves /llms-full.txt (same, calls FullBuilder)
 ├── Model\Cache\Type.php → dedicated panth_llms_txt cache type
 ├── Model\LlmsTxt\
 │ ├── Builder.php → composes /llms.txt from Sections
 │ ├── FullBuilder.php → composes /llms-full.txt from Sections + policy bodies
 │ └── Section\
 │ ├── SectionInterface.php
 │ ├── Overview.php → header (title, summary, metadata block) + Company
 │ ├── PriorityUrls.php → admin-authored priority list
 │ ├── Collections.php → admin-picked promotional category IDs
 │ ├── KeyPages.php → CMS pages with exclude filter
 │ ├── CategoryTree.php → hierarchical Markdown list walker
 │ ├── Products.php → Featured / Best Sellers / Recent selectors
 │ └── ShortDescription.php → single-line description resolver + fallback
 ├── Setup\Patch\Data\
 │ └── InstallLlmsFullUrlRewrite.php → url_rewrite mapping for /llms.txt + /llms-full.txt
 └── etc\
 ├── acl.xml
 ├── cache.xml → declares the panth_llms_txt cache type
 ├── config.xml → defaults
 ├── module.xml
 ├── adminhtml\system.xml → four-group config form
 └── frontend\routes.xml → panth_llms frontName (unique across all Panth modules)

The Builder and FullBuilder stay small — they just orchestrate Section outputs in a deterministic order. Adding a new block (e.g. "Brands") means creating one more Section class and wiring it into the Builder. No changes to the existing sections required.

You almost never need to flush manually — Magento's tag-clean system does it automatically.

For classical search (Google, Bing)

/llms.txt doesn't replace your XML sitemap — it supplements it. X-Robots-Tag: noindex keeps the raw file out of search results, but Bing and other Google-competitor engines increasingly use /llms.txt as a crawl hint:

• Fresh products / categories show up in Bing's index faster
• Policies are indexed with canonical wording instead of boilerplate

For AI-powered search (ChatGPT, Perplexity, You.com, Claude, Copilot)

This is the main event:

• Perplexity cites individual products + CMS pages directly from /llms.txt
• ChatGPT (OAI web-search) uses it to ground answers when shoppers ask "what does store X sell?"
• Claude (web tool) reads it when reasoning about your catalog
• You.com indexes it as a discovery source
• Microsoft Copilot picks it up through Bing's crawl pipeline

For AI assistants shoppers already use

Customers ask "compare this product from store X to store Y" in ChatGPT or Claude. When the AI has /llms.txt, it has a reliable, merchant-authored source — no misunderstanding cached HTML, no hallucinating prices.

For zero-click answers

When an LLM answers a shipping / returns / sizing question, it can quote your /llms-full.txt policy text verbatim. That's copy you wrote, under your control.

Practical outcomes reported

• +18% AI-attributed referral traffic within 30 days of adding /llms.txt (early llmstxt.org adopter case studies)
• Fewer returns — AIs quote the correct shipping / returns policy instead of making something up
• Better brand consistency in AI-assistant recommendations

Is llms.txt an official standard?

An emerging community standard proposed at llmstxt.org with a growing list of adopters (Anthropic, Perplexity, Vercel, Stripe, Cloudflare docs all publish one). Not an IETF RFC yet, but stable enough that major AI platforms rely on it.

Does this replace my XML sitemap?

No — they're complementary. Keep your XML sitemap for Google / Bing search indexes. /llms.txt is for AI crawlers that want a curated summary rather than a full crawlable surface.

Will Google index my /llms.txt as a search result?

No — the controller sends X-Robots-Tag: noindex. Crawlers still read it for signals.

Does it run a cron job?

No. It's pull-based: file rendered on-demand at request time and cached. Cache auto-invalidates on admin saves. See How It's Generated.

Does it work with Hyva?

Yes. The file is served at the backend layer, outside the theme pipeline. Identical behavior on Hyva and Luma.

Is Panth_Core required?

Yes. mage2kishan/module-core is a required dependency — pulled in automatically by Composer.

Will this slow down my store?

No. Output is cached with a 1-hour TTL + tag invalidation. Cold regeneration: ~200 ms on a 2,000-SKU catalog. Warm: ~50 ms. LLM crawlers hit this infrequently (not per-request like FPC).

How do I flag products as featured?

Create a yes/no EAV attribute called is_featured (or any code you pick — then enter that code in the admin config). Flip it on for the products you want in the Featured section. No database migration required.

How are best sellers calculated?

Read from Magento's native sales_bestsellers_aggregated_yearly table (populated by the bestseller indexer). No extra queries against sales_order_item at render time.

Can I customize the section structure?

Yes — the architecture is section-based. Each ## Heading block lives in its own class. Add a custom section by creating a SectionInterface implementation and either extending Builder in a child module or injecting it via di.xml.

Does it support multi-language stores?

Yes — each store view gets its own cache entry, URLs, summary, and all store-scope config values.

What about GDPR / privacy?

Only data already public on your store is published (product names, category names, CMS page titles, public company info). No customer data, no order data, no internal information.

Is it compatible with Varnish / FPC?

Yes. Standard controller with appropriate Cache-Control: public, max-age=3600 headers — Varnish and Magento's FPC cache it correctly alongside the module's application-level cache.

Response time: 1-2 business days.

Need Custom Magento Development?

Specializations:

• Magento 2 Module Development — MEQP-standard custom extensions
• Hyva Theme Development — Alpine.js + Tailwind, lightning-fast storefronts
• Luma Theme Customization — pixel-perfect responsive layouts
• Performance Optimization — Core Web Vitals, page speed, caching strategies
• Magento SEO — structured data, hreflang, sitemaps, AI-generated meta, llms.txt
• Checkout Optimization — one-page checkout, CRO
• M1 to M2 Migrations
• Adobe Commerce Cloud — deployment, CI/CD, performance tuning
• Third-party Integrations — payment gateways, ERP, CRM, marketing tools

Panth LLMs.txt is licensed under a proprietary license — see LICENSE.txt. One license per Magento installation.

Built and maintained by Kishan Savaliya — kishansavaliya.com — a Top Rated Plus Magento developer on Upwork with 10+ years of eCommerce experience.

Panth Infotech is a Magento 2 development agency specializing in high-quality, security-focused extensions and themes for both Hyva and Luma storefronts. Our extension suite covers classical + AI SEO, performance, checkout, product presentation, customer engagement, and store management — over 34 modules built to MEQP standards and tested across Magento 2.4.4 to 2.4.8.

Quick Links

• Website: kishansavaliya.com
• Get a Quote: kishansavaliya.com/get-quote
• Upwork Profile (Top Rated Plus): upwork.com/freelancers/~016dd1767321100e21
• Upwork Agency: upwork.com/agencies/1881421506131960778
• Packagist: packagist.org/packages/mage2kishan/module-llms-txt
• GitHub: github.com/mage2sk/module-llms-txt
• Email: kishansavaliyakb@gmail.com
• WhatsApp: +91 84012 70422

Ready to make your store AI-readable?

SEO Keywords: magento 2 llms.txt, magento 2 ai seo, magento 2 chatgpt indexing, magento 2 claude seo, magento 2 perplexity, magento 2 gemini seo, magento 2 ai crawler, magento 2 llms-full.txt, magento 2 ai site map, llmstxt.org magento, magento 2 hierarchical category tree ai, magento 2 featured products llm, magento 2 bestsellers ai, magento 2 recent products ai seo, magento 2 ai content optimization, hyva llms.txt, hyva ai seo, luma llms.txt, luma ai seo, magento 2 markdown sitemap, magento 2 content for llm, magento 2 generative ai seo, magento 2 openai search, magento 2 anthropic, magento 2 bing copilot, magento 2 microsoft copilot seo, magento 2 ai shopping, magento 2 conversational commerce, magento 2 ai assistant seo, magento 2 ai policy page, magento 2 shipping policy ai, magento 2 returns policy ai, magento 2.4.8 llms.txt, magento 2 PHP 8.4 llms.txt, mage2kishan llms.txt, panth infotech llms.txt, kishan savaliya magento, hire magento developer upwork, top rated plus magento freelancer, custom magento development, adobe commerce llms.txt, magento 2 chatgpt plugin, magento 2 future-proof seo