Shopify recently introduced native storefront routes for /llms.txt and /agents.md, and they now appear to be automatically generated by Shopify itself.
I noticed that previous proxy/redirect-based approaches for customizing llms.txt no longer work because Shopify serves these routes by default at the platform level.
Has anyone found a supported way to customize or override the content of these generated files?
Confirming that Jason’s solution works: adding templates/llms.txt.liquid to the theme does override Shopify’s auto-generated content, exactly like robots.txt.liquid does. Thanks @Jason_Richey – that saved us a lot of headache.
For anyone running into this: the previous workaround via URL redirects (Admin → Online Store → Navigation → URL Redirects) silently stopped working once Shopify started serving /llms.txt natively. The redirect entry still exists in the admin but is no longer honored.
One open question: is there an equivalent template hook for /agents.md? Couldn’t find one in the theme docs yet – happy to hear if anyone has tried.
Thanks @Nordalux ,
we have found for llms-full.txt also. it is same as templates/llms-full.txt.liquid
Same question still i’m figuring out for /agents.md
Hey all, I just wrote a LinkedIn article on this topic and thought I’d share here. Always learning and always looking for feedback: please tell me if this article is helpful or not. Thank you.
Shopify recently changed how llms.txt works. Earlier, many of us were using proxy/redirect methods to serve custom llms.txt, but now Shopify seems to internally redirect or generate the content through /agents.md, making overrides limited at the platform level.
We are facing the same issue and are currently exploring a proper solution for our app: Lumos AI SEO & LLMs.txt
The redirect from /llms.txt to /agents.md is expected. Shopify now uses /agents.md as the primary storefront discovery file for agentic and AI experiences, so /llms.txt is no longer the right place to customize.
To customize the discovery file itself, create or update templates/agents.md.liquid in your theme. The storefront URL remains /agents.md, but the editable theme file lives in the Templates folder.
If your goal is to influence how custom product data appears in AI shopping channels, Shopify Catalog Mapping is the supported place to review and map product data sources.
Thanks for your reply. However, we’re updating llms-full.txt accordingly to accommodate a wide range of crawlers. I still don’t see these changes in the changelog: Why weren’t they announced? As a result, I and other developers who regularly monitor llms.txt and llms-full.txt have been receiving error messages.
We went ahead and added agents.md file editor to TinySEO, but a lot of people relied on llms.txt and llms-full.txt and I hope It gets re-introduced back.
A possible solution would be to allow /llms.txt and /llms-full.txt if the files llms.txt.liquid and llms-full.txt.liquid exist. Otherwise, redirect them. However, removing support for the /llms.txt and /llms-full.txt paths entirely is not a good solution. The recent change is being viewed very negatively by our clients.
Only redirect if it not exist and respect the work of the dev/merchant on the llms files. At the very least let us know this via changelog with time to update.
Same issue here. We had a fully customized llms.txt served via app proxy, and it’s now overridden by Shopify’s auto-generated /agents.md.
Re: the templates/llms.txt.liquid workaround — overriding /agents.md through a theme template doesn’t feel like the right long-term solution. It ties a platform-level agent file to the theme layer (lost on theme switch, no path for headless stores), and one template appears to control two distinct routes (/llms.txt and /agents.md), even though they may need different content over time.
Subscribing to this thread and waiting for an official answer on the intended override mechanism.
Same issue here. the llms.txt stop working and the redirect to /agents.md seems not the best practice. Please bring the /llms.txt and /llms-full.txt back
Same issue here, we had setup a customized llms.txt for the client via llms.txt.liquid - and now it’s gone don’t appreciate the advertisement on agents.md either..
Same here, I think we should be able to keep both options (agents.md and llms.txt), specially since Google itself has included llms.txt to Lighthouse agentic browsing scoring recently: Lighthouse agentic browsing scoring | Chrome for Developers
Since you redirect llms.txt and llms-full.txt directly to /agents.md, but Google scans llms.txt, I’d be interested in the reasoning behind this decision.
In the shop’s Agentic Dashboard, we can’t configure everything we’d like to. This means additional work with meta fields, which we currently can’t handle (one customer’s shop has about 200 products, for which we had completely and very complexly customized llms.txt).
I now scan every change to llms.txt, llms-full.txt, and agents.md (as well as skill.md at shop.app/skill.md), since absolutely nothing has been written in the changelog so far. This is disheartening and means extra work. Making ad hoc changes overnight without notice is appropriate and important, but in cases like this, it’s frustrating. Especially since many apps could be taken offline overnight because the creator offers something that no longer works.
It would be nice if this could be implemented for some llms.txt and llms-full.txt files (via /templates/). The previously set default llms.txt was also good.