Adobe Commerce gives you full server access, so publishing llms.txt is the simple version of this task: place the file in your web document root and it serves at [yourdomain.com]/llms.txt, replacing yourdomain.com with your actual domain. The decision that actually matters on Adobe Commerce is whether to place the file by hand or install a generator extension, and that decision hinges on whether you run multiple store views.
Why Adobe Commerce is different
Two things separate it from the other full-access platforms. First, the document root in a standard install is pub/, not the project root; Adobe's own docs recommend pub/ as the docroot, so a file dropped in the project root next to app/ and vendor/ will not serve. Second, multi-store-view setups mean one file may not be enough: a store with English and German storefronts needs a sensible file per scope. Generator extensions on the Adobe Commerce Marketplace handle exactly this: per their user guides, they write the files into pub/ (the web root) and serve them per store view, for example at [yourdomain.com]/uk/llms.txt for a UK view.
The file you are publishing
The full format lives in our llms.txt guide. This is the file itself, from a sample outdoor gear store:
# Cedar and Pine Outfitters
> Cedar and Pine Outfitters sells outdoor apparel and camping gear from its Seattle storefront, shipping across the US. Runs an in-house tent repair service and publishes beginner backpacking guides.
## Shop
- [Tents](https://[yourdomain.com]/collections/tents): Two-person and family tents, described by season rating and packed weight.
- [Sleeping bags](https://[yourdomain.com]/collections/sleeping-bags): Down and synthetic bags, described by temperature rating.
- [Backpacks](https://[yourdomain.com]/collections/backpacks): Day packs and multi-day packs, listed with capacity in liters.
## Guides
- [Backpacking checklist](https://[yourdomain.com]/pages/backpacking-checklist): Complete gear list for a first overnight trip.
- [Tent care and repair](https://[yourdomain.com]/pages/tent-repair): How the in-house repair service works, turnaround and pricing.
## Policies
- [Shipping and returns](https://[yourdomain.com]/pages/shipping-returns): Free shipping over 75 dollars. 60-day returns on unused gear.
## Optional
- [Journal](https://[yourdomain.com]/blogs/journal): Trip reports and gear maintenance notes.Steps
- Check first. Open [yourdomain.com]/llms.txt in a browser and check the headers with
curl -I https://[yourdomain.com]/llms.txt. A 404 is the normal starting point.
2a. The hand-placed route. Write your Markdown (what goes in it is covered in our llms.txt guide), then place the file in your web document root: pub/ in a standard install, wherever your vhost points if your setup differs. The file must sit beside the web-accessible entry point, not one level up in the project root. Set permissions to 644. Verify the 200 and the text/plain content type; if .txt files serve with the wrong type, that is a web server config setting to fix.
2b. The extension route. If your catalog turns over often or you run multiple store views, install a generator extension from the Adobe Commerce Marketplace (several llms.txt generator extensions exist there; check the Marketplace for current options, install per its guide, and run its generate command to write llms.txt and optionally llms-full.txt into pub/ per store view scope). Review what it generates before you consider it done: a generator picks pages, but it does not know which categories matter most to your business.
- Update it on your own schedule. A hand-placed file is static; put it on your deployment checklist so catalog changes include a file refresh. If you use the extension, confirm how often it regenerates and who is responsible for checking the output.
While you are in the admin: Adobe Commerce lets you edit robots.txt per store view from the admin (Content > Design > Configuration, edit the store view, Search Engine Robots tab). If you are adding llms.txt, it is worth confirming in the same session that your robots.txt is not blocking the AI crawlers the file is meant for. Permissions and crawler rules are a separate topic; see our robots.txt guide.
The fundamentals
- •What goes in the file: your name, one-paragraph summary, and curated links with one-line descriptions, see our llms.txt guide
- •Crawler permissions live in robots.txt, never in llms.txt, see our robots.txt guide
- •The structured data behind the pages you link, see our product schema guide
A hypothetical example
Say you run Adobe Commerce with two store views, US and UK, and you hand-place one llms.txt in pub/. The US file links to your US shipping policy; the UK storefront ships under different terms, but both views now share one file that only describes the US side. A scan notes the mismatch. You switch to a generator extension with per-store-view output, and each scope gets its own file with the right policies. The Adobe Commerce lesson: the platform's multi-scope model applies to this file too, and one file for every storefront is a choice, not the default you want.
What this guide does not cover
Which generator extension is best for your setup (compare the Marketplace options against your store-view count and update cadence). Monitoring whether AI crawlers fetch the file or cite your store. The transaction layer.
Frequently Asked Questions
Where does llms.txt belong on Adobe Commerce and Magento 2?
Do I need to run setup:static-content:deploy after adding llms.txt?
Can Fastly on Adobe Commerce Cloud cache llms.txt?
Check your own brand now
Run the free scan at aizii.ai/aeo-scan. One click, no signup, and it shows how readable your store is to AI tools today.
Run the free scan