What does admin.ch do and who is it for? Explain it back to me.
- previous resource33%
- web search50%
- prior knowledge17%
The agent assembled a comprehensive explanation of admin.ch by combining web search results with fetches of the actual site, but had to rely heavily on prior knowledge and search context because the site itself is JavaScript-rendered and does not expose meaningful content in HTML. The agent successfully positioned admin.ch as Switzerland's Federal Council announcement portal, differentiated it from ch.ch, and identified key limitations (limited English content, vague services, unclear domain relationships). The site's client-side rendering made direct content extraction difficult, forcing the agent to infer structure and purpose from URL patterns and search snippets rather than clear semantic markup.
- ›All HTML responses ([1], [4], [7], [8], [10]) returned Nuxt/Vue.js boilerplate with no visible content — the agent explicitly noted this: 'JavaScript-heavy site' and 'actual content isn't visible in the HTML itself'. The agent could not extract answers directly from the site's own markup.
- ›Web search results ([6], [9], [11], [12]) provided the actual answer material: search snippets and URL patterns revealed that admin.ch hosts Federal Council press releases, decisions, and departmental information. Step [6] established admin.ch as 'the official website of the Swiss government' and returned a link to the press releases page. Step [9] introduced the ch.ch comparison, which became central to the agent's differentiation analysis.
- ›The agent never successfully rendered or parsed the live site's visible content; instead it bootstrapped understanding from (a) prior knowledge of Swiss government structure (17% of fetches), (b) search engine abstracts and titles (50% of fetches), and (c) URL structure inferred from search results (33% of fetches). The site itself did not self-describe its purpose or structure in an agent-readable format.
- ›The agent's final answer about what admin.ch does, who it serves, and how it differs from alternatives came almost entirely from search results and educated inference, not from parsing the destination site. No pricing model or subscription details were discoverable because admin.ch publishes none — the agent correctly inferred it was free based on it being a government portal.
- ›The agent explicitly flagged friction points: 'Limited English content', 'JavaScript-heavy site', 'No clear service offering page', and 'Unclear relation between domains'. These are all symptoms of poor machine-readability. The site required a human visitor to click through and understand context; the agent had to use web search as a proxy for human navigation.
See every agent that visits admin.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 →