Is bigshot.fashion AI agent ready? B · 68/100
Why we think this is Shopify (4 signals)
- · cdn.shopify.com assets
- · /cdn/shop/ assets
- · window.Shopify global
- · Shopify.theme
Scan history · 2 public scans of bigshot.fashion
4 failed · 1 partial out of 14 that apply to your site.
Fix automatically with AIScan
5 open checks (4 failing) can be handed to an AI agent: D3, B2, P1, M4, E2. 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://bigshot.fashion/”.
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://bigshot.fashion/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fbigshot.fashion%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://bigshot.fashion/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+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.
- 02Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- 03Fail+4 pts if fixed
API Catalog (RFC 9727)
See full detailsPublish /.well-known/api-catalog linking to your OpenAPI descriptions.
# Shopify agent-readiness fixes Site: https://bigshot.fashion/ Platform: shopify (99% confidence) AIScan score: 68/100 — Level 3 (Governed) Rubric: v2026.08.2 ## Failing checks - **[M4] Machine-readable pricing** — FAIL - Evidence: no pricing page found and no JSON-LD Offer on 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. - **[D3] Link header for discovery** — PARTIAL - Evidence: Link: <https://cdn.shopify.com>; rel="preconnect", <https://cdn.shopify.com>; rel="preconnect"; crossorigin, <//bigshot.fashion/cdn/shop/t/2/assets/base.css?v=169326838600611368151787519959>; as="style"; re - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag. - **[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. ## 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 (6): B1, B3, P2, P3, M3, E5 — 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
90Can agents find your pages? robots, sitemaps, llms.txt.
Content
100Can agents read your content cleanly? Markdown, structured data.
Bot Access
0Are 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
36Can 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 · 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
45Can 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 pricing page found and no JSON-LD Offer on 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.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of bigshot.fashion on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fbigshot.fashion%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (68/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=68&grade=B&host=bigshot.fashion" alt="AIScan.site Grade B — 68/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fbigshot.fashion%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
bigshot.fashion is built on Shopify. AI-agent readiness for Shopify walks through the same checks on that platform.
This page always shows the most recent public scan for bigshot.fashion.