snei.nl
success
Claude Code
intent

What does snei.nl do and who is it for? Explain it back to me.

4steps
31.9sduration
$0.1884cost
16,304tokens
6 steps2 reasoning steps
home
home
home
home
80%
answer from your site
75%
answer efficiency
100%
followed site links
answer sources
  • from this site80%
  • from agent knowledge20%
url discovery
  • given in the task25%
  • followed a link75%
insight

The agent successfully built a coherent, well-sourced explanation of SNEI's core business, pricing range, and competitive positioning by extracting information from the homepage across three separate fetches. The site's homepage was content-rich enough to answer the main questions, though it required the agent to ask for specific sections (pricing, differentiation) as separate queries rather than surfacing them all in a single overview.

  • ›Step [2] was the primary content source — a single homepage fetch returned the organization's overview, services, target audience, key features, and certifications in structured form, requiring no navigation to subpages.
  • ›Steps [3] and [4] appear to be re-fetches of the same homepage URL (typed from memory, not linked), suggesting the agent prompted the same resource separately to extract pricing and differentiation angles. This worked but was inefficient; the site did not surface dedicated pricing or comparison pages the agent could navigate to.
  • ›Pricing information was present but generic (€315–€452 range, 'varies by module'); the agent correctly noted it could not find per-exam breakdowns, indicating the site either lacks granularity or relegates it to a separate pricing page not discovered during the run.
  • ›The agent transparently flagged five substantive gaps (per-exam pricing, training services, exam content details, success metrics, alternatives) — all absences the site could have addressed but did not expose on the homepage, indicating weaker discoverability for comparative or operational details.
  • ›No search results or external third-party content were used; the agent relied entirely on the redirected homepage, making navigation and site structure the sole discovery mechanism. The 301 redirect from snei.nl → nederlandsexameninstituut.nl was handled correctly but added a step.

See every agent that visits snei.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 →