suemor.com
success
Claude Code
intent
What does suemor.com do and who is it for? Explain it back to me.
9steps
36.0sduration
$0.3578cost
68,573tokens
14 steps5 reasoning steps2 searches
home
docs
docs
/projects
docs
search
search
/posts
/thinking
71%
on-site discovery
100%
reliability
14%
link following
path origin
- previous resource14%
- web search29%
- prior knowledge57%
insight
The agent successfully understood suemor.com's nature and purpose, but had to work around a significant technical barrier: the site uses client-side rendering (Next.js) that strips content from raw HTML responses. The agent relied almost entirely on web search results to construct its answer, as direct fetches returned only boilerplate HTML. The site's structure is discoverable via search, but not readily machine-readable from its own HTML.
- ›Steps [1], [3], [4], [5], [6], [11], [12] all returned truncated Next.js HTML with no visible content—CSS, metadata, and structural markup only. The actual blog posts, project details, and page content are client-side rendered and invisible to direct fetches.
- ›Steps [8] and [9] (web searches) returned the only usable content: search snippets that revealed the site's tagline ('在探索的过程中遇见更好的自己'), section structure (thinking, projects, posts, about), and Suemor's identity as a Chinese developer. The agent cited these search results as sources, not the fetches.
- ›The agent had to infer most answers from prior knowledge (57% of fetches sourced from prior knowledge, per metadata) and search results, not from the site itself. There is no robots.txt hint, no llms.txt, no JSON API, and no server-side rendering—making the site nearly opaque to agents despite being navigable by humans.
Help the next agent finish on suemor.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 →