Shopify llms.txt app decision matrix

Choose app, no-app, edge, or headless publishing before generating Shopify llms.txt.

A Shopify app is optional. The useful proof is a public /llms.txt response that avoids private storefront paths and passes a live validator.

Fast answer

Use the simplest route that can serve public /llms.txt with HTTP 200.

Start with no-app or existing host control when available. Use app proxy/custom app, edge worker, or headless routing only when the store needs that infrastructure. Do not treat an app install, generated draft, crawler hit, or Search Console impression as live-file proof.

score 5 / 5

No app: direct root file or existing storefront host

The store already controls a host, route, or edge layer that can return a public root /llms.txt file.

Choose when

  • A developer can add a public root route.
  • The response can be plain text or Markdown with HTTP 200.
  • No private customer, cart, checkout, token, preview, or admin URLs are needed.

Avoid when

  • The only available option is a theme asset URL that is not served at /llms.txt.
  • The team cannot validate the root file with a public fetch.

Next action: Publish a short curated file at /llms.txt, then run the live validator.

score 4 / 5

App proxy or custom app route

The merchant needs app-managed generation, approvals, or a controlled endpoint, and understands the public route caveats.

Choose when

  • A Shopify app already exists or is planned.
  • The file needs merchant-managed generation or review.
  • A developer can ensure the final public endpoint is fetchable and cacheable.

Avoid when

  • The searcher only needs a one-time static file.
  • The app install is being treated as proof that /llms.txt is live.
  • The route cannot be validated as a public root file or documented support route.

Next action: Keep the app output static, cacheable, and limited to public storefront links.

score 4 / 5

Edge or CDN worker

Traffic already passes through Cloudflare, a CDN, or another edge layer that can return /llms.txt before Shopify.

Choose when

  • The team controls DNS, proxying, or edge routing.
  • The store wants a root /llms.txt response without changing Shopify theme files.
  • The output can be cached and revalidated after edits.

Avoid when

  • No one owns the edge configuration.
  • The worker would redirect to private admin or app URLs.

Next action: Serve plain text or Markdown, avoid redirects to private admin systems, and recheck HTTP 200.

score 3 / 5

Headless storefront route

The Shopify catalog is served through Hydrogen, Oxygen, or another headless frontend that can add public routes.

Choose when

  • The storefront frontend is code-owned.
  • A route can generate a curated public file from approved URLs.
  • The deployment can be tested with a public validator.

Avoid when

  • The store is standard Online Store only with no frontend deployment pipeline.
  • The generated file would dump the full product database.

Next action: Generate /llms.txt from curated public CMS or product URLs, not from the full product database.

Route decision table

RouteBest whenNext actionProof
No app: direct root file or existing storefront host The store already controls a host, route, or edge layer that can return a public root /llms.txt file. Publish a short curated file at /llms.txt, then run the live validator. proof route
App proxy or custom app route The merchant needs app-managed generation, approvals, or a controlled endpoint, and understands the public route caveats. Keep the app output static, cacheable, and limited to public storefront links. proof route
Edge or CDN worker Traffic already passes through Cloudflare, a CDN, or another edge layer that can return /llms.txt before Shopify. Serve plain text or Markdown, avoid redirects to private admin systems, and recheck HTTP 200. proof route
Headless storefront route The Shopify catalog is served through Hydrogen, Oxygen, or another headless frontend that can add public routes. Generate /llms.txt from curated public CMS or product URLs, not from the full product database. proof route

Proof links for AI agents

Official Shopify references and caveats

ReferenceUse forCaveat
Shopify app proxies documentation Use when a Shopify app needs to proxy a storefront URL to an app-controlled endpoint. An app proxy has configured prefix and subpath behavior; do not assume it proves a root /llms.txt file is live.
Shopify theme architecture documentation Use when checking whether the storefront theme can host supporting assets or reusable Liquid/HTML components. Theme assets are useful support files, but a theme asset alone should not be treated as proof that /llms.txt exists at the root.
Shopify Hydrogen and Oxygen documentation Use when the store is headless and can add a framework route that returns /llms.txt. A Hydrogen route still needs a public deployed URL and live validator proof.

FAQ

Do I need a Shopify app to publish llms.txt?

No, not if you already control a public route that can serve /llms.txt. Use an app or edge route only when the storefront cannot serve it directly or needs managed generation.

What is the proof that Shopify llms.txt is live?

A public fetchable /llms.txt file with HTTP 200 and safe public URLs. A generated draft, app installation, crawler hit, or impression is not enough.