LLMs.txt Generator for Magento 2

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.

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.

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

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.

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

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

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).

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.

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.

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.