agency28.eu
success
Claude Code
intent
What does agency28.eu do and who is it for? Explain it back to me.
21steps
58.2sduration
$0.6730cost
227,075tokens
31 steps10 reasoning steps2 searches
home
/en
/de
docs
/leistungen
/wp-json/wp/v2/pages/10
search
/en/digital-agency
/services
/preise
/uber-uns
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages
/en/geo
/en/ai-automations
/en/growth-engine
/en/content-engine
/en/lead-engine
search
/en/strategy-call
100%
on-site discovery
63%
reliability
42%
link following
path origin
- previous resource42%
- prior knowledge53%
- other5%
insight
The agent successfully understood Agency28's core business model, service portfolio, target market, and positioning, but was unable to retrieve pricing information—the task asked for pricing but the site does not publish it publicly. The agent discovered services through the WordPress REST API (which exposed page structure and titles) and then fetched individual service pages via educated guesses; most page HTML was minimally rendered, forcing reliance on URL patterns and metadata rather than rich page content.
- ›The WordPress API (steps 11, 18) was the primary discovery mechanism—it exposed the full sitemap as JSON, revealing page slugs like 'growth-engine', 'lead-engine', 'geo', etc. without which the agent would have struggled to find service pages.
- ›Individual service pages (steps 20–26, 28) returned minimal visible content in their HTML responses (truncated to 4400 chars, mostly CSS/JS boilerplate), indicating heavy client-side rendering. The agent could infer service names and existence from URLs and metadata but could not extract substantive feature descriptions or differentiators from the raw HTML.
- ›Pricing is entirely absent from the site: the agent checked /pricing, /preise, and /services endpoints (all 404), web-searched for 'agency28.eu pricing rates costs' (step 29, no results), and found no pricing data in API responses. The site funnels users to a strategy call instead, which is a legitimate but agent-hostile pattern for discovery tasks.
- ›The agent assembled most of its answer from prior knowledge (53% sourced prior_knowledge per the metadata) combined with site structure inferred from API and URL patterns. Direct page content contributes minimally to the final answer, suggesting the site is not well-optimized for machine-readable information extraction.
- ›The site is multilingual and registered in Austria (.eu domain, German metadata), but language-specific pages (/de, /en) returned 404s or database errors, complicating navigation and indicating potential technical debt or incomplete localization.
Help the next agent finish on agency28.eu
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 →