What should I ask when a vendor says llms.txt improves AI visibility?
Shopify already serves discovery files. Check their sources and ask which system needs a change before paying.
· Updated September 21, 2026
- When this applies
- A vendor offers discovery-file work, an audit flags llms.txt, or your storefront serves content you have not reviewed. [1] [2]
- When this does not apply
- Keep Shopify’s generated files when there is no documented consumer requirement for different content. A general visibility promise does not justify customization. [1] [2]
- Why this matters
- A theme override can change several discovery paths, while a published file or a request for it does not establish a shopping result. [1] [2]
- What to do
- Read all three discovery paths and identify each template or fallback. Ask the maintainer about unfamiliar content, and a vendor for its named consumer and evidence. [1] [2] [4]
- Sources checked
- September 21, 2026
Paid help and free options
- When paid help makes sense
- Pay for a specific consumer requirement and maintained implementation with a checkable result; do not buy an install service that recreates Shopify’s defaults. [1] [2]
- What’s already free
- Shopify supplies the default discovery files for its storefronts. Theme customization is available when different content is needed. [1]
Shopify already supplies discovery files. Before paying for llms.txt work, read the existing content and ask which system needs a change.
Check three public paths
Open /agents.md, /llms.txt, and /llms-full.txt. In the live theme, open Online Store > Themes > Edit code. Shopify’s May 28, 2026 changelog gives this source order:
| Path | First matching source used |
|---|---|
/agents.md | templates/agents.md.liquid, then generated default |
/llms.txt | templates/llms.txt.liquid, then templates/agents.md.liquid, then default |
/llms-full.txt | templates/llms-full.txt.liquid, then templates/agents.md.liquid, then default |
Record each source and read its output. Removing one template may expose the shared agents template rather than restore the default. A template identifies the current source, not its original author.
Ask the maintainer about unfamiliar text. Follow theme-editing precautions: back up, review before publishing, and reopen all three paths after changes. Check replacement themes too.
Ask what the vendor can prove
A useful proposal names the consuming system, required content, maintenance owner, and repeatable check. A claim that an AI system fetches your file needs request evidence; absent evidence stays unverified. Recreating defaults or promising general shopping visibility does not establish a needed change.
The Ahrefs study examined 137,210 domains in May 2026. Of roughly 38,000 with llms.txt, 97% had no requests that month. Its technical/SEO-heavy sample cannot diagnose your store. A fetch proves no use, ranking, traffic, or sale.
Shopify’s discovery guidance says these files help agents understand the store; they do not replace Catalog’s product feed.
Finish with each path’s source and a choice to keep it or approve one maintained, checkable change. Unknown historical authorship need not block that decision.