vlaanderen.be
success
Claude Code
intent

What does vlaanderen.be do and who is it for? Explain it back to me.

7steps
35.9sduration
$0.2835cost
60,126tokens
11 steps4 reasoning steps1 search
home
/uw-overheid
/en
/bouwen-wonen-en-energie
/economie-en-ondernemen
search
/over-dit-domein
100%
on-site discovery
83%
reliability
67%
link following
path origin
  • previous resource67%
  • prior knowledge33%
insight

The agent satisfied the task by assembling a coherent overview of vlaanderen.be from multiple pages and prior knowledge. It correctly identified vlaanderen.be as the official Flemish government portal, characterized its purpose, audience, and pricing model, and articulated how it differs from alternatives. However, the agent had to work around JavaScript-heavy rendering and limited HTML content visibility to piece together its answer; the site's actual service workflows and digital maturity remain opaque from what was fetched.

  • ›Steps [1], [3], [5], [6], [9] were content-bearing but returned only partial structure: HTML titles, schema.org metadata headers, and breadcrumb navigation. Actual page content was truncated or obscured by JavaScript frameworks, forcing the agent to rely on page titles and domain logic to infer function.
  • ›The agent discovered information primarily through prior knowledge (33%) and routing between pages (67%), not from explicit content. The site structure (topic areas like 'Bouwen, wonen en energie', 'Economie en ondernemen') was inferred from page titles, not from detailed service descriptions in the fetched HTML.
  • ›The site is moderately agent-ready for identity discovery (schema.org publisher metadata, clear titles, language variants) but poorly agent-ready for detailed service mapping: specific e-services, workflows, and digital maturity are not exposed in fetched HTML. The agent acknowledged this gap explicitly ('Limited visibility of actual service details').
  • ›Step [9] (English homepage) was cited as a source but was reached after the agent had already built its model from Dutch pages, suggesting the English version added no new discovery but confirmed the portal's multi-language support.
  • ›The agent correctly identified the task constraint: as THE official portal, there are no 'alternatives' to compare against, so the comparison frame had to shift to structural distinctiveness (life-event organization, multi-language support) rather than market competition.

See every agent that visits vlaanderen.be

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 →