Narrative
Everlane sits at 58/100 because the plumbing is right but the surface is empty: schema, prices, variants, and payment rails all check out, yet the product pages tell an agent nothing beyond a title and a price. The store is technically legible and commercially transactable, but it fails as a source of the decision-support content agents actually need to recommend it.
Where the points went
| Problem | Points lost | What an agent hits |
|---|---|---|
| Product pages carry no specs, description, or decision metadata | 11 | Agent cannot answer "is this silk machine washable" or "does it run small" |
| Checkout requires an initialized cart and hides guest path | 6 | Agent cannot simulate or complete purchase without a logged-in session |
| CAPTCHAs on cart and homepage | 4 | Automated add-to-cart trips reCAPTCHA/hCaptcha and dies |
| Inventory signals stop at binary in-stock text | 3 | Agent cannot promise ETA or shipping window to the shopper |
| No stated agent policy, no verifiable business address | 4 | Trust-scoring layers downrank the merchant by default |
The evidence
- Specification completeness (0/4) and conversational descriptions (0/2). Across 9 sampled PDPs, zero returned high signal and only the alpaca scarf reached medium. The classifier note on the 100% Human Crew is blunt: "no structured specifications such as material composition, dimensions, fit type, care instructions, size range."
- Checkout structure (2/6) and guest checkout (2/4). The checkout page could not be rendered without an initialized cart; the classifier saw "CONTINUE TO CHECKOUT" but "SIGN UP / LOG IN" was the only account path visible.
https://everlane.com/checkoutreturned 403 to the scanner. - CAPTCHA prevalence (0/4). Both reCAPTCHA and hCaptcha detected on the cart and homepage, with
transaction_blocking: true. This is the single most hostile signal to any agent that gets past the schema. - Inventory signals (2/5). All 9 URLs had schema availability or text availability but zero carried shipping data or ETA;
schemaHasShipping: falseon every product. - Stated agent policy (0/2) and merchant verifiability (1/3). Terms and privacy are "silent" on automated access, and the footer exposes a business name but no physical address or registration ID.
What already works
- Crawler posture is fully open: ChatGPT-User, Claude-User, PerplexityBot, OAI-SearchBot, and Amazonbot are all allowed in robots.txt, plus an
llms.txtis published. - Machine-readable commerce core: 9/9 PDPs carry Product + Offer JSON-LD, 9/9 expose price in raw HTML via schema, and 7/8 variant products enumerate SKUs (up to 15 variants on the gift card).
- Payment and cart rails: Shop Pay, PayPal, and Apple Pay are surfaced across product, cart, and homepage, and Shopify's
/cartendpoint is directly POST-able.
Fix first
- Ship structured spec blocks and 2 to 3 sentence descriptions on every PDP (+7 points across 6.1, 6.2, 6.3).
- Remove or scope reCAPTCHA/hCaptcha off the cart and homepage (+4 points on 4.2).
- Expose a guest checkout entry point before the login wall (+2 points on 3.2, with knock-on for 3.1).
The biggest opportunity is content: Everlane has built an agent-ready pipe and is pushing empty product pages through it.
ADiscoverability
Robots, sitemap, agent endpoints. strong.
BMachine Readability
Schema coverage, raw-HTML price, inventory, variants. mostly strong.
BTransactability
Checkout flow, guest, transparency, payment rails, cart API. mostly strong.
DAgent Posture
Bot detection, CAPTCHA, rate limiting, stated agent policy. patchy.
CTrust Signals
Return policy, merchant verifiability, price history, third-party anchors. partial.
EAgent-Native Content
Specs, descriptions, decision support, delivery, stability, absence of manipulation. broken.