Is dresslyn.shop AI agent ready? F · 28/100

# Shopify agent-readiness fixes

Site: https://dresslyn.shop/
Platform: shopify (50% confidence)
AIScan score: 28/100 — Level 1 (Discoverable)
Rubric: v2026.08.2

## Failing checks
- **[C1] Markdown content negotiation** — PARTIAL
  - Evidence: Accept: text/markdown → 404 (text/markdown; charset=utf-8)
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- **[D1] robots.txt present & sane** — PARTIAL
  - Evidence: 200 OK, 70 bytes
  - Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[C2] /llms.txt** — PARTIAL
  - Evidence: 200 OK, 106 bytes, has H1
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[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.
- **[D2] XML sitemap** — FAIL
  - Evidence: no /sitemap.xml or /sitemap_index.xml resolved
  - Fix: Publish /sitemap.xml and reference it in robots.txt.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 2, title: true, meta description: false, JSON-LD: false
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[P1] API Catalog (RFC 9727)** — FAIL
  - Evidence: 402 at /.well-known/api-catalog
  - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: 402, protected-resource: 402
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[E1] Correct 404 handling** — PARTIAL
  - Evidence: GET /aiscan-404-probe-d64dhf → HTTP 402, 10026 bytes, text/html
  - Fix: Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
- **[E3] Heading hierarchy & server-rendered text** — PARTIAL
  - Evidence: 44 words of server-rendered text, 1 <h2>, 0 <h3>
  - Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link header or <link> tag
  - 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.