goops.eu
partial
Claude Code
intent
What does goops.eu do and who is it for? Explain it back to me.
28steps
138.3sduration
$1.6337cost
257,032tokens
35 steps7 reasoning steps15 searches
home
docs
docs
/features
search
search
search
search
search
search
sitemap
/pranis
/tomas
/security
search
search
/company/goops-technol…
search
search
search
search
docs
search
/brand
/api
search
robots.txt
search
92%
on-site discovery
100%
reliability
54%
link following
path origin
- previous resource54%
- web search8%
- prior knowledge38%
insight
The agent gathered basic product positioning from the homepage metadata tag but could not access detailed information about pricing, features, team, or competitive differentiation because the website is a client-side-rendered React app that serves only an HTML shell to fetchers. The agent pieced together a partial answer—what GoOps does and who it's for—from the meta description alone, then exhaustively searched the web and probed the site structure without recovering additional content.
- ›Step [1] and step [13] (sitemap) were the only content-bearing sources: step [1] returned the homepage with meta description 'GoOps builds AI workers for transport fleets. Pranis coaches drivers on eco-driving; Tomas answers your breakdown line 24/7.' which became the backbone of the final answer; step [13] confirmed the product names (Pranis, Tomas) and site structure.
- ›Every other fetch (steps [3], [4], [5], [15], [16], [17], [26], [27], [31], [32]) returned identical HTML—the React app shell—with no rendered content, making those pages untraversable to the agent. The site uses client-side rendering exclusively, blocking server-side information discovery.
- ›Web searches (steps [7]–[12], [18]–[24], [28], [30], [33]) yielded no relevant results; search engines found unrelated companies (Goop beauty, TomTom, FleetOps, Toma AI) and no GoOps-specific press, funding news, pricing, or team information, indicating minimal public footprint or SEO presence.
- ›The agent correctly identified gaps (pricing, features, team, comparisons) but could not fill them—the site exposes only positioning via metadata, not operational details. No contact form, demo CTA, documentation, blog, or pricing page was reachable via either direct fetch or web search.
- ›The site is technically well-built (Vercel-hosted, optimized) but agent-hostile: it publishes no static content, no API documentation, no structured data (no JSON-LD, microdata, or OpenGraph beyond the meta description), and no fallback plain-text alternative. A user would need interactive JavaScript execution to see the actual product pages.
Help the next agent finish on goops.eu
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 →