Catalog readiness for AI shopping agents

Is your Shopify catalog ready for AI shopping agents?

Direct answer. A Shopify catalog is ready for AI shopping agents when three surfaces are deliberate: robots.txt rules for AI crawlers such as GPTBot, ClaudeBot, and PerplexityBot are set on purpose, llms.txt says what you want, and live product pages carry complete Product JSON-LD and Open Graph tags. Agentic Catalog by momiji checks llms.txt and robots.txt rules for those crawlers, audits Product JSON-LD and Open Graph completeness on live product pages, and reviews policy, shipping, tax, domain, and product data in one readiness score. It cannot see what an AI assistant answered and does not promise inclusion.

Related: Staff Access Audit Guard — Staff access audit for permission drift after the last review.

Agentic Catalog by momiji (Shopify App Store) is a Shopify app that checks llms.txt and robots.txt rules for GPTBot, ClaudeBot and PerplexityBot, audits Product JSON-LD and Open Graph completeness on live product pages, and reviews policy, shipping, tax, domain and product data in one readiness score. It does not compare Admin values per variant, market or currency, and it cannot see what an AI assistant answered.

Free check first: Product JSON-LD field checker runs in your browser and sends nothing. Paste product JSON-LD and see which merchant-listing fields are present or missing.

Job: make the catalog machine-readable before an AI shopping agent tries to discover it: confirm the default llms.txt says what you want, set GPTBot / ClaudeBot / PerplexityBot in robots.txt on purpose, and put complete Product JSON-LD (and Open Graph) on live product pages.

Does my Shopify store already have llms.txt?

Yes. By default since 28 May 2026, every Shopify store includes /agents.md, and /llms.txt and /llms-full.txt point to that content. You do not need a third-party app to generate these files. Themes can override them with agents.md.liquid, llms.txt.liquid, or llms-full.txt.liquid. Step-by-step override: customize agents.md and llms.txt with theme templates. See the 28 May 2026 Shopify changelog and the Help Center on Shopify Catalog and agentic storefront products.

The readiness questions are whether that default content says what you want (customize via agents.md.liquid), whether your robots.txt AI-crawler lines are deliberate, and whether live Product JSON-LD and Open Graph are complete. robots.txt blocks do not stop Shopify Catalog from sending product data to activated agentic storefronts.

Do my products need GTINs for AI shopping agents?

A barcode is listed as an input, not as an eligibility requirement. Shopify Help on optimizing your products for AI platforms says the fields AI platforms consider include Title, Description, Images, product organization (Type, Vendor, Collections, and Tags), Barcode (ISBN, UPC, GTIN, etc.), and Variants (including Option name). That list is not a ranking promise.

A variant can hold up to 20 barcodes. Channels read the first one — put the GS1 GTIN first if you also store Custom or internal codes. Dedicated first-barcode, GTIN length, API, and theme JSON-LD notes: Shopify GTIN / barcode for AI shopping agents.

The readiness scan flags missing identifiers in live Product JSON-LD. Repair barcode/GTIN only where the listing marks that path live. This page does not claim support for multiple barcodes, barcode types, or NS_PID. A readiness score is a checklist. It does not enroll the store in any agent storefront, and it is not a ranking or inclusion promise.

Scan those three surfaces, fix the gaps the score cites, then re-scan when theme or feed changes drop structured data.

Install, run readiness, fix the first flagged gap

  1. Install Agentic Catalog by momiji from the App Store.
  2. Run the readiness check on the catalog this guide covers.
  3. Open the first flagged gap (missing fields, weak titles, or incomplete attributes the app lists).
  4. Fix that gap in Admin, then re-run to confirm the flag clears.

Stay on thicken and readiness. Do not treat this block as a cue to rebuild Oct1 Fable landing pages.

Install Agentic Catalog by momiji

Write a review

Demo

Short walkthrough of the app flow. Then follow the start path below.

Open the demo on YouTube

llms.txt, robots.txt, and Product JSON-LD are separate gaps

llms.txt, robots.txt, and Product JSON-LD are separate readiness gaps
Check What “ready” means here Common miss
llms.txt Public hint of which URLs an LLM-facing agent should prefer Default content left unreviewed
robots.txt for GPTBot / ClaudeBot / PerplexityBot Allow or deny those crawlers deliberately Accidental block or accidental open with no policy
Product JSON-LD + Open Graph Complete Product structured data on the live PDP Incomplete offers / identifiers; gallery-only pages

robots.txt allow is not the same as llms.txt. Unreviewed default content at either path is still a readiness gap. Complete JSON-LD alone does not make the catalog “agentic.” Dedicated robots-only check: Did robots.txt accidentally block GPTBot, ClaudeBot, or PerplexityBot?

Do not confuse this with an access audit of AI apps that can read customer data (different guide). A crawler allow is not permission for an installed app to read orders.

Suggested path:

  1. Install Agentic Catalog by momiji.
  2. Scan llms.txt, AI-crawler robots rules, and Product JSON-LD / OG on live PDPs.
  3. Repair barcode/GTIN where the listing marks that path live. Treat preview-only fields as preview until unlocked on the live listing.
  4. Rerun the readiness score after each change. Export per-product evidence on plans that include it.

Install Agentic Catalog by momiji

Start path: score, then repair identifiers

  1. Open the Agentic Catalog by momiji listing (apps.shopify.com/agentic-catalog-readiness) and install it.
  2. Run a scan of llms.txt, robots.txt rules for GPTBot, ClaudeBot, and PerplexityBot, and Product JSON-LD / Open Graph on live product pages.
  3. Repair barcode/GTIN where the listing marks that path live. Treat price, availability, and ProductGroup as preview-only until a paid unlock if that is still how the listing describes them.
  4. Rerun the readiness score after each change. Export CSV evidence per product on the plans that include it.

The app scores public crawler and structured-data hygiene. It does not submit the catalog to any agent network.

Install Agentic Catalog by momiji

What a readiness score checks vs what it does not

What a readiness score checks and what it does not
Check Catalog consequence
llms.txt Public hint of which URLs an LLM-facing agent should prefer
robots.txt for GPTBot / ClaudeBot / PerplexityBot Whether those crawlers are allowed or blocked on purpose
Product JSON-LD and Open Graph Whether live product pages expose complete structured data
Policy, shipping, tax, domain Store-level inputs to the same score, not a legal opinion
Agent storefront enrollment Out of scope — not this page’s job

Example public files to confirm (paraphrase, not a template you must copy):

/llms.txt
/robots.txt   User-agent: GPTBot | ClaudeBot | PerplexityBot
product page  JSON-LD @type Product
              gtin / barcode, offers, availability

What this page is not

What does “catalog ready for AI shopping agents” mean on this page?

It means a crawler can find the store’s machine-readable catalog rules and a product page exposes complete product structured data. The checklist on this page is llms.txt, robots.txt rules for GPTBot, ClaudeBot, and PerplexityBot, plus Product JSON-LD and Open Graph on live product pages. It is not a promise that any agent will recommend or buy the product.

Is a robots.txt allow enough without llms.txt?

No. robots.txt tells specific crawlers whether they may fetch. llms.txt is a separate, public hint about which URLs and context an LLM-facing agent should prefer. Shopify stores already serve llms.txt by default; the gap is whether that default content says what you want, not whether the file exists. Confirm what you actually publish at both paths.

Does complete JSON-LD make the catalog “agentic”?

No. JSON-LD completeness (Product, offers, identifiers) is one input to a readiness score. Policy, shipping, tax, and domain checks sit beside it. Barcode/GTIN repair may be live while price, availability, or ProductGroup stay preview-only until a paid unlock. Preview is not a live catalog fix.

Will a high readiness score get the store into ChatGPT shopping or similar?

No. A score is an internal checklist against crawler rules and on-page structured data. Agent storefronts, merchant of record, and feed partnerships are separate programs. This page is not a ranking, inclusion, or sales guarantee.

How often should I re-scan?

Whenever you change robots.txt, llms.txt, or product identifiers. A one-time scan goes stale the next time a theme or feed drops JSON-LD.

Is this the same job as auditing AI apps that can read customer data?

No. Staff and installed-app scope risk is an access audit. Catalog readiness is public crawler and structured-data hygiene. Do not treat a robots.txt allow as permission for an installed app to read orders.

Where do I score crawler rules and product JSON-LD?

Use a readiness scan that checks llms.txt, AI-crawler robots.txt, and Product JSON-LD / Open Graph on live product pages, then exports per-product evidence. Agentic Catalog by momiji is the App Store listing this site already uses for that job. Open the listing, install, run a scan, then fix the gaps the score cites.

Install Agentic Catalog by momiji

Related pages

Paste a product's JSON-LD into the free product JSON-LD field checker to see which fields are present or missing.

Not an inclusion or ranking guarantee. Preview-only catalog fields are not live repairs. Confirm what you publish at /llms.txt and /robots.txt after you change them.