What does dsebastien.net do and who is it for? Explain it back to me.
- previous resource42%
- web search25%
- prior knowledge33%
The agent successfully assembled a comprehensive explanation of dsebastien.net by combining direct site exploration with web search fallbacks. The site is moderately navigable but fragmented across subdomains; key information (pricing, product details, positioning) was scattered across multiple pages and required both direct fetches and search-assisted discovery to piece together. The agent identified that dsebastien.net is a PKM coaching and products business, correctly extracted pricing from product pages, and identified the main differentiators—though some pricing remained incomplete and the ecosystem structure could have been clearer from the homepage alone.
- ›Content-bearing steps ([1], [2], [4], [5], [9], [10], [11], [13], [15]) returned HTML rich with meta descriptions and titles that scaffolded understanding—e.g., step [4] included 'Personalized guidance that courses can't provide. €99.99/session' in the meta description, and step [13] clearly stated 'AI-native Obsidian vault' with '1,000+ users.' These fragments were machine-extractable but required assembly.
- ›The site did NOT expose a unified overview page or product catalog with all offerings and pricing in one place. The agent had to guess URLs (/services returned 404 in step [3]; /coaching worked in step [4]) and rely on prior knowledge to navigate subdomains (store.dsebastien.net, tools.dsebastien.net). Navigation from the main page did not immediately lead to products or pricing.
- ›Pricing was inconsistently published: the coaching page meta-description included €99.99/session, but the Knowledge Management for Beginners course pricing was not found in fetched pages—the agent noted 'Price not clearly stated in my research.' The Obsidian Starter Kit pricing was inferred from search results and prior knowledge rather than extracted from the product page itself.
- ›The homepage (step [1]) and About page (step [2]) did not explicitly state 'here's what we sell' or 'here's our product lineup.' The agent had to infer the business model from scattered blog posts, product pages, and community references. Steps [9] and [10] fetched a '/start' page and '/projects' page, which returned but did not appear to be primary sales or positioning channels based on the agent's trajectory.
- ›Ecosystem fragmentation was a discovery barrier: knowii.net (step [7]) returned a Cloudflare challenge (403), making it unreachable; multiple subdomains existed with unclear relationships. The agent had to rely on web search (steps [8], [12], [14], [16], [17]) to map the full picture—search results were more authoritative for linking products to pricing than the site itself.
See every agent that visits dsebastien.net
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 →