kevin.riou.pro
partial
Claude Code
intent

What does kevin.riou.pro do and who is it for? Explain it back to me.

18steps
68.7sduration
$0.9959cost
244,539tokens
29 steps11 reasoning steps7 searches
home
/en
docs
/services
docs
/projects
/contact
search
search
/profile/kevinriou1
search
search
/sites/riou-kevin-web-…
/u/kevinriou
/rioukkevin
search
search
search
64%
on-site discovery
36%
reliability
27%
link following
path origin
  • previous resource27%
  • web search36%
  • prior knowledge36%
insight

The agent could not access the site's actual content due to its JavaScript-heavy SPA architecture, forcing it to rely heavily on web search results and GitHub to piece together an answer about Kevin Riou's portfolio. The agent determined kevin.riou.pro is a freelance fullstack developer's portfolio, but could not retrieve pricing, detailed service offerings, or specific project information directly from the site—instead assembling its answer from search snippets, prior knowledge of typical freelancer business models, and external profiles (Malt, GitHub), making the site largely opaque to machine-readable scraping.

  • ›The homepage fetch [1] and [3] returned only raw Next.js hydration markup with no readable text content; the site requires client-side JavaScript execution to render any information about Kevin, his services, or projects.
  • ›Attempts to find dedicated pages (/pricing, /services, /about, /projects, /contact) all returned 404s [4–9], indicating the site is purely single-page and content is embedded in the homepage via JavaScript—not discoverable through standard URL routing.
  • ›Web search results [11, 12, 17] provided the most actionable intelligence: search snippets confirmed he is a freelance fullstack developer; searches surfaced external profiles (Malt, LinkedIn, GitHub) where clients would need to look for actual pricing and detailed offerings.
  • ›The agent's final answer relied on prior knowledge of freelancer business models (per-project pricing, use of platforms like Malt) and inference from the portfolio being featured on CSS Design Awards [17]—not on content fetched from kevin.riou.pro itself.
  • ›GitHub profile fetch [22] was attempted but did not yield substantive information about services or pricing; external platforms were either Cloudflare-protected or blocked (Malt [14], The Rookies [20]).
  • ›The site is not agent-ready: no semantic HTML, no structured data (JSON-LD, schema.org), no llms.txt, and no server-side rendering of key identity/positioning information—everything deferred to client-side JavaScript.

Help the next agent finish on kevin.riou.pro

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 →