trivago.com
success
Claude Code
intent
What does trivago.com do and who is it for? Explain it back to me.
15steps
68.8sduration
$0.7416cost
184,057tokens
18 steps3 reasoning steps4 searches
home
docs
/en
home
docs
/help
/faq
home
search
/wiki/trivago
/trivago-business-model
search
search
/en/contact
search
82%
on-site discovery
91%
reliability
55%
link following
path origin
- previous resource55%
- web search18%
- prior knowledge18%
- other9%
insight
The agent successfully assembled a comprehensive explanation of trivago's business model, but had to rely almost entirely on external sources rather than the trivago.com site itself. The homepage and support pages returned only truncated HTML with no human-readable content, forcing the agent to use web search and Wikipedia to answer all substantive questions about what trivago does, who it's for, how it's priced, and how it differs from competitors. The site itself is not navigable for this discovery task.
- ›The trivago.com homepage and regional variants (UK, Australia) all returned JavaScript-rendered HTML that contained no fetchable, readable content describing the business, pricing, or value proposition — only metadata and truncated code snippets.
- ›The agent found no 'about' page, pricing page, or help documentation on trivago.com that explained their metasearch model, CPC revenue, or competitive positioning. The /about route redirected or returned the same unusable homepage markup.
- ›All substantive answers came from external sources: FourWeekMBA [15] for business model details, comparison articles [11] for competitive differentiation, and Wikipedia [12] for company structure. The agent also obtained SEC filings [14] to confirm Expedia Group ownership.
- ›The agent identified multiple confusions it could not resolve from the site itself: the lack of transparency about ranking algorithms, the hidden Expedia ownership relationship, the unclear distinction between consumer and business products, and what 'free' actually means for end users.
- ›The site is extremely agent-unfriendly for discovery tasks — no meta tags, structured data, or readable text content provided information about the service. The agent had to bridge entirely through prior knowledge and web search (55% prior_knowledge + 18% web_search vs. 0% direct content from the site's pages).
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →