Salesforce Commerce Cloud has no native llms.txt feature and no file system you can reach: the Business Manager screen that handles root files (Merchant Tools > SEO > Robots, now labeled SEO & Discoverability in newer versions) only manages robots.txt, and static files uploaded through Business Manager or WebDAV live under long platform paths, not at the site root. So this is a developer task, not a settings task: your developer adds a route that serves your file's content at [yourdomain.com]/llms.txt, replacing yourdomain.com with your actual domain, with a text/plain content type.
Why Salesforce Commerce Cloud is different
Every other platform in this series gives the merchant at least one self-serve path. SFCC gives you none, and the closest-looking options are traps. Uploading to the static library will not put the file at /llms.txt, and pasting Markdown into a content slot renders it inside your storefront template, not as plain text at the root. The workable plan: write the file's content yourself, hand it to your developer with one clear requirement ("serve this at /llms.txt, 200 status, text/plain"), and verify the result yourself with a browser and curl.
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. On a standard SFCC storefront you will get a 404 or the storefront's error page; that tells you no route exists yet.
- Write the file content. What goes in it is covered in our llms.txt guide. Write the final Markdown yourself so the developer is publishing copy, not inventing it.
- Hand it to your developer with this brief. On a classic SFRA storefront, the pattern is a small custom controller or route in your cartridge that responds at /llms.txt with your content and a text/plain content type. The content should come from somewhere your team can edit without a code deploy: a content asset in Business Manager is the usual choice, since merchandisers already know how to edit those. On a PWA Kit (composable) storefront, the same Express server setup that already serves your robots.txt is where the file gets served from.
- The edge alternative. If your storefront sits behind a CDN or edge layer you control, the developer can serve /llms.txt from an edge rule or worker instead of touching the cartridge. Same requirement: 200, text/plain, your content.
- Verify yourself. Open [yourdomain.com]/llms.txt and confirm your Markdown renders as plain text, not inside your site template. Check the headers with
curl -I https://[yourdomain.com]/llms.txtand confirm the 200 and the text/plain content type. If caching is enabled, remember that content changes can need a cache invalidation before they show.
One thing to check while you are in Business Manager: the Merchant Tools > SEO > Robots (SEO & Discoverability) screen already ships with commented-out rules for AI crawlers in newer versions. That is the permission layer, and it is separate from this file; 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 your brand runs on SFCC with a catalog of a few hundred products. You write the file, your developer adds a controller that reads it from a content asset, and /llms.txt serves your Markdown as plain text. Six months later you launch a new category. The file does not change, because the content asset nobody owned still says last year's categories. The scan flags stale links. The SFCC maintenance lesson: the file is only as current as the content asset behind it, so put "update the llms.txt content asset" on the same checklist as your catalog launch steps, and assign it to a person.
What this guide does not cover
The exact controller code (that belongs to your codebase and your developer). Cache invalidation details for your instance. Monitoring whether AI crawlers fetch the file or cite your store. The transaction layer.
Frequently Asked Questions
How do I deploy llms.txt in Salesforce Commerce Cloud?
Does SFCC eCDN block AI crawlers by default?
How do I verify the file deployment across multiple locales?
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