Can IA help â https://caper.media/p/dean-deluca-usa-trademark-lawsuit?
Yes â quickly
Yes â quickly. AI already reads your content; the gap is that your commerce isn't legible or attributed. That's exactly what IA injects at the edge â typically a zero-dev-lift deploy.
â Are AI bots reaching you? AI search bots can reach your content â you're eligible to be cited.
â ď¸Are your links coming through? Your content is read, but your commerce links aren't coming through: commerce data trapped in window.__remixContext.
đ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 is a trademark lawsuit article with no product offers or commerce elements, only a subscription CTA. The structured-data layer covers editorial metadata (Article, BreadcrumbList, Person, Organization) but contains no commerce schema whatsoeverâProduct, Offer, BuyAction, Review, and AggregateOffer types are absent and not applicable to this content type. The page is fully reachable to search-index and training crawlers; citation probes found two explicit mentions of the topic but zero citations by URL, meaning the content exists in training data without direct source attribution. IA's enrichment would surface implicit entitiesâlawsuit parties, jurisdiction, filing date, outcome statusâas discrete, machine-readable claims, making the legal relationships and timeline inferable from structured markup rather than reliant on text parsing alone.
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.
IA enrichment adds (derived from existing page content)
Page already has explicit commerce schema â no enrichment delta to add.
Result for AI extractors
A bot fetching the URL pulls all 0 offers from JSON-LD in microseconds â no LLM inference, no prose parsing, no guessing at which discount applies.
View IA-rendered flattened HTML
Is Dean & Deluca Going To Come Back to New York? — Caper
View IA-generated JSON-LD @graph
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "NewsArticle",
"headline": "Is Dean & Deluca Going To Come Back to New York?",
"url": "https://caper.media/p/dean-deluca-usa-trademark-lawsuit",
"publisher": {
"@type": "Organization",
"name": "Caper"
}
}
]
}
</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.
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
6 of 6 accessible to scanner
Build training datasets. Blocking these is the lawsuit-safe posture â does not affect AI citation eligibility.
gptbot200
claudebot200
perplexitybot200
ccbot200
google_extended200
applebot_extended200
Traditional search engines
2 of 3 accessible to scanner
Bingbot, Googlebot, Applebot â not AI-specific.
1 declared allowed in robots.txt â scanner observed a 4xx. We canât verify what real bots see from outside; the publisher edge logs are ground truth.
bingbot403
robots.txt: allowed ¡ scanner: blocked
googlebot200
applebot200
Raw fetch detail (status, bytes, timing)
Identity
Status
Bytes
Blocked?
Timing
gptbot
200
689,862
no
1439ms
chatgpt_user
200
689,862
no
1334ms
oai_searchbot
200
689,862
no
1315ms
claudebot
200
689,862
no
1236ms
claude_user
200
689,862
no
1244ms
claude_searchbot
200
689,862
no
1196ms
perplexitybot
200
689,862
no
1115ms
perplexity_user
200
689,862
no
1049ms
googlebot
200
689,862
no
1018ms
google_extended
200
689,862
no
926ms
bingbot
403
5,963
yes
305ms
applebot
200
689,862
no
857ms
applebot_extended
200
689,862
no
845ms
ccbot
200
689,862
no
772ms
human
200
689,862
no
1426ms
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
90/100
Mixed â text content is reachable, but commerce data is trapped (see JSON traps below)
FrameworkRemixHydration gap0%
Skeleton or loading placeholders in bot HTML
Content visible in raw HTML is a placeholder; real content loads client-side.
JSON traps â where the missing content is hiding
Found 3 large script-tag JSON blobs (397.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. At least one blob contains commerce data â product, price, or offer fields trapped where bots canât reach.
