The agent successfully assembled a comprehensive explanation of Agoda by relying almost entirely on web search results and prior knowledge, since the site itself (steps [0], [1], [6], [8]) returned heavy JavaScript with minimal readable content, and direct attempts to find pricing, loyalty program, and about pages all failed with 404s. The agent worked around an agent-hostile site architecture by pivoting to external sources (Wikipedia, CNBC comparison, Wise, Osum market analysis) to answer all core questions about what Agoda does, who it serves, how it's priced, and how it differs from competitors.

• ›The homepage and locale-specific pages (steps [0], [1]) returned JavaScript-heavy markup with no human-readable value proposition, making them non-parseable for extracting core business information.
• ›Dedicated information pages (/info, /about, /help, /en-us/promos, /en-us/agoda-cash, /en-us/agoda-vip) all returned 404s, forcing the agent to abandon site-native discovery entirely and rely on web search for loyalty program mechanics, pricing structure, and positioning.
• ›All substantive answers came from web searches (steps [7], [13], [14], [15]) and external sources—Wikipedia, CNBC comparison articles, Wise, and Osum market analysis—not from agoda.com itself. The support page (step [6], [8]) was fetched but not cited, suggesting it did not yield usable content.
• ›The agent correctly identified that core information (Best Price Guarantee terms, AgodaCash/PointsMax mechanics, hotel commission rates, and pricing transparency) was either missing or inaccessible on the public site, explicitly calling out these gaps.
• ›The site is substantially agent-hostile: no structured data, JavaScript-dependent rendering, missing information architecture, and 404s on logical content paths (/about, /info, /help, /promos). The agent had to synthesize an answer from third-party sources rather than primary sources.