parazettel.com
success
Claude Code
intent

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

15steps
69.7sduration
$0.8144cost
216,604tokens
18 steps3 reasoning steps4 searches
home
docs
/products
/products
docs
/shop
/courses
search
/premium
store.home
search
/articles/zettelkasten…
search
/articles
search
64%
on-site discovery
82%
reliability
27%
link following
path origin
  • previous resource27%
  • web search36%
  • prior knowledge36%
insight

The agent successfully assembled a comprehensive explanation of PARAZETTEL by combining information from the homepage, about page, premium page, store, and articles. The site was navigable but fragmented—pricing and product structure were scattered across multiple URLs (/premium, /upgrade, store.parazettel.com, /products), and the agent had to infer relationships between them. No dedicated pricing page existed, forcing the agent to piece together the offering from signup pages and the Lemon Squeezy store.

  • ›Step [1] (homepage) provided the core positioning and metadata (PARA + Zettelkasten hybrid, Obsidian-focused, created by Theo Stowell) but was light on pricing and product structure details.
  • ›Steps [9] and [11] (premium page and Lemon Squeezy store) returned signup flows and product listings but with truncated/obfuscated content; the agent had to extract pricing from page titles and metadata rather than rendered product descriptions.
  • ›Step [13] (zettelkasten-usability-alternative article) was content-bearing for differentiation but required web search discovery—not linked from the homepage or main navigation.
  • ›The site lacks a unified, machine-readable pricing/products page (/pricing returned 404; product details are split across /premium, /upgrade, /products, and an external Lemon Squeezy store), forcing the agent to rely on web search and prior knowledge (36% each) rather than on-site navigation.
  • ›Step [5] (about page) provided creator context but minimal product/pricing clarity; the agent had to use it as a reference point rather than an information source.
  • ›The agent never accessed rendered HTML content with full pricing tables, course lists, or feature comparisons—only titles, metadata, and redirects—indicating the site's product pages are either behind authentication, JavaScript-rendered, or deliberately truncated in the fetched responses.

See every agent that visits parazettel.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 →