2026-06-02 23:07 UTC · ready · vertical: unknown · schema score: 0/100

Summary

The page is a Samsung Galaxy S26 product review article with no detected offers or purchase links. The structured data layer is entirely absent—no schema markup for Product, Offer, AggregateOffer, BuyAction, Review, or AggregateRating—leaving machine-readable assertions about the device, its attributes, pricing, or editorial assessment unencoded. The page is unreachable to search-index citation bots and user-initiated fetchers across all probes tested, though training crawlers face the same access barrier; citation probes show the URL was cited explicitly in 1 of 2 result samples but mentions of the device appear in generic form only. IA enrichment would render the Samsung Galaxy S26 as a discrete Product entity with its attributes and review stance as explicit AggregateRating signals, making the article's factual assertions and critical assessment inferable from structured claims rather than free text alone.

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 402 · claude_searchbot 402

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 402 · claude_searchbot 402

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.

Bot accessibility

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

Search / index crawlers

0 of 2 accessible to scanner

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

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.

oai_searchbot402

robots.txt: allowed · scanner: blocked

claude_searchbot402

robots.txt: allowed · scanner: blocked

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.

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.

chatgpt_user402

robots.txt: allowed · scanner: blocked

claude_user402

robots.txt: allowed · scanner: blocked

perplexity_user402

Training-data crawlers

0 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.

gptbot402

robots.txt: allowed · scanner: blocked

claudebot402

perplexitybot402

ccbot402

google_extended402

applebot_extended402

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.

bingbot460

robots.txt: allowed · scanner: blocked

googlebot460

robots.txt: allowed · scanner: blocked

applebot402

robots.txt: allowed · scanner: blocked

Raw fetch detail (status, bytes, timing)

Identity	Status	Bytes	Blocked?	Timing
gptbot	402	612	yes	1186ms
chatgpt_user	402	612	yes	633ms
oai_searchbot	402	612	yes	917ms
claudebot	402	109	yes	1055ms
claude_user	402	109	yes	813ms
claude_searchbot	402	109	yes	1120ms
perplexitybot	402	612	yes	963ms
perplexity_user	402	612	yes	841ms
googlebot	460	10	yes	857ms
google_extended	402	612	yes	496ms
bingbot	460	10	yes	488ms
applebot	402	109	yes	680ms
applebot_extended	402	109	yes	391ms
ccbot	402	109	yes	553ms
human	402	612	yes	422ms

robots.txt policy per AI bot

CCBot: disallowed

GPTBot: allowed

Bingbot: allowed

Applebot: allowed

ClaudeBot: disallowed

Googlebot: allowed

Claude-User: allowed

ChatGPT-User: allowed

OAI-SearchBot: allowed

PerplexityBot: disallowed

Google-Extended: disallowed

Perplexity-User: disallowed

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.

Schema audit

0/100

Present · 0

No structured data detected

Missing · 0

Nothing critical missing

potentialAction — commerce paths

⚠ No commerce-action schema present — AI has no canonical path back to this publisher.

Present · 0

(none)

Missing · 0

(none — complete for this vertical)

Affiliate footprint

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