All case studies →
Intelligent Attribution
← All scans

https://www.retailmenot.com/view/reebok.com

2026-06-01 16:22 UTC · ready · vertical: product · schema score: 40/100
Can IA help — https://www.retailmenot.com/view/reebok.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 promotional offers for Reebok sitewide discounts and cashback, each with accompanying CTAs (Show Code, Get Reward, Get Deal) and a single outbound link to reebok.com. The structured data layer includes Offer and AggregateRating schemas but omits Product, AggregateOffer, BuyAction, and Review types—critical gaps for a product vertical where conversion intent is explicit. Citation-capable bots reach the page without restriction, though training crawlers block 3 of 5 sources on a lawsuit-posture basis that does not affect search citation; probe results confirm explicit URL citation in 1 of 2 cases. IA enrichment would surface the Reebok brand and discount intent as discrete Product entities and wrap the offer-to-redemption pathway in BuyAction markup, making the transactional signal legible to systems that infer merchant eligibility from structured commerce semantics rather than coupon page 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
Page screenshot
AI Bot Today — During Live Search
On the page
Brand
Reebok
Offers detected (10)
  • Up To $30 Off Sitewide$30
  • 8% Cash Back For Purchases Sitewide8%
  • 45% Off Sitewide + 50% Off Sale50%
  • 40% Off Sitewide40%
  • Mothers Day Sale! 40% Off Sitewide40%
  • Exclusive! 60% Off Sale Items60%
  • + 4 more
CTAs (3)
Show Code · Get Reward · Get Deal
Outbound merchant URLs (1)
reebok.com
In the JSON-LD layer
Types present (14)
AggregateRating, Answer, BreadcrumbList, FAQPage, ImageObject, ListItem, Offer, Organization, Person, PostalAddress, Question, 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 (Reebok)
  • + 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

40% Off Reebok Promo Code, Coupons + 8% Cash Back — Retailmenot

View IA-generated JSON-LD @graph
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "NewsArticle",
      "headline": "40% Off Reebok Promo Code, Coupons + 8% Cash Back",
      "url": "https://www.retailmenot.com/view/reebok.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
robots.txt: allowed · scanner: blocked
applebot_extended403
robots.txt: allowed · scanner: blocked
Traditional search engines
0 of 3 accessible to scanner
Bingbot, Googlebot, Applebot — not AI-specific.
3 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.
bingbot403
robots.txt: allowed · scanner: blocked
googlebot403
robots.txt: allowed · scanner: blocked
applebot403
robots.txt: allowed · scanner: blocked
Raw fetch detail (status, bytes, timing)
IdentityStatusBytesBlocked?Timing
gptbot200701,355no1056ms
chatgpt_user200701,355no1024ms
oai_searchbot200701,355no936ms
claudebot200701,355no1005ms
claude_user200703,331no651ms
claude_searchbot200701,355no796ms
perplexitybot200701,355no1068ms
perplexity_user200703,331no582ms
googlebot4035,758yes489ms
google_extended4035,587yes277ms
bingbot4035,651yes374ms
applebot4035,651yes297ms
applebot_extended4035,608yes389ms
ccbot200701,355no537ms
human4035,779yes185ms
robots.txt policy per AI bot
CCBot: allowed
GPTBot: allowed
Bingbot: allowed
Applebot: allowed
ClaudeBot: allowed
Googlebot: allowed
Claude-User: allowed
ChatGPT-User: allowed
OAI-SearchBot: allowed
PerplexityBot: allowed
Google-Extended: allowed
Perplexity-User: allowed
Claude-SearchBot: allowed
Applebot-Extended: allowed

Render risk — what AI bots can actually parse

100/100
Low — AI bots receive most of the text content
FrameworkUnknown / vanillaHydration gap0%
No render-risk signals triggered. AI bots receive substantially the same content as humans.
What AI bots are missing
Sample content only humans see:
  • Performing security verification
  • This website uses a security service to protect against malicious bots. This page is displayed while the website verifies you are not a bot.
  • Verification successful. Waiting for www.retailmenot.com to respond

Schema audit

40/100
Present · 14
AggregateRatingAnswerBreadcrumbListFAQPageImageObjectListItemOfferOrganizationPersonPostalAddressQuestionStoreThingWebPage
Missing · 3
ProductReviewBuyAction
Rubric breakdown (2 of 5 criteria met)
Offer25 pts
AggregateRating15 pts
Review0 pts
Product0 pts
BuyAction0 pts

potentialAction — commerce paths

⚠ No commerce-action schema present — AI has no canonical path back to this publisher.
Present · 0
(none)
Missing · 1
BuyAction

Affiliate footprint

No affiliate links detected in the page's raw HTML.