Why we think this is Shopify (2 signals)
- · cdn.shopify.com assets
- · /cdn/shop/ assets
2 failed · 3 partial out of 9 that apply to your site.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- 02Partial+4 pts if fixed
Markdown content negotiation
See full detailsServe text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.
- 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://pagefly.io/ Platform: shopify (80% confidence) AIScan score: 68/100 — Level 3 (Governed) Rubric: v2026-06-08.1 ## Failing checks - **[C1] Markdown content negotiation** — PARTIAL - Evidence: Accept: text/markdown → 200 (text/markdown; charset=utf-8) - Fix: Serve text/markdown when the client sends Accept: text/markdown, or expose /path/index.md. - **[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. - **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL - Evidence: h1: 1, title: true, meta description: true, JSON-LD: false - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD. - **[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, <https://cdn.amplitude.com>; rel="preconnect", <https://code.jquery.com>; rel="preconnect", <http - Fix: Add a Link header with rel="api-catalog" or rel="describedby". ## 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.
Discoverability
85Can agents find your pages? robots, sitemaps, llms.txt.
Content
72Can 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
How to fix itAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
1.⚡ Fix automatically with AIScanThe fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.Add explicit User-agent blocksDon't rely on `User-agent: *` alone. Address each major AI crawler so your policy is unambiguous.
3.Recommended blockUser-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
4.VerifyAfter deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Capabilities
50Can 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
How to fix itPublish /.well-known/api-catalog linking to your OpenAPI descriptions.
1.⚡ Fix automatically with AIScanThe fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.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" } ] }3.VerifyAfter deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Commerce
100Can agents transact? Catalogs, checkout, agentic commerce.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of pagefly.io on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fpagefly.io%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=pagefly.io" alt="AIScan.site Grade B — 68/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fpagefly.io%2F)
Track this over time
Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.
Scan your site