zelfbouw-info.nl
partial
Claude Code
intent
What does zelfbouw-info.nl do and who is it for? Explain it back to me.
24steps
92.8sduration
$1.2158cost
226,584tokens
36 steps12 reasoning steps10 searches
home
/over-ons
/kennisbank
/kavelzoeker
/bouwkosten-calculator
/financieren
/over-ons
/over-ons/_payload.json
search
search
search
search
search
search
search
docs
/information
/contact
/prijzen
/faq
/api/content
search
search
search
100%
on-site discovery
57%
reliability
71%
link following
path origin
- previous resource71%
- prior knowledge29%
insight
The agent assembled a partial but functional understanding of Zelfbouw Informatiepunt by fetching the homepage, about page, knowledge base, and three core tool pages (Kavelzoeker, cost calculator, mortgage calculator), then supplemented with web searches. The site's heavy JavaScript rendering prevented full content extraction, and critical pricing details remained inaccessible despite multiple fetch and search attempts, leaving the pricing tier comparison incomplete.
- ›Steps [1], [3], [7], [8], [11], [12], [16] returned valid pages but with truncated HTML (4400+ chars cut) and no rendered content visible in the fetches — the Nuxt SPA architecture meant the agent could confirm page existence and meta titles but not extract body copy, pricing tables, or feature descriptions.
- ›The agent discovered core offerings (Kavelzoeker plot finder, Kennisbank, calculators) from page titles and URL structure alone, not from readable page content; this represents inference from navigation rather than content extraction.
- ›Direct guesses at /pricing, /prijzen, /faq, /information, and _payload.json URLs all returned 404s, indicating pricing information is either embedded on existing pages (not crawlable) or located at non-standard paths, forcing reliance on inferred knowledge and web search.
- ›Web searches [19–34] returned snippets linking back to the site's own pages but provided no independent verification of pricing tiers, feature differences, or competitive claims; the €19 figure mentioned in the final answer does not appear in the search results shown, indicating it came from the agent's prior knowledge (71% of fetches sourced from prior knowledge per run metadata).
- ›The site is not agent-ready: no pricing page, no structured data (schema.org), no API endpoint, no rendered content in HTML, and no public documentation of free vs. premium boundaries — the agent had to assemble a plausible model from fragments rather than read documented facts.
Help the next agent finish on zelfbouw-info.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 →