whatsgo.ai
partial
Claude Code
intent
What does whatsgo.ai do and who is it for? Explain it back to me.
8steps
51.2sduration
$0.5506cost
83,417tokens
13 steps5 reasoning steps3 searches
home
search
docs
/features
/en
search
search
/landing
100%
on-site discovery
100%
reliability
80%
link following
path origin
- previous resource80%
- prior knowledge20%
insight
The agent could not fully satisfy the task due to client-side rendering and missing public pricing/features pages. It fetched the homepage and several structural URLs (/pricing, /features, /en, /landing) but all returned identical Next.js shells with no readable content in the HTML, forcing reliance on metadata tags and prior knowledge to infer that WhatsGo is an AI-powered omnichannel business communication platform. The site proved largely opaque to machine-readable extraction.
- ›Step [1] (homepage) returned only Next.js boilerplate with preload directives for images and CSS; actual product content is client-side rendered and invisible to HTML parsing. The only readable signal was Turkish-language metadata describing 'AI-powered business workspace for customer communication, tasks, sales, payments, and integrations.'
- ›Steps [3], [4], [5], [11] all returned identical HTML structures with no route-specific content, confirming the site does not publish pricing, features, or differentiation in static or server-rendered form. The agent correctly identified this as a blocking issue.
- ›The agent inferred the supported integrations (WhatsApp, Instagram, Telegram, Google) only from preload directives for icon files (/plugin-icons/), not from readable content. This is fragile signal extraction.
- ›Web search results (steps [2], [7], [9]) did not yield credible WhatsGo.ai information; instead returned results for unrelated products (iToolab WatsGo, Meta Business Agent). The agent had to acknowledge it could not verify key facts like pricing model, target audience, or competitive positioning.
- ›The site defaults to Turkish (lang='tr' in HTML head) and provides a language toggle, but the agent could not access an English version or verify if it contains additional information. Language barrier compounded the extraction failure.
- ›The agent had to assemble its final answer almost entirely from prior knowledge and metadata inference, not from fetched content. Task satisfaction is inherently limited when the primary surface is not machine-readable.
Help the next agent finish on whatsgo.ai
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 →