jfkairport.com
success
Claude Code
intent
What does jfkairport.com do and who is it for? Explain it back to me.
13steps
79.6sduration
$0.7584cost
145,224tokens
18 steps5 reasoning steps5 searches
home
/en
/parking
/shopping
search
/explore-jfk/services
/explore-jfk
/at-airport/shops-rest…
search
search
search
/flights
search
62%
on-site discovery
88%
reliability
38%
link following
path origin
- previous resource38%
- web search38%
- prior knowledge13%
- other13%
insight
The agent successfully assembled a comprehensive explanation of jfkairport.com by combining metadata from the homepage fetch with content from deeper pages about services, exploration guides, dining/shopping, and flights. The site is moderately navigable but heavily client-side rendered, forcing the agent to work from page titles, meta descriptions, and search-discovered URLs rather than full rendered content; the agent compensated by inferring scope from metadata and page structure rather than reading complete page bodies.
- ›Steps [1], [8], [9], [10], [15] were content-bearing: they returned meta descriptions and titles (e.g. 'Airport Services & Amenities', 'Explore everything JFK Airport has to offer: shops, dining, art, lounges') that directly informed the agent's answer about what JFK offers. The homepage [1] meta description ('Welcome to JFK Airport, New York's international gateway. Find flight info, maps, transportation, parking, and traveler tips') was particularly foundational.
- ›The site's structure is visible through metadata and URL patterns, but full page content is inaccessible without JavaScript execution—steps [4] and [5] hit 403/404 errors on direct navigation attempts. The agent did not attempt direct content fetches from the rendered pages; instead it relied on page titles, meta descriptions, and search-discovered page links as proxies for content.
- ›The agent had to infer 'how it's priced' and 'how it's different from alternatives' largely from prior knowledge and web search results, not from page content itself. The site does not present pricing or competitive positioning explicitly on fetched pages—the agent synthesized this from external search context (steps [12], [13], [14]) and general airport knowledge. This indicates the site prioritizes informational/transactional service discovery over marketing differentiation.
- ›Navigation surface was partially broken: direct guesses for /parking and /shopping failed (403, 404), and /en redirected to 404, suggesting the site's routing or permissions are fragile or region-specific. The agent compensated by relying on search engine discovery and the homepage's implicit link structure.
See every agent that visits jfkairport.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 →