alkago.com
partial
Claude Code
intent

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

6steps
29.2sduration
$0.2556cost
36,652tokens
10 steps4 reasoning steps1 search
home
/en
docs
docs
search
/en/transfers/cancun-a…
80%
on-site discovery
100%
reliability
60%
link following
path origin
  • previous resource60%
  • web search20%
  • prior knowledge20%
insight

The agent gathered a partial understanding of Alka-go by combining metadata from the homepage, search results identifying competitors, and a specific transfers page URL. The site's React-only architecture blocked direct extraction of pricing, terms, company information, and service details, forcing the agent to rely on search engine results and prior knowledge to fill critical gaps. While the agent correctly identified what Alka-go does (private airport transfers in Cancun/Riviera Maya) and who it serves, it explicitly could not retrieve transparent pricing or detailed differentiation claims from the website itself.

  • ›Step [1] (homepage) returned only HTML metadata: a Spanish description mentioning 'traslados privados en Cancun y Riviera Maya con cotizacion en linea, confirmacion digital y soporte por WhatsApp.' This was the only direct content-bearing fetch from the site itself; all subsequent site fetches ([3], [4], [5], [8]) returned identical or near-identical React shells without rendered content.
  • ›Step [7] (web search) was the primary source for competitive positioning and pricing reference points ($34 range from eTransfers), since Alka-go's own site did not surface pricing. The agent had to leave the domain to answer a core task question.
  • ›Step [8] (specific transfers page) was cited as a source but returned the same React shell as earlier fetches, providing no additional rendered content. The URL itself became the evidence of service availability rather than its response body.
  • ›The site's React-only rendering meant the agent could not access pricing pages, About sections, or terms—they all returned identical boilerplate HTML skeletons. The agent explicitly stated it 'couldn't find specific pricing information on their website directly' and that 'the site requires you to enter your trip details to get a quote.'
  • ›The agent populated ~60% of its answer from prior knowledge (competitor research, general market knowledge of transfer services) and web search (~20%), with only ~20% from direct site content—showing the site was not agent-readable for the stated task.

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