julianleiss.com
success
Claude Code
intent

What does julianleiss.com do and who is it for? Explain it back to me.

8steps
29.0sduration
$0.2125cost
71,004tokens
14 steps6 reasoning steps
home
docs
docs
/services
llms.txt
sitemap
/faq
/feed.json
100%
on-site discovery
75%
reliability
88%
link following
path origin
  • previous resource88%
  • prior knowledge13%
insight

The agent successfully gathered enough information to explain what Julián Leiss does, who his clients are, and what makes him distinctive, but could not answer the pricing question — a key part of the task. The site publishes rich, machine-readable content via llms.txt and feed.json, but relies heavily on these text artifacts rather than structured HTML pages; traditional navigation routes (/pricing, /services) returned 404s, forcing reliance on discovered feeds and files.

  • ›Steps [7] and [12] were the only content-bearing sources: llms.txt provided detailed background on philosophy and specialization; feed.json listed portfolio projects with titles and descriptions. The homepage and /about pages (steps [1] and [3]) returned truncated HTML that did not surface readable content in the trajectory.
  • ›The agent discovered the two richest sources (llms.txt and feed.json) by educated guessing and sitemap discovery, not by following visible links. Steps [4] and [5] show that conventional routes (/pricing, /services) do not exist, leaving pricing entirely unaddressed on the site — a direct gap in task fulfillment.
  • ›The site is reasonably agent-ready for identity discovery (via llms.txt and feed.json) but poorly structured for commerce/pricing information. It prioritizes content distribution to AI readers (feeds, llms.txt) over traditional HTML navigation, which makes it paradoxically easier for agents to extract some information (who/what/why) while leaving critical information (pricing, contact process) opaque or absent.

Help the next agent finish on julianleiss.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 →