Mixed signal. Agents can reach the page, but guess from there.

Reformation reads well to agents on the content and infrastructure layers, but craters on the two things that actually let an agent transact: the checkout is gated behind reCAPTCHA on every surface, and product attributes are locked in prose instead of structured markup. A 63 is the accurate verdict for a store that describes its products beautifully but treats an autonomous buyer as a threat.

Where the points went

The evidence

• reCAPTCHA everywhere (Check 4.2, 0/4): Providers detected on all 10 sampled product URLs, plus cart, checkout, and homepage. Two Eli Oversized Shirt pages stack both reCAPTCHA and hCaptcha. transaction_blocking: true.
• Zero structured attributes (Check 2.2, 0/6): Across 10 products, structuredHits: [] and labeledHits: [] on every URL. The composition data exists in copy ("50% Polyester, 45% Rayon and 5% Nylon") but nothing is exposed as spec markup or a labeled table.
• Checkout unreachable (Check 3.1, 2/6): Classifier could observe only one step, the empty bag state: "Your bag (0) Add some stuff to make your bag less empty. [CHECKOUT PAGE: unavailable]". Blind spot triggered on all three axes.
• No stated agent policy (Check 4.4, 0/2): Terms and privacy content returned nothing to classify. Agents defaulting to conservative behavior will assume automation is disallowed.
• No third-party trust anchors (Check 5.4, 0/2): Zero hits across Trustpilot, BBB, Yotpo, Bazaarvoice, and eight other platforms. aggregate_rating_hits: 0.

What already works

• Crawler posture is fully open (6/6): GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and Applebot-Extended all allowed in robots.txt.
• Product schema and pricing are clean (6/6 and 8/8): All 10 sampled URLs ship JSON-LD Product+Offer with prices in raw HTML.
• Content depth is elite (9/11 across dimension 6): High-signal specifications, conversational descriptions, and model measurements on 9 of 10 pages.

Fix first

1. Remove reCAPTCHA from product and cart surfaces, or whitelist declared agent user-agents (+4 points).
2. Emit product attributes as JSON-LD additionalProperty or a labeled spec table using the copy that already exists (+6 points).
3. Enable guest checkout and expose a linear, inspectable flow (+8 points combined across 3.1 and 3.2).

The single biggest lever is the CAPTCHA wall: the content and schema investment is already made, and it is being neutralized by a bot-detection posture that treats every agent as hostile.