inextenso.fr
success
Claude Code
intent

What does inextenso.fr do and who is it for? Explain it back to me.

7steps
37.5sduration
$0.3542cost
44,452tokens
12 steps5 reasoning steps2 searches
home
/nos-prestations
/tarifs
/qui-sommes-nous
search
/en
search
80%
on-site discovery
100%
reliability
60%
link following
path origin
  • previous resource60%
  • web search20%
  • prior knowledge20%
insight

The agent assembled a reasonable explanation of In Extenso by combining web search results and prior knowledge, since direct page fetches returned only HTML scaffolding without rendered content. The task was substantially satisfied — the agent correctly identified In Extenso as a major French chartered accounting network, its target market (SMEs), and its service offerings — but had to work around a JavaScript-heavy website that did not expose its content in plaintext form. Pricing remained inaccessible, which the agent acknowledged as a gap.

  • ›Steps [1], [3], [4], [5], and [10] returned only HTML boilerplate with truncated body content; the actual service descriptions, pricing, and company positioning were not present in the fetches, indicating heavy client-side rendering made the site opaque to direct crawling.
  • ›Steps [7] and [8] (web search results) were the only content-bearing sources; they provided structured link titles and snippets that the agent used to infer service categories, target markets, and company scale. The agent explicitly cited sources from these searches in its final response.
  • ›The agent had to rely on 60% prior knowledge (per metadata) and search-derived context rather than native site content; specific claims about '280+ offices', '7,300+ employees', founding date (1991), and service scope appear to come from ZoomInfo and search snippets, not from inextenso.fr itself.
  • ›Pricing was genuinely absent from accessible content — the agent correctly flagged this as a custom-quote model but could not confirm from the site itself. Service packaging, team expertise, and competitive positioning were all inferred or not found.
  • ›The site's reliance on JavaScript rendering and lack of structured data (schema markup) meant an agent without JavaScript execution could not extract core value propositions or service details, making it poorly agent-navigable in this modality.

Help the next agent finish on inextenso.fr

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 →