Is shopify.com AI agent ready? C · 51/100
Why we think this is Shopify (1 signals)
- · cdn.shopify.com assets
7 failed out of 15 that apply to your site.
Fix automatically with AIScan
8 open checks (7 failing) can be handed to an AI agent: C1, B2, B3, P1, P4, M4, E2, E5. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://www.shopify.com/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://www.shopify.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwww.shopify.com%2F'Returns every check with its complete fix guide.
Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://www.shopify.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+8 pts if fixed
Markdown content negotiation
See full detailsServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- 02Fail+6 pts if fixed
Machine-readable pricing
See full detailsPublish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
- 03Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
# Shopify agent-readiness fixes Site: https://www.shopify.com/ Platform: shopify (50% confidence) AIScan score: 51/100 — Level 3 (Governed) Rubric: v2026.08.2 ## Failing checks - **[C1] Markdown content negotiation** — FAIL - Evidence: Accept: text/markdown → 200 (text/html; charset=utf-8) - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md. - **[M4] Machine-readable pricing** — FAIL - Evidence: no JSON-LD Offer found on /pricing or the homepage - Fix: Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose. - **[B2] Explicit AI bot rules** — FAIL - Evidence: 0 known AI agent(s) addressed in robots.txt - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc. - **[P1] API Catalog (RFC 9727)** — FAIL - Evidence: 404 at /.well-known/api-catalog - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions. - **[P4] OAuth discovery metadata** — FAIL - Evidence: auth-server: 404, protected-resource: 404 - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints. - **[B3] Web Bot Auth key directory** — PARTIAL - Evidence: HTTP 200 - Fix: Optional: serve a JWKS-style key directory at /.well-known/http-message-signatures-directory. - **[E2] Machine-readable API description** — FAIL - Evidence: no /openapi.json, /api/openapi.json or swagger document found - Fix: Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link. - **[E5] Content feed (RSS / Atom / JSON Feed)** — FAIL - Evidence: no RSS, Atom or JSON Feed found at the conventional paths - Fix: Publish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't. ## How to apply on Shopify - **robots.txt**: edit `templates/robots.txt.liquid` to add AI bot directives (Shopify allows full override). - **llms.txt**: create a page `/pages/llms-txt` and a redirect `/llms.txt → /pages/llms-txt` (Shopify URL redirects). Content should index collections + key product/policy pages. - **Markdown negotiation**: not natively supported — expose JSON-LD richly on PDPs (Product, Offer, AggregateRating) as the agent-readable surface. - **Commerce (UCP / x402)**: track Agentic Commerce Protocol support — currently Shopify-side; nothing for merchants to deploy yet beyond keeping Storefront API + checkout permissions clean. - **Bot rules**: respect Shopify's bot-management UI in Settings → Customer events / Security.
How this score is calculated
Every check earns points against a weight. We divide the points you earned by the points that actually apply to a Shopify — so checks that don't apply never drag you down.
Baseline every site should meet.
Strong signals most sites benefit from.
Emerging standards. Can only add points.
Not counted (5): B1, P2, P3, M1, M3 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.
Discoverability
100Can agents find your pages? robots, sitemaps, llms.txt.
Content
56Can agents read your content cleanly? Markdown, structured data.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C1
What we foundAccept: text/markdown → 200 (text/html; charset=utf-8)
How to fix itServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
Serve text/markdown on Accept negotiation
When a client sends
Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel.mdfiles (e.g./about→/about.md) and rewrite based on the Accept header.Test it
curl -H "Accept: text/markdown" https://yoursite.com/
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E5
What we foundno RSS, Atom or JSON Feed found at the conventional paths
Measured againstHow to fix itPublish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't.
Publish a feed
RSS, Atom, or JSON Feed — any of them gives agents a cheap, dated changelog of new content that a sitemap can't.
Declare it in <head>
<link rel="alternate" type="application/rss+xml" title="Blog" href="/feed.xml" />
Keep dates accurate
Each item needs a real publish date; that's the freshness signal agents actually use.
Bot Access
13Are AI crawlers explicitly allowed or blocked?
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found0 known AI agent(s) addressed in robots.txt
Measured againstHow to fix itAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
Fix with StoreSEO (recommended on Shopify)
StoreSEO handles AI readiness for Shopify stores. Three ways to use it:
- Shopify Sidekick — Open Sidekick in your Shopify admin and ask in plain language: "Fix my store's AI readiness." Sidekick pulls StoreSEO data and surfaces specific fixes you can approve in chat.
- Claude / any AI assistant via MCP — In StoreSEO go to Settings → AI Toolkit → Generate Token. In Claude open Settings → Connector → Add Custom Connector and paste the MCP URL
https://mcp.storeseo.com/mcp. Then prompt: "Fix AI readiness issues for my store." - Manual in StoreSEO — Shopify admin → StoreSEO → AI Toolkit for the guided flow.
Shopify-specific guidance
Edit your theme's
templates/robots.txt.liquidto add explicitAllowrules for GPTBot, ClaudeBot, PerplexityBot, and Google-Extended. Or ask Sidekick: "Allow AI crawlers in my robots.txt."Append this block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: /
Capabilities
0Can agents do things? APIs, auth, MCP, Agent Skills.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P1
What we found404 at /.well-known/api-catalog
Measured againstHow to fix itPublish /.well-known/api-catalog linking to your OpenAPI descriptions.
Publish an API catalog (RFC 9727)
# Add to your homepage HTTP response headers Link: </.well-known/api-catalog>; rel="api-catalog" # And serve a JSON document at /.well-known/api-catalog: { "links": [ { "href": "/openapi.json", "rel": "service-desc", "type": "application/openapi+json" } ] }Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P4
What we foundauth-server: 404, protected-resource: 404
Measured againstHow to fix itPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at
/.well-known/oauth-authorization-serverand/or RFC 9728 at/.well-known/oauth-protected-resource.Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E2
What we foundno /openapi.json, /api/openapi.json or swagger document found
Measured againstHow to fix itPublish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.
Publish an OpenAPI 3.1 description
Serve it at
/openapi.json(or/openapi.yaml). Describe every public endpoint, its parameters, and its response schema.Advertise it
Reference it from
/.well-known/api-catalogas aservice-desclink and from aLinkresponse header.Link: </openapi.json>; rel="service-desc"; type="application/json"
Content sites can skip this
If you expose no programmatic API, this check is informational and costs you nothing.
Commerce
0Can agents transact? Catalogs, checkout, agentic commerce.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · M4
What we foundno JSON-LD Offer found on /pricing or the homepage
Measured againstHow to fix itPublish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
Add Offer JSON-LD to your pricing page
One block per plan (or one AggregateOffer covering the range) so an agent can answer "what does this cost?" without reading prose.
Example
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "name": "Pro", "offers": { "@type": "Offer", "price": "12.00", "priceCurrency": "USD", "priceSpecification": { "@type": "UnitPriceSpecification", "price": "12.00", "priceCurrency": "USD", "billingDuration": 1, "billingIncrement": 1, "unitCode": "MON" }, "availability": "https://schema.org/InStock", "url": "https://example.com/pricing" } } </script>Keep it truthful
The structured price must match the price a human sees; agents will quote it.
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of www.shopify.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fwww.shopify.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (51/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=51&grade=C&host=www.shopify.com" alt="AIScan.site Grade C — 51/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fwww.shopify.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
Automate your AI-readiness
Plug AIScan into your agent stack or chat with it on the go.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.