dholic.co.jp
success
Claude Code
intent

What does dholic.co.jp do and who is it for? Explain it back to me.

18steps
98.8sduration
$0.9851cost
208,137tokens
30 steps12 reasoning steps7 searches
home
home
/guide/about
/guide
/info/shipping
/info/faq
/info/company
search
/korean-startups/newsv…
/korean-startups/newsv…
search
/dholic
search
search
search
search
/transaction/bda-advis…
search
73%
on-site discovery
55%
reliability
18%
link following
path origin
  • previous resource18%
  • web search27%
  • prior knowledge55%
insight

The agent successfully assembled a comprehensive overview of DHOLIC despite the site's own pages being largely inaccessible (returning 500 errors or JavaScript-heavy rendering). The agent relied heavily on external sources—business news articles, partner announcements, and third-party reviews—to reconstruct DHOLIC's business model, market positioning, pricing, and differentiation. The site itself was not agent-ready for discovery-evaluation tasks; the agent had to work around missing homepage content and broken information pages.

  • ›The official dholic.co.jp homepage and all attempted information pages (guide, shipping, FAQ, company) either returned 500 errors or heavily JavaScript-dependent HTML that did not render meaningful content. The agent received only HTML scaffolding, not the actual product catalog, pricing, or business information.
  • ›All substantive information in the final response came from external sources: KED Global (business journalism), BDA Partners (M&A announcement), Favorite Korean Fashion (third-party review site), and Dealroom/PitchBook (startup profiles). These were discovered via web search, not surfaced by the site itself.
  • ›The agent correctly identified what it could not find from the site (detailed shipping costs, competitor list, recent financial metrics, full product range) and disclosed these gaps transparently. This demonstrates honest handling of partial site accessibility rather than hallucination.
  • ›The site does not publish structured metadata, FAQ, about pages, or pricing information in a machine-readable or directly navigable form. Business context had to be reverse-engineered from third-party business coverage, a heavy reliance on prior knowledge and web search (55% prior knowledge, 27% web search vs. 18% from site artifacts).
  • ›DHOLIC's own multi-channel distribution (Amazon, Rakuten, Qoo10) was more discoverable than their primary domain, suggesting the site's own infrastructure may be under-indexed or poorly maintained for agent crawling.

See every agent that visits dholic.co.jp

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 →