hotelist.com
success
Claude Code
intent
What does hotelist.com do and who is it for? Explain it back to me.
15steps
75.4sduration
$1.1221cost
138,079tokens
25 steps10 reasoning steps8 searches
home
home
docs
docs
/faq
search
/p/171814/hotelist
search
search
/projects
search
search
search
search
search
71%
on-site discovery
86%
reliability
14%
link following
path origin
- previous resource14%
- web search29%
- prior knowledge57%
insight
The agent successfully gathered enough information to explain Hotelist's core purpose, target audience, and differentiation, but had to work around a JavaScript-heavy site that didn't expose full details in static HTML. The site's homepage meta description and web search results provided the main value propositions; however, critical information about pricing/monetization, business model, and feature details remained unavailable or required inference, forcing the agent to acknowledge gaps rather than deliver a complete picture.
- ›Steps [1] and [3] (homepage fetches) returned only truncated static HTML with meta tags—the actual content is rendered client-side via JavaScript, making the site invisible to direct HTML parsing. The agent had to rely on the meta description ('No pay-to-play, only hotels rated by AI') as the only explicit site-native signal.
- ›Steps [9], [10], [14], [15], [22], [23] (web search results) carried nearly all substantive information: the tagline, the 90,000+ hotel count, creator attribution (Pieter Levels), and competitive positioning. The agent assembled its answer primarily from search snippets and external mentions, not from hotelist.com itself.
- ›Step [20] (levels.io projects page) and attempts to fetch /pricing, /about, and /faq (steps [5], [6], [7]) all returned the same truncated boilerplate HTML, indicating Hotelist is a pure SPA with no server-rendered detail pages. This made in-site navigation impossible.
- ›The agent's final answer explicitly calls out three critical unknowns: business model/monetization, affiliate program details, and exact rating-weighting methodology. These gaps exist because Hotelist does not publish this information in accessible form—not because the agent failed to search.
- ›The site is extremely low on agent-readiness: no structured data (JSON-LD, microdata), no API documentation link, no public methodology docs, and all content locked behind JavaScript. The agent succeeded only by reaching for external sources (search, creator's profile page) to fill in what the site itself withheld.
Help the next agent finish on hotelist.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 →