Everlane

Agent access

Infrastructure

Data signals

• JSON-LDDetected
• Schema.org ProductNot detected
• Open GraphYes
• Product feedYes
• llms.txtYes

1. Apr 6, 2026
   Google-Extended robots.txtno_rule→allowed

   CCBot robots.txtno_rule→allowed

   Amazonbot robots.txtno_rule→allowed

   robots.txt presencefalse→true

   ClaudeBot robots.txtno_rule→allowed

   Claude-Web robots.txtno_rule→allowed

   PerplexityBot robots.txtno_rule→allowed

   ChatGPT-User robots.txtno_rule→allowed

   GPTBot robots.txtno_rule→allowed
2. Apr 5, 2026
   PerplexityBot robots.txtallowed→no_rule

   Google-Extended robots.txtallowed→no_rule

   CCBot robots.txtallowed→no_rule

   Amazonbot robots.txtallowed→no_rule

   robots.txt presencetrue→false

   Claude-Web robots.txtallowed→no_rule

   ChatGPT-User robots.txtallowed→no_rule

   ClaudeBot robots.txtallowed→no_rule

   GPTBot robots.txtallowed→no_rule
3. Mar 30, 2026
   Google-Extended robots.txtno_rule→allowed

   CCBot robots.txtno_rule→allowed

   Amazonbot robots.txtno_rule→allowed

   robots.txt presencefalse→true

   ChatGPT-User robots.txtno_rule→allowed

   ClaudeBot robots.txtno_rule→allowed

   Claude-Web robots.txtno_rule→allowed

   PerplexityBot robots.txtno_rule→allowed

   GPTBot robots.txtno_rule→allowed
4. Mar 28, 2026
   Google-Extended accessallowed→no_rule

   CCBot accessallowed→no_rule

   Amazonbot accessallowed→no_rule

   ucptrue→false

   GPTBot accessallowed→no_rule

   ChatGPT-User accessallowed→no_rule

   ClaudeBot accessallowed→no_rule

   Claude-Web accessallowed→no_rule

   PerplexityBot accessallowed→no_rule

   json_ldtrue→false

   open_graphtrue→false

   cdncloudflare→unknown

   platformmagento→custom

The free public window is 90 days. Multi-year history, watchlists, and change alerts are part of Pro.

Fix it with Claude Code

Each failed check below has a ready-made prompt tailored to this scan's findings. Run it in Claude Code from your site's repository.

My e-commerce site is everlane.com. A scan found JSON-LD on the site but no Schema.org Product markup, so AI shopping agents can't reliably read our product names, prices, availability, or images. The site runs on magento, so prefer that platform's idiomatic way of serving these files/markup (theme templates, app settings, or metafields) over hand-rolled middleware where it exists.

In this repository:

1. Find the product page template/component and add a JSON-LD <script type="application/ld+json"> block with Schema.org Product markup: name, description, image, sku, brand, and an Offer with price, priceCurrency, availability (use schema.org/InStock | OutOfStock), and url. Populate every field from our real product data — no placeholders.
2. Add an Organization JSON-LD block to the base layout (name, url, logo) if missing.
3. If we have category/listing pages, add ItemList markup referencing the product URLs.
4. Show me one fully rendered example of the JSON-LD for a real product, then validate the shape against Google's Rich Results requirements for Product and fix any warnings you can detect statically.

Verify after deploy with https://search.google.com/test/rich-results on a product URL.

Embed this score

HTML

<a href="https://www.arcreport.ai/brand/everlane"><img src="https://www.arcreport.ai/badge/everlane.svg" alt="ARC Score for Everlane" height="22"></a>

Markdown

[![ARC Score for Everlane](https://www.arcreport.ai/badge/everlane.svg)](https://www.arcreport.ai/brand/everlane)

Updates automatically with each daily scan.