iieu.ch
success
Claude Code
intent

What does iieu.ch do and who is it for? Explain it back to me.

17steps
55.3sduration
$0.8009cost
185,908tokens
25 steps8 reasoning steps5 searches
home
/preise
/uber-uns
/leistungen
/leistungen/bekleidung
/factory
/kontakt
search
/leistungen/merchandis…
/leistungen/corporate-…
/referenzen
search
search
/impressum
search
search
home
67%
on-site discovery
83%
reliability
50%
link following
path origin
  • previous resource50%
  • web search33%
  • prior knowledge17%
insight

The agent assembled a comprehensive overview of iieu.ch by combining HTML fetches of service pages with web search results, successfully identifying what the company does, who it serves, and key differentiators. However, the site does not publish pricing, minimum order quantities (except sneakers), or turnaround times, forcing the agent to flag these as gaps and note that the site is designed to route inquiries to sales rather than enable self-service discovery. The Webflow-based site proved partially navigable—service pages existed and were reachable, but HTML responses were truncated, limiting direct content extraction.

  • ›Steps [1], [2], [8], [15], [16], [17], [22] successfully fetched service pages (/leistungen/bekleidung, /leistungen/merchandising, /leistungen/corporate-fashion, /factory, /impressum) that confirmed iieu's service categories and located them in Rubigen, Switzerland; HTML was truncated but titles and metadata were parseable.
  • ›Steps [12], [19], [20] (web searches) did not return external review sites or competitor comparisons—they returned iieu's own pages, indicating the agent had to infer differentiation from what iieu publishes rather than from third-party comparison.
  • ›The site does not publish pricing, most minimum order quantities, or turnaround times on any accessible page; the agent correctly identified this as a critical gap and noted the site is designed to collect leads rather than enable self-service evaluation.
  • ›The agent had to use prior knowledge (17% of fetches) to infer business model and structure; web search (33%) returned only iieu's own pages; and previous artifact context (50%) likely provided the framework for assembling service categories—suggesting the site's information architecture does not enable bottom-up discovery without external context.
  • ›No structured data (JSON-LD, microdata) or machine-readable product catalog was retrievable; the site's Webflow implementation and truncated HTML responses meant the agent could only extract service names and category labels, not detailed specifications, pricing tiers, or policy details.

Help the next agent finish on iieu.ch

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 →