eren.ch
success
Claude Code
intent
What does eren.ch do and who is it for? Explain it back to me.
18steps
89.2sduration
$1.1209cost
173,428tokens
29 steps11 reasoning steps9 searches
home
home
/a-propos
/tarifs
home
search
/organisation
/organisation/services…
/accompagnement
search
search
search
search
search
search
search
search
/services
67%
on-site discovery
56%
reliability
44%
link following
path origin
- previous resource44%
- web search33%
- prior knowledge22%
insight
The agent successfully assembled a comprehensive understanding of EREN by combining direct website fetches with web search results, ultimately delivering a clear explanation of the organization's mission, structure, and context. However, the website itself was poorly navigable — the homepage failed to load completely, common paths returned 404s, and pricing/service details were not directly accessible, forcing the agent to rely heavily on search results and prior knowledge to answer the task.
- ›Steps [13], [14], [15] returned valid organization pages (www.eren.ch/organisation, services-cantonaux, accompagnement) but with truncated HTML content, making it unclear how much structured information was actually available on-page versus inferred from markup alone.
- ›Step [26] fetched the ecclesiastical contribution page, which was explicitly cited as a source and directly addressed the 'pricing' question — revealing that EREN operates on a tax-like contribution model rather than service fees, a fundamental distinction the agent correctly highlighted.
- ›The agent discovered navigable URLs primarily through web search (steps [11], [18], [20], [23], [24], [26]), not from the homepage itself. Direct URL guesses (steps [5], [6], [7] for /a-propos, /services, /tarifs) all failed with 404s, indicating poor information architecture or missing standard pages.
- ›The site lacks published pricing or service offerings in machine-readable form; the agent had to synthesize understanding from organizational structure pages, search engine results, external sources (Wikipedia, CEVAA, news articles), and prior knowledge to answer what they do, who it's for, and how it's priced.
- ›The French-language, church-focused content and non-commercial nature meant standard e-commerce or SaaS patterns (pricing pages, service tiers, FAQs) do not exist, making the site fundamentally agent-unfriendly for a task expecting 'how it's priced' parity with commercial alternatives.
See every agent that visits eren.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 →