Shopify AI Readiness Checklist — 12 Checks Before You Scale

A Shopify AI readiness checklist is a fixed set of 12 checks that confirm ChatGPT, Perplexity and Google AI Overviews can fetch, understand and quote your store. Run it on four representative URLs — homepage, one collection, one product and one policy page — before you scale ad spend or ship a theme update. Printable beats memorable: a list you run every quarter catches breakage that memory never will.

What is AI readiness for a Shopify store?

AI readiness means a public page exposes clean, machine-readable facts that an AI model can use without guessing. For an online store that comes down to four things: the page can be fetched (not password-gated, not marked noindex), the page is described in structured data (JSON-LD — a small hidden block of code that labels the shop name, product, price and stock in a format machines read reliably), the crawlers you want are allowed in robots.txt, and an optional llms.txt file at your domain root points models at the pages that matter.

It is not a ranking score and it is not a guarantee of citations. It is the minimum condition for being quoted accurately rather than invented.

Why run a checklist before you scale?

Theme updates, SEO app installs and catalogue relaunches all change what a crawler sees, and none of them show a warning in Shopify admin. A collection you are about to put $5,000 of ads behind may be marked noindex by a forgotten app setting. A product page may show one price to shoppers and an old price in JSON-LD. A checklist forces the same questions on the same page types every time, so the answer is "we checked" rather than "we assumed."

The 12 Shopify AI readiness checks

Each check has a merchant-level test you can do yourself.

1. Production store is not password-gated. Open the store in an incognito window. If you see the password page, crawlers do too.
2. Key pages are not noindex. View page source and search for noindex. Also check Search Console → Pages for "Excluded by noindex tag."
3. Canonicals point at the right page type. A product's canonical should be /products/handle, not a collection-scoped copy. See canonical URLs on Shopify.
4. og:title and og:image are present. Search the source for og:title. Paste the URL into a Slack or WhatsApp message and confirm a preview appears.
5. Homepage carries Organization or WebSite markup. Search the homepage source for "@type": "Organization" or "WebSite".
6. Products carry an Offer with price and availability. Paste the product URL into Google's Rich Results Test and confirm a Product result with price and availability.
7. Collections are marked as collections with product links. The HTML should include real product anchors, not only an infinite-scroll placeholder.
8. Breadcrumbs exist where you would expect them. Visible trail plus BreadcrumbList in the source.
9. Names agree across H1, og:title and JSON-LD. Three different product names make a model hedge.
10. AI bot policy is intentional in robots.txt. Open /robots.txt and confirm GPTBot, ClaudeBot, PerplexityBot and Google-Extended are allowed or disallowed on purpose. See GPTBot and robots.txt on Shopify.
11. llms.txt is live and useful. Open /llms.txt. It should return short text with links, not a 404 or a theme page.
12. A prompt test in ChatGPT matches reality. Ask "What does [store] sell and what does [product] cost?" and compare the answer to the live page.

How do I run the checklist on a Shopify store?

1. Pick four URLs: homepage, your highest-traffic collection, your best-selling product and your shipping or returns policy page.
2. Open each in an incognito window and note the visible name, price and stock state.
3. Right-click → View page source and search for ld+json, noindex, canonical and og:title.
4. Paste each URL into Google's Rich Results Test and note any missing fields.
5. Open /robots.txt and /llms.txt on your domain.
6. Run checks 1–11 via the SEO & AI Audit — the free ChatGPT SEO check for Shopify stores — on the same four URLs, and do check 12 manually with the ask buttons.
7. Record pass/fail in one sheet with the date and theme version.

Where the fixes live in Shopify

Most structured data lives in your theme code: Online Store → Themes → ⋯ → Edit code, then a snippet or section file with json or schema in the name. robots.txt is edited through a robots.txt.liquid template in the same editor. Store name and contact details come from Settings → Store details. Password protection is under Online Store → Preferences.

Worked example: a fashion store before a Black Friday push

Say a store plans to put ad budget behind /collections/winter-coats. The checklist run shows: check 2 fails (an SEO app added noindex to the collection during a test), check 6 passes on the hero coat, check 8 fails (the theme has no breadcrumbs), check 11 fails (no llms.txt). The noindex is a P0 and gets fixed the same afternoon in the app settings. Breadcrumbs go on the theme partner's list for next week. llms.txt is a 20-minute job for marketing. Ads start once check 2 is confirmed fixed in view-source — not once someone "thinks" it is.

How should I triage failed checks?

What are the most common mistakes?

• Checking in the theme editor preview instead of the live URL. Apps and customisations only show up live.
• Fixing one product and assuming all products are fixed. Templates differ; check a product on each template.
• Blocking every bot "for safety" and then wondering why AI tools describe the brand from third-party sites.
• Adding review markup when reviews are not shown on the page.

How often should I re-run it?

Quarterly for the full pass. Ad hoc after theme updates, SEO app changes, or a catalogue relaunch. If a check fails twice in a row for the same reason, the fix is not the checklist item — it is the process that keeps breaking it.

Checklists beat memory. Tape this one next to your launch runbook and refuse to scale spend on a URL that has not passed.

Frequently asked questions

Share: X LinkedIn Copy link

Ninety9 Team

We build 5 conversion apps used by Shopify merchants in Bulgaria and beyond. Everything we write here comes out of what we see in real store data.