onspect.nl
success
Claude Code
intent
What does onspect.nl do and who is it for? Explain it back to me.
26steps
90.5sduration
$1.7168cost
353,749tokens
28 steps2 reasoning steps14 searches
home
home
/het-platform
docs
/over-ons
search
search
/modules
/wp-json/wp/v2/pages/1…
search
search
/referenties
search
/contact
search
/kwaliteitszorgsysteem…
search
search
search
search
/onspect-voor-vo
search
/wp-json/wp/v2/pages
search
search
search
67%
on-site discovery
83%
reliability
17%
link following
path origin
- previous resource17%
- web search33%
- prior knowledge42%
- other8%
insight
The agent successfully gathered enough information to explain OnSpect's core purpose, audience, features, and pricing, though it had to work around a poorly organized website and missing dedicated pricing/competitive pages. The site published key content across scattered detail pages rather than cohesive sections, forcing the agent to synthesize information from multiple fetches and rely on prior knowledge to fill gaps about alternatives and market positioning.
- ›Steps [1, 14] (homepage and main quality system page) provided the foundational value proposition ('digital quality assurance for Dutch schools') but only as meta descriptions and hero text—no structured feature lists or overview were prominently displayed in the HTML.
- ›Steps [5, 19] (About page and secondary education page) added context about school segments (PO, VO, MBO) but did not surface pricing, competitive positioning, or differentiation directly; the agent inferred these from page content and prior knowledge.
- ›Steps [9, 10, 21, 24] (Modules, References, and feature-specific searches) revealed the modular architecture (Kwaliteitskalender, Schooldossier, etc.) only through targeted fetches—the site did not present these in a machine-readable index or API response that would have made discovery trivial.
- ›Pricing information ([18] search result, sourced from prior knowledge fallback, not from a dedicated pricing page) was explicitly absent from the website's public URLs; the agent had to rely on embedded knowledge or infer it was mentioned in a search snippet, making this a major navigation friction point.
- ›The site's navigation and content organization made it difficult for the agent to discover competitive alternatives or differentiation without resorting to external web searches; OnSpect's own website provided no comparative positioning.
- ›The agent successfully cited 7 distinct pages from onspect.nl in its final Sources list, but many were discovered via targeted search queries rather than by following visible navigation—indicating poor discoverability of key information architecture.
See every agent that visits onspect.nl
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 →