Most Shopify stores do not need to create or buy an llms.txt generator. Shopify now serves /agents.md, /llms.txt and /llms-full.txt on the bare primary domain. The managed default is the right starting point unless your team has a specific, testable reason to maintain different agent-facing information.

The direct answer

Open the three native URLs on your own store before changing anything. If they return current store, policy and discovery information, keep the managed default. Customize agents.md.liquid only when you need one maintained brief across all three URLs. Add a separate llms.txt.liquid only when /llms.txt genuinely must differ from /agents.md. None of these files is a Google ranking shortcut.

What Shopify changed

Shopify's current documentation identifies /agents.md as the canonical agent-discovery document. The /llms.txt and /llms-full.txt paths provide compatible alternatives for systems that look for those conventions. By default, Shopify manages the content, so an ordinary store is not starting with a missing-file problem.

The platform also provides Liquid templates for advanced customization. An agents.md.liquid template controls the shared fallback. A dedicated llms.txt.liquid overrides only /llms.txt, and llms-full.txt.liquid controls only the full variant. The files are served from the bare primary domain, not from every Shopify Markets language or country subfolder.

Keep Shopify's managed default when

  • The native URLs resolve and describe the store accurately.
  • Your team does not have a named owner and review schedule for custom content.
  • You only want a standard agent-discovery entry point.
  • Your real problem is incomplete product, shipping or policy data.

Consider customization when

  • The managed description is materially incomplete for your business model.
  • You need to expose a stable, approved set of policies or discovery endpoints.
  • A custom integration requires different content at one of the three paths.
  • You can monitor the file after catalog, policy and domain changes.

Choose the smallest configuration that solves the problem

Option
Use it when
Main responsibility
Managed default
The native output is accurate and sufficient
Verify periodically; Shopify maintains the template
agents.md.liquid
All three discovery URLs need the same custom brief
Maintain one source and review it after business changes
llms.txt.liquid
Only /llms.txt must differ from the canonical document
Prevent drift between the exception and /agents.md
Third-party app
A maintained app solves a documented workflow beyond native output
Audit permissions, ownership, uninstall behavior and recurring cost

A file generator is not automatically wrong, but it should earn its place. If it duplicates Shopify's default, introduces unverified claims, or leaves theme code behind after uninstall, it adds operational risk without fixing product accuracy or crawlability.

Verify your store before touching theme code

Confirm the primary domain

Use the customer-facing domain that Shopify lists as primary. Do not test a preview domain, a market subfolder or a translated path first.

Evidence: record the exact primary-domain URL and test date.

Open all three discovery URLs

Visit /agents.md, /llms.txt and /llms-full.txt. Each should return a readable response rather than a storefront 404, login page or unrelated redirect.

Evidence: save status, final URL and a short content fingerprint.

Check the important facts

Review store identity, canonical domain, sitemap, policies and discovery endpoints. Do not add claims that are missing from the public storefront or cannot be kept current.

Pass: the discovery brief agrees with public, purchase-relevant facts.

Separate discovery files from product distribution

Shopify Catalog, product feeds, web crawling and agent-discovery files are different paths. Fix incomplete titles, variants, prices, availability and policies in their source systems.

Continue with the AI shopping product-data checklist.

Define a reason and an owner before customization

Write the exact difference the custom file must create, who approves it and what event triggers a review. If those answers are unclear, the managed default is safer.

Pass: every custom statement has a source and review owner.

Test after publishing

Repeat the three URL checks, confirm there is no HTML error page, and verify that the content remains available without cookies or authentication. Recheck after theme deployment or primary-domain changes.

Do not treat a 200 response as proof of recommendation or ranking.

What matters more than the file

For Google Search, Google's own guidance says llms.txt is not used for visibility or rankings, including generative features. The durable work remains familiar: useful original content, crawlable pages, a clear site structure, consistent product information and a good page experience. Review the Shopify technical SEO checklist before prioritizing an optional agent file.

For Shopify's agentic commerce surfaces, Shopify identifies Catalog as the authoritative product-data path. The discovery documents can describe the store and point to resources, but they do not replace accurate catalog mapping. If an offer, inventory value or policy is wrong in the source, a polished text file cannot make the transaction reliable.

Questions Shopify merchants ask

What is an llms.txt file?

It is a plain-text or Markdown-style discovery document at a standard root URL. On Shopify, it is an alternate path to the platform's canonical /agents.md document.

Is llms.txt required?

No. Shopify already serves a managed version, and Google says the file is not required for Search or its generative features. Other services may choose to read it, so verify the platform you actually care about.

Are llms.txt files worth it?

The managed Shopify file is worth verifying because it costs no extra maintenance. A custom version is worthwhile only when it communicates accurate, useful differences and your team will keep it current.

Is llms.txt actually used?

Adoption varies by system. Shopify provides the path for compatibility with agents and crawlers that look for it. Google Search explicitly says it does not use the file for visibility or ranking.

How do I create a custom file?

In Shopify's theme code, advanced users can create agents.md.liquid, llms.txt.liquid or llms-full.txt.liquid. Back up the theme first and follow Shopify's current template documentation.

Do I need one file per market or language?

No. Shopify documents these discovery files on the bare primary domain and says /llms.txt has no localized counterpart. Put locale-specific customer facts on the correct market pages instead.

Seven common mistakes

  1. Buying a generator before opening the native URLs. Verify the actual gap before adding software.
  2. Calling llms.txt an AI ranking factor. That claim conflicts with Google's published guidance.
  3. Using the file as a substitute for product data. Catalog attributes, prices, availability and policies need their own source-of-truth controls.
  4. Creating three independently maintained copies. Prefer the shared agents.md.liquid fallback unless one path truly needs different content.
  5. Generating a separate file for every locale. Shopify serves the root discovery files outside Markets subfolders.
  6. Publishing claims that customers cannot verify. Agent-facing descriptions should agree with the visible store and policies.
  7. Skipping ownership and regression checks. Custom theme files can become stale after changes, migrations or app removal.

What this setup cannot guarantee

A valid file is a technical state, not a visibility result.

It cannot guarantee crawling, citation, recommendation, indexing, ranking or sales. Different assistants and crawlers use different discovery and product-data systems. Platform behavior can change, and Shopify's current documentation should be rechecked before any theme customization.

The defensible goal is smaller: make the store's agent-discovery endpoints accurate, remove unnecessary duplication, and connect every statement to a maintained business fact. That creates a cleaner system even when no measurable referral follows.

Official references

Decide from evidence, then change the smallest thing.

ShopXN audits Shopify discovery, catalog and technical signals as separate controls so optional files do not distract from the source-of-truth problems that affect customers.

Discuss your Shopify system