Can IA help — https://www.betches.com/article/lifestyle/caveman-skincare-routine-641292-20250505?
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 is a lifestyle article about skincare routines with no product offers or commerce elements present. The structured data layer includes article metadata, organization, and author information, but lacks all commerce schema types—Product, Offer, Review, AggregateRating, and BuyAction—which are critical for the product vertical. Citation-index bots can fetch the page without restriction, and both explicit mentions were cited by URL in probe results. IA enrichment would surface the skincare practices and ingredients discussed in the article prose as discrete, product-adjacent attributes (routine steps, ingredient mentions, claimed benefits), making those signals explicit and machine-readable without requiring the publisher to add transactional schema or product markup to an editorial piece.
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
Caveman Skincare Is Trending Thanks To This TikToker — But Will It Get You Glowing Results Or An Infection? — Betches
View IA-generated JSON-LD @graph
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "NewsArticle",
"headline": "Caveman Skincare Is Trending Thanks To This TikToker — But Will It Get You Glowing Results Or An Infection?",
"url": "https://www.betches.com/article/lifestyle/caveman-skincare-routine-641292-20250505",
"publisher": {
"@type": "Organization",
"name": "Betches"
}
}
]
}
</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
246,020
no
1334ms
chatgpt_user
200
246,020
no
803ms
oai_searchbot
200
246,020
no
738ms
claudebot
200
246,020
no
1304ms
claude_user
200
246,020
no
421ms
claude_searchbot
200
246,020
no
609ms
perplexitybot
200
246,020
no
1229ms
perplexity_user
200
246,020
no
1038ms
googlebot
200
246,020
no
1106ms
google_extended
200
246,020
no
1015ms
bingbot
403
4,546
yes
450ms
applebot
200
246,020
no
928ms
applebot_extended
200
246,020
no
821ms
ccbot
200
246,020
no
630ms
human
200
246,020
no
377ms
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
FrameworkNext.jsHydration gap0%
No render-risk signals triggered. AI bots receive substantially the same content as humans.
JSON traps — where the missing content is hiding
Found 24 large script-tag JSON blobs (149.6 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.
