aeolo.io
partial
Claude Code
intent

What does aeolo.io do and who is it for? Explain it back to me.

20steps
142.5sduration
$2.1236cost
263,843tokens
24 steps4 reasoning steps15 searches
home
docs
docs
search
search
search
search
search
/landing
search
search
search
search
search
search
home
search
search
search
search
80%
on-site discovery
100%
reliability
60%
link following
path origin
  • previous resource60%
  • web search20%
  • prior knowledge20%
insight

The agent gathered enough information to explain what Aeolo does, who it's for, and how it differs from alternatives, but could not locate specific pricing numbers or direct competitive comparisons because the company publishes minimal public documentation. The homepage and landing page returned valid HTML but were truncated in the fetch responses, limiting what structured content was actually readable; the agent assembled its final answer primarily from web search results and prior knowledge rather than from the site's own content.

  • ›Steps [1], [11], and [18] fetched aeolo.io's homepage/landing pages but the responses were truncated (4400+ chars removed), making it impossible to extract actual page content—the agent saw only preload tags and meta descriptions, not the body content where pricing or feature details would live.
  • ›The /pricing and /about routes (steps [2] and [3]) both returned 'Aeolo Dashboard' title tags and identical truncated responses, suggesting they are authentication-gated dashboard pages rather than public marketing pages—the site does not expose pricing or company info as public web content.
  • ›The agent relied heavily on web search (steps [5]–[22]) to infer Aeolo's positioning, with 13 searches performed but most returning either generic AEO/GEO tool comparisons or results for the competitor 'Apollo.io'—Aeolo itself appears rarely indexed in third-party comparison articles, indicating either very recent launch (2025) or limited public visibility.
  • ›The site's agent-readiness is low: no public pricing page, no blog or help docs discoverable via site: search, no structured data visible in meta tags, and key marketing pages apparently behind authentication. The agent had to construct its explanation from fragmentary search results and inferences rather than from authoritative site sources.
  • ›The agent was transparent about gaps: it flagged that exact pricing, case studies, team information, and competitive positioning details were not publicly available, correctly attributing this to the company's recent founding and limited documentation rather than claiming ignorance.

Help the next agent finish on aeolo.io

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 →