llms.txt for Shopify: complete setup guide for AI search visibility (2026)

May 6, 2026
Shopify Tips
17 min read
llms.txt for Shopify: complete setup guide for AI search visibility (2026)

llms.txt is the file at /llms.txt on your domain that tells AI agents like ChatGPT, Claude, Perplexity, and Gemini what your site is and where the important content lives. Think of it as a curator’s note. Robots.txt says “here is what you can crawl.” Sitemap.xml says “here is every page.” llms.txt says “here is what matters, in plain markdown, optimized for an LLM to parse in one read.”

The format was proposed by Jeremy Howard at Answer.AI in late 2024. By mid-2026, Anthropic, Cloudflare, Vercel, and most major SaaS companies serve one. AI agents increasingly use it as a fast-path to a site’s structure when answering shopper queries. Shopify merchants who skip it leave a lot of AI surface area on the table. The catch: Shopify does not natively let you upload arbitrary files to your root domain. So this post walks through the format, the Shopify-specific setup methods that actually work, and what to put in the file if you sell physical products instead of documenting an API.

We at Craftshift host llms.txt files on all three of our sites (the one you are reading, plus our two app sites). Setting them up surfaced the Shopify-specific quirks below: which methods work, which fail silently, and how to host the file without installing an app.

In this post

What llms.txt actually is (and is not)

llms.txt is a plain markdown file at https://yourdomain.com/llms.txt. The spec is short. The file contains:

  • An H1 heading with your site or store name
  • A blockquote with a one-or-two sentence summary
  • Optional body paragraphs explaining anything important
  • One or more H2 sections, each containing a curated list of links with short descriptions

That is the entire spec. No XML, no schema, no required fields beyond the H1. The bet is that markdown is already what LLMs read most reliably, so a curated markdown file gives them a fast, low-noise summary of your site. The file is meant to be small (under 50KB ideally) and link-rich, not exhaustive. Think of it as a sitemap that is hand-curated for taste.

What llms.txt is not:

  • It is not a replacement for robots.txt. You still need robots.txt to tell crawlers what they can fetch. (See our Shopify robots.txt guide for that side.)
  • It is not a replacement for schema.org structured data. Both are still important. llms.txt gives a high-level map; schema gives per-page detail.
  • It is not enforced by any AI vendor. No bot is required to fetch it. But growing numbers of LLMs check for it as a hint, and adoption is rising fast.
  • It is not yet ranking-determinative. Having one will not magically rank you in ChatGPT. But the absence is starting to look like a missing signal among the stores that AI agents prefer to cite.

Why a Shopify store needs one in 2026

Three reasons specific to ecommerce:

  1. AI shoppers are real now. Since Shopify rolled out Agentic Storefronts in March 2026, your products are surfacing inside ChatGPT, Perplexity, Copilot, and Google AI Mode by default. The agents fetch product data through the Shopify catalog, but they cross-reference with your domain when ranking and citing. A clean llms.txt is one of those cross-reference signals.
  2. It tells the agent what your store is, not just what products you sell. “We make handmade ceramics in Lisbon, ship worldwide, returns within 30 days” is an entity-level statement that does not live in any single product page. llms.txt is where you put it.
  3. It pre-empts hallucinations. Without a curated entry point, an agent that gets asked about your brand has to infer from scattered crawled pages. Inference invents facts. A good llms.txt grounds the agent in your actual offering, your actual policies, your actual price ranges. Less guessing means fewer wrong citations.

Reality check: llms.txt is not going to single-handedly transform your traffic. It is a small file with limited adoption and no guaranteed effect. But the cost of adding one is low (maybe an hour of work) and the upside is real and growing. Skip it and you are betting that AI agents will not become a meaningful traffic source. That is a bet worth questioning.

The format spec, with a Shopify-shaped example

Here is what a working llms.txt looks like for a Shopify apparel store. Replace the contents with your own.

# Honey Co. Apparel

> Family-run apparel brand based in Brighton, UK. We make organic cotton basics for women and men, ship worldwide, and offer free returns within 30 days. Sizes XS to 4XL.

We launched in 2018 and now sell 12,000 orders a month. Our pieces are designed to last five years of wear, with a free repair service for owners. We do one product launch a quarter, no fast fashion drops.

## Shop
- [All products](https://honeyco.shop/collections/all): Browse the full catalog, filter by size, color, and category.
- [Best sellers](https://honeyco.shop/collections/bestsellers): Top 20 products by review count and revenue.
- [New arrivals](https://honeyco.shop/collections/new): Latest 30 days of releases.
- [Tee shirts](https://honeyco.shop/collections/tee-shirts): Organic cotton tees in 8 colors.
- [Hoodies](https://honeyco.shop/collections/hoodies): Heavyweight hoodies in 12 colors and 7 sizes.

## About the brand
- [Our story](https://honeyco.shop/pages/about): Founder background, sustainability commitments, supplier list.
- [Materials](https://honeyco.shop/pages/materials): Fabric sourcing, certifications, dye process.
- [Repair service](https://honeyco.shop/pages/repair): Free repairs for the lifetime of the garment.

## Customer help
- [Sizing guide](https://honeyco.shop/pages/sizing): Detailed size charts for every product category.
- [Returns and exchanges](https://honeyco.shop/policies/refund-policy): 30-day free returns, exchange instructions.
- [Shipping](https://honeyco.shop/policies/shipping-policy): Free shipping over £80, worldwide tracked delivery.
- [Contact](https://honeyco.shop/pages/contact): Live chat, email, and phone support hours.

## Optional
- [Press kit](https://honeyco.shop/pages/press): Logos, brand assets, founder bio.
- [Wholesale inquiries](https://honeyco.shop/pages/wholesale): B2B catalog and minimum order details.

Notice what is in there and what is not. There is no link to every product (that is what your sitemap is for). There are no marketing slogans. The descriptions are factual: “Free repairs for the lifetime of the garment,” not “we love what we do.” Every line has a job. The agent reads this once and walks away with a working mental model of your store.

Aim for 30 to 60 links total in the file. More than that and you start losing the curation benefit. Less than 10 and there is not enough signal for the agent to do anything useful with.

Setup method 1: file upload + URL redirect (recommended for most stores)

This is the path we recommend for 90% of Shopify stores. No app, no theme code, takes about 15 minutes.

  1. Write your llms.txt content in any plain text editor. Save it as llms.txt (lowercase, no extension games).
  2. In your Shopify admin, go to Content > Files. Click Upload files and pick your llms.txt. Shopify will accept it and store it on its CDN. Copy the resulting URL (it will look something like https://cdn.shopify.com/s/files/1/.../llms.txt).
  3. Go to Online Store > Navigation > URL Redirects. Click Create URL redirect. Set Redirect from to /llms.txt and Redirect to to the CDN URL you just copied. Save.
  4. Open https://yourdomain.com/llms.txt in an incognito browser tab. You should see your file content. If you see a 404 or your homepage, double-check the redirect path.

Caveats:

  • The file in Shopify Files is served with Content-Type: text/plain, which is what LLMs expect. You do not need to set headers manually.
  • If you ever want to update the file, re-upload to Shopify Files (delete the old one first, or upload with a new filename and update the redirect).
  • The redirect adds one extra HTTP hop (302 then 200) compared to a true root file. AI bots handle this without complaint, but if you are extremely latency-sensitive, methods 2 or 3 give you a direct 200.

Setup method 2: custom Liquid template (theme-level)

This method serves the file as a true 200 from your storefront. It requires a theme edit and you have to keep the template in sync if you change themes. Worth it for stores that want the cleanest possible setup.

  1. In your Shopify admin, go to Online Store > Themes, click Customize on your live theme, then Edit code from the three-dot menu.
  2. Under Templates, click Add a new template. Choose page, name it llms-txt, and pick liquid as the file type. Shopify will create page.llms-txt.liquid.
  3. Replace the entire contents of that file with your raw llms.txt markdown content. No HTML, no Liquid wrappers, just the text. Save.
  4. Create a page in Shopify (Online Store > Pages > Add page). Title it “LLMs Manifest” or anything (the title only shows in admin). In the template selector on the right, pick page.llms-txt. Save.
  5. Copy the resulting page URL (something like /pages/llms-manifest).
  6. Set up a URL redirect from /llms.txt to that page URL (same as method 1, step 3).

The reason for still using a redirect: Shopify does not let custom pages live at root paths. /pages/llms-manifest is the closest you can get. The redirect bridges the URL the spec calls for to the URL Shopify will serve.

Note: page templates render with the theme’s HTML wrapper by default. To get pure plain text output, you may need to strip the layout. Add {% layout none %} at the top of page.llms-txt.liquid to disable theme.liquid wrapping. Without this line, the file will be wrapped in your site’s HTML, which defeats the purpose.

Setup method 3: install a dedicated app

The Shopify App Store has at least eight llms.txt apps as of mid-2026. They auto-generate the file from your products and pages, refresh on changes, and handle the hosting. Pricing ranges from free to $19/month. Pick one if you want zero maintenance.

Honest take: most of these apps generate too much content. They will dump every product, every collection, every blog post into the file. That is not what the spec wants. A 5,000-line llms.txt is worse than a 60-line one because it forces the agent to wade through clutter. If you go the app route, look for one that lets you curate which sections to include, or generates a separate llms-full.txt for the dump and a curated llms.txt for the highlights.

We do not currently make an llms.txt app, so this is a vendor-neutral recommendation. Read the most recent reviews, look at the demo file output, and avoid anything that produces an uncurated catalog dump.

What to actually put in your llms.txt

For an ecommerce store, the sections that matter most:

  • Shop: Main collection links, top categories, best-sellers. Not every collection. Pick the 8 to 12 most important.
  • Brand and policies: About page, sustainability or sourcing, returns, shipping. The agent uses these to answer “is this brand legit?” and “do they ship to me?”
  • Customer help: Sizing, FAQ, contact. Reduces the agent’s need to guess.
  • Content hub: If you blog, link the 5 to 10 highest-performing posts. Not the blog index page, the actual posts.
  • Optional: Press kit, wholesale, careers. Nice to have but skippable for an agent answering shopping queries.

What to leave out:

  • Every individual product page (use sitemap.xml for that)
  • Tag-based collections (auto-generated, low signal)
  • Cart, checkout, account pages (no shopper-facing content)
  • Marketing copy. Stick to factual descriptions.

If you sell variant-heavy products and use combined listings, link the parent collection rather than the individual product groups. The agent finds the parent, then drills down through normal crawling. (We have a deeper post on how variant grouping affects AI shopping discovery if you have not set that up yet.)

How to test that AI agents can read it

After you publish, run these four checks:

  1. Direct fetch. Open https://yourdomain.com/llms.txt in an incognito browser. The full file should display as plain text. If it renders as HTML or shows a 404, your setup is wrong.
  2. Curl from terminal. Run curl -L https://yourdomain.com/llms.txt. Confirm 200 OK and plain text. The -L follows redirects, which is what AI bots do.
  3. ChatGPT round-trip. In ChatGPT (with web browsing on), ask: “Fetch https://yourdomain.com/llms.txt and tell me what this brand sells.” If it summarizes correctly, the file is doing its job.
  4. AI bot check. Use our AI Bot Checker to confirm GPTBot, ClaudeBot, PerplexityBot, and Google-Extended are not blocked in your robots.txt. The best llms.txt in the world does nothing if the bots that fetch it are blocked.

If you want a deeper read on which crawlers should be allowed and why, our Shopify robots.txt guide covers the full bot landscape and the specific user-agents you want to allow for AI search.

Common mistakes (and the file content that gets ignored)

  • Putting the file in /assets. Some merchants upload llms.txt to Online Store > Themes > Edit code > Assets. That serves the file at /assets/llms.txt, not /llms.txt. AI bots do not look in /assets. Use Files + redirect, or the template method.
  • Forgetting {% layout none %} on the template method. Without it, your llms.txt is wrapped in HTML and the agent sees an HTML page with markdown inside, which defeats the spec.
  • Auto-generated dumps. If your llms.txt is 8,000 lines of every product in your catalog, you have a sitemap, not an llms.txt. Curate.
  • Marketing copy. “We are passionate about quality” tells the agent nothing. “Hand-stitched in Porto, Portugal, by 8 craftspeople” tells the agent everything.
  • Stale links. If you link a product that no longer exists, the agent fetches a 404 and downgrades the rest of your file. Re-check the file every quarter, or after major catalog changes.
  • Not setting up llms.txt at all but still expecting AI traffic. Adoption is up across the industry. Stores that wait will be the last to be cited.

llms-full.txt vs llms.txt: do you need both?

The spec also defines an optional llms-full.txt file. The idea: llms.txt is the curated executive summary, llms-full.txt is the firehose of every page on your site, in markdown. Documentation sites use both because LLMs sometimes want the full text of every doc page in one read.

For a Shopify store, llms-full.txt is usually overkill. Your sitemap.xml plus the agent’s normal crawling cover the same ground. We recommend skipping llms-full.txt unless you have a content-heavy site (lots of how-to articles, manuals, or product documentation) where the agent benefits from being able to ingest your whole content corpus in one fetch.

If you do publish llms-full.txt, follow the same hosting method (Files + redirect or template route). Cap the file at 1MB to keep it parseable.

Try Rubik Variant Images free
Try Rubik Combined Listings free

Frequently asked questions

What is llms.txt and why do I need it on Shopify?

llms.txt is a curated markdown file at /llms.txt that summarizes your site for AI agents like ChatGPT, Claude, and Perplexity. It complements robots.txt and sitemap.xml. On Shopify, it helps AI shopping agents (now active in ChatGPT and other platforms via Agentic Storefronts) understand what your brand sells, your policies, and your top content. Without one, the agent has to infer everything from scattered crawled pages.

Can I add llms.txt to my Shopify store without an app?

Yes. The most common method is to upload your llms.txt to Content > Files in Shopify admin, then create a URL redirect from /llms.txt to the file’s CDN URL under Online Store > Navigation > URL Redirects. Visitors and AI bots that hit /llms.txt get redirected to your file. No app required.

Can I host llms.txt at the root domain on Shopify?

Not natively. Shopify does not let merchants place arbitrary files in the root of their domain. The closest you can get is a URL redirect from /llms.txt to a Shopify Files URL or a custom Liquid page template. AI bots follow redirects without penalty, so this is a working solution.

Does llms.txt help with Google rankings?

Not directly. llms.txt is for AI assistants and answer engines, not Google’s traditional search index. It helps with AI search visibility (ChatGPT, Perplexity, Claude, Google AI Mode), which is becoming a separate traffic source. For Google rankings, focus on your sitemap, schema markup, and on-page SEO.

How big should my llms.txt file be?

Small. Aim for 30 to 60 curated links and under 50KB total file size. The point of llms.txt is to be a curated executive summary, not a sitemap dump. Files that exceed several thousand lines start losing their utility because the agent has to wade through noise to find signal.

Do I still need robots.txt and sitemap.xml?

Yes. llms.txt complements them, it does not replace them. robots.txt tells crawlers what they can and cannot fetch. sitemap.xml is the comprehensive list of every URL on your site. llms.txt is the curated guide for AI agents. Each does a different job. All three should be live on a 2026 Shopify store.

Which AI bots actually read llms.txt?

As of mid-2026, no AI vendor publicly confirms guaranteed llms.txt reads. But Anthropic, Cloudflare, and Vercel host their own and reference the format. Adoption is increasing in OpenAI, Perplexity, and Google AI Mode systems. Treat llms.txt as a useful signal that more agents check every quarter.

If you set yours up and want a sanity check, fetch ours at craftshift.com/llms.txt and copy the structure. Steal the format, replace the contents.

Co-Founder at Craftshift

You may also like