A Shopify app is optional. The useful proof is a public /llms.txt response that avoids private storefront paths and passes a live validator.
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.
The classifier separates app install, generated draft, theme asset, no-app root control, app proxy, edge worker, headless route, private-path safety, live root validation, and real traffic proof before recommending a Shopify route.
Proves: Google is testing Shopify llms.txt generator and app-decision queries.
Does not prove: It does not prove demand has converted into traffic, app installs, route selection, or live-file validation.
Current observation: 19 zero-click impressions across Shopify llms.txt generator/app queries.
Next action: Keep the generator and app decision matrix aligned, then wait for Search Console recrawl before judging CTR.
Proves: A merchant may have an app workflow available.
Does not prove: It does not prove the storefront returns a public /llms.txt file, uses safe public URLs, or is accessible to crawlers.
Next action: Validate the final public URL after any app proxy or custom app route is configured.
Proves: The merchant has a copy-ready candidate file.
Does not prove: It does not prove the file was uploaded, routed, cached, or served from the canonical storefront root.
Next action: Publish first, then run the live Shopify checker or root-file validator.
Proves: A theme can host supporting files or Liquid output inside Shopify's theme architecture.
Does not prove: It does not prove /llms.txt exists at the root URL where agents expect it.
Next action: Use a route, proxy, edge worker, or headless frontend when the required proof is root /llms.txt.
Proves: The store may be able to serve /llms.txt without installing a Shopify app.
Does not prove: It does not prove the route is already deployed or content-safe.
Next action: Prefer this route when root hosting is available, then validate HTTP 200 and private-path safety.
Proves: A Shopify app proxy or custom app can be part of a managed publishing workflow.
Does not prove: It does not prove root-path availability, cache behavior, or final public response quality by itself.
Next action: Document the proxy route, publish the generated content, and run a public fetch test.
Proves: An edge/CDN layer can serve /llms.txt before Shopify when the team controls routing.
Does not prove: It does not prove the worker is deployed safely or free from private URL leakage.
Next action: Serve a short cached file at /llms.txt and validate it from the public canonical host.
Proves: A Hydrogen/Oxygen or headless storefront can add a code-owned /llms.txt route.
Does not prove: It does not prove the route has been deployed, fetched, or limited to curated public URLs.
Next action: Deploy the route, fetch the public file, and check canonical/storefront URL quality.
Proves: The draft or route was reviewed for cart, checkout, account, customer, discount, token, preview, filtered, search, and admin paths.
Does not prove: It does not prove the whole Shopify store has no private or sensitive URLs elsewhere.
Next action: Run the Shopify checker and private-path review before launch.
Proves: The canonical store can publicly return /llms.txt and the fetched body can be inspected.
Does not prove: It does not guarantee rankings, AI citations, referrals, or conversions.
Next action: Save the live validation proof and measure Search Console clicks and tool activations separately.
Proves: Real traffic requires clicks, qualified referrals, live checker runs, generated drafts, copied plans, or conversions.
Does not prove: Search impressions, app installs, crawler hits, and self-clicks are not traffic proof.
Next action: Measure generator runs, route planner usage, live checker runs, Search Console clicks, and qualified referrals.
Tick what is true for the store. The chooser keeps the route conservative: root control first, then edge, then headless, then app proxy/custom app only when an app-owned workflow is actually needed.
Recommended route: no-app discovery first. Why: if a store can serve a public root /llms.txt file, an app is optional. Proof: validate the live root file before claiming Shopify llms.txt is live.
Open the machine-readable decision JSON and Shopify CTR pack.
The store already controls a host, route, or edge layer that can return a public root /llms.txt file.
Next action: Publish a short curated file at /llms.txt, then run the live validator.
The merchant needs app-managed generation, approvals, or a controlled endpoint, and understands the public route caveats.
Next action: Keep the app output static, cacheable, and limited to public storefront links.
Traffic already passes through Cloudflare, a CDN, or another edge layer that can return /llms.txt before Shopify.
Next action: Serve plain text or Markdown, avoid redirects to private admin systems, and recheck HTTP 200.
The Shopify catalog is served through Hydrogen, Oxygen, or another headless frontend that can add public routes.
Next action: Generate /llms.txt from curated public CMS or product URLs, not from the full product database.
| Route | Best when | Next action | Proof |
|---|---|---|---|
| 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 |
| Reference | Use for | Caveat |
|---|---|---|
| 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. |
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.
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.
Search Console has already tested this URL for related long-tail queries. These support blocks answer that demand on the existing page, link to proof routes for AI agents, and avoid creating doorway pages.
Use the Shopify llms.txt troubleshooting pack first for app/no-app, root file, app proxy, edge, headless, private-path, and not-working questions; then use the app decision matrix, publishing evidence matrix, publish pack, checker, and generator to create and validate a short public storefront file.
Open proof-linked content brief