All case studies →
Intelligent Attribution
← All scans

https://www.forbes.com/health/supplements/best-pre-workout/

2026-06-02 21:14 UTC · ready · vertical: unknown · schema score: 0/100
Can IA help — https://www.forbes.com/health/supplements/best-pre-workout/?
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 supplement guide article with no product offers, pricing, or purchase links embedded in the content. The structured-data layer contains no schema markup of any kind—Product, Offer, AggregateOffer, BuyAction, Review, and AggregateRating types are all absent, leaving product claims and comparisons entirely in untagged prose. All citation bots tested (search-index, user-initiated, and training crawlers) failed to fetch the page, though explicit URL citations were recorded in both cases where the page was mentioned elsewhere. IA's enrichment layer would surface product entities, claim provenance, and comparison signals as explicit schema objects, making the evaluative relationships in the text parseable by downstream systems without requiring page access.

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
Page screenshot
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.

Bot accessibility

Edge / CDN: fastly· x-timer header · x-served-by: cache-<POP>
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_searchbot403
robots.txt: allowed · scanner: blocked
claude_searchbot403
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.
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.
chatgpt_user403
robots.txt: allowed · scanner: blocked
claude_user403
robots.txt: allowed · scanner: blocked
perplexity_user403
robots.txt: allowed · scanner: blocked
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.
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.
gptbot403
claudebot403
perplexitybot403
ccbot403
google_extended403
robots.txt: allowed · scanner: blocked
applebot_extended403
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
gptbot403770yes1080ms
chatgpt_user403770yes1060ms
oai_searchbot403772yes989ms
claudebot403770yes868ms
claude_user403772yes841ms
claude_searchbot403770yes794ms
perplexitybot403770yes662ms
perplexity_user403772yes623ms
googlebot403770yes542ms
google_extended403772yes545ms
bingbot403770yes367ms
applebot403770yes476ms
applebot_extended403770yes1099ms
ccbot403770yes351ms
human403770yes253ms
robots.txt policy per AI bot
CCBot: disallowed
GPTBot: disallowed
Bingbot: allowed
Applebot: allowed
ClaudeBot: disallowed
Googlebot: allowed
Claude-User: allowed
ChatGPT-User: allowed
OAI-SearchBot: allowed
PerplexityBot: disallowed
Google-Extended: allowed
Perplexity-User: allowed
Claude-SearchBot: allowed
Applebot-Extended: disallowed

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.