phillips.shef.ac.uk
success
Claude Code
intent

What does phillips.shef.ac.uk do and who is it for? Explain it back to me.

15steps
55.8sduration
$0.6624cost
175,574tokens
18 steps3 reasoning steps4 searches
home
/pub/svdv/fd
/pub/svdv/fd/about
/pub/svdv/fd/about
search
home
/content/article/sensi…
search
search
/content/article/hf-ra…
search
home
/pub/svdv/lb
/pub/svdv/lb/about
/pub/svdv/ko
73%
on-site discovery
82%
reliability
36%
link following
path origin
  • previous resource36%
  • web search27%
  • prior knowledge36%
insight

The agent successfully assembled a comprehensive overview of phillips.shef.ac.uk and its parent service (Seaview Realtime SVDV) by combining minimal on-site information with external research. The site itself is sparsely informative—a one-liner homepage with three data viewer links—requiring the agent to supplement with web searches and off-site content (Hydro International articles) to answer questions about functionality, pricing, and differentiation. The agent filled critical gaps using prior knowledge and external sources rather than finding answers in the site's own documentation.

  • ›The homepage [1] provided only a 3-line description ('A waves group server') and contact info; it surfaced nothing about use cases, pricing, or capabilities. The agent had to infer purpose by following the three data viewer links.
  • ›The 'About' pages [5, 6] were retrieved but truncated in the response; the agent could not extract substantive content from them, forcing reliance on external sources like the Hydro International article [13, 16] which actually explained HF radar, wave measurement, and deployment context.
  • ›Pricing information was not on phillips.shef.ac.uk; the agent sourced it from search results pointing to Seaview Sensing FAQs and Hydro International, which stated pricing was 'a tenth of the cost of the radar' and required contact for quotes.
  • ›Competitor/alternative information [15] search yielded generic 'Seaview' alternatives (unrelated products) rather than domain-specific HF radar platforms; the agent had to use prior knowledge to construct differentiation (HF radar specialization, academic foundation, web stack).
  • ›The site is not self-explanatory to a crawler: no meta descriptions, no structured data (schema.org), no introductory documentation. The agent succeeded only by escaping the site boundary and triangulating external sources.
  • ›Access barrier: full functionality appears behind login [5, 6 responses truncated], preventing the agent from exploring data viewer interfaces or access procedures without credentials.

See every agent that visits phillips.shef.ac.uk

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 →