# Legible report: Kestrel & Pine

- **Score:** 98/100, grade A (Agent-ready)
- **Store:** https://kestrelpine.example/
- **Product page:** https://kestrelpine.example/products/alpine-merino-hoodie
- **Platform:** Shopify (high confidence)
- **Scanned:** 2026-10-06 09:14 UTC (demo report, fictional store)
- **Online report:** https://legible.digitalage.studio/report/demo-kestrel-pine

## Pillars

| Pillar | Score | Weight | Pass | Warn | Fail |
| --- | --- | --- | --- | --- | --- |
| Access | 95 | 30% | 7 | 1 | 0 |
| Understanding | 100 | 30% | 7 | 0 | 0 |
| Trust | 100 | 20% | 4 | 0 | 0 |
| Transaction | 95 | 20% | 4 | 0 | 0 |

## Access (95/100)

### [WARN] Fast first byte

Slowest time to first byte: 690 ms. Aim for under 600 ms.

_Why it matters:_ User-triggered agents fetch pages while someone waits for an answer, with short timeouts. A slow server is a skipped store.

- /: 182 ms
- /products/alpine-merino-hoodie: 690 ms

**Fix:** Cache full HTML pages so they are served without hitting the application.

- Shopify serves HTML from its CDN. Slow TTFB usually means heavy Liquid loops or apps injecting server-side content: audit apps.

### [PASS] Homepage answers an agent

HTTP 200.

_Why it matters:_ Every agent starts with an HTTP request. Anything other than a fast 200 with HTML ends the visit before it begins.

- Status: 200
- Final URL: https://kestrelpine.example/
- Redirects: 0
- Content-Type: text/html; charset=utf-8

### [PASS] No bot wall in front of the store

Bots and browsers receive the same page.

_Why it matters:_ Bot-protection that challenges every non-browser client blocks AI agents even when robots.txt welcomes them. Agents cannot solve JavaScript challenges or CAPTCHAs.

- As LegibleBot: HTTP 200
- As a browser: HTTP 200
- Size difference: 0 KB

### [PASS] AI search and shopping agents are allowed

Every AI search and user-triggered agent may fetch the homepage and the product page.

_Why it matters:_ Search agents (OAI-SearchBot, Claude-SearchBot, PerplexityBot, Googlebot, Bingbot) build the indexes assistants search before recommending a product. User-triggered agents (ChatGPT-User, Claude-User, Perplexity-User) fetch your page while a shopper waits. Blocking either removes you from the answer.

- OAI-SearchBot (OpenAI): Allowed
- ChatGPT-User (OpenAI): Allowed
- Claude-SearchBot (Anthropic): Allowed
- Claude-User (Anthropic): Allowed
- PerplexityBot (Perplexity): Allowed
- Perplexity-User (Perplexity): Allowed
- Googlebot (Google): Allowed
- Bingbot (Microsoft): Allowed
- Amzn-SearchBot (Amazon): Allowed

### [PASS] robots.txt is valid

robots.txt parses cleanly: 3 groups, 1 sitemap.

_Why it matters:_ RFC 9309 says a robots.txt that errors with 5xx means "crawl nothing", and an HTML page served as robots.txt is noise. A clean file also points agents at your sitemap.

- Groups: 3
- Sitemap lines: 1
- Unrecognised lines: none

### [PASS] XML sitemap lists your products

Valid sitemap with 8 product URLs.

_Why it matters:_ Crawlers that build AI search indexes discover product URLs from sitemaps far more reliably than from links, especially on large catalogues.

- Location: https://kestrelpine.example/sitemap.xml
- Found via: robots.txt
- Type: Sitemap index (4 child sitemaps)
- Product sitemap: https://kestrelpine.example/sitemap_products_1.xml?from=1&to=99 (8 URLs)

### [PASS] Lean HTML

6 KB of HTML for /products/alpine-merino-hoodie.

_Why it matters:_ Agents download and tokenise your HTML. Megabytes of inline scripts and styles bury product facts and can hit size caps before the content.

- HTML size: 6 KB
- Inline script: 0 KB in 2 tags
- Visible words: 147

### [PASS] Pages are not marked noindex

No noindex directives on the pages scanned.

_Why it matters:_ A noindex meta tag or X-Robots-Tag header tells search agents to drop the page from their index, even when robots.txt allows crawling.

- Homepage: no directive
- Product page: no directive

### [INFO] Training crawler policy

5 training crawlers blocked, 3 allowed.

_Why it matters:_ Training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot and others) collect content for future models. Blocking them is a legitimate business choice and does not affect AI search visibility. Legible reports your stance but does not score it.

- GPTBot (OpenAI): Blocked
- ClaudeBot (Anthropic): Blocked
- Google-Extended (Google): Blocked
- Applebot-Extended (Apple): Allowed
- Amazonbot (Amazon): Allowed
- meta-externalagent (Meta): Allowed
- CCBot (Common Crawl): Blocked
- Bytespider (ByteDance): Blocked


## Understanding (100/100)

### [PASS] Product facts are in the raw HTML

Name, price and 147 words of content are in the server HTML.

_Why it matters:_ Most AI fetchers do not run JavaScript. If the name, price and description only appear after scripts run, the agent sees an empty page and moves on.

- Visible words (no JS): 147
- Product name in text: Yes
- Price in text: 129.00

### [PASS] Complete Product structured data

Product schema is 100% complete.

_Why it matters:_ Schema.org Product and Offer JSON-LD is the most reliable way for agents and shopping indexes to read price, currency, stock, identifiers, shipping and returns without guessing from layout.

- name: Alpine Merino Hoodie
- image: https://kestrelpine.example/cdn/shop/files/alpine-merino-hoodie-moss.jpg
- description: A 260 g/m² merino wool hoodie with a scuba hood, flatlock seams and thumb loops.
- offers.price: 129
- offers.priceCurrency: EUR
- offers.availability: https://schema.org/InStock
- sku: KP-AMH-MOSS-M
- gtin / mpn: 3856012345678
- brand: Kestrel & Pine
- shippingDetails: present
- hasMerchantReturnPolicy: present
- aggregateRating: present

### [PASS] Organization and WebSite schema

Organization and WebSite schema identify the store as "Kestrel & Pine".

_Why it matters:_ Organization and WebSite markup tells an agent the store's official name, logo, URL and social profiles, so it can tell your shop apart from resellers and lookalikes.

- Organization: Kestrel & Pine
- WebSite: Kestrel & Pine
- logo: present
- sameAs: present

### [PASS] OpenGraph product preview

Complete OpenGraph (og:type product).

_Why it matters:_ Chat interfaces render link previews and many agents fall back to OpenGraph when JSON-LD is missing. og:title, og:image and og:type are the minimum.

- og:title: Alpine Merino Hoodie
- og:description: 260 g/m² merino hoodie with scuba hood and thumb loops.
- og:image: https://kestrelpine.example/cdn/shop/files/alpine-merino-hoodie-moss.jpg
- og:url: https://kestrelpine.example/products/alpine-merino-hoodie
- og:type: product

### [PASS] Canonical URL and language

Canonical set, language en.

_Why it matters:_ A canonical URL collapses filter and tracking variants into one product, and a lang attribute tells the agent which language and market the price and policies apply to.

- canonical: https://kestrelpine.example/products/alpine-merino-hoodie
- html lang: en

### [PASS] One clear H1 with the product name

H1 "Alpine Merino Hoodie" with 3 H2 sections.

_Why it matters:_ Extractors use the heading outline to split a page into sections. One H1 naming the product, then H2s for details and reviews, makes the page easy to chunk.

- H1: Alpine Merino Hoodie
- H2: 3

### [PASS] llms.txt guide for agents

Valid llms.txt with 3 sections and 7 links.

_Why it matters:_ llms.txt is a proposed markdown index of a site's most useful pages. No major assistant has confirmed it uses the file, so it carries little weight here, but it is cheap and gives agents a clean map of products and policies.

- Title: Kestrel & Pine
- Summary blockquote: present
- Sections: Products, Policies, Optional
- Links: 7
- llms-full.txt: not found


## Trust (100/100)

### [PASS] HTTPS everywhere, with HSTS

HTTPS with HSTS, and HTTP redirects to HTTPS.

_Why it matters:_ Agents that hand a shopper off to checkout will not send them to an insecure page. HSTS proves the store never falls back to plain HTTP.

- Final URL scheme: https
- http:// redirects to https: yes (301)
- Strict-Transport-Security: max-age=31536000; includeSubDomains

### [PASS] Policy pages are linked

Shipping, returns, privacy, terms and contact pages are all linked.

_Why it matters:_ Before recommending a purchase, assistants look for shipping costs, the return window and who to contact. In the EU, consumers have a 14-day right of withdrawal for most online purchases (Directive 2011/83/EU, Art. 9), so returns terms are a deciding fact.

- Shipping: https://kestrelpine.example/policies/shipping-policy
- Returns: https://kestrelpine.example/policies/refund-policy
- Privacy: https://kestrelpine.example/policies/privacy-policy
- Terms: https://kestrelpine.example/policies/terms-of-service
- Contact: https://kestrelpine.example/pages/contact

### [PASS] Business identity is machine-readable

Legal identity, address and contact details are all machine-readable.

_Why it matters:_ Agents weigh whether a merchant is real. A legal name, postal address and a contact point in Organization schema are the strongest signals short of a marketplace listing.

- address: present
- email / telephone / contactPoint: present
- legalName / vatID: present

### [PASS] Visible price matches structured data

The visible price and JSON-LD agree on EUR 129.00.

_Why it matters:_ When the price a shopper sees differs from the price in JSON-LD, agents quote the wrong number or distrust both. Google Merchant Center suspends listings for mismatches, and under EU consumer law the price shown must be the price charged.

- JSON-LD price: EUR 129.00
- Current prices on page: 129.00
- Microdata price: none


## Transaction (95/100)

### [PASS] UCP business profile

Valid UCP profile (2026-08-25) with checkout. 1 suggestion.

_Why it matters:_ The Universal Commerce Protocol (UCP), announced by Google in January 2026, lets agents discover a store's capabilities from /.well-known/ucp and complete checkout through a standard API. It powers buying in Google AI Mode and Gemini. Current spec version: 2026-08-25.

- ucp.version: 2026-08-25
- Services: dev.ucp.shopping
- Transports: rest, mcp
- Capabilities: Checkout, Cart, Fulfillment (extension), Orders
- Payment handlers: declared
- Signing keys: none
- $.keys: No signing keys published. Recommended so agents can verify signed responses.

### [PASS] Machine-readable catalogue

2 catalogue signals detected.

_Why it matters:_ Agent channels (ChatGPT shopping, Google AI Mode, Copilot) prefer a structured product feed they can refresh over crawling pages. A feed keeps price and stock current between crawls.

- Signal: Shopify catalogue (syncable to agent channels through Agentic Storefronts)
- Signal: Product sitemap (8 URLs)

### [PASS] Agentic Commerce Protocol readiness (signal)

All ACP prerequisites are in place. Enrolment itself happens with OpenAI and cannot be detected from outside.

_Why it matters:_ OpenAI and Stripe's Agentic Commerce Protocol (ACP) launched in September 2025 to let shoppers buy inside ChatGPT. There is no public discovery file: merchants are onboarded through OpenAI and submit a product feed. In March 2026 OpenAI moved checkout back to merchants' own sites, so discovery in ChatGPT now depends on that feed and on crawlable pages. Legible scores the prerequisites, not enrolment.

- OAI-SearchBot allowed: yes
- Product structured data: yes
- Feed source available: yes

### [PASS] Add-to-cart works without scripts

The product page has a server-rendered add-to-cart form or link.

_Why it matters:_ Browser-driving agents (ChatGPT agent, Gemini in Chrome and similar) click through your real checkout. A plain form or link for add-to-cart in the server HTML is the most robust path when no protocol is available.

- Cart form in HTML: yes
- Add-to-cart link: no
- Add-to-cart button: yes

### [INFO] Platform and remediation path

Detected Shopify (high confidence).

_Why it matters:_ What you can fix, and how fast, depends on the platform. Shopify merchants can switch most of this on; WooCommerce, Magento and custom stores need it built or configured.

- Signal: cdn.shopify.com assets
- Signal: Shopify global object
- Signal: x-shopid / powered-by Shopify header

## What an agent extracts

From https://kestrelpine.example/products/alpine-merino-hoodie, about 199 tokens from 6 KB of HTML.

| Fact | Found | Source |
| --- | --- | --- |
| Product name | Alpine Merino Hoodie | both |
| Price | EUR 129.00 | both |
| Availability | InStock | both |
| Brand | Kestrel & Pine | json-ld |
| GTIN / EAN | 3856012345678 | json-ld |
| Shipping | Declared in JSON-LD | both |
| Returns | Declared in JSON-LD | both |
| Rating | Declared in JSON-LD | both |

## Requests made

- 200 https://kestrelpine.example/ (Homepage (as LegibleBot), 202 ms)
- 200 https://kestrelpine.example/ (Homepage (as a browser, for bot-wall comparison), 202 ms)
- 200 https://kestrelpine.example/robots.txt (robots.txt, 84 ms)
- 301 http://kestrelpine.example/ (HTTP to HTTPS redirect probe, 50 ms)
- 200 https://kestrelpine.example/llms.txt (llms.txt, 90 ms)
- 404 https://kestrelpine.example/llms-full.txt (llms-full.txt, 130 ms)
- 200 https://kestrelpine.example/.well-known/ucp (UCP business profile, 108 ms)
- 200 https://kestrelpine.example/sitemap.xml (XML sitemap, 140 ms)
- 200 https://kestrelpine.example/sitemap_products_1.xml?from=1&to=99 (Product sitemap, 160 ms)
- 200 https://kestrelpine.example/products/alpine-merino-hoodie (Product page (as LegibleBot), 710 ms)

Evaluated against UCP 2026-08-25 and the agent list of 2026-10-07. Agent categories: Training crawler, Search / index, User-triggered.

---
Generated by Legible, a Digital Age product (https://digitalage.studio/en/).
