frankenergie.nl
success
Claude Code
intent

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

16steps
81.6sduration
$1.3147cost
164,522tokens
20 steps4 reasoning steps10 searches
home
/nl/over-frankenergie
/nl/tarieven
/nl/hoe-het-werkt
search
search
/dynamische-energie/aa…
/energieleverancier/fr…
search
search
search
search
search
search
search
search
67%
on-site discovery
50%
reliability
17%
link following
path origin
  • previous resource17%
  • web search33%
  • prior knowledge50%
insight

The agent successfully assembled a comprehensive profile of Frank Energie by working around an inaccessible primary website (Next.js SPA that returned 404s on direct navigation) and instead piecing together information from third-party review and comparison sites, web search results, and cached news articles. The site itself was not machine-readable; the agent had to rely on external sources (energievergelijk.nl, salderingswijzer.nl, search snippets) to answer what Frank Energie does, who it's for, how it's priced, and how it differs from competitors.

  • ›Step [9] (jeroen.nl third-party review) and step [10] (energievergelijk.nl comparison tool) were the only content-bearing fetches; both were external aggregators, not Frank Energie's own site. They contained pricing details (€4.99/month fee, €0.0175/kWh markup), service positioning, and award recognitions.
  • ›Step [15] search result (salderingswijzer.nl) was cited as the primary source for exact 2026 pricing (€0.0175/kWh + €4.99/mnd) — this structured pricing data was available only on third-party tariff comparison sites, not on frankenergie.nl itself.
  • ›Frank Energie's homepage (step [1]) and all attempted direct navigation URLs (steps [3], [4], [5]) failed to render usable content; the site is a client-side React app with no server-side HTML. The agent never successfully fetched a readable page from the primary domain.
  • ›The agent relied heavily on web search (7 searches across steps [7]–[18]) to discover third-party sources and news articles. Search snippets themselves (not full fetches) often contained the summary information needed.
  • ›Information about smart charging, solar integration, battery compatibility, and competitive differentiation came from news articles and case studies (Enode partnership, Reversed Digital case, LinedIn) found via search, not from the company's website.
  • ›The site publishes news/award articles on frankenergie.nl/nl/nieuws/ (referenced in search results but not fetched) but these URLs were not directly navigable during the run. The agent reconstructed this information from search results pointing to those URLs.

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