hotelperula.com
success
Claude Code
intent

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

13steps
46.1sduration
$0.5108cost
119,100tokens
16 steps3 reasoning steps2 searches
home
/en/rooms
/en
/en/pricing
/en/about
/en/facilities
/en/offers
/en/contact
/en/booking
search
search
/en/sultanahmet-hotel-…
/en/reservation
82%
on-site discovery
64%
reliability
18%
link following
path origin
  • previous resource18%
  • web search18%
  • prior knowledge64%
insight

The agent assembled a comprehensive overview of Hotel Perula by combining fragments from the hotel's Next.js-rendered website (homepage, rooms, about, contact pages) with web search results and third-party booking platforms. The site itself exposed limited machine-readable content due to client-side rendering, forcing the agent to rely heavily on prior knowledge (64%) and search results (18%) to construct claims about pricing, positioning, and differentiation. The agent succeeded in explaining what the hotel does, who it serves, pricing range, and competitive positioning, but acknowledged significant gaps in amenity details, room-type-specific pricing, and spa services that the website structure did not expose.

  • ›The homepage and room pages (steps [0], [1]) returned only Next.js boilerplate and CSS metadata—no actual content about room types, pricing, or amenities was visible in the HTML source, forcing the agent to note this technical limitation explicitly.
  • ›The agent discovered a dedicated pricing comparison page (step [13]: /en/sultanahmet-hotel-prices) and reservation page (step [14]) only via web search results, not via site navigation or internal linking visible in the fetched HTML, indicating poor discoverability of these resources within the site itself.
  • ›Web search results (steps [11], [12]) provided the core factual claims about location (100m from Blue Mosque), room count (30 rooms, later questioned as possibly 20), price range ($51–$71), and luxury positioning—none of which appeared in the fetched page source, demonstrating the site does not publish these key differentiators in an agent-readable form.
  • ›The agent repeatedly attempted conventional URL guesses (/en/pricing, /en/facilities, /en/offers, /en/booking) that all returned 404s, showing the site has an unconventional or sparse navigation structure that does not follow typical hotel site patterns.
  • ›The agent explicitly called out three categories of missing information: room amenities and comparisons, dining/restaurant details, and spa service details—all referenced in search results but not found in the fetched website HTML, indicating the site keeps detailed operational information behind JavaScript rendering or off-site.

Help the next agent finish on hotelperula.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 →