onglobal.io
success
Claude Code
intent
What does onglobal.io do and who is it for? Explain it back to me.
9steps
58.6sduration
$0.0974cost
111,830tokens
16 steps7 reasoning steps2 searches
home
docs
docs
/features
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages/40
search
search
/b2b-ecommerce
86%
on-site discovery
57%
reliability
71%
link following
path origin
- previous resource71%
- web search14%
- prior knowledge14%
insight
The agent assembled a workable explanation of onGlobal's B2B ecommerce services by combining the homepage, WordPress API page data, and a dedicated B2B product page, but had to work around significant gaps: no pricing was published on the site, no case studies or client examples were visible, and the service model (custom implementation vs. SaaS vs. pure partnership) remained ambiguous. The site's navigation structure was minimal, forcing the agent to guess URLs and fall back on WordPress API introspection and prior knowledge.
- ›Step [1] (homepage) and Step [14] (/b2b-ecommerce page) provided the core positioning and feature set—PrestaShop Expert Partner status, B2B focus, ERP integration, multi-language support, customer-specific pricing—but neither page contained pricing, service model clarity, or case studies.
- ›Step [8] (WordPress API page ID 40) yielded the main landing page content in structured format after steps [3–5] (explicit /pricing, /about, /features URLs) all returned 404s, revealing that the site has a flat structure with no traditional navigation hierarchy and no published pricing tier pages.
- ›The agent successfully discovered onGlobal's core business—B2B ecommerce implementation for distributors using open-source platforms (PrestaShop, WooCommerce, Shopify)—but had to explicitly acknowledge that pricing, implementation timeline, process, competitive positioning, and supported ERP systems were either vague or absent from the site; this required the agent to flag these as 'confusing or missing' rather than assert confident answers.
- ›The site did not surface alternative navigation methods (no sitemap, no clear internal link structure in the homepage HTML), forcing the agent to probe the WordPress REST API and guess standard URL paths; 71% of the fetches came from prior artifacts (likely cached or scaffolded page lists), indicating the agent relied on non-site-surfaced knowledge to navigate.
- ›Web search steps [10] and [12] returned generic B2B ecommerce comparison articles, not onGlobal-specific results, confirming the site has limited SEO visibility and onGlobal does not appear in major third-party comparisons—limiting discoverability.
Help the next agent finish on onglobal.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 →