esadex.com
partial
Claude Code
intent

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

28steps
107.5sduration
$1.8168cost
250,647tokens
30 steps2 reasoning steps17 searches
home
docs
docs
/features
search
sitemap
/privacy
/terms
search
search
search
search
search
search
search
search
docs
/dashboard
/login
robots.txt
search
search
search
search
search
search
search
search
100%
on-site discovery
45%
reliability
36%
link following
path origin
  • previous resource36%
  • prior knowledge64%
insight

The agent was unable to answer the core task: it could not determine what esadex.com does, who it's for, how it's priced, or how it differs from alternatives. The site is live and properly structured with sitemap and privacy/terms pages, but it exposes almost no meaningful content. The agent retrieved the homepage (which contained only boilerplate Nuxt framework HTML), discovered the sitemap and robots.txt, and confirmed the existence of privacy and terms pages—but none of these yielded business-facing information. The site is essentially a black box from an agent discovery perspective.

  • ›Step [1] returned the homepage as a Nuxt-rendered application with no visible text content in the HTML response—only CSS variable stubs and framework boilerplate. The actual service description, if it exists, is client-side rendered and inaccessible to static fetching.
  • ›Step [9] revealed the sitemap structure (home, privacy, terms, plus Spanish/Ukrainian/Russian language variants), proving the site is SEO-aware but not content-rich. Only five pages exist in the index.
  • ›Steps [10] and [11] confirmed that privacy and terms pages exist and are fetchable (200 status), but both returned identical Nuxt framework HTML with no visible legal text—content is likely also client-side rendered.
  • ›The site does not publish any discoverable business information: no About page, no Pricing page, no Features section, no Docs, no Login flow, no blog, no public API documentation, and no embedded structured data (Schema.org markup was not extracted or cited).
  • ›The agent relied entirely on prior knowledge guesses (64% of fetch sources) for URLs like /pricing, /about, /features, /docs, /dashboard, /login—all returned 404. Web search (0% of fetch sources in successful steps) yielded no external references to esadex.com or its purpose, only unrelated similarly-named services (Esendex, Exadex, EADX Exchange, etc.).
  • ›The site's agent-readiness is very poor: it is a client-side SPA with no server-side rendered content, no public documentation, no structured metadata, no external press or social presence, and no indexable business description. An agent cannot self-serve an explanation of the product.

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