Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# How to check if AI agents can buy from your Shopify store

On Shopify the buy check starts from a different place than on a custom store, because the platform already does part of the work for you. Your theme already emits structured data, your sitemap is generated for you, and your robots.txt file is preconfigured. The check below is therefore shorter on setup and sharper on the two places Shopify stores actually fail: duplicate markup from apps, and a checkout that an agent cannot reach or verify.

Platform screens change over time. If a menu name in this guide does not match what you see, check the vendor docs linked in Sources for the current path.

## Why Shopify is different

Three things are specific to the platform. First, the theme is the markup source. Shopify renders product pages from Liquid templates on its servers, and the structured data lives in those templates. Shopify's own help pages say your theme automatically includes microdata in its code, with product pages carrying microdata about prices, availability, and reviews, and that current Shopify-supported themes and Theme Store themes include this by default. Second, there is no server access and no plugin layer like WordPress. Everything goes through theme files, apps, or product data. Third, apps are the usual duplicate source. SEO and review apps inject their own Product blocks, and a page with two conflicting blocks is the most common Shopify failure in this check.

## The check, in order

### 1\. Check what your theme already outputs

Open a live product page, view the page source, and search for `application/ld+json`. Count the Product blocks and work out which one the theme emits and which ones apps emit. Do this before touching anything. The theme block should carry the name, price, currency, availability, and brand for the selected variant. If a review app or SEO app emits a second Product block with a different price, that is a fail on its own. Pick one source of truth: either disable the app's schema output, which most apps let you do with a toggle, or remove the theme block and let the app own it. Never leave both.

### 2\. Compare the markup with the visible page, variant by variant

Check a product with variants and a product that is out of stock. The availability in the markup must match the actual stock for the variant shown, and the price must match the price a shopper sees, including any sale price. A hardcoded price in a Liquid template goes stale the moment you run a sale, so the markup should pull its values from Liquid variables, not from typed-in numbers. Test the same URLs in Google's Rich Results Test and the Schema Markup Validator, and include at least one variant URL and one out-of-stock product in the test.

### 3\. Check robots.txt, and know who should edit it

Open your robots.txt file at \[yourdomain.com\]/robots.txt, replacing yourdomain.com with your actual domain, and confirm it allows OAI-SearchBot, Googlebot, PerplexityBot, and ClaudeBot. Shopify generates the file for you, and its help pages say all stores have a preconfigured and optimized robots.txt file, so you should not need to change it unless you have a specific reason. If you do need a change, it is a developer job, not a dashboard job: a developer adds a robots.txt.liquid file to the templates folder of your theme in the code editor, using Liquid to add or remove directives while keeping Shopify's default rules. A marketer should not edit theme code alone. Ask your developer or a Shopify Partner to make the change, and confirm the live file afterwards at your robots.txt URL.

### 4\. Check the sitemap Shopify generates for you

All Shopify stores automatically generate a sitemap.xml file with links to products, the primary product image, pages, collections, and blog posts. Open it at \[yourdomain.com\]/sitemap.xml, replacing yourdomain.com with your actual domain, and confirm your products are listed. If a product is missing, check that it is published and visible in the online store sales channel, not hidden by a draft status or a channel setting.

### 5\. Walk the checkout as a guest

Add a product to the cart and go to checkout without logging in. Confirm shipping options, tax, and a total appear before any payment step, and that your shipping zones and rates cover the address you test with. If the store forces an account before showing shipping, that is a fail for an agent with no account. Confirm your shipping and returns policies are published pages with working links. An agent that cannot compute a total cannot complete the order, no matter how good the markup is.

### 6\. Check the protocol paths in your admin, and confirm their current status

Open your Shopify admin and look for the agentic commerce settings for your store, and check the vendor docs in Sources for the current path, since these settings change. Two protocol paths can let an agent buy without leaving its own interface. The first is Google's Universal Commerce Protocol, which needs a Merchant Center account in good standing with approved products, return policies and support information set in Merchant Center, and the checkout eligibility attribute set on the products you want to offer. The second is OpenAI's Agentic Commerce Protocol, which is an approved-partner path, not a switch that works for every store. For both paths, confirm the current availability for your store with the platform before you build against them. A Shopify store that has not set up either path can still be bought from by an agent that browses like a human and checks out on the site, provided the markup and the guest checkout pass the steps above.

### 7\. Test with a real prompt, and read the result carefully

Ask an assistant for one of your products by name, then ask for its price and whether it is in stock. Note what it cites and whether the price and stock match your site. Then ask it to buy the product and watch where it stops. A real abort is an agent genuinely attempting a purchase and failing, for example because it cannot verify the price or the checkout blocks it. Friction alone, such as a slow page or an extra click, is not an abort. Do not claim a measured walkthrough rate from one test. One prompt tells you where this product fails today. Repeat the test across products and assistants to find the pattern.

### The fundamentals

-   •The complete JSON-LD reference this check builds on, see our [product schema guide](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •How to add product schema on Shopify, see our [Shopify product schema guide](https://aizii.ai/learn/ai-search/how-to-add-product-schema-on-shopify)
-   •Whether AI crawlers can reach your pages at all, see our [robots.txt guide](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)

### Say you run a coffee gear store on Shopify

You pick your best-selling pour-over set and run the check. The page source shows two Product blocks: the theme emits price and availability but no brand, and a reviews app emits a second block with the rating but a different price format. Your robots.txt allows the search crawlers, and the sitemap lists the product. Guest checkout shows shipping before payment. The fix is not a third block. You disable the app's product schema output, keep the theme block, and add brand to the theme template with Liquid variables. One block, generated from the same data that renders the page, is what turns a blind buy into a verified one.

## What this guide does not cover

This covers checking whether an agent can buy from your Shopify store today. It does not cover building a protocol checkout integration, which is engineering work with the platform, or the monitoring work of keeping prices and availability accurate as inventory changes. It also does not cover your own brand agent, which sells from the fixed data this check verifies.

## Check your own brand now

Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your product pages today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)

## Sources

-   Shopify Help Center, finding and submitting your sitemap (specific): [https://help.shopify.com/en/manual/promoting-marketing/seo/find-site-map](https://help.shopify.com/en/manual/promoting-marketing/seo/find-site-map)
-   Shopify Help Center, editing robots.txt.liquid (specific): [https://help.shopify.com/en/manual/promoting-marketing/seo/editing-robots-txt](https://help.shopify.com/en/manual/promoting-marketing/seo/editing-robots-txt)
-   Shopify developer docs, customize robots.txt (specific): [https://shopify.dev/docs/storefronts/themes/seo/robots-txt](https://shopify.dev/docs/storefronts/themes/seo/robots-txt)
-   OpenAI bots documentation (specific): [https://platform.openai.com/docs/bots](https://platform.openai.com/docs/bots)
-   Google Search Central, Product structured data (specific): [https://developers.google.com/search/docs/appearance/structured-data/product](https://developers.google.com/search/docs/appearance/structured-data/product)
-   Google Universal Commerce Protocol, prepare your Merchant Center account (specific): [https://developers.google.com/merchant/ucp/guides/overview/merchant-center](https://developers.google.com/merchant/ucp/guides/overview/merchant-center)
-   Schema.org, Product type (general standard): [https://schema.org/Product](https://schema.org/Product)

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
