Shopify llms.txt: Keep the Default or Customize It?
Shopify already publishes agent-discovery files for stores. Before installing an app or editing your theme, verify what exists, understand what each file controls, and decide whether a custom version solves a real maintenance problem.
01Verify the managed output before adding an app
For a standard Shopify-hosted storefront, begin by opening /agents.md, /llms.txt and /llms-full.txt on its primary domain. Keep the managed output unless a specific, maintained requirement is missing. A generator is not a prerequisite for having these endpoints.
Shopify announced the customization mechanism on May 28, 2026[1]. That makes older advice to upload a text file and invent a redirect a poor starting point. First identify what the actual public request returns and which layer owns it.
For a headless storefront or domain routed through an external content layer, do not assume editing a Shopify theme changes the public endpoint. Ask the routing owner to trace it. This article explains the Shopify theme mechanism; it does not establish that a custom proxy forwards those routes.
What the evidence does and does not prove
| Fact | What it establishes | What it does not establish |
|---|---|---|
Shopify serves /llms.txt by default, mirroring /agents.md | You do not need an app to have the file | That any assistant reads or cites it |
A dedicated llms.txt.liquid overrides the shared template | Why an old app's template can keep /llms.txt unchanged | That Shopify ignored your shared template |
| Google says new AI text files are not needed for Search | llms.txt is not a Google ranking setting | That other AI services ignore it |
02Four similarly named things, four different jobs
- Public /agents.md
- An agent-facing description of the store and its discovery capabilities. Shopify treats it as the canonical document for these agent-discovery paths.
- Public /llms.txt
- A compatible alternative endpoint. It is not a crawler permission file, a product feed or proof that an assistant has read the store.
- Theme-root AGENTS.md
- Development instructions for coding agents working on a theme. Shopify documents it as source context, not the public shopping-agent response.
- Catalog and buying systems
- The product and transaction systems still own current offers, inventory and purchasing behavior. Describing a capability in Markdown does not implement it.
The capitalization and location matter. Do not paste internal engineering notes, customer information or credentials into a public discovery document. See Shopify's separate theme-root AGENTS.md documentation[2].
Nor is this a Google Search ranking configuration. Google's generative AI optimization guide[3] says new AI text files and special markup are not needed for Search, including its generative features. Treat vendor-specific discovery and ordinary search visibility as separate objectives.
03Choose the output you actually need to change
| Requested path | First choice | Fallbacks |
|---|---|---|
| /agents.md | agents.md.liquid | Shopify-generated output |
| /llms.txt | llms.txt.liquid | agents.md.liquid, then generated output |
| /llms-full.txt | llms-full.txt.liquid | agents.md.liquid, then generated output |
These are templates in the theme's templates directory, not three files you must always create. Shopify's llms.txt template reference[4] recommends the managed default for most stores and a shared agents template when all paths need the same customization.
A practical consequence: if an old app already created llms.txt.liquid, changing only the agents template will not necessarily change /llms.txt. Inspect existing dedicated overrides before calling the shared-template update broken. Record the owning app or developer before altering an override.
The documented URLs are on the primary-domain root, without Markets language or country subfolders. Do not manufacture a localized endpoint for every country. Actual customer-facing policy and product translations belong at their real localized URLs.
04Why a copied theme snippet may render blank
The discovery template is not a normal product template. Shopify's agents template reference[5] describes a restricted context containing request and agents; ordinary global objects such as shop, articles and collections are not injected. A loop copied from a storefront collection page can therefore fail to provide the content you expected.
The supported agents object supplies store and discovery metadata. Follow the current reference for its exact properties and use supported dynamic endpoints instead of freezing implementation addresses in prose. Do not guess new object names or claim that every store metafield is accessible here.
Keep the custom file small enough to audit. A maintained explanation of where public policies live is more useful than a hard-coded copy of a volatile product catalog. If a required statement has no approved public source or owner, leave it out until that gap is resolved.
05A change procedure with a real rollback
- Capture the baseline. Save the three public responses, final URLs and time. Check for storefront HTML or an error document masquerading as a successful response. Save any existing custom templates separately.
- Write the requirement. State exactly which missing fact or endpoint the customization must expose, its source and who will maintain it. “Better AI SEO” is not an acceptance criterion.
- Inspect ownership. Confirm the active theme and whether a dedicated override or external router owns each path. Preserve unrelated templates and app configuration.
- Prepare a controlled version. Work in a duplicate theme or development environment. Compare the proposed output with the baseline, especially policy and discovery links. Never add private access tokens to make an endpoint usable.
- Publish only the reviewed change. The authorized theme owner should deploy the precise template change, then fetch all three public endpoints again. A theme preview alone does not verify the final primary-domain route.
- Rollback the producing change if needed. Restore the previous custom template, or remove only a newly introduced override when the intended result is the documented fallback. Do not delete another app's template without checking ownership. Recheck all three paths after rollback.
No template edits or app installations are performed by reading this guide. If you cannot identify the current producer, stop at the baseline and ask the owner; replacing all three outputs may hide the conflict rather than resolve it.
06What passing this check actually proves
A useful acceptance record has one row per endpoint: status and final URL, current content, the expected template or fallback, public links checked, reviewer and date. It should explain every intentional difference between responses.
Hypothetical example: a team needs one approved public explanation of its custom content directory. It adds that explanation through the shared template, but /llms.txt still contains an obsolete brief. Finding an older dedicated override explains the difference; it does not show that Shopify ignored the shared template. The team either maintains that exception or removes it with its owner's approval and retests the fallback.
Recheck after a theme switch, domain change or material policy change. Do not manually copy short-lived prices into this document and then assume they follow catalog updates.
Successful endpoint checks prove that the intended public document is available. They do not prove indexing, citations, assistant recommendations or sales. Keep any observed agent requests and referral outcomes as separate evidence; an unknown crawler user agent does not identify a verified service.
07Copy this llms.txt change record and fill in the brackets
llms.txt change record
Requirement: [the missing public fact or link], source [URL], owner [name] Baseline saved: /agents.md [status, hash], /llms.txt [status, hash], /llms-full.txt [status, hash] on [date] Existing overrides found: llms.txt.liquid [yes/no, owner], llms-full.txt.liquid [yes/no], agents.md.liquid [yes/no] Change made in: [template] on theme [ID/name], reviewed by [name] After publish: three endpoints re-fetched on [date], differences explained: [text] Rollback: restore [previous template file] / remove [new override], owner [name]
08Next decision and review scope
Reviewed October 8, 2026 against the linked Shopify template references, developer changelog and Google Search guidance. This is a configuration decision guide, not a live merchant implementation or ranking experiment.
If the discovery document is accurate, move to the product-data readiness guide rather than adding more text files. If the problem concerns advertised protocol capabilities, use the UCP discovery-profile guide. For broader crawl and content issues, return to the Shopify SEO guide.
09Questions
Did Shopify remove llms.txt?
No. Since late May 2026 Shopify serves /llms.txt itself by default. Custom files that were uploaded or redirected the old way stopped working, which is why some merchants thought it had been removed.
Do I need an llms.txt app?
Not to have the endpoint. Customise only when a specific, maintained requirement is missing from the managed output.
Does llms.txt help Google rankings?
Google's guidance says new AI text files are not needed for Search, including its generative features.
Sources and what still needs a direct check
- Shopify developer documentation, Customization mechanism on May 28, 2026. Checked October 8, 2026.
- Shopify developer documentation, Theme-root AGENTS.md documentation. Checked October 8, 2026.
- Google Search Central, Generative AI optimization guide. Checked October 8, 2026.
- Shopify developer documentation, Llms.txt template reference. Checked October 8, 2026.
- Shopify developer documentation, Agents template reference. Checked October 8, 2026.
Still to check yourself
- What your three endpoints return today on the primary domain.
- Whether an app or developer created a dedicated override, and who owns it.
- Whether a proxy or headless front end serves these paths instead of the theme.