2026-05-31 14:11 UTC · ready · vertical: product · schema score: 0/100

Can IA help — https://www.westelm.com/products/hughes-storage-cabinet-f434/?pkey=cwest-elm-office&sb=WE?

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 Akamai, 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 displays a single West Elm furniture product (Hughes Storage Cabinet) with no detectable offer pricing or purchase options rendered. No schema markup is present; Product, Offer, Review, and BuyAction types are entirely absent from the structured-data layer. Search-index citation bots cannot fetch the page, and the citation probe returned one explicit mention but only partial URL citation, indicating the product is referenced in external contexts without reliable linkage back to this specific product resource. IA enrichment would surface the product entity and its attributes as explicit structured signals, making the product identifiable and relatable to external references independent of publisher schema implementation or bot reachability constraints.

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.

Bot accessibility

Edge / CDN: akamai· server: AkamaiGHost

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.

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

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

applebot_extended403

Traditional search engines

0 of 3 accessible to scanner

Bingbot, Googlebot, Applebot — not AI-specific.

bingbot403

googlebot403

applebot403

Raw fetch detail (status, bytes, timing)

Identity	Status	Bytes	Blocked?	Timing
gptbot	403	1,790	yes	954ms
chatgpt_user	403	1,790	yes	810ms
oai_searchbot	403	1,790	yes	877ms
claudebot	403	1,790	yes	752ms
claude_user	403	1,790	yes	687ms
claude_searchbot	403	1,790	yes	674ms
perplexitybot	403	1,790	yes	697ms
perplexity_user	403	1,790	yes	605ms
googlebot	403	1,790	yes	501ms
google_extended	403	1,790	yes	412ms
bingbot	403	1,790	yes	541ms
applebot	403	1,790	yes	448ms
applebot_extended	403	1,790	yes	405ms
ccbot	403	1,790	yes	235ms
human	403	1,790	yes	341ms

robots.txt policy per AI bot

CCBot: not_mentioned

GPTBot: not_mentioned

Bingbot: not_mentioned

Applebot: not_mentioned

ClaudeBot: not_mentioned

Googlebot: not_mentioned

Claude-User: not_mentioned

ChatGPT-User: not_mentioned

OAI-SearchBot: not_mentioned

PerplexityBot: not_mentioned

Google-Extended: not_mentioned

Perplexity-User: not_mentioned

Claude-SearchBot: not_mentioned

Applebot-Extended: not_mentioned

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 · 5

ProductOfferReviewAggregateRatingBuyAction

Rubric breakdown (0 of 5 criteria met)

✗Offer	0 pts
✗Review	0 pts
✗Product	0 pts
✗BuyAction	0 pts
✗AggregateRating	0 pts

potentialAction — commerce paths

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

Present · 0

(none)

Missing · 1

BuyAction

Affiliate footprint

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