2026-06-02 23:34 UTC · ready · vertical: mixed · schema score: 0/100

Can IA help — https://www.cntraveler.com/hotels/maldives/maldives/huvafen-fushi?

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

Implementation friction: Low — you're on Cloudfront, 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 presents a single hotel property, Huvafen Fushi, with two booking CTAs directed to Booking.com and Expedia, but carries no structured data markup—no Product, Offer, Review, or rating schemas are present. Search-index citation bots can fetch the page without restriction, and probe results show explicit mentions are being cited by URL while generic references achieve partial citation. IA's enrichment would surface the property as a discrete Product entity with associated offer and rating signals, making the accommodation's commercial intent and guest feedback legible to systems that currently parse only the editorial text layer.

Citation bots reachable — oai_searchbot, claude_searchbot

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.

Human view

AI Bot Today — During Live Search

On the page

Brand

Huvafen Fushi

Offers detected (0)

none

CTAs (2)

Book Now at Booking.com · Book Now at Expedia

In the JSON-LD layer

Types present (0)

none

Commerce types present

none

Commerce types missing

Product, Offer, AggregateOffer, BuyAction, Review, AggregateRating

The gap

Offers visible to humans0

Offers in machine-readable form0

Click-throughs wrapped as BuyAction0

AI bot — with IA enrichment

IA enrichment adds (derived from existing page content)

+ 1 Product entity (Huvafen Fushi)

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

Huvafen Fushi, Maldives – Hotel Review | Condé Nast Traveler — Cntraveler

View IA-generated JSON-LD @graph

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "NewsArticle",
      "headline": "Huvafen Fushi, Maldives – Hotel Review | Condé Nast Traveler",
      "url": "https://www.cntraveler.com/hotels/maldives/maldives/huvafen-fushi",
      "publisher": {
        "@type": "Organization",
        "name": "Cntraveler"
      }
    }
  ]
}
</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.

Bot accessibility

Edge / CDN: cloudfront· x-amz-cf-id header · x-amz-cf-pop header · via: cloudfront

Search / index crawlers

2 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_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

3 of 3 accessible to scanner

Bingbot, Googlebot, Applebot — not AI-specific.

bingbot200

googlebot200

applebot200

Raw fetch detail (status, bytes, timing)

Identity	Status	Bytes	Blocked?	Timing
gptbot	200	2,074,740	no	1316ms
chatgpt_user	200	2,074,740	no	934ms
oai_searchbot	200	2,074,740	no	887ms
claudebot	200	2,074,740	no	999ms
claude_user	200	2,074,740	no	1170ms
claude_searchbot	200	2,074,740	no	380ms
perplexitybot	200	2,074,740	no	475ms
perplexity_user	200	2,074,740	no	590ms
googlebot	200	2,074,740	no	1063ms
google_extended	200	2,074,740	no	1071ms
bingbot	200	2,074,740	no	562ms
applebot	200	2,074,740	no	878ms
applebot_extended	200	2,074,740	no	884ms
ccbot	200	2,074,740	no	605ms
human	200	2,074,740	no	1195ms

robots.txt policy per AI bot

CCBot: disallowed

GPTBot: allowed

Bingbot: allowed

Applebot: allowed

ClaudeBot: disallowed

Googlebot: allowed

Claude-User: disallowed

ChatGPT-User: allowed

OAI-SearchBot: allowed

PerplexityBot: disallowed

Google-Extended: disallowed

Perplexity-User: disallowed

Claude-SearchBot: disallowed

Applebot-Extended: disallowed

Render risk — what AI bots can actually parse

89/100

Mixed — text content is reachable, but commerce data is trapped (see JSON traps below)

FrameworkUnknown / vanillaHydration gap28%

Hydration gap: 28%
AI bots see 72% of the rendered content. The remaining 28% loads via client-side JavaScript and is invisible to crawlers that don't execute JS.

What AI bots are missing

links missing

rendered 88 · bot 82

paragraphs missing

rendered 38 · bot 33

Sample content only humans see:

“Please provide information on the privacy center and press “submit.” You can also submit this request by calling 1-877-241-4999. This information will not be used or disclosed for any purpose other than for processing this request.”
“All listings featured on Condé Nast Traveler are independently selected by our editors. If you book something through our links, we may earn an affiliate commission.”

JSON traps — where the missing content is hiding

Found 3 large script-tag JSON blobs (1.42 MB 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.

window.gladlyConfigcustom

2.5 KB of serialized data

__REDUX_STATE__redux

1.42 MB of serialized data

Commerce data detected — keys present: products, product, offers, price, seller, brand, reviews

Top-level keys: componentConfig, config, featureFlags, renditions, transformed, locale, env

window.dataLayercustom

1.1 KB of serialized data

Commerce data detected — keys present: brand

Top-level keys: event, content, marketing, page, search, site, syndication

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

BuyActionOrderActionReserveAction

Affiliate footprint

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