Shopify
Make a Shopify store agent-ready: robots.txt.liquid, product feeds, and AI bot rules.
Shopify is one of the friendliest platforms AIScan grades — much of the work is already done by the platform itself. On a Shopify scan, Commerce gets a 1.2× weight and Content drops to 0.6× (Shopify limits how much HTML you can rewrite, so the scanner doesn't punish you for it).
Browse the platform guide index for other stacks, or compare Shopify's built-in commerce signals with the WordPress guide. The steps below connect directly to Discoverability, Bot Access, Content, Capabilities, and Commerce checks.
Fix with StoreSEO (recommended)
StoreSEO handles AI readiness for Shopify stores end-to-end. 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. See the Sidekick guide.
- Claude or 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." Setup steps: connect StoreSEO MCP. - Manual in StoreSEO — Shopify admin → StoreSEO → AI Toolkit for the guided flow. Reference: AI Toolkit overview.
robots.txt.liquid (D1)
Shopify manages robots.txt via the templates/robots.txt.liquid template in your theme. StoreSEO can optimize it for you — or ask Sidekick: "Update my robots.txt to allow AI crawlers." If you prefer editing the template directly:
{% for group in robots.default_groups %}
{{- group.user_agent -}}
{% for rule in group.rules -%}
{{ rule }}
{% endfor -%}
{% if group.sitemap != blank %}
{{ group.sitemap }}
{% endif %}
{% endfor %}
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /Sitemap (D2)
Shopify auto-generates /sitemap.xml, so D2 should already pass. Submit it to Google Search Console. StoreSEO improves sitemap quality by keeping product, collection, and page entries clean.
Structured product data (C3)
StoreSEO automatically adds Product, Organization, and BreadcrumbList JSON-LD schema. Enable it in StoreSEO → Schema → Enable for products and collections. If you'd rather hand-roll it, add a script to sections/product.liquid:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": {{ product.title | json }},
"image": {{ product.featured_image | image_url: width: 1200 | json }},
"description": {{ product.description | strip_html | json }},
"sku": {{ product.selected_or_first_available_variant.sku | json }},
"offers": {
"@type": "Offer",
"price": "{{ product.price | money_without_currency }}",
"priceCurrency": {{ cart.currency.iso_code | json }},
"availability": "{% if product.available %}https://schema.org/InStock{% else %}https://schema.org/OutOfStock{% endif %}"
}
}
</script>AI bot rules (B2)
Edit templates/robots.txt.liquid to add explicit Allow rules for GPTBot, ClaudeBot, PerplexityBot, and Google-Extended (see the block above). Or ask Sidekick: "Allow AI crawlers in my robots.txt."
MCP server (P2)
StoreSEO already exposes an MCP server at https://mcp.storeseo.com/mcp. Connect it to Claude via Settings → Connector → Add Custom Connector to give AI agents full access to your store's SEO data — they can read scores, identify missing meta titles or alt text, and apply fixes from plain-language prompts.
Agent Skills / AI Toolkit (P3)
Use StoreSEO's AI Toolkit (Shopify admin → StoreSEO → Settings → AI Toolkit) to generate API tokens for Claude Code, Cursor, or VS Code. Each token lets the AI agent act against your store with scoped permissions. Sample prompts: "SEO optimize all my least scoring products", "Generate alt text for all product images", "Fix meta descriptions for all products."
Further reading
- Content Signals in robots.txt: 117 of 799 Sites Declare One
Of 799 sites in our scan database on 2 November 2026, 117 serve a robots.txt with a ContentSignal line 14.6%. Among the 677 sites that serve a usable robots.txt at all, that is 17.3%. Another 682…
- Does robots.txt Need a Sitemap Line? 782 Sites Show What Happens
Of 782 sites in our scan database on 29 October 2026, 572 serve a robots.txt that declares a sitemap, 89 serve a robots.txt with no Sitemap line, and 121 fail the robots.txt check outright. Declaring…
- JSON-LD in Google Tag Manager is missing from your served HTML: test it and move it server-side
If your JSONLD is added by a Google Tag Manager Custom HTML tag, a plain HTTP fetch of your page contains zero schema blocks. Google can still read it, because Googlebot renders JavaScript. Crawlers…
- How Big Is an llms.txt? Size and Structure Across 779 Real Sites
Of the 779 sites in our scan database on 28 October 2026, 427 served an /llms.txt file that returned a 200, and the typical file that passes our check is small: a median of 4,403 bytes, with 80% of…
- llms.txt on Astro, Docusaurus, Framer, Ghost, Hugo, Next.js, Replit, Shopify, Squarespace, Webflow and Wix
Updated on 26 October 2026. Every platform section was checked on the dates shown inside it. Squarespace, Webflow and Wix joined this guide on 26 October 2026, so all eleven platforms that had their…
- AI readiness setup guide by platform (2026)
Verified 17, 18, 20 and 22 October 2026. Updated on 22 October 2026. An AIready site needs six things: a robots.txt that names AI crawlers D1, B2, a sitemap D2, a declared feed E5, an llms.txt C2,…
- Platform League Table: WordPress, Next.js, Astro and Shopify Across 728 Sites
Every few weeks someone asks which platform produces the most agentready sites. WordPress, Next.js, Astro and Shopify all have fans, and a ranked table is the answer people expect. We have the data…
- Declare your content-use policy to AI: Content Signals, ai.txt, TDMRep
Blocking or allowing a crawler answers one question: may it fetch this page. It says nothing about what the crawler may do afterwards. This guide covers the three places a site can state that second…