Home › AI for small firms › Putting it to work
Putting it to work
llms.txt for Shopify: check the native file before buying an app
Shopify now generates agent-facing files natively. Check llms.txt, agents.md and template overrides, then decide whether a custom file is worth maintaining.
Shopify now provides native agent-facing files, including llms.txt, so check your store's existing output before buying an app. A custom template is an optional maintenance choice, not a prerequisite for creating the file.
An llms.txt file is a readable guide to public information. Its presence does not prove that ChatGPT has read it, that a product has been indexed or that an assistant will recommend your store.
Where can I find Shopify's existing files?
Open your primary HTTPS store domain followed by /llms.txt and /agents.md. Check the domain root rather than a translated storefront subfolder. Record the response, final URL and actual content, not merely whether the browser displays a page.
Shopify's current developer documentation describes the generated default and template precedence. By default, llms.txt mirrors agents.md. A dedicated override can make their contents differ.
Run the free validator against the live domain. Read any warnings in context: the test concerns a file format and its contents, not a guaranteed ranking factor.
What is the difference between the files?
| Resource | What to check |
|---|---|
| /llms.txt | Concise public guidance and useful links |
| /agents.md | The store's agent-facing guidance and default fallback source |
| /llms-full.txt | The separately served full-file path, if used |
| /robots.txt | Crawler access rules, with a different purpose |
Keep access policy separate from descriptive guidance. A sentence in llms.txt does not secure a private page or override a crawler restriction. The Shopify crawl guide covers the effective public access checks.
When should I keep the generated default?
Keep it when it accurately describes the public store and provides useful current links. A manual file creates a recurring obligation: somebody must update it when products, policies or page addresses change.
For a UK shop with seasonal ranges, stable links to delivery, returns, contact and category pages can be easier to maintain than a hand-written inventory. Verify that each destination exists and describes the current offer.
Do not copy a long product list merely to make the file longer. Stale prices, obsolete delivery promises and unavailable items can be worse guidance than a short file linking to authoritative pages.
How do I add a deliberate template override?
Ask the person responsible for the theme to review the change. Shopify documents the following route for a dedicated file:
- Open Online Store, then the theme's Edit code option.
- In Templates, create llms.txt.liquid.
- Add the intended public guidance and save.
- Check /llms.txt on the published primary domain.
The dedicated template takes precedence for that path. An agents.md.liquid template can supply the fallback; the generated output applies when no relevant custom template exists. Shopify also documents a separate llms-full.txt.liquid override.
The supported Liquid context is restricted. Do not assume examples written for normal product templates can access every global object here. Follow the current developer reference rather than pasting an untested loop from a forum.
What should a useful custom file contain?
Give the store's public name, a short factual description and links to pages that answer real customer questions. Include the service or delivery area when it matters and is accurately stated on the linked page.
For a UK furniture retailer, useful destinations might explain delivery regions, assembly options, dimensions and returns. This is an illustrative content plan, not a claim that a named shop has achieved more AI traffic.
Keep private customer details, order identifiers and internal instructions out of the file. It is public. A request asking an assistant to ignore its instructions or prefer the business is not useful product documentation.
How do I know whether the change helped?
First, verify the technical result: a successful response, expected text and working links. Then check that the public store pages agree with it. Keep the old output with the date of the change.
Measure actual AI visibility using a stable set of customer questions, dates and citations. Separate the file check from referral traffic and completed sales. A technical improvement can be worthwhile without proving that a later citation was caused by that one change.
If the generated default already meets your needs, spend the next hour improving the product or policy page that customers struggle to understand. The answer-readiness checker can help identify a clearer next edit.
Which questions come up most often?
Does Shopify need an app for llms.txt?
Current Shopify provides a generated default and theme override support. Check your live file before buying an app.
Does a dedicated llms.txt template change agents.md?
A dedicated llms.txt.liquid override changes that path. Check each served file separately rather than assuming they remain identical.
Will the file guarantee AI recommendations?
The file provides public guidance. Citations, referrals and sales need separate observation and are not guaranteed by its presence.
Where this comes from: Shopify developer llms.txt.liquid reference and May 2026 agent-file template changelog; native support checked 30 October 2026; checked 30 October 2026. Worked examples are illustrative unless a source is named.
Put a number on it: AI readiness score: is your business ready for AI? · How many hours can AI save me each week? Free, in your browser, no sign-up.
AEO Lookup editorial team
We write practical guides for people who run small UK firms, and we check every fact against its source on the date shown. Read how we review, or tell us if something has changed.