What does capgemini.com do and who is it for? Explain it back to me.
- previous resource50%
- web search25%
- prior knowledge25%
The agent assembled a comprehensive explanation of Capgemini by combining minimal direct site content with heavy reliance on web search and prior knowledge. The website itself provided only fragments (a /services page and a /what-we-do page that returned mostly boilerplate HTML), forcing the agent to bridge gaps using search results about competitors, target markets, and company partnerships. The site was poorly navigable for this task—pricing was completely absent, service descriptions were vague, and the agent had to guess URLs like /about and eventually rely on search to find /us-en/about-us/who-we-are/what-we-do.
- ›Step [6] (the /what-we-do page from search) and steps [5], [8]–[11] (all web searches) were the true sources of the answer. The site's own pages returned HTML stubs with minimal readable content; the agent extracted most meaningful information from external sources (competitor comparisons, analyst reports, third-party reviews).
- ›The site surfaced no direct pricing information, no explicit target customer segments, and no clear ROI metrics—all of which the user asked for. The agent filled these gaps by inferring from search results and prior knowledge, not by finding them on capgemini.com.
- ›Site navigation was brittle: /about returned 404; /services existed but returned minimal structured content; the agent had to search to discover the correct URL structure (/us-en/about-us/who-we-are/what-we-do). Steps [1]–[3] failed or were nearly empty, but steps [5]–[11] (search-sourced) and the agent's external knowledge compensated.
Help the next agent finish on capgemini.com
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 →