wdev.io
success
Claude Code
intent

What does wdev.io do and who is it for? Explain it back to me.

12steps
49.1sduration
$0.1469cost
81,852tokens
21 steps9 reasoning steps5 searches
home
home
search
docs
/contact
/services
search
search
/in/zewish
/zewish
search
search
71%
on-site discovery
86%
reliability
43%
link following
path origin
  • previous resource43%
  • web search29%
  • prior knowledge29%
insight

The agent successfully identified what wdev.io is (a personal consulting site for Iskren Slavov offering full-stack development, legacy system migration, and AI automation services) and who it serves, but encountered significant gaps in the site's content: pricing information is completely absent, contact methods are not visible, and availability status is unclear. The site is lean and relies on visitors discovering the person behind it via external profiles rather than publishing structured, machine-readable information about services, rates, or differentiation.

  • ›Steps [1] and [3] (repeated fetches of wdev.io/) returned the same homepage HTML with only meta description visible in the truncated response; the agent did not show access to full rendered page content that might have contained service details, rates, or contact forms.
  • ›The agent attempted discovery paths (/pricing, /contact, /services at steps [7], [8], [9]) that all returned 200 status but the same generic homepage HTML—indicating either no routing for these paths or a single-page app that doesn't expose subpage content via raw HTML.
  • ›Pricing information is genuinely absent from the site: the agent explicitly called this out as 'a major gap' with no hourly rates, project fees, retainer models, or even a way to request a quote visible on any accessible page.
  • ›The agent assembled most of its answer from the meta description tag ('I help businesses save money and work smarter through technology solutions...') visible in step [1], not from richer page content—suggesting the homepage content itself is either not machine-readable or heavily client-side rendered.
  • ›The agent relied on external sources (LinkedIn, GitHub, web search results) to provide context and detail, since the website itself offers minimal structured information beyond positioning.
  • ›The site does not surface pricing, contact, availability, team size, or competitive differentiation—key discovery-layer information—requiring a visitor to initiate outreach through external channels.

Help the next agent finish on wdev.io

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 →