i22.de
success
Claude Code
intent

What does i22.de do and who is it for? Explain it back to me.

21steps
102.1sduration
$1.9251cost
286,660tokens
23 steps2 reasoning steps14 searches
home
search
/company/i22-digitalag…
/en
search
/agency/i22-digitalage…
search
/organization/i22
search
/leistungen
search
search
search
/ueber-uns
search
search
search
search
search
search
search
29%
on-site discovery
57%
reliability
14%
link following
path origin
  • previous resource14%
  • web search71%
  • prior knowledge14%
insight

The agent successfully assembled a comprehensive overview of i22.de by combining direct site fetches (homepage, services, about pages) with web search context, producing a coherent account of what the company does, who it serves, and how it differs. However, the site itself was only partially navigable—the agent retrieved raw HTML from a Next.js-rendered site but could not parse detailed content from those pages, forcing it to rely heavily (71%) on web search results and prior knowledge to fill in the gaps. Pricing information remained unavailable despite explicit search attempts.

  • ›Step [1] (homepage) and steps [11], [17] (services/about pages) returned raw Next.js HTML that was truncated and non-readable—the agent could not extract structured content from the site's own pages, suggesting heavy reliance on client-side rendering that breaks machine parsing.
  • ›The agent successfully inferred i22's core positioning ('operating' digital solutions, not just building them) and service portfolio from search results and LinkedIn, but these were NOT clearly stated on the site itself—they were reconstructed from external sources like Clutch article and LeadIQ summary.
  • ›Pricing was explicitly searched for (steps [6], [18]) but no public pricing page or model exists on the site; the agent had to tell the user 'requires direct contact,' acknowledging a real gap rather than fabricating.
  • ›The site's language is German-only (no /en path), and the agent discovered this via a 404 attempt (step [4])—the site does not provide language negotiation or multilingual content, limiting discovery for non-German-speaking evaluators.
  • ›Four of the five explicitly cited sources in the final response are NOT the site itself (LinkedIn, LeadIQ, Clutch, Glassdoor, OMT), indicating the site's own content was insufficient; only 2 of 7 citations point to i22.de pages, and those are architecture/structure-only (no semantic content was extracted from them).

Help the next agent finish on i22.de

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 →