The checklist we work from. Use it without us.
57 checks in six passes. It’s the list we run on paying stores. Most of it needs no code.
Start with Shopify’s own free checker at commerce-readiness.shopify.io. It runs 31 checks on your public storefront in about 30 seconds and tells you what’s wrong. This list shows you how to confirm each problem, and it covers what only your admin can show.
Last checked against Shopify, OpenAI, Anthropic, Perplexity and Google documentation: 16 November 2026.
How to read it: “Fix” says who can fix a failed check. Admin: you can, in your Shopify admin, without code. Code: it needs a theme edit. Owner: only the store’s owner can do it.
Print this page. It’s built for it.
Pass 1. Channel and eligibility: are you let in?
Shopify decides whether your products enter its catalogue for AI channels. Eligible stores are in by default. Find out which you are before you touch anything else.
| Channel | Buyers it reaches | Where they pay | State |
|---|---|---|---|
| ChatGPT | United States | Your store’s checkout | On by default for eligible stores |
| Microsoft Copilot | United States | Inside Copilot, or your store if you switch that off | On by default |
| Google AI Mode and Gemini | Rolling out. In-chat checkout for the US, Canada and Australia. | Inside Google where available, otherwise your store | Rolling out to eligible stores |
| Meta AI | 11 countries, including the US, Canada and Mexico | Inside Meta, or your store if you switch that off | On by default for eligible stores |
Source: Shopify, 11 November 2026. For ChatGPT your store can be based anywhere, as long as it sells to US buyers.
| # | Check | A pass looks like | Check it yourself | Fix | |
|---|---|---|---|---|---|
| 1.1 | Shopify Catalog shows your store as eligible | A product count beside Shopify Catalog. No ineligibility reason. | Admin: Sales channels > Agentic > Sources > Shopify Catalog | Depends on the reason shown | |
| 1.2 | The store is open and on a paid plan | Starter plan or higher. No storefront password. Not B2B-only. | Open your store in a private window. A password prompt is a fail. | Admin | |
| 1.3 | The three policies are filled in | Terms of service, privacy policy, and refund and return policy all hold real text. | Admin: Settings > Policies | Admin | |
| 1.4 | The Agentic Storefronts terms are accepted | Accepted, by the store’s owner. | Admin: Sales channels > Agentic | Owner. We flag it. We don’t accept legal terms for you. | |
| 1.5 | A US buyer can check out | A US address gets a shipping rate at checkout. | Add a product to your cart and enter a US address. | Admin | |
| 1.6 | Each product meets Catalog’s basics | A title, at least one image, a price above zero, published to the Online Store, not Unlisted, not hidden from search engines. | Admin: Products. Filter by status and sales channel. | Admin | |
| 1.7 | No product is uncategorized or excluded | Every product has a category and enough detail for Shopify to classify it. None is on Shopify’s excluded list, which includes alcohol, vaping, CBD supplements, weapons and adult products. | Admin: the Category field on each product | Admin for the category. Excluded types can’t be fixed. | |
| 1.8 | Channel switches are set on purpose | For ChatGPT, Copilot, Google and Meta, Catalog access and direct checkout are on or off because you chose it. | Admin: Sales channels > Agentic | Admin | |
| 1.9 | Google Merchant Center is connected and clean | Connected, with no account-level issues. Google’s AI Mode and Gemini need it. | Merchant Center, or the Google & YouTube channel in your admin | Admin | |
| 1.10 | Account security is on | Your email is verified and two-step authentication is on. | Admin: your account’s security settings | Owner |
Pass 2. Discovery and crawler access: can they reach you?
Shopify serves three agent files on every store without being asked. Nobody needs to sell you an llms.txt. What goes wrong is access: a robots.txt rule, an app or a firewall turning the wrong crawler away.
| Company | Crawler | What it does | Obeys robots.txt |
|---|---|---|---|
| OpenAI | OAI-SearchBot | Builds ChatGPT’s search results | Yes |
| OpenAI | GPTBot | Collects training data | Yes |
| OpenAI | ChatGPT-User | Fetches a page when a user asks | Not always |
| Anthropic | Claude-SearchBot | Builds Claude’s search results | Yes |
| Anthropic | ClaudeBot | Collects training data | Yes |
| Anthropic | Claude-User | Fetches a page when a user asks | Yes |
| Perplexity | PerplexityBot | Builds Perplexity’s search results | Yes |
| Perplexity | Perplexity-User | Fetches a page when a user asks | Generally not |
Block a search crawler and you drop out of that company’s search answers. Blocking a training crawler doesn’t do that. Google’s and Microsoft’s assistants lean on Googlebot and Bingbot.
| # | Check | A pass looks like | Check it yourself | Fix | |
|---|---|---|---|---|---|
| 2.1 | /agents.md loads | Status 200. It names your store and its catalogue and checkout endpoints. | Visit yourstore.ca/agents.md | Nothing to fix by default. Shopify serves it. | |
| 2.2 | /llms.txt and /llms-full.txt load | Status 200. By default each mirrors agents.md. | Visit both addresses. | Nothing to fix by default. | |
| 2.3 | /.well-known/ucp loads | Status 200, and a JSON profile of what your store supports. | Visit yourstore.ca/.well-known/ucp | Shopify support | |
| 2.4 | Nobody has overridden those files badly | No agents.md.liquid or llms.txt.liquid in your theme. Or, if there is one, it’s current and still points to the UCP and MCP endpoints. | Admin: Online Store > Themes > Edit code > Templates | Code | |
| 2.5 | robots.txt lets the search crawlers in | No “Disallow: /” under OAI-SearchBot, Claude-SearchBot, PerplexityBot, Googlebot or Bingbot. | Visit yourstore.ca/robots.txt | Code | |
| 2.6 | Training crawlers are a decision | GPTBot and ClaudeBot are allowed or blocked because you chose it. | The same file | Code | |
| 2.7 | Product pages make sense without JavaScript | The title, price and description are in the page source. | On a product page, choose View page source and search for the price. | Code | |
| 2.8 | Crawlers get the page people get | A request sent as OAI-SearchBot, Claude-SearchBot or PerplexityBot returns the same status and content as a browser. | Needs a command line. If that isn’t you, skip it: 2.5 and 2.9 catch most cases. | App or firewall settings | |
| 2.9 | Nothing in front of the store turns bots away | No bot-blocking app. No firewall or proxy rule that challenges AI crawlers. | Admin: Apps. If you use a proxy such as Cloudflare, check its bot settings. | Admin | |
| 2.10 | The sitemap and addresses are clean | /sitemap.xml lists your products. Each product address loads on your main domain without a chain of redirects. | Visit yourstore.ca/sitemap.xml | Admin |
Honest limit: check 2.8 can’t prove a real crawler gets through. Firewalls check where a request comes from as well as what it calls itself. It does catch the common failures.
Pass 3. Catalogue data: do they understand the product?
This is where most of the work is. A machine can’t infer what you didn’t write down. Shopify’s own example is a candle listed with its scent, wax type, size and burn time. Every check here applies to every product.
| # | Check | A pass looks like | Check it yourself | Fix | |
|---|---|---|---|---|---|
| 3.1 | The title names the product | What it is, plus the one attribute a buyer would search by. No slogans, no strings of keywords. | Read it aloud. Would a stranger know what’s in the box? | Admin | |
| 3.2 | The description states facts | Material, dimensions, weight, what’s included, care, compatibility: whichever apply. Adjectives don’t count. | Count the facts that contain a number or a noun. | Admin | |
| 3.3 | The category and its attributes are filled | A category from Shopify’s product taxonomy, with its attribute fields completed: colour, material, size and so on. | Admin: the Category field, then the category metafields beneath it | Admin | |
| 3.4 | Options have real names | “Size”, “Colour”, “Scent”, with values a buyer would recognize. No “Default Title”. No internal codes. | Admin: the Variants section of each product | Admin | |
| 3.5 | Every variant is complete | A price, an inventory state, and a weight where shipping depends on it. | Admin: the bulk editor | Admin | |
| 3.6 | GTINs are in the Barcode field | Every variant that has a GTIN (a UPC or EAN) carries it. Variants without one are left blank. Never invent one. | Admin: the bulk editor’s Barcode column | Admin. GS1 Canada issues GTINs. | |
| 3.7 | Brand and SKU are consistent | Vendor holds the brand name, spelled one way. SKUs are unique. | Admin: the bulk editor | Admin | |
| 3.8 | Images match the product | At least one image of the actual item. Variant images assigned to their variants. Alt text that says what is pictured. | Admin: the Media section of each product | Admin | |
| 3.9 | Important custom fields are mapped | Facts you keep in custom metafields are mapped in Shopify’s Catalog mapping, so the channels receive them. | Admin: Catalog mapping, in the Agentic channel | Admin | |
| 3.10 | One product, one listing | Colours and sizes are variants of one product, or grouped as a combined listing. Not separate products. | Search your own store for the product’s name. | Admin | |
| 3.11 | Price and stock agree everywhere | Your admin, the product page and the structured data show the same price, currency and availability. | Compare the three for one product. | Admin or code |
Pass 4. Schema and reviews: is it in their format?
Structured data is the same facts in a format a machine parses without guessing. Two free tools check it: the Schema Markup Validator and Google’s Rich Results Test.
| # | Check | A pass looks like | Check it yourself | Fix | |
|---|---|---|---|---|---|
| 4.1 | Product structured data exists | One Product or ProductGroup block of JSON-LD in the source of every product page. | View page source and search for “application/ld+json”. | Code | |
| 4.2 | It validates | No errors in the Schema Markup Validator or Google’s Rich Results Test. | Paste a product address into either tool. | Code | |
| 4.3 | It is complete | name, description, image, sku, brand, and offers with price, priceCurrency, availability and url. Plus gtin when you have one. | Read the fields the tools detect. | Code | |
| 4.4 | There is only one of it | Your theme and your apps don’t each add a Product block with different values. | Count the Product blocks in the page source. | Code or app settings | |
| 4.5 | Variants are covered | Each variant’s price and availability is present, not only the first. | Run the Rich Results Test on a product with several variants. | Code | |
| 4.6 | Organization data is on the home page | name, url, logo, a contact point and links to your social profiles. | Run the Rich Results Test on your home page. | Code | |
| 4.7 | The return policy is machine-readable | A MerchantReturnPolicy with country, return window and fees. In markup, or set in Merchant Center or Search Console, which Google reads first. | The Rich Results Test, and Merchant Center’s shipping and returns settings | Code or admin | |
| 4.8 | Shipping is machine-readable | Rate, destination and delivery time for the US, in markup or in Merchant Center. | The same two places | Code or admin | |
| 4.9 | Ratings in the markup are true | aggregateRating matches the rating and count shown on the page. No markup for reviews a shopper can’t see. | Compare the Rich Results Test output with the page. | Review app settings | |
| 4.10 | Review text is in the page | The words of your reviews appear in the page source, not only inside a widget that loads later. | View page source and search for a phrase from a review. | Review app settings |
Pass 5. Facts as text: can they answer a buyer?
When a buyer asks an assistant “can I return it?”, the answer has to exist as text somewhere the assistant can read. Not in an image. Not in a widget that loads late.
| # | Check | A pass looks like | Check it yourself | Fix | |
|---|---|---|---|---|---|
| 5.1 | Shipping is written down, with numbers | Where you ship, what it costs and how long it takes, as text on a shipping or policy page. | Read your shipping page and count the numbers. | Admin | |
| 5.2 | US buyers get straight answers | Currency, duties and taxes, and delivery time to the US, stated plainly. | Read the page as a US buyer would. | Admin | |
| 5.3 | Returns are written down, with numbers | The window in days, who pays return shipping, the condition required and how to start. | Read your refund policy. | Admin | |
| 5.4 | Size charts are tables, not pictures | Sizing is an HTML table or text. Not an image. Not a PDF. | Try to select the chart’s text with your cursor. | Admin or code | |
| 5.5 | Product facts are text, not artwork | Ingredients, materials, dimensions and care appear as text, not only inside product images. | The same cursor test | Admin | |
| 5.6 | Facts load with the page | Tabs and accordions hold their text in the page source. Nothing essential arrives only by script. | View page source and search for a sentence from the tab. | Code or app settings | |
| 5.7 | Shopify’s Knowledge base is reviewed | The store facts listed under Sources are correct, and missing ones are added: for example, who pays return shipping. | Admin: Sales channels > Agentic > Sources | Admin | |
| 5.8 | The business is identifiable | Your business name, where you operate and a way to reach you, as text on the site. | Read your contact page. | Admin | |
| 5.9 | Every source gives the same answer | The policy page, the product page, the Knowledge base and the structured data agree on shipping and returns. | Compare all four for your return window. | Admin or code |
Pass 6. Fix and verify: can you prove it?
A fix you can’t show is a claim. Keep a before and an after for everything you change.
| # | Check | A pass looks like | How to do it yourself | |
|---|---|---|---|---|
| 6.1 | The before state is recorded | For each failed check: the raw value, the address, the date and time, the tool used. | Keep a spreadsheet. One row per check per product. | |
| 6.2 | There is a way back | The theme is duplicated and the product data exported before anything changes. | Admin: Themes > Duplicate, and Products > Export | |
| 6.3 | Every change is logged | The field, the old value, the new value and the date. | The same spreadsheet | |
| 6.4 | The after state is recorded the same way | The same address, tool and request as in 6.1. | Re-run each check. | |
| 6.5 | Catalog status is read again | Still eligible, with no fewer products than before. | Admin: Sales channels > Agentic > Sources | |
| 6.6 | What wasn’t fixed is listed | Every open item has a reason and an owner. | Write them down. Don’t round up. | |
| 6.7 | The record is kept | Before, after, change log and rollback notes, in one place. | One file per round of fixes |
Stuck on the ones marked “Code”?
That’s the part we do. Start with the free scan and we’ll tell you which checks are costing you.