Can IA help — https://www.nytimes.com/athletic/7308133/2026/05/26/victor-wembanyama-rookie-card-sells-for-record-5-11-million/?
Yes — with some work
Yes — with some work. First we'd open up AI bot access (a policy/edge change on your side), then layer in the commerce signals that earn citations and clicks.
⛔Are AI bots reaching you? AI search bots are blocked (gptbot, chatgpt_user, oai_searchbot, claudebot) — you can't be cited in AI answers at all right now.
✅Are your links coming through? Your commerce links are legible to AI crawlers.
🔌Implementation friction: Low — you're on Fastly, 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 is a New York Times sports article reporting on the sale of a Victor Wembanyama rookie card for $5.11 million, with a single outbound link to eBay but no product listings or price information embedded in the article itself. The structured-data layer includes NewsArticle and SportsTeam schemas but omits all commerce-related types—Product, Offer, BuyAction, and Review schemas are absent, leaving the transactional event undeclared to machines. Search-index citation bots cannot reach the page, and probe results show zero explicit or generic citations across both attempts, though some training crawlers have access (a legal-posture matter independent of citation capability). IA's enrichment layer would wrap the sale event and eBay reference in a BuyAction schema, making the transactional intent and merchant link machine-readable without altering the publisher's article structure or access controls.
Citation bots blocked at publisher edge
Publisher bot policy blocks the AI search indexes. IA enrichment requires the publisher to allow these bots first. See bot accessibility for detail.
Blocked: oai_searchbot 403 · claude_searchbot 403
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
Citation bots cannot reach this URL
oai_searchbot 403 · claude_searchbot 403
This reflects the publisher's bot-management policy at their CDN/WAF. IA does not control publisher edge policy and does not unblock crawlers. Enrichment only applies once the publisher allows AI search bots.
AI bot — with IA enrichment
IA enrichment requires citation bots to reach the page first. Not applicable on this URL until publisher policy allows AI search bots.
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.
Build the search index AI assistants query when answering. Allowing these is what makes a publisher AI-citation-eligible.
oai_searchbot403
claude_searchbot403
User-initiated fetchers
0 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_user403
claude_user403
perplexity_user403
Training-data crawlers
2 of 6 accessible to scanner
Build training datasets. Blocking these is the lawsuit-safe posture — does not affect AI citation eligibility.
gptbot403
claudebot403
perplexitybot403
ccbot403
google_extended200
applebot_extended200
Traditional search engines
3 of 3 accessible to scanner
Bingbot, Googlebot, Applebot — not AI-specific.
bingbot200
googlebot200
applebot200
Raw fetch detail (status, bytes, timing)
Identity
Status
Bytes
Blocked?
Timing
gptbot
403
139,269
yes
1023ms
chatgpt_user
403
139,269
yes
969ms
oai_searchbot
403
139,269
yes
900ms
claudebot
403
139,269
yes
761ms
claude_user
403
139,269
yes
697ms
claude_searchbot
403
139,269
yes
642ms
perplexitybot
403
139,269
yes
568ms
perplexity_user
403
139,269
yes
518ms
googlebot
200
269,071
no
470ms
google_extended
200
269,071
no
431ms
bingbot
200
269,071
no
425ms
applebot
200
269,071
no
257ms
applebot_extended
200
269,071
no
238ms
ccbot
403
139,269
yes
815ms
human
200
269,071
no
261ms
robots.txt policy per AI bot
CCBot: disallowed
GPTBot: disallowed
Bingbot: allowed
Applebot: allowed
ClaudeBot: disallowed
Googlebot: allowed
Claude-User: disallowed
ChatGPT-User: disallowed
OAI-SearchBot: disallowed
PerplexityBot: disallowed
Google-Extended: disallowed
Perplexity-User: disallowed
Claude-SearchBot: disallowed
Applebot-Extended: disallowed
Render risk — what AI bots can actually parse
49/100
High — AI bots see scaffolding, not content
FrameworkUnknown / vanillaHydration gap94%
Hydration gap: 94%
AI bots see 6% of the rendered content. The remaining 94% loads via client-side JavaScript and is invisible to crawlers that don't execute JS.
What AI bots are missing
226
links missing
rendered 248 · bot 22
81
images missing
rendered 81 · bot 0
47
paragraphs missing
rendered 48 · bot 1
2
headings missing
rendered 4 · bot 2
1
JSON-LD blocks missing
rendered 1 · bot 0
Sample content only humans see:
“Sports Memorabilia and Collectibles”
“Victor Wembanyama rookie card sells for record $5.11 million”
“Victor Wembanyama cards have been rapidly rising in value over the last few weeks. Courtesy of PSA”
“A Victor Wembanyama rookie card that was previously the subject of some controversy sold in a private deal for $5.11 million, making it the most expensive known sale of a non-autographed NBA card.”
“The sale of the San Antonio Spurs center’s 2023-24 Panini Prizm one-of-one Black parallel rookie card, which has a Gem-Mint PSA 10 grade, was brokered by Fanatics Collect. It’s the fourth highest publicly known sale of an NBA card, according to online card sales database Card Ladder.”
JSON traps — where the missing content is hiding
Found 1 large script-tag JSON blob (120.2 KB of serialized data total). AI crawlers do not evaluate JavaScript or parse arbitrary inline state — content stored in these blobs is invisible to GPTBot, ClaudeBot, and the other AI indexers, even when the rest of the page renders correctly for humans.