2026-05-25 22:48 UTC · ready · vertical: product · schema score: 40/100

Can IA help — https://www.retailmenot.com/view/sephora.com?

Maybe — limited lift

Maybe limited lift here — your page is already reachable and your commerce is legible. We'd look at competitive positioning and citation share rather than basic legibility.

Are AI bots reaching you? AI search bots can reach your content — you're eligible to be cited.

Are your links coming through? Your commerce links are legible to AI crawlers.

Implementation friction: Low — you're on Cloudflare, so IA deploys via an edge connector with no changes to your site.

Next step:Introduce us to your SEO / dev teamBook a 20-min intro call

Summary

The page displays ten discount and promotional offers for Sephora (percentage discounts ranging 4–50%, free gifts, and cashback) with three call-to-action types (Show Code, Get Deal, Get Reward) linked to a single merchant URL. The schema layer includes Offer entities but lacks Product, AggregateOffer, BuyAction, and Review types—critical absences for a product vertical where offer-to-product binding and purchase-intent signals are foundational. Citation bots can reach the page and one explicit mention was cited by URL; training crawlers face partial blocking that reflects publisher edge policy rather than a reachability gap for AI search. Adding Product entities and BuyAction wrappers would make the transactional intent and product scope of each offer explicit at the semantic layer, allowing downstream systems to infer which products qualify for each promotion without inferring from promotional text alone.

Citation bots reachable — oai_searchbot, claude_searchbot

This URL is reachable by the AI search indexes that drive live citations. Enrichment (next panel) is applicable here.

What humans see vs what AI extracts today vs with IA enrichment

The gap between these columns is the enrichment IA layers on top of the page for AI extractors. Edge-level blocking is a separate dimension — see the bot-accessibility section.

Human view

AI Bot Today — During Live Search

On the page

Brand

Sephora

Offers detected (10)

20% Off Sitewide — 20%
4% Cash Back For Purchases Sitewide — 4%
Up To An Extra 20% Off Sitewide — 20%
Free Gift With $40 Purchase — FREE
Free Skincare Sample Set With $45+ Order — FREE
Free Shipping On Sitewide Orders Over $50 — FREE
+ 4 more

CTAs (3)

Show Code · Get Deal · Get Reward

Outbound merchant URLs (1)

sephora.com

In the JSON-LD layer

Types present (15)

AggregateRating, Answer, BreadcrumbList, FAQPage, ImageObject, ListItem, Offer, Organization, Person, PostalAddress, Question, SiteNavigationElement, Store, Thing, WebPage

Commerce types present

Offer, AggregateRating

Commerce types missing

Product, AggregateOffer, BuyAction, Review

The gap

Offers visible to humans10

Offers in machine-readable form10

Click-throughs wrapped as BuyAction0 of 1

AI bot — with IA enrichment

IA enrichment adds (derived from existing page content)

+ 1 Product entity (Sephora)
+ 1 BuyAction nodes wrapping existing outbound link
+ 1 ItemList grouping the offers

Result for AI extractors

A bot fetching the URL pulls all 10 offers from JSON-LD in microseconds — no LLM inference, no prose parsing, no guessing at which discount applies.

View IA-rendered flattened HTML

20% Off Sephora Promo Codes, Coupons + 4% Cash Back — Retailmenot

View IA-generated JSON-LD @graph

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "NewsArticle",
      "headline": "20% Off Sephora Promo Codes, Coupons + 4% Cash Back",
      "url": "https://www.retailmenot.com/view/sephora.com",
      "publisher": {
        "@type": "Organization",
        "name": "Retailmenot"
      }
    }
  ]
}
</script>

Surface — do AI models cite this publisher?

Each model is queried twice — with web search off (training memory) and on (live fetch). The diff shows whether your AI presence is stale, current, or absent.

Bot accessibility

Edge / CDN: cloudflare· cf-ray header · server: cloudflare

Search / index crawlers

2 of 2 accessible to scanner

Build the search index AI assistants query when answering. Allowing these is what makes a publisher AI-citation-eligible.

oai_searchbot200

claude_searchbot200

User-initiated fetchers

3 of 3 accessible to scanner

Fetch a specific page when a user shares it in chat. Allowing these lets users reference your content in AI conversations.

chatgpt_user200

claude_user200

perplexity_user200

Training-data crawlers

4 of 6 accessible to scanner

Build training datasets. Blocking these is the lawsuit-safe posture — does not affect AI citation eligibility.

2 declared allowed in robots.txt — scanner observed 4xx. We can’t verify what real bots see from outside; the publisher edge logs are ground truth.

gptbot200

claudebot200

perplexitybot200

ccbot200

google_extended403