icehotel.com
success
Claude Code
intent

What does icehotel.com do and who is it for? Explain it back to me.

8steps
36.2sduration
$0.3412cost
75,313tokens
10 steps2 reasoning steps1 search
home
/booking
docs
/rooms
/en
/price
search
/packages-deals
86%
on-site discovery
57%
reliability
57%
link following
path origin
  • previous resource57%
  • web search14%
  • prior knowledge29%
insight

The agent successfully assembled a comprehensive explanation of ICEHOTEL by combining the homepage meta description, a booking page fetch, and a packages-deals page discovered via web search. The site's navigation and URL structure were largely unhelpful (direct guesses at /about, /rooms, /price all returned 404s), forcing the agent to rely on prior knowledge and search to fill gaps around pricing, room types, and seasonal operations. Despite incomplete transparency on the site itself, the agent synthesized enough information to answer all four required dimensions (what, who, how priced, differentiation).

  • ›Step [1] (homepage) provided only the high-level meta description ('hotel and art exhibition with ice and snow') — foundational but thin on business model, pricing, and target audience details.
  • ›Step [2] (booking page) returned HTML but the response was truncated and the agent extracted no pricing or room-type data from it in the final answer, suggesting the booking engine itself requires interaction (JS, form submission) to surface rates.
  • ›Step [8] (packages-deals page) was discovered via web search, not site navigation, and its meta description alone ('all-inclusive Arctic packages...sleep in ice, see northern lights, dog sled...') provided much of the activity and bundling positioning that differentiated ICEHOTEL from alternatives.
  • ›The agent explicitly called out pricing opacity and acknowledged that specific rates (1,500 SEK for warm rooms, $90–$200+ for ice rooms, $1,339+ for art suites) came from external sources (TripAdvisor, Booking.com) cited in the final response, not from icehotel.com itself.
  • ›Direct URL guesses (/about, /rooms, /price) all failed with 404s, indicating poor URL predictability and forcing reliance on web search and prior knowledge (57% of fetches came from previous_artifact, suggesting heavy bridging by the agent's reasoning).
  • ›The site does not expose room inventory, seasonal availability, booking windows, or activity pricing in a transparent, machine-readable form on its public pages — all information the agent noted as 'missing' or 'confusing.'

See every agent that visits icehotel.com

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →