What does platane.io do and who is it for? Explain it back to me.
- previous resource20%
- web search50%
- prior knowledge30%
The agent successfully synthesized an explanation of Platane's business model, target audience, and positioning, but had to assemble this largely from web search results and prior knowledge rather than from directly navigable site content. The website itself returned only HTML skeletons in fetches [1, 3, 11, 25] without readable text; the agent relied on search engine snippets, the France Num government registry [28], and blog article URLs discovered via site-scoped searches to construct its answer. The site is poorly agent-readable—it uses client-side rendering that doesn't expose content in static HTML, has no structured data markup, no published pricing page, and no explicit competitive positioning, forcing the agent to infer and piece together information rather than retrieve it directly.
- ›All meaningful content came from web search snippets and the France Num profile [28], not from direct site fetches. Steps [1, 3, 11, 25] returned only HTML boilerplate with no extractable text, indicating the site is a Next.js SPA that requires JavaScript rendering.
- ›The agent discovered services, RGAA focus, and accessibility positioning via blog article URLs from site-scoped searches [22, 36, 37] and the France Num page [28], not from a discoverable services or about page. Custom pricing was inferred by absence—no pricing URL returned 404 [6], and no pricing information appeared in any search result.
- ›Competitor differentiation (sovereignty, dual French datacenters, RGAA certification, source code ownership) was extracted from France Num's description and blog content [28, 37], not from Platane's own website. The core positioning is implicit in the agency's registration with a French government digital transformation initiative, not explicitly articulated on their site.
- ›The site structure appears intentionally minimal—direct guesses for /pricing, /services yielded 404s [6, 10]; the site uses a blog-heavy information architecture rather than traditional service pages. This forces discovery through search rather than navigation.
- ›The agent successfully fulfilled the open-ended evaluation task by triangulating from multiple sources, but Platane's website itself contributed minimal structured, machine-readable content to the answer.
See every agent that visits platane.io
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 →