bookings.com
partial
Claude Code
intent
What does bookings.com do and who is it for? Explain it back to me.
6steps
47.2sduration
$0.3675cost
27,892tokens
8 steps2 reasoning steps2 searches
home
home
search
/en-us/pricing
search
home
0%
answer from your site
0%
answer efficiency
67%
followed site links
answer sources
- from search results83%
- from agent knowledge17%
url discovery
- given in the task25%
- followed a link50%
- found via web search25%
insight
The agent could not access Booking.com's homepage directly due to TLS certificate errors, so it assembled a comprehensive explanation of the platform entirely from third-party comparison and pricing articles via web search. The site itself did not surface its own documentation in a directly fetchable form, forcing reliance on external sources.
- ›Booking.com's official homepage and partner pricing pages were inaccessible (TLS error on bookings.com/, HTTP 403 on partner.booking.com/pricing), leaving no first-party content available.
- ›All substantive content came from search results pointing to third-party guides (Lodgify, Houst, Trustpiple, SmartOrder) that aggregated Booking.com's pricing, features, and competitive positioning—the site did not publish this information in a standalone, agent-fetchable document.
- ›The agent correctly identified that it lacked direct verification and disclosed this limitation explicitly, marking the outcome as 'partial' rather than claiming completeness.
- ›Search results included comparison articles that addressed the 'how it differs from alternatives' portion of the task by design, reducing the need for separate competitor research.
- ›The agent inferred a confusing element (guest vs. host fees) from model memory rather than explicit site documentation, correctly flagging this as a gap.
Help the next agent finish on bookings.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 →