Shopify agentic readiness scanner: a 2026 guide

Short answer: Shopify’s agentic readiness scanner at shopify.com/agentic-readiness is a free, no-login audit of one storefront URL: a score, a category breakdown and a ranked list of failed checks. It diagnoses, does not fix, and grades a page, not a product. Octolift, built by Craftshift, scores every product against the live Shopify Catalog and drafts the fixes. Free for 5 products.

In late April 2026, Shopify quietly shipped a free scanner at shopify.com/agentic-readiness. You paste a public storefront URL, click Scan, and shortly afterwards you get a score, a breakdown by category, and a ranked list of every failed check with what the fix looks like. There is no login. There is no install. It works on any Shopify store, yours or a competitor’s.

The Shopify agentic readiness scanner is the most useful diagnostic Shopify has shipped this year. It is also, deliberately, the most uncomfortable one. Across the public write-ups of it (the Shopify Community thread, Shopifreaks’ launch coverage) the same gaps come up again and again: incomplete product JSON-LD, thin policy pages, and agent files that an older or headless build does not serve. The scanner exposes the soft underbelly of catalog data that most merchants never look at because the storefront still looks fine in a browser.

This guide is what we wish a real merchant had written when we first opened the tool. It covers what the scanner measures, what every category is for, what the ranked fix list is for, and what to fix in what order. The details come from the public scan output, Shopify’s own pages, and the coverage linked above; where something is not confirmed by Shopify we say so.

In this post

1. What the scanner is and where to find it
2. How the scan runs
3. The five categories, in plain English
4. The three failures almost every store has
5. What a good score is (and what Shopify does not publish)
6. How to read the impact-effort matrix
7. The big limitation: it diagnoses, it does not fix
8. The fix order we recommend
9. Where product structure shows up in the score
10. The disclaimer worth reading twice
11. Our take
12. FAQ
13. Related reading

What the scanner is and where to find it

Officially, the tool is called the Agentic Commerce Audit. Most people who write about it call it the readiness scanner because that phrasing matches the original subdomain. Both names point to the same product. The current URL is shopify.com/agentic-readiness; the old commerce-readiness.shopify.io still works and 301s to the new location.

It’s free. There is no login wall. You don’t even need to own the store you’re scanning. That’s part of the point. The scanner is a public diagnostic, designed to make the technical readiness gap visible to merchants, agencies, and the press. You can scan your own store. You can also scan your top three competitors. We did, and the results were instructive.

The output is three things stacked on one page:

• An overall score (0 to 100), positioned next to a benchmark cohort
• A breakdown of how you scored in each of the five categories
• An impact-effort matrix that lists every failing check, what the fix looks like, and how much it will move your score

That third panel is the actually useful one. Skip past the score itself. Spend your time inside the matrix.

How the scan runs

You give it one URL. The tool page itself describes the job as reviewing the product page for the structured data AI agents read to answer shoppers’ questions, and the launch coverage describes 31 checks across five categories. Some checks read a single thing (is there a product JSON-LD block, does it carry offers and reviews), some read content rather than presence (does the shipping policy actually say when and where you ship). Shopify does not publish the check list itself, so anything more precise than that is somebody’s reverse engineering, including ours, and we have cut the request-level detail an earlier version of this post carried because we could not re-verify it.

What it does not do: it does not crawl beyond the URL you submit, and it does not test the whole catalog. If your review widget or a schema app paints structured data into the page after it loads, assume the audit may not see it, and check the server response yourself (view source, search for “@type”: “Product”).

The five categories, in plain English

Shopify’s marketing materials and the in-product UI use slightly different category names for the same thing. Both name sets show up in third-party writeups, which gets confusing fast. Here is the mapping:

Marketing name	In-product name	What it actually measures
AI discoverability	Agent Discovery	Can an AI agent find and read your store? Tests robots.txt, llms.txt, sitemaps, the UCP discovery endpoint.
Product schema	Product Intelligence	Does each product page expose clean, complete JSON-LD with the fields AI agents need to recommend it?
Transaction readiness	Transaction Readiness	Is your store actually capable of completing an agent-driven checkout? Guest checkout enabled, prices and inventory current, no required account sign-in.
Trust signals	Store Quality	The signals AI agents and shoppers use to decide if you are a real business. Policy pages, About, contact, FAQ depth.
Operational maturity	Operational Readiness	The boring infrastructure layer. Shipping policy clarity, return windows, currency declarations, locale variants of sitemaps.

The two name sets are interchangeable. We will use the marketing names in the rest of this post because that is what most other coverage uses.

The three failures almost every store has

Across the public write-ups, three checks fail almost every time. If you do nothing else after reading this post, fix these.

1. Missing or broken /llms.txt

llms.txt is a markdown file at the root of your domain that gives an AI agent a curated overview of who you are and what you sell. Since May 2026 Shopify serves /llms.txt, /llms-full.txt and /agents.md automatically for every store, generated from your store’s data. So on a Shopify-hosted storefront this check now fails for one of two reasons: a headless or custom build that does not serve the file, or an old URL redirect from /llms.txt to a stale upload that is still overriding the maintained one.

The fix: open yourdomain.com/llms.txt and look. If you see Shopify’s generated “Agent Instructions” file, you pass. If you see an old upload, delete the redirect. If you are headless, serve the file yourself. We covered the current state, including how to customize it with a templates/agents.md.liquid file, in our llms.txt guide.

2. Incomplete product JSON-LD

This is the gap most stores do not realize they have. We measured Shopify’s own structured_data Liquid filter on a live storefront in September 2026: it emits a ProductGroup or Product node with name, description, offers and per-variant sku and gtin, and it emits no aggregateRating, no review, no shippingDetails, no hasMerchantReturnPolicy, no priceValidUntil and no itemCondition. Review apps usually paint their stars client-side. So a typical store has a schema block that is valid and thin at the same time.

If your review widget paints its stars after the page loads, assume an audit of the served HTML will not count them. Same for any structured data injected by an app on a DOM event. The fix is to make sure the JSON-LD is present in the initial HTML response, not added later, and that your review app writes the rating and count into Shopify’s reserved product rating metafields, which is also what Shopify’s own “product reviews” listing signal reads.

Generate a clean baseline block with our free JSON-LD Schema Generator and validate it with the Shopify SEO Checker. If your theme is fighting you, push the schema into the page via a server-rendered metafield rather than relying on the app.

3. Thin or template policy pages

Shopify’s agentic channels require a completed terms of service, privacy policy and return and refund policy before a store can sell through ChatGPT, Google or Meta, and the Agentic page’s “shop policy completeness” signal checks whether your shipping, returns, refund and other policies are present. A 30-word generic shipping policy (“we ship within 5 to 7 business days”) is present and useless at the same time.

AI agents pull policy content into the answer they give a shopper. If your shipping policy is empty, the agent invents one or warns the shopper that the information is unclear. Either is bad for conversion. The fix is to actually write the policies. Include shipping windows by region, the return window in days, the cancellation rules, the contact channel for refunds, and the data categories you process.

What a good score is (and what Shopify does not publish)

Shopify publishes no benchmark distribution, no pass mark and no band labels. Any table of “most stores score between X and Y” you read, including one an earlier version of this post carried, is somebody’s sample, and the tool changes. Use the score the way it is built to be used: as a progress marker. Run it, fix the top of the ranked list, run it again, watch it move.

For a per product grade with Shopify’s name on it, the better instrument is in your admin: Sales channels, Agentic, Listing insights, which scores every product on five named signals (description completeness, image coverage, product reviews, variant and option completeness, shop policy completeness). The scanner grades a URL. Listing insights grade the catalog record the assistants actually read. Doing that for a whole catalog by hand is the point where Octolift scores every product from 0 to 100 against the live Shopify Catalog and drafts the description, title and category fields to earn the missing points. Free for 5 products, $29 a month for 100.

How to read the impact-effort matrix

The matrix is the part of the output most merchants skip. That is a mistake. The matrix takes every failing check, scores it on two axes (how much it will move your overall score, how much developer effort it will need), and plots it. The cells you care about are the top-left quadrant: high impact, low effort.

Typical wins that land in the top-left quadrant on a 50-band store:

• Adding brand and sku to your product JSON-LD (Liquid edit, 30 minutes)
• Writing real shipping and return policies (an afternoon of writing)
• Filling in alt text on product images (a few hours, or a CSV pass)
• Adding an About page with structured contact information

Bottom-right quadrant items (high effort, lower impact) typically include rebuilding a headless storefront to server-render schema, migrating away from a review app that only paints client-side, or implementing the UCP MCP endpoint manually. Worth doing eventually. Not the first move.

The big limitation: it diagnoses, it does not fix

The single most honest line you can write about this tool: it is a diagnostic, not a remedy. The scanner tells you what is broken and ranks the gaps by priority. It does not write your llms.txt. It does not patch your JSON-LD. It does not draft your shipping policy. A Shopify Community post on the launch (written, with disclosure, by the developer of a competing app) made the same point: useful for diagnosing and ranking, fixes nothing.

That gap is where most agencies, third-party apps, and (yes) we ourselves at Craftshift have built tooling. Shopify’s first-party scanner is the universal benchmark for the page. Octolift is our answer for the product: it reads the catalog record per product, scores it, and writes the fix for you to approve. The actual work of fixing each gap still lives in your theme, your apps, your content and your product data. There is no scan-and-resolve button. Anyone who tells you otherwise is selling.

The fix order we recommend

If you score below 50 on your first run, do these in order. The sequencing matters because some fixes set up others.

1. Confirm /llms.txt and /.well-known/ucp resolve. Visit both URLs in a browser. Shopify serves both for every hosted storefront; a 404 means a headless build or a redirect override, not a Shopify setting.
2. Write real policy pages. Shipping, returns, privacy, terms. 300+ words each. Include concrete data: shipping windows by region, return window in days, refund timeline, contact email.
3. Audit your product JSON-LD in the rendered HTML. View source on a product page. Search for "@type": "Product". Make sure offers, brand, sku, and (if applicable) aggregateRating are present in the initial response, not injected by JavaScript.
4. Fix variant image binding. The scanner does not flag the wrong image on the wrong color (yet), but downstream AI surfaces will. This is foundational catalog hygiene. We use Rubik Variant Images for this; if you have your own solution, fine, but make sure each variant resolves to the right photo in the JSON product feed.
5. Clean up runaway variant products. Shopify Catalog consolidates variants and clusters identical items, so a big variant product is not invisible, but its “variant and option completeness” signal reads the option values and stock. Spell colours out, retire variants you will never restock, and if you sell distinct colors as separate products, look at Combined Listings so each color keeps its own URL and the storefront still shows swatches.
6. Fill in alt text and image filenames. Run our free image audit tool or generate AI-suggested alt text for the gaps.
7. Re-scan. The scanner has no rate limit we have hit. Run it again. Watch the score move.

One round of those seven items, in the order listed, moves the score. More importantly it moves the catalog record, which is what the assistants read. It isn’t magic. It’s hygiene.

Where product structure shows up in the score

Product Intelligence is the category that punishes bad catalog structure hardest. The scanner does not yet test for the specific failure modes that hurt you in an AI chat (wrong variant image, runaway variant counts, mis-clustered listings), but those failures show up as missing fields in the JSON-LD it does test for.

Picture three stores:

• Store A has clean schema but every variant linked to the same hero image. The scanner passes it. A shopper who asks an assistant for the olive version and lands on the brown photo does not.
• Store B has a t-shirt with 14 colours as variants, option values like “BLK” and “NVY”, and half of them out of stock. The scanner gives it a decent score because the schema is complete. Shopify’s own listing signal for variant and option completeness does not.
• Store C has separate products per colour, each with a thin forty word description. The scanner does not care. The catalog record for each colour comes back with “Not specified” where the material and fit should be, and the assistant has nothing to compare.

The scanner is a lagging indicator. The score will go up if you ship clean schema. The actual revenue impact depends on whether the record underneath that schema is complete. Run the scanner, sure. Then read Listing insights in your admin, pair it with our product page grader for storefront-level signals, and if your catalog is brushing the 2,048 variant limit, our variant combination calculator.

The disclaimer worth reading twice

At the bottom of the scanner page, Shopify includes a footnote. In substance: these are product page information signals that AI assistants can use to discover, evaluate and recommend your products, and they do not guarantee that AI assistants will surface your products. That line is easy to read past. Don’t.

The scanner tests technical readiness. The AI surface still picks winners by competitive signals: brand familiarity, review volume, conversion rate, price competitiveness, return rate. A perfect 100 with no reviews and a 4-week shipping window will lose to a 70 with 800 reviews and 2-day shipping. The score is necessary, not sufficient.

If your colours live as separate products rather than variants of one product, Rubik Combined Listings groups them into a single listing with swatches instead. Free to install, 5.0 stars across 110 reviews.

Our take

The scanner is the most useful free tool Shopify has shipped to merchants in the last two years. We are saying that out loud because most of Shopify’s recent free tools have been thin. This one isn’t. It’s calibrated to what actually matters for AI discoverability, the URL list it tests is real and not vanity, and the impact-effort matrix is the kind of output most third-party SEO tools do not bother to compute.

What annoys us: the score is published prominently and the disclaimer is buried. A merchant who hits 85 will feel done. They aren’t done. The score measures technical readiness, which is the floor, not the ceiling.

What we expect: the scanner will get more rigorous, and the admin’s Listing insights will keep growing into the per product grade the scanner cannot be. Stores that ship the seven-step fix order now will be ahead of whatever the next version checks.

The Octolift scoring guide lists all twelve of its checks with their point values, if you want the per product version of the scanner’s categories.

FAQ

Where is the Shopify agentic readiness scanner?

The current URL is shopify.com/agentic-readiness. The original commerce-readiness.shopify.io still works and redirects there. You do not need to be logged in to use it.

Is the scanner free?

Yes. No login required, no Shopify account needed, no usage cap mentioned on the page. You can scan any public Shopify URL, including stores you do not own.

How long does the scan take?

Under a minute in the write-ups we have seen. Shopify does not publish a figure, and the exact request pattern an earlier version of this post described could not be re-verified, so we have removed it.

What is a good score?

Shopify publishes no benchmark, pass mark or bands. Treat the score as a progress marker: fix the top of the ranked list, re-scan, and watch it move. For a per product grade, use Listing insights under Sales channels, Agentic.

Does a high score guarantee AI discoverability?

No. The scanner page itself disclaims this. A perfect 100 measures technical readiness, not competitive readiness. AI agents still weigh review volume, brand familiarity, price, shipping speed, and return rates when picking winners.

Does the scanner fix the gaps for me?

No. It is a diagnostic tool, not a remediation tool. It surfaces failed checks and ranks them by impact and effort. The work of fixing each gap (writing policies, adding JSON-LD fields, restructuring variants) lives outside the scanner in your theme, apps, and content team.

Can I scan a competitor’s store?

Yes. The scanner accepts any public storefront URL. This is one of its quietly useful features. Run it on your top three competitors and you will see exactly which checks they are passing that you are not. That tells you where the cheap wins are.

Which app should I use to fix what the scanner finds?

For the product data half, Octolift, built by Craftshift: it queries the live Shopify Catalog for every product, scores it from 0 to 100 across twelve checks, drafts the description, title and category fields for you to approve, and checks your shopper questions in ChatGPT, Gemini and the Shopify catalog. Free for 5 products, $29 a month for 100. For per-variant images, Rubik Variant Images; for grouping separate colour products, Rubik Combined Listings.

Related reading

• Shopify Catalog and AI channels: the 2026 guide
• Shopify shipped native llms.txt, agents.md, and an agentic discovery sitemap to every store
• Shopify stores are shoppable inside ChatGPT: what merchants need to know
• The Shopify AEO guide: how to win in ChatGPT, Perplexity, and Google AI
• The llms.txt Shopify setup guide
• See what ChatGPT sees on your Shopify product
• Shopify’s five listing quality signals for AI
• Shopify variant images FAQ (rubikvariantimages.com)
• Shopify Combined Listings explained (rubikify.com)